1 | English French Notes Complete/Exclude
|
---|
2 | code sheet deletion has begun for station
|
---|
3 | I am deleting all
|
---|
4 | code sheets created or transmitted on or before
|
---|
5 | Done - deleted
|
---|
6 | code sheets.
|
---|
7 | code sheets remaining.
|
---|
8 | I will now begin cleaning up the Log Transmission Record file.
|
---|
9 | I will delete all
|
---|
10 | batches and transmission records created on or before
|
---|
11 | Done - Deleted
|
---|
12 | Batch and Transmission records.
|
---|
13 | transmission/batch records remaining.
|
---|
14 | This option will release code sheets to the VADATS system for transmission
|
---|
15 | to the Austin DPC. You will have the option of releasing individual batches
|
---|
16 | or all batches within a certain Transmission Number.
|
---|
17 | Do you wish to release by Batch or Transmission number? (B/T) T//
|
---|
18 | of each Batch that you wish to release to Austin. A 'T', will cause
|
---|
19 | ALL batches within the Transmission to be released automatically.
|
---|
20 | TRANSMIT
|
---|
21 | Batch
|
---|
22 | has already been released/scheduled for release. No action has been taken on this batch.*
|
---|
23 | TOM9.5
|
---|
24 | TOM NEEL TESTING - DVA
|
---|
25 | YOU HIT ES1^PRCFACR AND DID ESIG^PRCUESIG
|
---|
26 | MESSAGE =
|
---|
27 | LOG
|
---|
28 | ISM
|
---|
29 | CODE SHEETS
|
---|
30 | FEE/FEN/LOG/ISM/EDI BATCH
|
---|
31 | Do you wish to add another code sheet to a batch
|
---|
32 | There is an error in this code sheet, please edit it to insure it is correct!
|
---|
33 | This Code sheet has not been assigned to a batch, no action is necessary.
|
---|
34 | I will now remove this code sheet from batch
|
---|
35 | <Removal Completed>*
|
---|
36 | I was unable to correct the Batch Header in batch
|
---|
37 | . Please use
|
---|
38 | the 'Edit Keypunched Code Sheet' option to correct prior to transmission.
|
---|
39 | Do you wish to add this code sheet to another batch
|
---|
40 | Will this Code Sheet be transmitted at a later date
|
---|
41 | A 'YES' will queue the code sheet for retransmission.
|
---|
42 | Code Sheet has been retained in File, but will not be transmitted.
|
---|
43 | has already been released to Austin.
|
---|
44 | If you will not be retransmitting the batch, you are not permitted to
|
---|
45 | remove a code sheet from that batch.
|
---|
46 | This code sheet has already been assigned to Batch
|
---|
47 | You must remove the code sheet from the batch before assigning it to another.
|
---|
48 | This option will allow you to keypunch a
|
---|
49 | Code Sheet when there
|
---|
50 | is no other way to get it into the system.
|
---|
51 | Transaction Type.Status Code
|
---|
52 | LOG Transaction Type
|
---|
53 | Transaction Type
|
---|
54 | not found in file.
|
---|
55 | Is it OK if I use
|
---|
56 | If you answer 'YES', I will use
|
---|
57 | as the Transaction Type for this code sheet.
|
---|
58 | No new code sheet created - Files inaccessible at this time.*
|
---|
59 | Do you wish to enter another code sheet
|
---|
60 | Answer YES if you wish to enter an additional code sheet
|
---|
61 | <CODE SHEET DELETED>
|
---|
62 | This code sheet may not be edited until it has been released for transmission.
|
---|
63 | This Code Sheet will no longer be editable using the standard option.
|
---|
64 | ID has been changed to
|
---|
65 | Answering 'YES' to this option will cause the Code Sheet ID to be changed.
|
---|
66 | This change will cause the Code Sheet to be uneditable using standard edit
|
---|
67 | This option is designed to RERELEASE a batch. You may not do original releases
|
---|
68 | using this option.
|
---|
69 | <Option Aborted>
|
---|
70 | <No Action Taken>*
|
---|
71 | I will now RERELEASE batch
|
---|
72 | to Austin.
|
---|
73 | <Batch has been Rereleased to Austin>*
|
---|
74 | There appears to be Code Sheets transmitting at this time. Please try
|
---|
75 | again in 30 minutes.
|
---|
76 | Try later
|
---|
77 | Do you want to overide transmission at this time
|
---|
78 | The following purchase order was not obligated
|
---|
79 | and has been 'RETURNED' by Fiscal Service !!
|
---|
80 | Purchase Order information is as follows:
|
---|
81 | Purchase Order Number:
|
---|
82 | RETURNED PURCHASE ORDER NOTIFICATION
|
---|
83 | ...Purchase Order returned, bulletin transmitted...*
|
---|
84 | Requisition #
|
---|
85 | The delivery date for
|
---|
86 | has been changed from
|
---|
87 | by the above Purchasing Agent for control point
|
---|
88 | Please note this change.
|
---|
89 | Notification for delivery date change on a P.O.
|
---|
90 | Delivery date changed ! Bulletin transmitted.*
|
---|
91 | FISCAL NOTIFICATION
|
---|
92 | The following Purchase Order Amendment was not obligated
|
---|
93 | and has been 'RETURNED' by Fiscal Service !!
|
---|
94 | Amendment Number:
|
---|
95 | Automatic Deletion Date:
|
---|
96 | RETURNED PURCHASE ORDER AMENDMENT NOTIFICATION
|
---|
97 | ...Purchase Order Amendment was returned, bulletin has been transmitted...
|
---|
98 | Do you wish to post this information to the Fiscal Status of Funds Tracker
|
---|
99 | If you answer 'YES', you will be asked the information necessary to post
|
---|
100 | the code sheet to the Fiscal Status of Funds. A 'NO' or an '^' will
|
---|
101 | skip the bypass the posting.
|
---|
102 | SIGNATURE CODE FAILURE
|
---|
103 | LOG\IRS
|
---|
104 | IRS\ISM
|
---|
105 | Code Sheet file not available - File lock timeout.*
|
---|
106 | PRCF(
|
---|
107 | CODE SHEET DELETED
|
---|
108 | PRCFA TT
|
---|
109 | This program deletes all template maps and recreates them from the
|
---|
110 | input templates found in file 420.4. OK to continue
|
---|
111 | Unable to locate template in file .402, no action taken.*
|
---|
112 | THIS CODE SHEET HAS ALREADY BEEN PRINTED.
|
---|
113 | DO YOU WISH TO RETRANSMIT IT
|
---|
114 | 'YES' to mark for retransmission.
|
---|
115 | 'NO' or '^' to hold in file.
|
---|
116 | NO ACTION TAKEN
|
---|
117 | TRANSMITTED CODE SHEET WILL BE AS FOLLOWS:
|
---|
118 | Code sheet does not equal
|
---|
119 | Do you wish to TRANSMIT this Code Sheet to
|
---|
120 | 'YES' will mark the code sheet for transmission.
|
---|
121 | 'NO' will give you a chance to edit the code sheet.
|
---|
122 | '^' will delete the code sheet.
|
---|
123 | Do you want to edit this Code Sheet
|
---|
124 | 'YES' to edit, 'NO' or '^' for chance to delete code sheet.
|
---|
125 | Error in editing this code sheet. Please re-enter.
|
---|
126 | Are you sure you want to delete this Code Sheet
|
---|
127 | 'YES' to delete, 'NO' or '^' to retain, but not transmit.
|
---|
128 | <Code Sheet Retained in File>*
|
---|
129 | CODE SHEET DELETED*
|
---|
130 | NAMES(
|
---|
131 | an unknown person
|
---|
132 | lock was set by
|
---|
133 | No further action taken. Contact your supervisor to clear the lock.
|
---|
134 | Corruption exists in the FISCAL LOCK file.
|
---|
135 | PLEASE CONTACT YOUR SITE MANAGER.
|
---|
136 | Lock is not in use. No action taken.
|
---|
137 | It looks like the lock was set by
|
---|
138 | Have you checked with all your users to be sure that
|
---|
139 | is not in progress on the system
|
---|
140 | Are you sure that you want to clear this lock
|
---|
141 | OK, I will now clear the
|
---|
142 | No action taken
|
---|
143 | ALD Code missing from Control Point File
|
---|
144 | PLEASE NOTIFY YOU COORDINATOR
|
---|
145 | Invalid ALD Code
|
---|
146 | in Control Point
|
---|
147 | PLEASE NOTIFY YOUR COORDINATOR
|
---|
148 | The first position indicates contract length and the second indicates
|
---|
149 | contract beginning month. Each position should be coded with an alpha
|
---|
150 | The values will be as follows:
|
---|
151 | [Example: CA = 3 month contract beginning in October.]
|
---|
152 | Receiving Report is incomplete. Cannot transmit!
|
---|
153 | Record in use please try later.
|
---|
154 | Error: Receiving Report NOT queued,
|
---|
155 | unable to obtain the batch transaction
|
---|
156 | number. Please try again.
|
---|
157 | RECEIVING REPORT
|
---|
158 | STK#:
|
---|
159 | NSN:
|
---|
160 | Items per
|
---|
161 | GSA/DLA# :
|
---|
162 | QUANTITY DISCOUNT
|
---|
163 | ITEMS:
|
---|
164 | ESTIMATED SHIPPING &/OR HANDLING
|
---|
165 | Are you ready to send the receiving reports to Austin
|
---|
166 | A 'YES' will start the transmission process, a 'NO' or an '^'
|
---|
167 | will exit this option.
|
---|
168 | Have you printed and reviewed the list of Receiving Reports
|
---|
169 | to be released
|
---|
170 | Please review the list for accuracy before continuing.
|
---|
171 | Are you ready to continue
|
---|
172 | RELEASE RECEIVING REPORTS TO AUSTIN
|
---|
173 | Select Receiving Report to be deleted:
|
---|
174 | OK to delete
|
---|
175 | <Deleted from list>*
|
---|
176 | Select Next Receiving Report:
|
---|
177 | Inadequate information to continue.*
|
---|
178 | Select Receiving Report.Partial Number:
|
---|
179 | Select Next Receiving Report.Partial Number:
|
---|
180 | TOTAL AMOUNT OF RECEIVING REPORT:
|
---|
181 | ** More ** Hit <Return> to Continue, Enter '^' to Exit
|
---|
182 | FMS Line #:
|
---|
183 | FMS Amount:
|
---|
184 | PRCFA TRANSMIT
|
---|
185 | Are you sure you wish to send this Receiving Report to Austin
|
---|
186 | A 'NO' or an '^' will prevent release to Austin.
|
---|
187 | Receiving Report has NOT been released to Austin.*
|
---|
188 | TRANSMIT RR
|
---|
189 | TO AUSTIN
|
---|
190 | Receiving Report Queued for Immediate Transmission*
|
---|
191 | This receiving report has already been transmitted to Austin.
|
---|
192 | It may NOT be rereleased using this option.
|
---|
193 | RECEIVING REPORT HAS NOT BEEN RELEASED.
|
---|
194 | Unable to Queue at this time, Please use option to queue manually.
|
---|
195 | Receiving report placed on transmission list.*
|
---|
196 | Don't forget to mail this Receiving Report to Austin.*
|
---|
197 | Select PURCHASE ORDER NUMBER:
|
---|
198 | Select Partial Number:
|
---|
199 | This partial has already been transmitted to Austin. <No Action Taken>
|
---|
200 | Select Next PURCHASE ORDER NUMBER:
|
---|
201 | This partial has not yet been transmitted to Austin. <No Action Taken>
|
---|
202 | Do you want this transmitted immediately
|
---|
203 | A 'YES' will cause the receiving report to go to Austin immediately.
|
---|
204 | A 'NO' will queue it for release using the 'Transmit Receiving Reports'
|
---|
205 | Option. An '^' will terminate this option.
|
---|
206 | Unable to QUEUE at this time
|
---|
207 | Not Queued>*
|
---|
208 | Receiving report has been put on transmission list.*
|
---|
209 | This Receiving Report is ALREADY Queued for Transmission.
|
---|
210 | XXX@Q-CRD.VA.GOV
|
---|
211 | There are no PURCHASE ORDERS ready for processing at this time.
|
---|
212 | Purchase Order Amendment
|
---|
213 | There are no PURCHASE ORDER AMENDMENTS ready for processing at this time.
|
---|
214 | Receiving Report
|
---|
215 | There are no RECEIVING REPORTS ready for processing at this time.
|
---|
216 | The following documents are ready for processing:
|
---|
217 | Do you want to run the report at this time
|
---|
218 | The system can now generate a report that will list the type and number
|
---|
219 | of each document that is ready for processing at this time.
|
---|
220 | But, it may take a while to complete.
|
---|
221 | Enter 'NO' or 'N' or 'RETURN' if the report should not be run at this time.
|
---|
222 | Enter 'YES' or 'Y' to run the report
|
---|
223 | YES// ^NO// ^(YES/NO)
|
---|
224 | ANSWER 'YES' OR 'NO' ('^' TO QUIT):
|
---|
225 | You may enter a 'Yes', or a 'No', or you may enter an '^' to Quit.
|
---|
226 | Select ADJUSTMENT VOUCHER
|
---|
227 | This Adjustment Voucher has already been processed by Fiscal,
|
---|
228 | Do you need to process a code sheet for this Adjustment Voucher
|
---|
229 | Do you need to enter an additional code sheet
|
---|
230 | No Adjustment Vouchers are entered for this order, please check with Supply.
|
---|
231 | Option is being aborted.
|
---|
232 | Select PURCHASE ORDER:
|
---|
233 | Current Status is undefined
|
---|
234 | Current status is:
|
---|
235 | Select NEW STATUS:
|
---|
236 | Are you sure you want to change the status
|
---|
237 | ---- STATUS NOT CHANGED ----
|
---|
238 | I will now convert your IFCAP site parameter file to support the new data structure.
|
---|
239 | Enter the date on which FMS will accrue their prior year documents.
|
---|
240 | The MM/DD/YY is provided by Central Office/FMS, normally via MailMan
|
---|
241 | Is this correct?
|
---|
242 | IFCAP will allow 'SO's to be sent to Austin as 'AR's starting on
|
---|
243 | Enter 'Y' to accept your entry, 'N' to change it
|
---|
244 | ERROR PROCESSING
|
---|
245 | This invoice is being edited by someone else, please try later!
|
---|
246 | Do you wish to continue processing this invoice now
|
---|
247 | Do you wish to view current information for this invoice?
|
---|
248 | Is this the correct invoice?
|
---|
249 | This invoice is flagged as MONEY MANAGEMENT EXEMPT. Return to Voucher Audit for review/correction
|
---|
250 | There are no BOCs on this obligation, processing terminated.
|
---|
251 | Exiting.
|
---|
252 | FMS Line #
|
---|
253 | OBLIGATION AMOUNT:
|
---|
254 | Warning - Computed Liquidation amt of $
|
---|
255 | total obligated amt of $
|
---|
256 | for BOC
|
---|
257 | ****WARNING**** - Certified Invoice total $
|
---|
258 | does not match sum of
|
---|
259 | Line Amounts: $
|
---|
260 | If you believe that the Total Invoice Amount Certified for
|
---|
261 | payment is incorrect, the invoice should be returned to voucher audit
|
---|
262 | for review.
|
---|
263 | There are no Line Amounts - FMS will not accept this!
|
---|
264 | An original FMS SO or MO document could not be found for
|
---|
265 | Please review obligation history for this Purchase Order.*
|
---|
266 | OK to process this payment to FMS
|
---|
267 | Unliquidated obligation amounts and BOCs on this order are:
|
---|
268 | Total Invoice Amount Certified for Payment=$
|
---|
269 | <Option Terminated.>*
|
---|
270 | Edit exited abnormally. Action terminated.*
|
---|
271 | Do you want to return this invoice to Voucher Audit
|
---|
272 | Liquidation #
|
---|
273 | has been deleted and unposted.
|
---|
274 | FMS PAYMENT VOUCHER
|
---|
275 | Invoice ID#: ~?48
|
---|
276 | Certification Required? ~!!
|
---|
277 | Document Locator Number: ~?38
|
---|
278 | Date of Invoice: ~?38
|
---|
279 | Date Invoice Received:
|
---|
280 | Date Goods/Services Received: ~?48
|
---|
281 | Invoice Type: ~!
|
---|
282 | Vendor: ~!!
|
---|
283 | FMS Vendor ID#: ~!
|
---|
284 | Vendor Stub Name:
|
---|
285 | Total Payment: $ ~!!
|
---|
286 | Shipping: $
|
---|
287 | Discount %: ~!
|
---|
288 | NET
|
---|
289 | Discount Amount:
|
---|
290 | Interest Indicator: ~!!
|
---|
291 | Money Management Status:
|
---|
292 | Liquidation Code: ~!
|
---|
293 | BOC #1: ~!
|
---|
294 | Liquidation Amt #1: $ ~?38
|
---|
295 | BOC #2: ~!
|
---|
296 | Liquidation Amt #2: $ ~?38
|
---|
297 | Are you ready to release this invoice to FMS
|
---|
298 | <Action Terminated>*
|
---|
299 | Unable to select CAPPS transaction type 900.00. Please try again.
|
---|
300 | No new FMS document created - Files inaccessible at this time.*
|
---|
301 | Transferring invoice data to CAPPS transmittal document.*
|
---|
302 | Transmittal document was
|
---|
303 | #################### #################### ####################
|
---|
304 | #################### #################### ####################
|
---|
305 | #################### #################### ####################
|
---|
306 | #################### #################### ####################
|
---|
307 | #################### #################### ####################
|
---|