| [604] | 1 | English French Notes Complete/Exclude
|
|---|
| 2 | Locations currently in the space file:
|
|---|
| 3 | UPDATING 'UNIT CONVERSION FACTOR' AND 'SKU' IN FILE 441 FROM FILE 445.
|
|---|
| 4 | EDI STATUS
|
|---|
| 5 | (Error Code is
|
|---|
| 6 | PRC(1)
|
|---|
| 7 | IFCAP SERVER PROCESSOR
|
|---|
| 8 | PRCXM(
|
|---|
| 9 | IFCAP EDI/RFQ MESSAGE ERROR
|
|---|
| 10 | UM;0@.dIon}4_Pw-8qyC?K/YV|6t7sE]fx'D`TB%R#a{\!G<29h5rc:|m|
|
|---|
| 11 | Nv*}z&da|6|
|
|---|
| 12 | RLVu{oBv=P?8+X-j%A!(<]|Z|
|
|---|
| 13 | QW'CfD&;}- (6Bv>kYgj_GJFE`q]!H27usXz5ZxR%p.Kh{)tUe|:=LV@/[Sw1<ObP#,8daoT\4cri?Al|+|
|
|---|
| 14 | GTeO=MFIZ5vbu>m_9)C}6Ps73%x]w[?Xrf+QKRqWB<4EY8DSn1kL |oV-@2#lU(Jp,A{;0d/H&jg.Niy!:'|t|
|
|---|
| 15 | UAJ4{q[0|m|
|
|---|
| 16 | CMiqpj=,:|a)glXJn0RbwFfDz*e(\H9hc6.{TSY|E|
|
|---|
| 17 | This routine changes ALL code sheets created before
|
|---|
| 18 | ' that have a status of 'TRANSMITTED'
|
|---|
| 19 | and changes the status to 'ACCEPTED BY FMS'.
|
|---|
| 20 | Do you wish to print the Document Identifier of each code
|
|---|
| 21 | sheet changed
|
|---|
| 22 | no action taken.
|
|---|
| 23 | Change Generic Code Sheet Status
|
|---|
| 24 | No Create Date (CRDT). Program exiting.
|
|---|
| 25 | Changing Generic Code Sheets created before
|
|---|
| 26 | from a status of 'TRANSMITTED'
|
|---|
| 27 | to a status of 'ACCEPTED BY FMS'.
|
|---|
| 28 | At PRCODCT, PRCDA =
|
|---|
| 29 | IFCAP FMS MESSAGE SERVER
|
|---|
| 30 | IFCAP SERVER ERROR
|
|---|
| 31 | Document Confirmation Transaction (DCT)
|
|---|
| 32 | System ID:
|
|---|
| 33 | Receiving Station #:
|
|---|
| 34 | Transaction Code :
|
|---|
| 35 | Transaction Date :
|
|---|
| 36 | Transaction Time :
|
|---|
| 37 | Interface Version #:
|
|---|
| 38 | Accepted.
|
|---|
| 39 | Rejected:
|
|---|
| 40 | FMS Document
|
|---|
| 41 | You are not an A&MM EMPLOYEE, exiting option.
|
|---|
| 42 | Do you want to see all the records now
|
|---|
| 43 | Answering Yes or Y to this question will let you
|
|---|
| 44 | see information about all the PHA, RFQ and TXT
|
|---|
| 45 | transactions from all SENDERs.
|
|---|
| 46 | Answering No or N will limit you to viewing the
|
|---|
| 47 | PHA, RFQ and TXT transactions from one SENDER.
|
|---|
| 48 | Exiting option.
|
|---|
| 49 | NP12-INVOICE ADDRESS pointer is missing.
|
|---|
| 50 | NPIA-Invoice address missing.
|
|---|
| 51 | NMIL-MAIL INVOICE LOCATION information in file 411 missing.
|
|---|
| 52 | NMIC-No mail invoice city in file 411.
|
|---|
| 53 | NMIS-No state file pointer in file 411.
|
|---|
| 54 | NMIZ-No mail invoice ZIP CODE entry in file 411.
|
|---|
| 55 | NST0-'STATE' record is missing in STATE file.
|
|---|
| 56 | NSTA-Abbreviation missing in state file entry.
|
|---|
| 57 | NV0-No vendor record found in vendor file.
|
|---|
| 58 | NSTP-No Vendor Address pointer to the State file.
|
|---|
| 59 | NVID-Missing a vendor ID number for an EDI vendor.
|
|---|
| 60 | NST0-No state file record.
|
|---|
| 61 | NSTA-No abbreviation in state file.
|
|---|
| 62 | NBT-No Vendor Business Type.
|
|---|
| 63 | NSIT-No site entry in file 442.
|
|---|
| 64 | NSTL-No ship to pointer to entry in file 411.
|
|---|
| 65 | NRL-No receiving location record in file 411.
|
|---|
| 66 | NSTT-No State file pointer in Receiving Location in file 411.
|
|---|
| 67 | NSTS-There is no ship to suffix for receiving location for
|
|---|
| 68 | this EDI P.O.
|
|---|
| 69 | -No SITE information in file 411.
|
|---|
| 70 | -No facility type pointer for SITE in file 411.
|
|---|
| 71 | -No entry in file 411.2 for facility type pointer from file 411.
|
|---|
| 72 | NST0-No record in state file.
|
|---|
| 73 | NOPT-No patient file entry for direct delivery patient pointer.
|
|---|
| 74 | NDP0-No record for direct delivery patient pointer.
|
|---|
| 75 | NSTDP-No State file pointer in Direct Delivery Address.
|
|---|
| 76 | NST0-No record in the state file.
|
|---|
| 77 | NPPT-No prompt payment terms entered in P.O.
|
|---|
| 78 | NSC-No SORCE CODE for this P.O.
|
|---|
| 79 | -No contract number for this P.O.
|
|---|
| 80 | -No quantity listed for this ITEM.
|
|---|
| 81 | -No unit of purchase pointer for this ITEM.
|
|---|
| 82 | -No entry in unit of issue file for unit of purchase pointer in
|
|---|
| 83 | ITEM entry in P.O. file.
|
|---|
| 84 | -No name entry in unit of purchase file for unit of
|
|---|
| 85 | purchase pointer in ITEM entry in P.O. file.
|
|---|
| 86 | -No actual unit cost for this ITEM.
|
|---|
| 87 | -This order requires a contract number but none was entered
|
|---|
| 88 | for this ITEM.
|
|---|
| 89 | NP12-No node 12 in file 442 for this P.O.
|
|---|
| 90 | NPOD No purchase order date in file 442 for this P.O.
|
|---|
| 91 | NDD No delivery date for this P.O. in file 442.
|
|---|
| 92 | NPPM No purchasing agent entry in file 442 for this P.O.
|
|---|
| 93 | NPHN No phone number node in the person file for this PPM.
|
|---|
| 94 | NPH No phone number for this PPM in the person file.
|
|---|
| 95 | NOPR No PROPOSAL entry in file 442 for this P.O.
|
|---|
| 96 | NPO0 Zero node of record missing. Unable to check further.
|
|---|
| 97 | NPO1 Node 1 missing in record.
|
|---|
| 98 | not generated - purchase order corrupted.
|
|---|
| 99 | not generated - inappropriate for this order.
|
|---|
| 100 | not generated - PO informated corrupted
|
|---|
| 101 | not generated - not used for GSA Supply Depot orders.
|
|---|
| 102 | ...now generating the
|
|---|
| 103 | not generated - missing information (data code:
|
|---|
| 104 | PRC(2)
|
|---|
| 105 | PRCO EDI REPORTS
|
|---|
| 106 | EDI Transactions from IFCAP Reports
|
|---|
| 107 | Sender is
|
|---|
| 108 | TXT/RFQ
|
|---|
| 109 | Select one of the valid actions above, or enter '??' for extended help.
|
|---|
| 110 | There are no records to report on at this time.
|
|---|
| 111 | Select PHA, RFQ or All:
|
|---|
| 112 | Enter a selection, more than one selection separated with a ','
|
|---|
| 113 | a range of selections seperated with a '-' or exclude an entry with a '.
|
|---|
| 114 | Enter the DATE/TIME CREATED starting date
|
|---|
| 115 | Enter the DATE/TIME CREATED ending date
|
|---|
| 116 | Your selection will generate the Transaction Summary Statistical Report
|
|---|
| 117 | for the following date range:
|
|---|
| 118 | Transaction Summary Statistics Report
|
|---|
| 119 | Summary of Processed Records:
|
|---|
| 120 | # of accepted (ACT) records -
|
|---|
| 121 | # of rejected (RJT) records -
|
|---|
| 122 | Summary of Transactions Waiting Austin Processing
|
|---|
| 123 | # of PHA records -
|
|---|
| 124 | # of RFQ records -
|
|---|
| 125 | # of TXT records -
|
|---|
| 126 | TRANSACTION SUMMARY STATISTICS REPORT
|
|---|
| 127 | TRANSACTION SUMMARY STATISTICS REPORT for
|
|---|
| 128 | Date Range for Report:
|
|---|
| 129 | Press <ENTER> to
|
|---|
| 130 | EC/EDI Reconciliation Report
|
|---|
| 131 | EC/EDI RECONCILIATION REPORT
|
|---|
| 132 | EC/EDI RECONCILIATION REPORT for
|
|---|
| 133 | DOCUMENT #
|
|---|
| 134 | AUSTIN ACCEPTANCE
|
|---|
| 135 | No transactions for the date range selected.
|
|---|
| 136 | ** REJECT CODE==>
|
|---|
| 137 | EC/EDI Exceptions Report
|
|---|
| 138 | Reject Reason Code:
|
|---|
| 139 | EC/EDI EXCEPTION REPORT
|
|---|
| 140 | EC/EDI EXCEPTION REPORT for
|
|---|
| 141 | >>>> PRJ EXCEPTIONS <<<<
|
|---|
| 142 | REFERENCE #
|
|---|
| 143 | DATE/TIME PROCESSED
|
|---|
| 144 | INCORRECT SEGMENT
|
|---|
| 145 | INCORRECT FIELD
|
|---|
| 146 | LINE#
|
|---|
| 147 | DESC-LINE#
|
|---|
| 148 | DE-SEQ#
|
|---|
| 149 | CO-SEQ#
|
|---|
| 150 | FIELD CONTENTS
|
|---|
| 151 | >>>> POA EXCEPTIONS <<<<
|
|---|
| 152 | LINE ITEM #
|
|---|
| 153 | QTY EXCEPTED
|
|---|
| 154 | EXCEPTION REASON
|
|---|
| 155 | >>> Incoming processing errors <<<
|
|---|
| 156 | No records meet the selection criteria.
|
|---|
| 157 | Enter the line number of the PO/RFQ
|
|---|
| 158 | LINE NUMBER:
|
|---|
| 159 | Please enter the line number next to the PO/RFQ Number.
|
|---|
| 160 | Response must be no greater than
|
|---|
| 161 | THE ENTRY IN FILE 443.75 IS MISSING
|
|---|
| 162 | Please use option View RFQ [PRCHQ15] to review this line item.
|
|---|
| 163 | IFCAP 'POA' for Purchase Order
|
|---|
| 164 | IFCAP 'POA' SERVER
|
|---|
| 165 | segment is not found in the POA transaction.
|
|---|
| 166 | Contact the EDI HELP DESK in Austin about this transaction.
|
|---|
| 167 | site listed in the POA transaction can not be found
|
|---|
| 168 | in the IFCAP ADMIN ACTIVITY SITE PARAMETER file.
|
|---|
| 169 | was not found in file 443.75.
|
|---|
| 170 | does not have a VENDOR ID number.
|
|---|
| 171 | Purchase Order Acknowledgment
|
|---|
| 172 | was not found in the PO file.
|
|---|
| 173 | Item
|
|---|
| 174 | was not found in PO
|
|---|
| 175 | The Vendor Stock Number wasn't found in item
|
|---|
| 176 | There is no quantity listed for item
|
|---|
| 177 | There is no Unit of Purchase listed for item
|
|---|
| 178 | There is no Unit Cost listed for item
|
|---|
| 179 | The Vendor Stock Number from the POA doesn't match the one from item
|
|---|
| 180 | The Quantity listed in the POA doesn't match the one listed in item
|
|---|
| 181 | The Unit of Purchase listed in the POA doesn't match the one in item
|
|---|
| 182 | The Unit Cost listed in the POA doesn't match the one in item
|
|---|
| 183 | The POA for PO
|
|---|
| 184 | is missing a line item number.
|
|---|
| 185 | IFCAP 'POA' PROBLEM
|
|---|
| 186 | POA Server Interface
|
|---|
| 187 | ) AND REPLACE ALL VARIABLES
|
|---|
| 188 | IFCAP 'INV' for Purchase Order
|
|---|
| 189 | IFCAP 'INV' SERVER
|
|---|
| 190 | was not found in the CI file.
|
|---|
| 191 | was not found in CI
|
|---|
| 192 | The Vendor Stock Number from the INV doesn't match the one from item
|
|---|
| 193 | The Quantity listed in the INV doesn't match the one listed in item
|
|---|
| 194 | The Unit of Purchase listed in the INV doesn't match the one in item
|
|---|
| 195 | The Unit Cost listed in the INV doesn't match the one in item
|
|---|
| 196 | IFCAP 'INV' PROBLEM
|
|---|
| 197 | INV Server Interface
|
|---|
| 198 | No P.O. selected...quitting
|
|---|
| 199 | This P.O. has never been sent to Austin in a PHA transaction. It can't be
|
|---|
| 200 | sent using this option.
|
|---|
| 201 | The Purchasing Agent has specified that this order not go out EDI.
|
|---|
| 202 | This P.O. can't be sent using this option.
|
|---|
| 203 | For some reason there is no vendor listed in this P.O. This P.O. can't be
|
|---|
| 204 | processed in this option.
|
|---|
| 205 | This P.O. is not going to a vendor that can accept a P.O. electronically.
|
|---|
| 206 | This P.O. can't be sent in this option.
|
|---|
| 207 | Do you want to re-transmit PO
|
|---|
| 208 | If you have an EDI TRANSACTION REPORT for a rejected PHA transaction
|
|---|
| 209 | and have corrected the P.O. answer YES to send a new PHA transaction.
|
|---|
| 210 | OK ^ MAIL MESSAGE NO. =
|
|---|
| 211 | PRCO VENDOR REVIEW
|
|---|
| 212 | VENDOR REQUESTs for review
|
|---|
| 213 | No VRQs to review
|
|---|
| 214 | FMS VENDOR
|
|---|
| 215 | There are no VRQs for you to review at this time.
|
|---|
| 216 | Select a printer:
|
|---|
| 217 | No printer selected -- quitting.
|
|---|
| 218 | VALMY(
|
|---|
| 219 | Complete review of vender entry
|
|---|
| 220 | VENDOR Review
|
|---|
| 221 | Ordering Address:
|
|---|
| 222 | FMS Name:
|
|---|
| 223 | Payment ADDRESS:
|
|---|
| 224 | PAYMENT CONTACT PERSON:
|
|---|
| 225 | PAYMENT PHONE NUMBER:
|
|---|
| 226 | FMS VENDOR CODE:
|
|---|
| 227 | ALT-ADDR-IND:
|
|---|
| 228 | TAX ID/SSN:
|
|---|
| 229 | SSN/TAX ID IND:
|
|---|
| 230 | NON-RECURRING/
|
|---|
| 231 | RECURRING VENDOR:
|
|---|
| 232 | 1099 VENDOR INDICATOR:
|
|---|
| 233 | VENDOR TYPE:
|
|---|
| 234 | DUN & BRADSTREET:
|
|---|
| 235 | Vendor Name:
|
|---|
| 236 | Ordering Address:
|
|---|
| 237 | FMS Name:
|
|---|
| 238 | Payment ADDRESS:
|
|---|
| 239 | VENDOR NAME:
|
|---|
| 240 | PAGE: 2
|
|---|
| 241 | FMS VENDOR CODE:
|
|---|
| 242 | TAX ID/SSN:
|
|---|
| 243 | SSN/TAX ID IND:
|
|---|
| 244 | RECURRUNG VENDOR:
|
|---|
| 245 | VENDOR TYPE:
|
|---|
| 246 | IFC,ISM
|
|---|
| 247 | missing in RD.
|
|---|
| 248 | IFCAP ISMS MESSAGE SERVER
|
|---|
| 249 | IFCAP message router error
|
|---|
| 250 | Sent to Server:
|
|---|
| 251 | MailMan Message #:
|
|---|
| 252 | Sent From:
|
|---|
| 253 | Message Subject:
|
|---|
| 254 | What this server thinks is the CONTROL segment of the transaction:
|
|---|
| 255 | This is the CONTROL segment from the saved transaction in file 423.6:
|
|---|
| 256 | Sending Station #:
|
|---|
| 257 | Sales or Order #:
|
|---|
| 258 | Message File (423.6) #:
|
|---|
| 259 | Recieving Station #:
|
|---|
| 260 | IFC-
|
|---|
| 261 | There are new ITEM MASTER entries from ISMS SSO transaction to be added.
|
|---|
| 262 | New items from SSO transactions to add
|
|---|
| 263 | SOURCE OK
|
|---|
| 264 | There are new GENERIC INVENTORY entries from ISMS SSO transaction to add
|
|---|
| 265 | to the warehouse inventory.
|
|---|
| 266 | ITEM DESCRIPTION:
|
|---|
| 267 | New items from SSO transaction to add to Warehouse
|
|---|
| 268 | There are new REPETITIVE ITEM LIST entries created from ISMS SSO
|
|---|
| 269 | transactions ready to be generated into 2237's.
|
|---|
| 270 | # OF ITEMS:
|
|---|
| 271 | TOTAL COST:
|
|---|
| 272 | REPETITIVE ITEM LIST FROM 'SSO' TRANSACTIONS
|
|---|
| 273 | has no
|
|---|
| 274 | I can find NO warehouse entry in the GENERIC INVENTORY file for station
|
|---|
| 275 | IFCAP 'SSO' message
|
|---|
| 276 | IFCAP 'SSO' SERVER
|
|---|
| 277 | CAN'T CREATE MAILMAN MESSAGE
|
|---|
| 278 | IFCAP 'SSO' MESSAGE
|
|---|
| 279 | PRCO VENDOR EDIT FOR AR
|
|---|
| 280 | Edit vendor selected by AR user
|
|---|
| 281 | No Vendor records to edit.
|
|---|
| 282 | There are no vendor records to edit at this time.
|
|---|
| 283 | * Payment ADDRESS:
|
|---|
| 284 | * = REQUIRED FIELD
|
|---|
| 285 | * TAX ID/SSN:
|
|---|
| 286 | * SSN/TAX ID IND:
|
|---|
| 287 | * VENDOR TYPE:
|
|---|
| 288 | This record has already been sent to Austin or FISCAL.
|
|---|
| 289 | Review the vendor selected
|
|---|
| 290 | Edit the Vendor record
|
|---|
| 291 | * = REQUIRED FIELD
|
|---|
| 292 | This record in now properly vendorized. You may delete it.
|
|---|
| 293 | This record is sent. It needs to be removed.
|
|---|
| 294 | This entry can not become a VRQ yet. Re-edit it.
|
|---|
| 295 | This record needs to be edited first.
|
|---|
| 296 | This record needs to be sent first.
|
|---|
| 297 | entries in your IFCAP SITE PARAMETER file.
|
|---|
| 298 | You need to set one as the PRIMARY STATION.
|
|---|
| 299 | DOES A VRQ NEED TO GO TO AUSTIN (YES/NO)
|
|---|
| 300 | Creating the FMS VENDOR REQUEST.
|
|---|
| 301 | Vendor Request
|
|---|
| 302 | The system determined that no VRQ needed or could be created.
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
