Home » Categories » Solutions by Business Process » E-Business » XML |
Lookup File Structure |
Article Number: 1886 | Rating: Unrated | Last Updated: Thu, Jun 22, 2023 at 4:34 PM
|
Datafile Software Lookup File Structure Item Name Type Size Description 1 CODE X 17 Lookup code, which might be a trading partner code, an EAN product or location code, or any other code 2 NAME X 40 Description or name 3 INTERNAL-CODE X 17 Used to hold an EAN code or similar item 4 PROCESS X 4 Used, for example, to hold a 4-digit short form name for a customer or supplier, used (say) in constructing a file reference number or pathname 5 FLAG ? 1 Y/N flag for whatever purpose required 6 DATE-ADDED E 10 Automatically filled when record added 7 USER X 6 … ditto 8 EAN-CODE(NON) X 17 An alternative to the INTERNAL-CODE above if needed 9 HO-ACCOUNT X 10 Your trading partner’s account code for your company 10 STOCK-CODE = 17 Where the INTERNAL-CODE item is a stock code and you are using multi-location stock, this extracts just the stock code element 11 DEF-STK-LOCN X 10 Default stock location in a multi-stock system 12 PRICE K 10 Where CODE is for a product, holds price from stock file 13 UNOR N 4 Use this as the pack-size: the number of consumer units in a traded unit 14 PATHNAME-1 X 12 ) 15 FILENAME-1 X 20 ) Holds pathname and filename reference in 16 PATHNAME-2 X 12 ) template pathname and filename commands. 17 FILENAME-2 X 20 ) Up to 3 sets to allow for 3 different types of XML 18 PATHNAME-3 X 12 ) file that could be sent (easy to add more below) 19 FILENAME-3 X 20 ) The entries below define what type of GLU table this entry represents. Normally one and only one is marked with a Y, except where an entry is present in more than one table. 20 LOCN-IN? ? 1 ) Y for incoming customer/location entry (e.g. EAN code) 21 LOCN-OUT? ? 1 ) Y for outgoing customer/location entry (own code) 22 PRODUCT? ? 1 ) Y for incoming product entry (e.g. EAN code) 23 FLAG4? ? 1 ) Flags below are spares for your own use 24 FLAG5? ? 1 ) 25 FLAG6? ? 1 ) 26 FLAG7? ? 1 ) 27 FLAG8? ? 1 ) 28 FLAG9? ? 1 ) 29 FLAG10? ? 1 ) 36 XML-FILE N 4 A sequence number for use in outgoing XML files 37 FILE-REF-NO N 4 Reserved for EDI use 38 PRINT? ? 1 Reserved for EDI use – 82 – Item Name Type Size Description 40 SP-VER-ORD X 5 ) 41 SP-VER-ACK X 5 ) The XML schema template version number for the 42 SP-VER-DEL X 5 ) outgoing schemas used in the sales order cycle 43 SP-VER-INV X 5 ) 44 SP-VER-CRN X 5 ) 50 PP-VER-ORD X 5 ) 51 PP-VER-ACK X 5 ) The XML schema template version number for the 52 PP-VER-DEL X 5 ) outgoing schemas used in the purchase order cycle 53 PP-VER-INV X 5 ) 54 PP-VER-CRN X 5 ) 60 FLGN-ORDERS N 4 ) 61 FLGN-ACKNOWS N 4 ) File generation numbers for the (output) files in question 62 FLGN-DELIVS N 4 ) 63 FLGN-INVS N 4 ) 64 FLGN-CRNS N 4 ) 70 TEST-A? ? 1 ) 71 TEST-B? ? 1 ) Some currently undefined flags, expected to be used for 72 TEST-C? ? 1 ) the file types: orders, acknowledgements, deliveries, 73 TEST-D? ? 1 ) invoices and credit notes 74 TEST-E? ? 1 ) 81 KEEP? ? 1 "Y” if this stock or location record is not to be deleted 82 HO-A/C? ? 1 "Y” indicates this is the main company account 83 MULT-LOCN? ? 1 "Y” indicates multi-location stock in use (but see CON) 84 FOREIGN-CURR? ? 1 "Y” indicates foreign currency in use (but see CON) 85 MULT-COMPY? ? 1 "Y” indicates that this single company processes the incoming files of more than one company (but see CON) 86 ALTN-STK? ? 1 "Y” indicates use alternate stock code (not implemented) 87 CR-NOTES? ? 1 "Y” indicates that sales credit notes are to be sent as well as invoices (although in a separate file) 88 OMIT-ZERO? ? 1 "Y” indicates that zero-valued sales invoice or credit notes or detail lines are to be omitted from output files 89 POD-NEEDED ? 1 "Y” indicates that proof of delivery is required 90 CRN-AUTHORITY ? 1 "Y” indicates that the credit note must first be authorised 91 DEFLT-B/O ? 1 "Y” indicates that back orders are to be sent by default 92 APP-FLAG12? ? 1 ) 93 APP-FLAG13? ? 1 ) Spare Y/N flags as required 94 APP-FLAG14? ? 1 ) 95 APP-FLAG15? ? 1 ) 100 ALT-CODE1 X 16 ) 101 ALT-CODE2 X 16 ) Alternate stock codes (not implemented) 102 ALT-CODE3 X 16 ) 103 ALT-CODE4 X 16 ) 104 ALT-CODE5 X 16 ) 106 SIDN-SCODE X 12 Leave for compatibility with EDI. 111 BRANCH X 2 ) 112 RDC-MNEMONIC X 3 ) These were added specifically for Spicers, but may have 113 VAN-ROUTE X 2 ) further uses too 114 COMB-AC-BR & 12 ) 121 PRD=EAN ? 1 ) These two items were added in expectation of use in 122 PRD=ALT-NO Y 1 ) purchase orders to determine which supplier code to use, but nothing implemented at time of writing. Note — Item 160 THIS ITEM MUST BE KEPT BUT NOT BE USED. This is used by some ProFiler applications as the dummy lookup item for this file in database profiles, where the actual lookup item is defined within (say) screen entry design. |
Attachments
There are no attachments for this article.
|
XML Template Display
Viewed 1448 times since Mon, Jul 9, 2012
XML Audit Trail Error Codes
Viewed 1911 times since Tue, Jul 10, 2012
Archive XML Orders
Viewed 1388 times since Mon, Jul 9, 2012
Application Considerations - Sales Order Processing
Viewed 1891 times since Tue, Jul 10, 2012
XML General Configuration
Viewed 1353 times since Mon, Jul 9, 2012
Purchase Order Header (POH)
Viewed 3369 times since Tue, Jul 10, 2012
addto
Viewed 1364 times since Mon, Jul 9, 2012
additions
Viewed 1357 times since Mon, Jul 9, 2012
restore
Viewed 1448 times since Mon, Jul 9, 2012
Template Attributes
Viewed 1404 times since Mon, Jul 9, 2012
|