EDI PROCESSING INTERFACE MODULE... 1

Transcription

1 Table of Contents... 1 EDI PROCESSING OVERVIEW... 3 TRANSACTIONS PROCESSED:... 3 PRODUCT REQUIREMENTS:... 3 CUSTOMER TRANSACTION FLOW:... 3 VENDOR TRANSACTION FLOW... 4 SETUP PROCEDURE... 5 TRANSFER PROCEDURE... 6 FTPCFGM-... FTP CONFIGURAGTION MAINTENANCE... 7 FTPRECV-... FTP DATA RECEIVING PROGRAM FTPSEND-... FTP DATA SENDING PROGRAM EDIPOG-... EDI PURCHASE ORDER GENERATION MONITORING AND ALERTS PROGRAMS EDIPOLDQ-... EDI CUSTOMER P.O. PROCESSING QUERY/ALERT PROGRAM SETUP AND MAINTENANCE PROGRAMS EDITPM-... EDI TRADING PARTNER MAINTENANCE EDITPVM-... EDI TRADING PARTNER VENDOR MAINTENANCE EDISVM-... EDI TRADING PARTNER SHIP VIA MASTER TABLE MAINT EDITERM-... EDI TRADING PARTNER TERMS MASTER TABLE MAINT EDIUOM-... EDI TRADING PARTNER U.O.M. XREF TABLE MAINT PROCESSING INBOUND TRANSACTIONS EDIPOLD-... EDI PURCHASE ORDER UPLOAD PROGRAM PROGRAM OVERVIEW B1 - UPLOAD/IMPORT ASCII/EXCEL FILE OPTION B2 - VALIDATION OPTION B3 - MAINTENANCE OPTION B4 - ORDER CREATION OPTION B5 - PURGE OPTION C - CUSTOM PROGRAM ROUTINE CAPABILITY D - FILE AND FIELD LAYOUTS E - INBOUND CUSTOMER PURCHASE ORDER ASCII FILE DEFINITION (850) G - EDI INBOUND P. O. HEADER TABLE MAPPING (EDINH) TO ORDER TABLES H - EDI INBOUND P. O. DETAIL TABLE MAPPING (EDIND) TO ORDER TABLES I - ACF OPTIONS FOR THE EDI MODULE PROCESSING OUTBOUND TRANSACTIONS EDIASNG-... EDI OUTBOUND ADVANCED SHIP NOTICES GENERATION EDIINVCG-... EDI OUTBOUND INVOICE ASCII FILE GENERATION EDIPOG -... EDI PURCHASE ORDER ASCII FILE GENERATION EDIMNTU-... EDI ORDER MAINTENANCE FILE UPDATE EDIBILU-... EDI BILLING FILE UPDATE EDIPRG-... EDI FILES PURGE EDITPMCM-... EDI TRADING PARTNER MANUAL CUSTOMER MAINT. PROGRAM EDIMCG-... EDI MANUAL CUSTOMER TRANSACTION GENERATION

2 Proprietary Notice This manual contains information which is proprietary to Munics Information Systems, Inc. and all rights are reserved. No part of this manual or its contents may be used or reproduced by any means without the express written permission of Munics Information Systems, Inc. Disclaimer of Warranty The material contained herein is subject to change without notice. Munics Information Systems, Inc. makes no warranty, express, implied or by description, regarding the information set forth herein. Munics Information Systems, Inc. does not guarantee, warrant or make any representation regarding the use of, or the results of the use of, the programs in terms of correctness, accuracy, reliability, currency or otherwise, and the purchaser relies on the programs and the results solely at his/her own risk. NEXT GENERATION is a registered trademark of Munics Information Systems, Inc. Copyright Munics Information Systems, Inc. Release NGS-7.00 EDI- 2

3 EDI PROCESSING OVERVIEW TRANSACTIONS PROCESSED: - Incoming Purchase Order Transactions (850) from your customers. - Outgoing Advanced Ship Notices (856), Invoices (810) and Combined Advanced Ship Notices / Invoices (857) to your customers. - Outgoing Purchase Order Transactions (850) to your vendors. PRODUCT REQUIREMENTS: - The Next-Generation TM EDI Processing Subsystem. - A Third Party PC or UNIX based EDI communication, translation and mapping package with the capabilities of sending and receiving the EDI transactions from your trading partners, translating these documents into an ASCII format and mapping each trading partner document to the required Next- Generation TM standard ASCII file formats. - If you use a PC product, the PC must be interfaced to the UNIX system and have the capability of transferring ASCII files from the PC to the UNIX system and vice versa. CUSTOMER TRANSACTION FLOW: The third party EDI communication, translation and mapping software package must receive EDI purchase order transactions (850), translate and map them to our standard EDI ASCII File Format, and upload them into a directory on the UNIX system so that the Next-Generation TM Software can access these files. Once the above is completed, the Next-Generation TM EDI Software will take over. The EDI Inbound Processing Program (EDIPOLD) will process the 850 transactions: - The UPLOAD option will be processed to upload the ASCII files into Informix database files. This will generate data records in the EDI header and detail files on the Next-Generation TM system. - The VALIDATION option will be processed once the files are uploaded to validate the data sent in and determine the customer and items to be processed. The system will flag any invalid transactions such as invalid trading partners, invalid ship to customers, invalid items, duplicate purchase orders and purchase orders outside of a defined date range. - The MAINTENANCE option must be processed for invalid transactions to modify the invalid fields manually or to remove the invalid records. - The VIEW option may be processed to provide a report to the screen, printer or a hold file of the EDI transactions. - The ORDER CREATION option will be processed for validated records. The system will create temporary order files based on the information provided from the EDI files. The system will set additional fields based on the default fields defined for the customer and item on the Next Generation TM database. As each record is processed, the system will generate an order in the standard order database tables from the temporary files. Release NGS-7.00 EDI- 3

4 - The PURGE option may be utilized to remove records, which have been updated to the order tables, at regular intervals. Once the order has been generated, the Next-Generation TM order processing system is utilized to print forms, generate reports, provide inquiries and process the order. Once the order is ship confirmed, the EDI Advanced Ship Notices Processing Program (EDIASNG) is utilized to generate an ASCII file in our standard format for Advanced Ship Notice documents (856). Once the order is billed, the EDI Invoice Processing Program (EDIINVCG) is utilized to generate ASCII files in our standard format for Invoice documents (810) or Combined Advanced Ship Notice / Invoice douments (857). Once the ASCII files are generated, the EDI processing on the Next-Generation TM system is completed. The ASCII files must then be downloaded to the PC, processed through the Third Party communications, translation and mapping software and then transmitted to the trading partners. VENDOR TRANSACTION FLOW Once the purchase order has been entered, the EDI Purchase Order Generation Program (EDIPOG) is utilized to generate an ASCII file in our standard format for Purchase Order documents (850). Once the ASCII file is generated, the EDI processing on the Next-Generation TM system is completed. The ASCII files must then be downloaded to the PC, processed through the Third Party communications, translation and mapping software and then transmitted to the trading partners. The third party EDI communication, translation and mapping software package must map our standard EDI purchase order ASCII file format to the EDI purchase order document (850) based on the trading partner requirements, translate the data to the standard EDI Transaction Document (850), and transmit the document to the trading partner mailbox. The Next-Generation TM purchase order processing system is utilized to print forms, generate reports, provide inquiries and process the purchase order and purchase order receipt. Release NGS-7.00 EDI- 4

5 SETUP PROCEDURE 1. The following data files/fields must be setup prior to utilizing EDI: - CM If desired, a memo field may be defined to flag customers which will do EDI transactions. - CICR - Setup applicable customer part numbers if customer part verification will be performed. - IM - If the customer will be using the UPC code, the UPC code may be setup in the item crossreference field in the item master table. The UPC code may also be setup in the Item Interchange Table through the UPCLOAD program. As an alternative (or if different customers have different UPC codes), the Customer Item Cross-Reference File (CICR) may be used. - EDITPM - Each EDI customer must be setup in the EDI Trading Partner Maintenance program (editp table). - If the customer will be using outbound transactions (856, 857, 810), records must be setup in the EDI Ship Via Maintenance (EDISVM: edisv table) and the EDI Terms Table Maintenance (EDITERM: editerm table) programs. - If the customer will be using unit of measure conversions, records must be setup in the EDI Unit Of Measure Cross-Reference Maintenance program (EDIUOM: ediuom table). 2. The ACF options' default values (all of which have an option code beginning with the characters 'edi') should be analyzed and, if necessary, changed. 3. If the trading partner will receive EDI Invoice transmissions, modifications may be required to the Invoice Print program (INVP) to correspond to the customer's need to send invoices to EDI customers. 4.All fields are brought into the EDI files themselves (edinh, edind). Records are generated as the transaction is processed to the EDI Order Tables (orderc, orddet2), EDI Order Maintenance Tables (ormntc, ormntd2), EDI Open Invoice Tables (invoicec, invdet2) and EDI Invoice History Tables (invc, invd2). These tables may be used to produce custom reports through ODBC capabilities (if you have purchased the components required) and are used as a source of information to send back data to the trading partner on outbound Advanced Ship Notice and Invoice transactions. Analysis must be done of the EDI transactions done by the customer to determine if any additional fields sent need to be mapped to the standard order (and ship and invoice tables). If additional fields, are required, additional customization may be required. Note that the EDI Outbound transactions (advanced ship notices and invoices) require that the transactions were originally added to the system through an EDI Inbound transaction (purchase order). Release NGS-7.00 EDI- 5

6 TRANSFER PROCEDURE In order to utilize EDI, ASCII files need to be generated on the PC for the EDI transactions. Once these files are generated, there are several methods to "transfer" these files to the Unix system. 1) One method is to transfer the file using a diskette. This is the method that must be used if the PC is not networked with the Unix system. You would upload the file from the PC to the diskette and download the file from the diskette to the Unix system. 2) Another method is to create a "shared" directory between the PC and Unix system. When the EDI ASCII file is generated in this directory, it is immediately available for processing by the Unix system. 3) Another method is to use a PC transfer utility (for example, FTP). If FTP is used, only the user who transferred the ASCII file will have sufficient access to upload the file on the Unix system. When FTP transfers a program, it transfers for the user and group of the user. The permissions are set to 640 (owner has read/write permission, group has read permission, others have no permission). Therefore, since read/write permission is required to upload the file, only the owner (the user that performed the transfer) can perform the upload. If it is desired for another user to have access, after transferring the file to the Unix system, go into the applicable directory (normally $EDIPROGS/edin/data) and change the permissions on the file so all users have access (normally by chmod 666 <filename>). An example of FTP procedure session (make sure you follow your own FTP procedure): - windows. - Start. - programs. - msdos prompt. - cd to directory in which ASCII file resides. - ftp (Unix system name> (i.e. ftp sco). - enter Unix user name (i.e. smith). - enter user password (i.e.???). - binary to transfer in binary mode. - put <source filename> <full pathname of destination filename> put edi850.dat /edi850/edi850.dat - quit to exit ftp. - exit to return to windows. 4) A method of receiving edi files via the ftp process is by using the FTPRECV pgm to connect with your EDI partner or 3 rd party provider. FTPRECV performs the screen handling functions then calls program FTPRECVT to do the actual transfer. Another program to send edi files to your EDI partner or 3 rd party provider is FTPSEND. FTPSEND performs the screen handling functions then calls program FTPSENDT to do the actual transfer. The parameters for both programs are setup in a configuration file via the FTPCFGM program. Release NGS-7.00 EDI- 6

7 FTPCFGM- FTP CONFIGURAGTION MAINTENANCE Introduction File Transfer Protocol (FTP) is a standard network protocol used to transfer files from one host to another host over a TCP-based network, such as the Internet. FTP operates using client-server architecture and utilizes separate control and data connections between the client and server. The FTP Configuration Maintenance program (FTPCFGM) allows the user to pre-define both client and server ftp locations for the purpose of sending data through the FTPSEND programs and receiving data through the FTPRECV program. Procedure From the menu, enter "FTPCFGM": Menu Options available: Add Update Remove The ADD option is used to enter a new record. The UPDATE option is used to change an existing record(s). When this option is chosen the user is required to define which record(s) are to be selected for update. The user must enter the appropriate data by which to search the file and then click the OK button to allow the program to search the file for any record(s) meeting the entered search criteria OR click OK to select all customer records. The REMOVE option is used to delete an existing record(s). Query The QUERY option allows the user to display an existing record on the screen Release NGS-7.00 EDI- 7

8 with the ability to scroll forward or backward from record to record when more than one record is selected. When this option is chosen the user is required to define which record(s) are to be selected. The user must enter the appropriate data by which to search the file and then click the OK button to allow the program to search the file for any record(s) meeting the entered search criteria OR click OK to select all customer records. Help Run Exit Program For online help regarding menu options. The RUN option is used to temporarily exit the program allowing the user to run another program. Exit the program. Adding Records: From the menu, enter "FTPCFGM": Field Definitions: Program ID Host Address FTP User ID Enter the program that will be utilized in sending or receiving the data. For example: If sending a batch of invoices to a customer, use FTPSEND; if receiving a batch of orders from a customer use FTPRECV; if sending an edi purchase order directly to the vendor from the Purchase Order Entry program, use EDIPOG. A unique identifier that can identify the sending or receiving party for the Program specified. For example this could be used to define a 3 rd party EDI trading partner that this program will send data to or receive data from. When in the FTPSEND and FTPRECV program, a list of Programs and ID's that were entered here will be displayed requiring the user to select one from the list. REMOTE (FTP Server/Connect To) SETUP Enter the URL or the Network s TCP/IP Address for the remote server (where you are going to send files to and receive files from). Enter the User ID to log into the server. Release NGS-7.00 EDI- 8

9 FTP Password Enter the Password to log into the server. Receiving Directory Receiving File Sending Directory Sending File Enter the Directory on the remote server that ftp will write to when the user is executing the send function. Enter the File on the remote server that ftp will write to when the user is executing the sending function. This may be left blank if you are not sending a specific filename each time or the program will control the file sent. Enter the Directory on the remote server that ftp will read from when the user is executing the receiving function. Enter the File on the remote server that ftp will read from when the user is executing the receiving function. Sending Directory Sending File Receiving Directory Receiving File LOCAL (FTP Client/Connect From) SETUP Enter the Directory on the client or local server that ftp will read from when the user is executing the sending function. Enter the File on the client or local server that ftp will read from when the user is executing the sending function. This may be left blank if you are not sending a specific filename each time or the program will control the file sent. Enter the Directory on the client or local server that ftp will write to when the user is executing the receiving function. Enter the File on the client or local server that ftp will write to when the user is executing the receiving function. This may be left blank if you are not receiving a specific filename each time or the program will control the file sent. Release NGS-7.00 EDI- 9

10 FTPRECV- FTP DATA RECEIVING PROGRAM Introduction The FTP Data Receiving Program (FTPRECV) allows the user to receive data files from one server to another using FTP protocol. It is a method that can be used to receive EDI files from an EDI partner or third party provider. The calling program, FTPRECV, performs the screen handling functions then calls program FTPRECVT which performs the actual transfer functions. When the program is executed the user will be prompted for an External ID. These ID's must be set up ahead of time and are pre-defined in the FTP Configuration Program (FTPCFGM). Once you select the desired External ID, all fields are propagated from the matching external ID in the FTPCFGM program table. When ready, enter the word "PROCEED" and the program will begin transferring the data. Once the data is successfully transferred, the file is now available for the user to use in other applications, as an example, the EDI Interface Module. You can monitor or view a log of the activity done in this program by calling the PGC Trace Interface Activity program (PGCTM), selecting the desired option and entering ftprecvt in the program name field. Procedure From the menu, enter "FTPRECV": External ID - name of the 3 rd party provider you want to connect to, to receive data From Server IP address of the party you re connecting with From Directory the directory where the data is stored on the external party s system From File Name name of the file you are retrieving. Note: * will retrieve all files in the above directory. Our Directory the directory where the data will be placed on your system. Our File Name filename stored in the above directory. Blank or * will store as the same name of the file you are retrieving; which is probably what you want. PROCEED - enter PROCEED to continue with the ftp process. Release NGS-7.00 EDI- 10

11 FTPSEND- FTP DATA SENDING PROGRAM Introduction The FTP Data Sending Program (FTPSEND) allows the user to send data files from one server to another using FTP protocol. It is a method that can be used to send EDI files to an EDI partner or third party provider. The calling program, FTPSEND, performs the screen handling functions then calls program FTPSENDT which performs the actual transfer functions. When the program is executed the user will be prompted for an External ID. These ID's must be set up ahead of time and are pre-defined in the FTP Configuration Program (FTPCFGM). Once you select the desired External ID, all fields are propagated from the matching external ID in the FTPCFGM program table with the exception of the "Our Filename Field". At this prompt, the user can choose which file to send. This file must exist in the Directory that was established in the configuration program. When ready, enter the word "PROCEED" and the program will begin transferring the data. Once the data is successfully transferred, the file is now available to the EDI partner or third party provider to use in their applications. You can monitor or view a log of the activity done in this program by calling the PGC Trace Interface Activity program (PGCTM), selecting the desired option and entering ftpsendt in the program name field. Procedure From the menu, enter "FTPSEND": External ID - name of the 3 rd party provider you want to connect to, to send data. To Server IP address of the party you re connecting with. To Directory the directory where the data will be stored on the external party s system To File Name name of the file you are sending. Blank will store it as the same name. Our Directory the directory where the data is stored on your system. Our File Name filename that you are going to send. PROCEED - enter PROCEED to continue with the ftp process. Release NGS-7.00 EDI- 11

12 EDIPOG- EDI PURCHASE ORDER GENERATION Introduction The EDI Purchase Order Generation Program (EDIPOG) allows the user to create an ASCII file that contains purchase order information which can be sent electronically to a vendor or third party provider. After entering the selecting criteria for outgoing EDI purchase orders, the user will be presented with an options window. Under the sort option section, choose "By Trading Partner ID, Purchase Order Number". Under the Print Options section, choose "Only Lines Where Quantity Ordered is Present". Under the ASCII File Options, enter information about where the ASCII file will be created. Under the Proceed section choose the FTP option. At this point a list of valid FTP ID's will appear. These ID's must be set up ahead of time and are pre-defined in the FTP Configuration Program (FTPCFGM), with a program id of "EDIPOG". Procedure From the menu, enter "EDIPOG": Enter your selection criteria. Release NGS-7.00 EDI- 12

13 Enter Options and choose FTP under the Proceed sections: A valid list of valid FTP ID's will appear. These ID's must be set up ahead of time and are predefined in the FTP Configuration Program (FTPCFGM), with a program id of "EDIPOG". Release NGS-7.00 EDI- 13

14 MONITORING AND ALERTS PROGRAMS EDIPOLDQ- EDI CUSTOMER P.O. PROCESSING QUERY/ALERT PROGRAM Introduction The EDIPOLDQ program is a diagnostic program that will check whether or not transactions exist in the EDI Inbound Table which have not yet been updated including transactions which have not yet been validated, transactions in error and transactions which have been validated but not yet been converted to sales orders. If any transactions exist, an alert will be generated. Procedure From the menu, enter "EDIPOLDQ": If you desire to have this program run automatically, through the AUTOMATED ALERT SYSTEM, you need to make sure a record exists in the alerth table by using the ALERTM program (see documentation on AUTOMATED ALERT SYSTEM). There are two alerts both called edipoldq. Check For Failed Validation (All Transactions) and Check For Failed Validation (Most recent transactions). Parameter 1 field is set to ALERT for both, The difference is that one contains the word "last" in parameter 2, and one does not. These alerts monitor whether or not transactions exist in the EDI Inbound Table which have not yet been updated including transactions which have not yet been validated, transactions in error and transactions which have been validated but not yet been converted to sales orders. If any transactions exist, an alert will be generated. We recommend that two separate alerts be set up. One alert can be run every morning that checks ALL transactions and notifies the user of any issues. The other alert will have the Parameter 2 field set to the word "last". This tells the program to only check transactions going forward from the last time the alert was run. Release NGS-7.00 EDI- 14

15 SETUP AND MAINTENANCE PROGRAMS EDITPM- EDI TRADING PARTNER MAINTENANCE A. Program Summary. This program will allow the user to add, update, remove, query and view records in the Trading Partner Master table. The purpose of the table is to define customers for EDI processing. B. Program Detail. The following describes the logic for each menu option. B1. Add Menu Options Logic. trading partner id / mailbox number. This field will be unique and will be the key to the record. customer id and will validate that the customer is a valid customer and display the customer name to the right of the customer id. The drop down window will allow the operator to select the customer based on the customer id, customer name, and customer cross-reference or phone number. trading partner name. This field will default to the customer name. sold to validation method. The valid methods are defined below: 0 Use the customer id and prefix (when applicable) defined for the trading partner to determine the customer sold to id. 1 - Use SOLD TO ID sent in directly from the EDI transmission as the customer sold to id for the transaction. 2 Use the customer prefix defined for the trading partner and the SHIP TO ID sent in directly from the EDI transmission to determine the customer sold to id for the transaction. The sold to id will be selected based on the trading partner customer prefix matching the first characters of the customer id in the customer master and the ship to id existing in the ship to master for the customer. 3 - Use SOLD TO ID sent in directly from the EDI transmission and match it to the customer cross-reference field in the Customer table to determine the customer sold to id for the transaction. customer prefix (which will be used to access the proper customer records when multiple customer records are setup for the trading partner). For example, if trading partner ' ' has a main customer record of 'XXXX' setup in the system and all sold-to customer's for the trading partner begin with 'XXXX', the prefix would be set to 'XXXX'. When a transaction is validated, the system will use the 'XXXX' prefix before the bill to ID passed from the EDI ASCII file as the sold to id. If this feature is not required for the trading partner, leave the field blank. ship to validation method. The valid methods are defined below: method "1" - If the bslook field on the inbound transaction is set to 'BS', the system will validate that the EDI ship to id is a valid ship to id in the ship to table for the customer and use this as the validated ship to id. The ship to name and address on the order will be the ship to name and address in the ship to table. If the bslook field on the inbound transaction is not set to 'BS', the validated ship to ID will be set to 'X' (once the system determines that a ship to id of 'X' exists for the customer). The ship to name and address will be set to the EDI ship to name and address. This provides the ability to Release NGS-7.00 EDI- 15

16 define a generic ship to record for the customer for EDI transactions. method "2" - If the EDI bill to id is equal to the EDI ship to id, the validated ship to id will be set to 'SAME'.If the EDI bill to id is not equal to the EDI ship to id, the system will validate that the EDI ship to id is a valid ship to id in the ship to table for the customer and use this as the validated ship to id. The ship to name and address on the order will be the EDI ship to name and address. If all the EDI ship to name and address fields are blank, the system will use the ship to name and address in the ship to table. method "3" - If the Ship to Validation Method is set to a "3", the system will validate the shipto id from the EDI input file to the SHIPTO table in the standard system. The field that will be used for validation is the monitor_shipto field (program STM). This is a new option added for customers such as Walmart who use a global distribution code as their shipto identifier. customer id to be used to obtain the item retail price. The field will be validated to insure that the code entered is a valid customer in the system. The drop down window will allow the operator to select the customer based on the customer id, customer name, customer crossreference or phone number. If the field has a value, the system will calculate the retail price for the customer during the EDI validation and load the value into the table. If the field is blank, the system will leave the retail price as it is uploaded into the table. This field is solely used to be sent back to the trading partner on outbound documents. if the trading partner requires processing of sales orders through EDI. A 'Y' or 'N' value must be entered. advanced ship notices through EDI. A 'Y' or 'N' value must be entered. Note that only transactions which have been created through the EDI process, from an 850 document, are available for outbound transactions. if the trading partner requires processing of invoices through EDI. A 'Y' or 'N' value must be entered. Note that only transactions which have been created through the EDI process, from an 850 document, are available for outbound transactions. if the trading partner requires processing of order status transactions through EDI. A 'Y' or 'N' value must be entered. Note that this field is for future use. item lookup field method. The valid methods are defined below: 1 - Use EDI item id field to access the item id field in the Item Master Table. 2 - Use EDI item id field to access the item cross-reference field in the Item Master Table (UPC method). 3 - Use EDI item field to access the customer part id in the Customer/Item Cross-reference Table (cixref). 4 Use EDI item field to access the customer part id in the Contract Pricing Table for a valid contract for the customer id. 5 Use EDI item field to access the UPC/Interchange ID in the Item Interchange Table maintained by the UPCLOAD program. UPC lookup field method. The valid methods are defined below: 1 - Use EDI item id field to access the item id field in the Item Master Table. 2 - Use EDI item id field to access the item cross-reference field in the Item Master Table (UPC Release NGS-7.00 EDI- 16

17 method). 3 - Use EDI item field to access the customer part id in the Customer/Item Cross-reference Table (cixref). 4 Use EDI item field to access the customer part id in the Contract Pricing Table for a valid contract for the customer id. 5 Use EDI item field to access the UPC/Interchange ID in the Item Interchange Table maintained by the UPCLOAD program. customer part id lookup field method. The valid methods are defined below: 1 - Use EDI customer part id field to access the item id field in the Item Master Table. 2 - Use EDI customer part id field to access the item cross-reference field in the Item Master Table (UPC method). 3 - Use EDI customer part id field to access the customer part id in the Customer/Item Cross-reference Table (cixref). 4 Use EDI customer part id field to access the customer part id in the Contract Pricing Table for a valid contract for the customer id. 5 Use EDI customer part id field to access the UPC/Interchange ID in the Item Interchange Table maintained by the UPCLOAD program. shipvia lookup method. The purpose of this is to allow the EDI Inbound PO Processing program to do a validation of the Shipping Method provided by the trading partner and use it to determine the applicable ship via code for the transaction. Currently, the validation is done to the ship via code in the SVC program for option 0 and the EDISVM program for options 1 and 2. 0 Trading Partner will provide your Ship Via Code. 1 Trading Partner will provide their Ship Via Code. 2 Trading Partner will provide their Ship Via Code or will provide the Carrier and Shipping Method. customer part id combine method. The valid methods are defined below: 1 - Validate customer part id 1. If customer part id 1 fails validation, attempt to validate customer part id Combine the customer part id 1 and part id 2 fields with a dash (-) separating them and use this value for the customer part id validation. 3 - Combine the customer part id 1 and part id 2 fields with no separator and use this value for the customer part id validation. The program will then prompt for the customer part id lookup (which will be the customer id to utilize when accessing the Customer Part ID Cross-reference Table (cixref)). The field will be validated to insure that the code entered is a valid customer in the system. The drop down window will allow the operator to select the customer based on the customer id, customer name, Release NGS-7.00 EDI- 17

18 customer cross-reference or phone number. If the field is left blank, the system will use the sold to customer ID when accessing the Customer Part ID Cross-reference Table. Note that this feature is only applicable to the EDI upload and the trading partner customer part ID will not be utilized by any other programs in the system. sell price validation flag to indicate whether the selling price should be validated for the trading partner's transactions. The following are the valid values: Y Validate the selling price from the EDI transmission against the price calculated by the standard system. *Note* If you bring in a selling price of zero OR if the user overrides the selling price to zero, It will use the selling price calculated by the system. Logic behind this is if the Trading Partner sends in a zero price, they are accepting the price you calculated. N Do not perform the validation of the selling price. The selling price on the transaction will be the price calculated by the standard system. O - Do not perform the validation of the selling price. The selling price from the EDI or website transmission file will be the selling price used in the standard system. The price origin code will be set to a '1'. NOTE : Option 'O' means that the selling price from the EDI or website transmission file will be the selling price used in the standard system. C Validate the selling price from the EDI transmission against the contract pricing tables only. No other pricing methods (i.e. matrix pricing) will be utilized. E - The selling price from the EDI or website transmission file will be the selling price assigned to the sales order transaction. The price origin code will be set to a value of '1'. Unlike option 'O', the system will still calculate the normal selling price based on the standard system calculations in order to determine if it varies from the price on the EDI transaction. If the selling price calculated by the standard system is different than the selling price from the EDI transaction, an Audit Trail record will be generated when the order is created which will include both the selling price calculated by the system and the selling price assigned to the sales order transaction from the trading partner's EDI transaction. maximum normal order value. If this field is not zero, the system will validate that the total order value of the EDI transaction does not exceed this amount. unit of measure. This will be output to the Advanced Ship Notice. Leave the field blank if you want to output the sales order's unit of measure instead. packaging code. This will be output to the Advanced Ship Notice. the transaction type method for assigning transaction types to the trading partner's transactions. The valid methods are defined below: 0 Always assign transaction type "OR" to EDI transactions. 1 Use the TRANSACTION CODE sent in directly from the EDI transmission. Valid transaction codes are "OR" for orders and "RM" for return merchandise. 2 Use TRANSACTION CODE sent in directly from the EDI transmission. Valid transaction Release NGS-7.00 EDI- 18

19 code is "DS" which will be used for DROP SHIP orders and will create drop ship PO's in the system if acf parameters are setup to do so. duplicate purchase order validation method to use when verifying if a duplicate purchase order exists for the trading partner's transactions: 0 - Perform the duplicate purchase order validation based on the validated sold to id. If a duplicate purchase order exists for the sold to id, the validation will fail. 1 - Perform the duplicate purchase order validation based on the validated sold to id and the validated ship to id. If a duplicate purchase order exists for the sold to id AND the ship to id, the validation will fail. If a duplicate purchase order exists for the sold to id for a different ship to id, the validation will not fail. 2 -l*************important PLEASE READ BELOW************************ No checking is done for duplicate purchase order numbers. The user must be aware if this option is chosen that no validation of duplicate batches for this Trading Partner is being performed. UCC128 Label Format. A new field for the UCC128 Label Format. The field name is ucc128fmt_editp and is 10 characters. Enter the valid UCC128 Label format for the trading partner to define the label that will be produced. EDI Format. EDIPOLD-EDI Inbound Record Format Definition This option defines the format to utilize when processing the EDI Inbound records for this trading partner. If this field is left blank, the format for this trading partner will be based on the value specified in acf option edinfmt. Valid option values are blank,0,1,2 or Define transactions based on the trading partner id and the purchase order number. 1 - Define transactions based on the trading partner id, purchase order number and sold to for the EDI transaction. 2 - Define transactions based on the trading partner id, purchase order number and for assigning transaction invoice number (memoh23_edinh). 3 - Define transactions based on the trading partner id, purchase order number, sold to and ship to for the EDI transaction. (soldto must be in memod22_edind and shipto must be in memod23_edind). The following fields will be prompted on screen 2 of the maintenance program. These fields are utilized on the EDI Outbound Invoice ASCII File: remit to name. price basis code. allowance charge indicator. Release NGS-7.00 EDI- 19

20 allowance charge method. allowance charge definition. The following values will be accepted: 0 - No allowance charge applicable for trading partner. 1 - Allowance charge will be freight amount. 2 - Allowance charge will be handling amount. 3 - Allowance charge will be insurance amount. 4 - Allowance charge will be miscellaneous 1 amount. 5 - Allowance charge will be miscellaneous 2 amount. 6 - Allowance charge will be miscellaneous 3 amount. 7 - Allowance charge will be miscellaneous 4 amount. 8 - Allowance charge will be surcharge amount. 9 Allowance charge will be the trade discount amount. special charge definition. The following values will be accepted 0 - No special charge applicable for trading partner. 1 - Special charge will be freight amount. 2 - Special charge will be handling amount. 3 - Special charge will be insurance amount. 4 - Special charge will be miscellaneous 1 amount. 5 - Special charge will be miscellaneous 2 amount. 6 - Special charge will be miscellaneous 3 amount. 7 - Special charge will be miscellaneous 4 amount. 8 - Special charge will be surcharge amount. 9 Special charge will be the trade discount amount. total charge definition. The following values will be accepted: 0 - No total charge applicable for trading partner. 1 - Total charge will be based on the gross amount of transaction. 2 - Total charge will be based on the net amount of transaction. 3 - Total charge will be based on the gross amount - trade discount. 4 - Total charge will be based on the net amount - trade discount. total additional charge definition. The following values will be accepted. 0 - No additional amounts are applicable for trading partner. 1 - Add the insurance amount to the total amount. 2 - Add the handling amount to the total charge amount. 3 - Add the miscellaneous 1 amount to the total charge amount. 4 - Add the miscellaneous 2 amount to the total charge amount. 5 - Add the miscellaneous 3 amount to the total charge amount. 6 - Add the miscellaneous 4 amount to the total charge amount. 7 - Add the surcharge amount to the total charge amount. Release NGS-7.00 EDI- 20

21 The program will prompt for the invoice print flag. The following value will be accepted: Y - Yes to print invoices in addition to generating EDI invoice transactions. N - No to not print invoices in addition to generating EDI invoice transactions. 2 character Bill through EDI BILL generation field 2 character Invoice / Order # assignment from EDI Memo fields Document Types - control what type of ordsend records to create / update to for an order s address when sent via EDI. Map Address from EDI Field To Transaction Record. Provide the capability of generating or updating the order's address records based on a field recieved through EDI. Utilize New field: emldoccd_editp. Vendor ID - stores the vendor id for Florence Paper's UCC128 Label Program (UCCLG). The filed is vendorid_editp - 30 characters. 30 character memo 1 field. 30 character memo 2 field. 10 character memo 3 field. memo 4 field, which allows decimal numeric values. memo 5 date field. B2. Update Menu Options Logic. The program will allow selection based on any of the fields within the trading partner table. The system will provide the options for Update, Next record, Previous record, Help and Exit. When utilizing the update option, the system will prompt for each non-key field sequentially and allow the operator to override them. B2-A. Duplicate Menu Options Logic. The DUPLICATE option is used to duplicate the values in one trading partner record to another trading partner record. User will be required to input the Trading Partner ID and Customer ID fields for the new record being created. B3. Query Menu Options Logic. The program will allow selection based on any of the fields within the trading partner table. B4. Remove Menu Options Logic. The program will allow selection based on any of the fields within the trading partner table. When removing the trading partner record, the system will also delete any records in the EDI Manual Customer Table (Table name: editpmc; where partnrid_editpmc = partnrid_editp). B5. View Menu Options Logic. The program will allow selection based on any of the fields within the trading partner table. The program will allow you to sort by the trading partner id or the customer id with a different report format for each sort option and will allow the report to be output to screen, printer, or hold file. Release NGS-7.00 EDI- 21

22 C. Screen Layouts. C1. Maintenance Screen 1. C2. Maintenance Screen 2. Release NGS-7.00 EDI- 22

23 Release NGS-7.00 EDI- 23

24 C3. Maintenance Screen 3. Fields on this screen are for future-use. Release NGS-7.00 EDI- 24

25 C4. Maintenance Screen 4. Fields on this screen are for future-use. Release NGS-7.00 EDI- 25

26 C5. Maintenance Screen 5. Fields on this screen are for future-use. Release NGS-7.00 EDI- 26

27 C6. View Sort Options Screen. Release NGS-7.00 EDI- 27

28 File and Field Layouts D1. EDITP - EDI TRADING PARTNER MASTER FILE FIELDS NAME SIZE TYPE DESCRIPTION partnrid_editp 27 CHAR TRADING PARTNER ID / MAILBOX NUMBER. name_editp 27 CHAR TRADING PARTNER NAME. custid_editp 10 CHAR CUSTOMER ID. custprfx_editp 10 CHAR SOLD TO ID PREFIX. custpart_editp 10 CHAR CUSTOMER PART ID LOOKUP. orderflag_editp 2 CHAR PROCESS ORDERS. shipflag_editp 2 CHAR PROCESS ADVANCED SHIP NOTICES. invflag_editp 2 CHAR PROCESS INVOICES. statflag_editp 2 CHAR PROCESS STATUS. cashflag_editp 2 CHAR <FUTURE USE> chgbkflag_editp 2 CHAR <FUTURE USE> shipmeth_editp 2 CHAR SHIP TO VALIDATION METHOD. itemlook_editp 2 CHAR ITEM LOOKUP METHOD. upclook_editp 2 CHAR UPC LOOKUP METHOD. cpartlook_editp 2 CHAR CUSTOMER PART ID LOOKUP METHOD. cpartmeth_editp 2 CHAR CUSTOMER PART ID COMBINE METHOD. retailid_editp 10 CHAR RETAIL PRICE CUSTOMER ID. normalval_editp 0 DEC MAXIMUM NORMAL ORDER VALUE. package_editp 5 CHAR PACKAGE TYPE uom_editp 2 CHAR TRADING PARTNER UNIT OF MEASURE. remitto_editp 35 CHAR REMIT TO NAME pricebase_editp 2 CHAR PRICE BASIS CODE allowind_editp 1 CHAR ALLOWANCE CHARGE INDICATOR. allowmeth_editp 2 CHAR ALLOWANCE CHARGE METHOD. allowchg_editp 2 CHAR ALLOWANCE CHARGE DEFINITION. speclchg_editp 2 CHAR SPECIAL CHARGE DEFINITION. totalchg_editp 2 CHAR TOTAL CHARGE DEFINITION. totaladd_editp 2 CHAR TOTAL ADDITIONAL CHARGES DEFINITION. invprt_editp 2 CHAR INVOICE PRINT FLAG memo1_editp 30 CHAR MEMO 1 FIELD (ALPHA). memo2_editp 30 CHAR MEMO 2 FIELD (ALPHA). memo3_editp 10 CHAR MEMO 3 FIELD (ALPHA). memo4_editp 10 DEC MEMO 4 FIELD (NUMERIC). memo5_editp 4 DATE MEMO 5 FIELD (DATE). soldmeth_editp 2 CHAR SOLD TO VALIDATON METHOD. pricemeth_editp 2 CHAR VALIDATE SELLING PRICE FLAG. tranmeth_editp 2 CHAR TRANSACTION TYPE ASSIGNMENT METHOD. duplpometh_editp 2 CHAR DUPLICATE PO VALIDATION METHOD. contrsrt_editp 2 CHAR altstkmeth_editp 2 CHAR mis1_editp 10 CHAR mis2_editp 2 CHAR mis3_editp 2 CHAR mis4_editp 23 CHAR mis5_editp 10 CHAR edinfmt_editp 2 CHAR EDI Inbound Record Format Definition ucc128fmt_editp 2 CHAR edibilltp_editp 2 CHAR Invoice / Order # assignment from EDI Memo fields assignmeth_editp 2 CHAR Bill through EDI BILL generation field emldoccd_editp 30 CHAR what type of ordsend records to create / update vendorid_editp 30 CHAR svialook_editp 2 CHAR Release NGS-7.00 EDI- 28

29 Indexes: Unique index on partnrid_editp. Index on custid_editp, partnrid_editp. Release NGS-7.00 EDI- 29

30 D2. EDITP2 - EDI TRADING PARTNER MASTER TERTIARY FILE FIELDS NAME SIZE TYPE DESCRIPTION partnrid_editp2 27 CHAR Trading Partner ID. from_id_editp2 20 CHAR from_domain_editp2 30 CHAR po_host_editp2 60 CHAR po_page_editp2 80 CHAR po_port_editp2 4 INT po_logdir_editp2 16 CHAR podeploymt_editp2 30 CHAR poackmeth_editp2 1 CHAR auth_editp2 60 CHAR inv_host_editp2 60 CHAR inv_page_editp2 80 CHAR inv_port_editp2 4 INT inv_logdir_editp2 16 CHAR invdeploymt_editp2 30 CHAR admin1_editp2 10 CHAR admin2_editp2 10 CHAR admin3_editp2 10 CHAR admin4_editp2 10 CHAR svc_method_editp2 1 CHAR fob_method_editp2 1 CHAR brch_method_editp2 1 CHAR invreject_editp2 1 CHAR ftpid_editp2 10 CHAR memo01_editp2 30 CHAR memo02_editp2 30 CHAR memo03_editp2 30 CHAR memo04_editp2 30 CHAR memo05_editp2 10 CHAR memo06_editp2 10 CHAR memo07_editp2 10 CHAR memo08_editp2 10 CHAR memo09_editp2 50 CHAR memo10_editp2 50 CHAR memo11_editp2 50 CHAR memo12_editp2 50 CHAR memo13_editp2 2 CHAR memo14_editp2 2 CHAR memo15_editp2 2 CHAR memo16_editp2 2 CHAR memo17_editp2 10 DEC memo18_editp2 10 DEC memo19_editp2 10 DEC memo20_editp2 10 DEC memo21_editp2 10 DEC memo22_editp2 4 DATE memo23_editp2 4 DATE memo24_editp2 4 DATE memo25_editp2 4 DATE memo26_editp2 4 DATE Indexes: Unique index editp2_ix1 on editp2(partnrid_editp2); Release NGS-7.00 EDI- 30

31 EDITPVM- EDI TRADING PARTNER VENDOR MAINTENANCE. A. Program Summary. The program will allow the user to add, update, remove, query and view records in the Trading Partner Vendor Master Table. The purpose of this table is to define vendors, which will do EDI processing. B. Program Detail. The following describes the logic used to maintain records in the Trading Partner Vendor Master Table for each menu option. The screen display format is defined in section C. B1. Add Menu Options Logic. - The program will prompt for the division id. A valid division must be entered. A drop down window option is provided to select the division by the division id or division name. - The program will prompt for the department id. A valid department must be entered. A drop down window option is provided to select the department by the department id or department name. An entry of the constant "ALL" is permissible in this field. - The program will prompt for the branch id. A valid branch must be entered. A drop down window option is provided to select the branch by the branch id or branch name. An entry of the constant "ALL" is permissible in this field. - The program will prompt for the entry of the corresponding vendor id and will validate that the vendor is a valid vendor and display the vendor name to the right of the vendor id. A drop down window option is provided to select the vendor by vendor id, vendor name, vendor cross-reference, vendor city and vendor state. The vendor id, along with the division id, department id and branch id, is the unique "key" to the record. - The program will prompt for the trading partner id / mailbox number. - The program will prompt for the entry of the trading partner name. This field will default to the vendor name. - The program will then prompt for the bill to code and id. The bill to code is the identifier code for the bill to which should be transmitted to the trading partner. The bill to id is the bill to id that the trading partner identifies you by. - The program will then prompt for the sold to id. This is the sold to id that the trading partner identifies you by. - The program will then prompt for the ship to code and id. The ship to code is the identifier code for the ship to which should be transmitted to the trading partner. The ship to id is the ship to id that the trading partner identifies you by. - The program will prompt whether the trading partner processes purchase order (850) EDI documents. A "Y" or "N" must be entered at this prompt. The field will default to "N". - The program will then prompt for the PO print flag. If you want the purchase order to be available to print for the EDI transaction after the EDI PO ASCII File has been generated, set the field to "Y". If you do not want the purchase order to be available to print after the EDI PO ASCII file has been generated, set the field to "N". A "Y" or "N" must be entered at this prompt. The field will default to "Y". Please note that the purchase order will always be available to print prior to the EDI PO ASCII File generation. Release NGS-7.00 EDI- 31

32 - The program will then prompt for the output date format. - An entry of "1" indicates that all dates sent to the trading partner will be output in "YYMMDD" format. - An entry of "2" indicates that all dates sent to the trading partner will be output in "MMDDYY" format. The field will default to "1" and no other values will be accepted. - The program will prompt for the output ship to state format. - An entry of "1" indicates that the ship to state field on the purchase order will be truncated to 2 positions; only the first 2 characters will included in the EDI ASCII file generated. - An entry of "2" indicates that the entire 4 character state should be included in the EDI ASCII file generated. The field will default to "1"; no other values will be accepted. - The program will prompt for the output ship to zip code format. - An entry of "1" indicates that the ship to zip code field on the purchase order will be truncated to 5 positions; only the first 5 characters will be included in the EDI ASCII file generated. - An entry of "2" indicates that the field will be truncated to 9 positions; only the first 9 characters will be included in the EDI ASCII file generated. - An entry of "3" indicates that the full 10 character field will be included in the EDI ASCII file generated. The field will default to "1"; no other values will be accepted. - The program will prompt for the PO transaction code. This is the transaction set purpose for the document and will default to "00". - The program will prompt for the PO transaction type. This is the purchase order type for the document and will default to "NE". - The program will then prompt for the PO unit of measure method. If set to "0", the system will always send the primary or alternate unit of measure on the po line, based on the quantity ordered. If there is no alternate quantity ordered, the system will use the quantity ordered and the primary unit of measure. If there is an alternate unit of measure quantity, the system will convert the quantity ordered plus the alternate quantity ordered to the alternate unit of measure and use the alternate unit of measure. This method assumes that your unit of measure codes will always match the trading partners. If the method is set to "1", the system will always use the default unit of measure entered in the next field (trading partner PO default unit of measure). This assumes that you are always utilizing a single unit of measure with the trading partner and that this is the primary unit of measure in the item table. If the method is set to "2", the system will first attempt to convert the unit of measure for the po line (primary or alternate, based on the logic defined for method zero) to the trading partner unit of measure xref file (ediuom). If a record does not exist for the trading partner & item id & unit of measure code and a default unit of measure exists in the next field, the system will use the trading partner default unit of measure. If a record does not exist for the trading partner & item id & unit of measure and there is no default unit of measure defined for the trading partner, the system will use the unit of measure in the purchase order detail table. - The program will then prompt for the PO trading partner default unit of measure. If you are only dealing in a single unit of measure with the trading partner, their unit of measure code may be entered here (i.e. EA). - The program will then prompt for the 2 character PO weight basis code. This field is information only at this time.

33 - The program will then prompt for the 2 character PO volume basis code. This field is information only at this time. - The program will then prompt for the 2 character EDI Payment Handling Code - The program will then prompt for the 3 character Payment Reference Identification - The program will then prompt for a FTP ID field that contains the EDI partner you will be sending the data to. - The program will then prompt for the information only memo fields. Once all the fields are entered, the system will generate a record in the EDI Vendor Trading Partner Master Table (table name: editpv). If a record does not already exist for the trading partner in the EDI Trading Partner Master Table (table name: editp), a record will be generated in the EDI Trading Partner Master Table (editp) based on the mapping detailed in section D2. This will allow vendor trading partners to access the EDI cross-reference tables for ship via, terms and unit of measure codes. Note that the Trading Partner Maintenance program (editpm) has been changed to exclude records from being accessed in any option (including view) if the customer id (field name: custid_editp) is set to the value "VENDORID". B2. Update Menu Options Logic. - The program will allow selection based on any of the trading partner vendor fields on the screen. - The system will provide the options for Update record, Next record, Previous record, Help and Exit. - When utilizing the update option, the system will prompt for each field sequentially. B3. Query Menu Options Logic. - The program will allow selection based on any of the trading partner vendor fields on the screen. - The system will provide the options for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. - The program will allow selection based on any of the trading partner vendor fields on the screen. - The system will provide the options for Remove record, Next record, Previous record, Help and Exit. B5. View Menu Options Logic. - The program will allow selection based on any of the trading partner vendor fields on the screen. - The program will allow you to sort the report by the trading partner id or the vendor id. - The program will allow the report to be output to the screen, printer or hold file. The view screen format is defined in section C. Release NGS-7.00 EDI- 33

34 C. Screen Layouts. C1. Maintenance Screen. C2. View Sort Options Screen. Release NGS-7.00 EDI- 34

35 File and Field Layouts D1. EDITPV - EDI TRADING PARTNER VENDOR MASTER FILEFIELD NAME SIZE TYPE DESCRIPTION division_editpv 4 CHAR DIVISION ID. dept_editpv 5 CHAR DEPARTMENT ID. branch_editpv 8 CHAR BRANCH ID. vendor_editpv 10 CHAR VENDOR ID. partnrid_editpv 27 CHAR TRADING PARTNER ID / MAILBOX NUMBER. name_editpv 27 CHAR TRADING PARTNER NAME. poflag_editpv 2 CHAR PROCESS PURCHASE ORDERS (850) (Y/N). asnflag_editpv 2 CHAR PROCESS ADVANCED SHIP NOTICES (856). *FUTURE USE* (DEFAULT TO "N"). invflag_editpv 2 CHAR PROCESS INVOICES. *FUTURE USE* (DEFAULT TO "N"). billto_editpv 35 CHAR BILL TO ID. soldto_editpv 35 CHAR SOLD TO ID. shipto_editpv 35 CHAR SHIP TO ID. btlook_editpv 2 CHAR BILL TO LOOKUP CODE. bslook_editpv 2 CHAR SHIP TO LOOKUP CODE. potrancd_editpv 2 CHAR PO TRANSACTION CODE. potrantyp_editpv 2 CHAR PO TRANSACTION TYPE. poprtflag_editpv 2 CHAR PO PRINT FLAG. (Y/N). dateform_editpv 2 CHAR DATE FORMAT: 1 = YYMMDD. 2 = MMDDYY. stateform_editpv 2 CHAR SHIP TO STATE FORMAT: 1 = 2 CHARACTERS (TRUNCATED). 2 = 4 CHARACTERS (NON-TRUNCATED). zipform_editpv 2 CHAR SHIP TO ZIP CODE FORMAT. 1 = 5 CHARACTERS (TRUNCATED). 2 = 9 CHARACTERS (TRUNCATED). 3 = 10 CHARACTERS (NON-TRUNCATED). pouommeth_editpv 2 CHAR UNIT OF MEASURE METHOD. 0 = USE PO PRIMARY/ALTERNATE UNIT OF MEAS. 1 = USE TRADING PARTNER DEFAULT UNIT/MEAS 2 = USE EDI UNIT OF MEASURE Cross-reference. pouom_editpv 2 CHAR DEFAULT UNIT OF MEASURE CODE. powgt_editpv 2 CHAR PO WEIGHT UNIT BASIS. *FUTURE USE* povol_editpv 2 CHAR PO VOLUME UNIT BASIS. *FUTURE USE* memo1_editpv 30 CHAR MEMO 1 FIELD (ALPHA). memo2_editpv 30 CHAR MEMO 2 FIELD (ALPHA). memo3_editpv 10 CHAR MEMO 3 FIELD (ALPHA). memo4_editpv 10 DEC MEMO 4 FIELD (NUMERIC). memo5_editpv 4 DATE MEMO 5 FIELD (DATE). payflag_editpv 2 CHAR EDI PAYMENT HANDLING CODE payreftyp_editpv 3 CHAR EDI REFERENCE IDENTIFICATION TYPE ftpid_editpv 8 CHAR FTP partner (must match ID in FTPCFGM record Indexes Required: Indexing is required based on division id, department id, branch id and vendor id (unique) and based on partner id. Release NGS-7.00 EDI- 35

36 EDISVM- EDI TRADING PARTNER SHIP VIA MASTER TABLE MAINT. A. Program Summary. The program will allow the user to add, update, remove, query and view records in the EDI Trading Partner Ship Via Master Table. This table is used to provide information on EDI outbound transactions. B. Program Detail. The following describes the logic used to maintain records in the EDI Trading Partner Ship Via Master table for each menu option. The screen display formats are defined in section C. B1. Add Menu Options Logic. - The program will prompt for the following fields: - trading partner id and will validate that the trading partner is a valid trading partner in the trading partner table (partnrid_editp). The trading partner name will be displayed. The drop down window option will allow selection by the trading partner id and the trading partner name fields. - ship via code and will validate that the ship via code is a valid ship via code in the hip via table (svcode_shipvia). The ship via description (svdesc_shipvia) will be displayed. The drop down window option will allow selection by the ship via code and ship via description. - partner ship code - is used when the EDI Trading Partner is defined to provide THEIR shipping code in the Shipping Method field on the Inbound Customer Purchase Order transaction rather than the actual Ship Via Code. The EDI Inbound PO Processing program will validate the Shipping Method provided by the trading partner and to determine the corresponding Ship Via Code to assign to the transaction. - 2 character routing code. - 4 character SCAC code. - 2 character transportation method code character carrier name. - 2 character shipping reference qualifier character default tracking number. - 5 characters special services code. - 2 character ship method of payment. - 2 character shipping mode code. - alphanumeric memo 1 field. - alphanumeric memo 2 field. - alphanumeric memo 3 field. - numeric memo 4 field. - date memo 5 field. Once all the fields are entered, the system will generate a record in the EDI Trading Partner Ship Via Master Table (table name: edisv). Release NGS-7.00 EDI- 36

37 B2. Update Menu Options Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Ship Via Master table. - The system will provide the options for Update, Next record, Previous record, Help and Exit. - When utilizing the update option, the system will prompt for each field sequentially. B3. Query Menu Options Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Ship Via Master table. - The system will provide the options for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Ship Via Master table. - The system will provide the options for Remove, Next record, Previous record, Help and Exit. B5. View Menu Options Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Ship Via Master table. - The program will allow sort options by trading partner id or ship via code. - The program will allow the report to be output to the screen, printer, hold file, or exit. The view screen format is defined in section C. B6. Count Menu OptionsLogic. - The program will allow selection based on any of the fields within the EDI Trading Partner Ship Via Master table. - The program will display the number of records in the EDI Trading Partner Ship Via Master Table that meet the search criteria entered. B7. Duplicate Menu Option. - When the duplicate option is selected, the system will display the trading partner source duplication entry criteria window. The operator may enter selection criteria for the trading partner id, trading partner name and customer id for the trading partner being duplicated from. The system will select records based on the respective fields in the trading partner table (partnrid_editp, name_editp, custid_editp). Applicable records which meet the selection criteria will be displayed. The operator will have the option of accepting the current record on the screen, viewing the next record, viewing the previous record or exiting the duplication process. - Once a source trading partner has been accepted, the system will display the trading partner destination duplication window. The operator may enter selection criteria for the trading partner id, trading partner name and customer id for the trading partner being duplicated to. The system will select records based on the respective fields in the trading partner table (partnrid_editp, name_editp, custid_editp). Applicable records which meet the selection criteria will be displayed. The operator will have the option of accepting the current record on the screen, viewing the next record, viewing the previous record or exiting the duplicate process. - Once a destination trading partner has been accepted, the system will require the operator to verify that they want to duplicate the information from the source trading partner EDI Trading Partner Ship Via records to the destination trading partner EDI Trading Partner Ship Via records. Release NGS-7.00 EDI- 37

38 - The system will then delete all EDI Ship Via records for the destination trading partner. The system will then select all EDI Ship Via records for the source trading partner (based on the partner id in the EDI ship via table (partnrid_edisv)), and insert records in the table for the trading partner being duplicated to. All fields in each destination will match the fields in the source record with the exception of the trading partner id. Once the process is completed, the system will display the completion message at the bottom of the screen and, once the operator enters a character, the program will return to the menu option selection. Release NGS-7.00 EDI- 38

39 C. Screen Layouts. C1. Maintenance Screen. C2. View Sort Options Screen. Release NGS-7.00 EDI- 39

40 C3. Duplicate Menu Option Window - Source Trading Partner Entry. C4. Duplicate Menu Option Window - Destination Trading Partner Entry. Release NGS-7.00 EDI- 40

41 D. File and Field Layouts D1. EDISV - EDI TRADING PARTNER SHIP VIA MASTER TABLE. FIELD NAME SIZE TYPE DESCRIPTION partnrid_edisv 27 CHAR TRADING PARTNER ID. svcode_edisv 4 CHAR SHIP VIA CODE. routing_edisv 2 CHAR ROUTING CODE. scac_edisv 4 CHAR SCAC CODE. trmethod_edisv 2 CHAR TRANSPORTATION METHOD. pymethod_edisv 2 CHAR SHIPMENT METHOD OF PAYMENT. carrier_edisv 35 CHAR CARRIER DESCRIPTION. shipqual_edisv 2 CHAR SHIPPING QUALIFIER. trackno_edisv 30 CHAR DEFAULT TRACKING NUMBER. spclsrv_edisv 5 CHAR SPECIAL SERVICES CODE. memo1_edisv 30 CHAR MEMO 1. memo2_edisv 30 CHAR MEMO 2. memo3_edisv 10 CHAR MEMO 3. memo4_edisv 10 DEC MEMO 4. memo5_edisv 4 DATE MEMO 5. tpsvcode_edisv 4 CHAR TRADING PARTNER SHIP VIA CODE Indexes Required: partnrid_edisv, svcode_edisv. E. View Report Fields Utilized. Detail Line 1: partnrid_edisv svcode_edisv carrier_edisv scac_edisv trmethod_edisv spclsrv_edisv Detail Line 2: name_editp (based on partnrid_editp = partnrid_edisv). svdesc_shipvia (based on svcode_shipvia = svcode_edisv). trackno_edisv routing_edisv shipqual_edisv pymethod_edisv Detail Line 3: memo1_edisv Detail Line 4: memo2_edisv Detail Line 5: memo3_edisv Detail Line 6: memo4_edisv Detail Line 7: memo5_edisv Release NGS-7.00 EDI- 41

42 EDITERM- EDI TRADING PARTNER TERMS MASTER TABLE MAINT. A. Program Summary. The program will allow the user to add, update, remove, query and view records in the EDI Trading Partner Terms Master table. This table is used to provide information on EDI outbound transactions. B. Program Detail. The following describes the logic used to maintain records in the EDI Trading Partner Terms Master table for each menu option. The screen display format is defined in section C. B1. Add Menu Options Logic - The program will prompt for the following fields: - trading partner id and will validate that the trading partner is a valid trading partner in the EDI Trading Partner Table (partnrid_editp). The trading partner name (name_editp) will be displayed. The drop down window option will allow selection by the trading partner id and trading partner name fields. - terms code and will validate that the terms code is a valid terms code in the standard terms table (code_terms). The terms description (desc_terms) will be displayed. The drop down window option will allow selection by the terms code and terms description. - 2 character terms type code. - 2 character terms date basis code. - alphanumeric memo 1 field. - alphanumeric memo 2 field. - alphanumeric memo 3 field. - numeric memo 4 field. - date memo 5 field. Once all the fields are entered, the system will generate a record in the EDI Trading Partner Terms Master Table (table name: editerm). B2. Update Menu Options Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Terms table. - The system will provide the options for Update, Next record, Previous record, Help and Exit. - When utilizing the update option, the system will prompt for each field sequentially. B3. Query Menu Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Terms table. - The system will provide the options for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Terms table. - The system will provide the options for Remove, Next record, Previous record, Help and Exit. Release NGS-7.00 EDI- 42

43 B5. View Menu Options Logic. - The program will allow selection based on any of the fields within the EDI Trading Partner Terms table. - The program will allow you to sort the report by the trading partner id or the terms code. - The program will allow the report to be output to the screen, printer or hold file. The view screen format is defined in section C. C. Screen Layouts. C1. Maintenance Screen. Release NGS-7.00 EDI- 43

44 C2. View Sort Options Screen. D. File and Field Layouts D1. EDITERM - EDI TRADING PARTNER TERMS TABLE. FIELD NAME SIZE TYPE DESCRIPTION partnrid_editerm 27 CHAR TRADING PARTNER ID terms_cd_editerm 4 CHAR TERMS CODE termtype_editerm 2 CHAR TERMS TYPE CODE. termbase_editerm 2 CHAR TERMS DATE BASIS CODE. memo1_editerm 30 CHAR MEMO 1. memo2_editerm 30 CHAR MEMO 2. memo3_editerm 10 CHAR MEMO 3. memo4_editerm 10 DEC MEMO 4 memo5_editerm 4 DATE MEMO 5. Indexes Required: partnrid_editerm, terms_cd_editerm. E. View Report Fields Utilized. Detail Line 1: Detail Line 2: Detail Line 3: Detail Line 4: Detail Line 5: partnrid_editerm. terms_cd_editerm. termtype_editerm. termbase_editerm. memo1_editerm. name_editp (based on partnrid_editp = partnrid_editerm). desc_terms (based on code_terms = terms_cd_editerm). memo2_editerm. memo3_editerm. memo4_editerm. memo5_editerm. Release NGS-7.00 EDI- 44

45 EDIUOM- EDI TRADING PARTNER U.O.M. XREF TABLE MAINT. A. Program Summary. The program will allow the user to add, update, remove, query and view records in the EDI Trading Partner Unit of Measure Cross-Reference Table. The purpose is to provide a table to allow a cross-reference from a trading partner unit of measure codes for items to the Item Master unit of measure and alternate unit of measure code for EDI Validation purposes. All trading partner items that will have a unit of measure on incoming or outgoing EDI transactions that differs from the primary or alternate unit of measure in the Item table must be setup here for the validation to be successful. The trading partner unit of measure must correspond to either the primary or alternate unit of measure in the item table. B. Program Detail. The maintenance program will allow add, update, remove, query, view, help and exit options. See Section D for the screen display formats. B1. Add Menu Options Logic - The program will prompt for the trading partner id and allow drop down window to access the trading partner table. Selection is provided by trading partner id and trading partner name. Once a valid trading partner id is entered or selected, the system will display the trading partner name. - The program will then prompt for the item id and allow drop down window access to the item table. Selection is provided by item id, item cross-reference, item description 1, item description 2, product group, commodity, item memo 1, item memo 2, item memo 3, item memo 4, item sales analysis category 1, item sales analysis category 2, item sales analysis category 3 and item sales analysis category 4. Once a valid item id is entered or selected, the system will display the item description 1 field, unit of measure code, alternate unit of measure code and the alternate to stock conversion factor. - The program will then prompt for the trading partner's unit of measure code. Up to 2 characters of text may be entered. The system will do no verification of the unit of measure entered other than to verify that the field is not blank or <NULL>. - The program will then prompt for the unit of measure code. The entry will be verified to insure that the unit of measure code matches either the item's unit of measure or alternate unit of measure (uom_item, alteruom_item). Once all the fields are entered, the system will generate a record in the EDI Trading Partner Unit Of Measure Cross-Reference Table (table name: ediuom). B2. Update Menu Options Logic. - Record selection will be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - The program will allow you to modify the item unit of measure code only (since the "key" to the file is trading partner, item and partner unit of measure code). The entry will be verified to insure that the unit of measure code matches either the item's unit of measure or alternate unit of measure (uom_item, alteruom_item). - The system will provide the options for Update, Next record, Previous record, Help and Exit. B3. Query Menu Options Logic. - Record selection will be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - The system will provide the options for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. Release NGS-7.00 EDI- 45

46 - Record selection will be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - The system will provide the options for Remove, Next record, Previous record, Help and Exit. B5. View Menu Options Logic. - Record selection will be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - Report sort options will be provided by trading partner id or item id. - The program will prompt whether you want to output to the screen, printer or hold file. The view screen format is defined in section C. Release NGS-7.00 EDI- 46

47 C. Screen Layouts. C1. Maintenance Screen. C2. View Sort Options Screen. Release NGS-7.00 EDI- 47

48 D. File and Field Layouts D1. EDIUOM - EDI TRADING PARTNER UNIT OF MEASURE CROSS-REFERENCE TABLE. FIELD NAME SIZE TYPE DESCRIPTION partnrid_ediuom 27 CHAR TRADING PARTNER ID. itemid_ediuom 18 CHAR ITEM ID custuom_ediuom 2 CHAR PARTNER UNIT OF MEASURE CODE uom_ediuom 2 CHAR UNIT OF MEASURE CODE. memo1_ediuom 30 CHAR MEMO 1 memo2_ediuom 30 CHAR MEMO 2 memo3_ediuom 10 CHAR MEMO 3 memo4_ediuom 10 DEC MEMO 4 memo5_ediuom 4 DATE MEMO 5 Create unique index on partnerid_ediuom, itemid_ediuom, custuom_ediuom. E. View Report Fields Utilized. Line Position Field Conditions partnerid_ediuom itemid_ediuom custuom_ediuom uom_ediuom name_editpm Based on partner id desc1_item Based on item id. F. Fields To Display On Main Screen: Line Position Field Name partnerid_ediuom (validated from editpm) name_editp (where partnrid_editp = partnerid_ediuom) itemid_ediuom (validated from item) desc1_item (where id_item = itemid_ediuom) desc2_item (where id_item = itemid_ediuom) uom_item (where id_item = itemid_ediuom) alteruom_item (where id_item = itemid_ediuom) altstkcnv_item (where id_item = itemid_ediuom) custuom_ediuom uom_ediuom (validated from item where id_item = itemid_ediuom where uom_ediuom = uom_item or uom_ediuom = alteruom_item). Release NGS-7.00 EDI- 48

49 PROCESSING INBOUND TRANSACTIONS EDIPOLD- EDI PURCHASE ORDER UPLOAD PROGRAM. PROGRAM OVERVIEW This program provides the ability to upload, validate, maintain, view, generate customer orders and purge information uploaded from ASCII files. ASCII is a standard that allows ASCII-only plain text files (unlike most other file types) to be freely interchanged and readable on Unix, Macintosh, Microsoft Windows, DOS, and other systems. These files contain only ordinary textual characters with essentially no formatting or no control characters. The ASCII files that are used as input to this interface can only be in one of four formats. (1) They can be generated on a PC from a third party "mapper" product for the EDI purchase order transaction set (850) and moved to the UNIX system with a utility such as FTP. (2) They can also be generated through text editor products like WORD, Notepad, WordPad these also need to be moved from the PC to the UNIX system. (3) They can be generated through EXCEL spreadsheets. (4) They can be generated as an XML file. The differences are: (1) Method 1: If you are importing the 850 tranaction from a third party product, the ASCII file must be mapped to the Next Generation file format, the ASCII file must be a fixed length (139 fields) delineated with a pipe sign ( ). Every field has to be accounted for, which means if no data is available for one of the fields, you would have to put pipe signs together to accommodate for the missing data. The ASCII file is imported from a PC to the UNIX System. An Example of this input file would be: DROP T009 ROBERT SMITH 566 Garden Pkwy. CLIFTON NJ US T009 ACR DROP T009 ROBERT SMITH 555 Garden Pkwy. CLIFTON NJ US T009 ACR Note: Each field has to be accounted for and must map to the precise field that is definend in the Inbound ASCII file layout described at the end of this chapter. (2) Method 2: If you are importing the transaction from an ASCII file you created, you need to supply the header (i.e. the name of the column) in the first row, followed by a pipe sign ( ) or comma (,). The pipe sign or comma must be included between each field in every row. With this method, you do not need to supply all 139 fields that are available, but you do need to supply the minimum information required. The ASCII file is imported from a PC to the UNIX System. (See below for minimum fields requirement.) An Example of this input file would be: partnrid_edinh shipto_edinh cust_po_edinh podate_edinh sellitem_edind orgprice_edind qtyord_edind PO /23/ PO /23/ PO /23/ PO /23/ PO /23/ Note: It does not matter what order the columns are in but the column names must be in the first line and be identical to the field name in the edihn and edind tables on the Next Generation System. (3) Method 3: If you are importing from an EXCEL spreadsheet, the data on the spreadsheet that is Release NGS-7.00 EDI- 49

50 going to be used as input to this module must have each of the fields in a separate column on the spreadsheet (i.e. the partner id in one column, the ship-to id in another, the customer purchase order in another, the item id, the quantity, etc). The field names, which are defined in the edinh and edind tables, of the columns that are to be uploaded must be listed across the first row of the spreadsheet (i.e. partnrid_edinh, shipto_edinh, cust_po_edinh, podate_edinh, sellitem_edind, orgprice_edind, qtyord_edind). These field names must correspond to the data that is in the column. Once this is defined, the import function will handle the rest. (See below for minimum fields requirement.) When loading data from a spreadsheet, if field names are supplied, the following checks will occur. Special Characters such as the single quote or a slash cannot exist in the trading partner id and the customer po number. If the transaction date is blank, set it to the system date If the required date is blank set it to the transaction date + the value in ACF option OE022. If the ship to id is not loaded from Excel, set the ship to id to the customer's default ship to id. If the EDI transaction type is blank, set it to "00" If the ship date is blank, set it to the default date of 01/01/1980 If the cancel date is blank, set it to the default date of 01/01/1980 Provided the capability of allowing the system to accept the selling price "as is" based on a new selling price override flag. If the user sets the selling price override flag to "Y", the system will accept the selling price on the EDI transaction regardless of whether it passes or fails the price validation routine. In this manner, if a trading partner provides a selling price that does not match the system's calculated price, the user can use that selling price for that transaction. This also gives the user the capability of manually overriding the selling price on the EDI transaction and using this manual price when the sales order is created. An Example of what the EXCEL file would be: partnrid_edinh shipto_edinh cust_po_edinh podate_edinh sellitem_edind orgprice_edind qtyord_edind PO /23/ PO /23/ PO /23/ PO /23/ PO /23/ Note: It does not matter what order the columns are in but the column names must be in the first line and be identical to the field name in the edihn and edind tables on the Next Generation System. Release NGS-7.00 EDI- 50

51 (4) Method 4: If you are importing from an XML file, the field names are embedded within the transmitted file followed by the data. For example, the city below is coded as <city> Cedar Knolls, an item number and quantity would come in as; <itemnumber> abc95497 <qty>100. An Example of what an XML file would be: <?xml version="1.0" encoding="utf-8"?> - <dbiresponse>- <purchaseorder>- <vendor> <vendorid>8</vendorid> <vendorname>test VENDOR</vendorname> </vendor> <ponumber>b419572</ponumber> <isdropship>0</isdropship> - <terms> <termid>127</termid> <description>10% 45</description> </terms> <dateordered>9/23/2007 5:14:34 PM</dateordered> <comments /> - <shipto> <name>munics INFO SYSTEMS</name> <shiptoid>2</shiptoid> <addr1>2 Ridgedale Ave</addr1> <addr2 /> <city>cedar Knolls</city> <state>nj</state> <zip>07927</zip> <phone> </phone> </shipto>- <billto> <billtoid>2</billtoid> <name>munics INFO SYSTEMS</name> <addr1>2 Ridgedale Ave</addr1> <addr2 /> <city>cedar Knolls</city> <state>nj</state> <zip>07927</zip> <phone> </phone> </billto>- <poitems>- <poitem> <linenumber>1</linenumber> <iscancelled>0</iscancelled> <cancelifbackorder>0</cancelifbackorder> <upc> </upc> <itemnumber>abc95497</itemnumber> <custprice>21.10</custprice> <qty>4</qty> </poitem>- <poitem> <linenumber>10</linenumber> <iscancelled>0</iscancelled> <cancelifbackorder>0</cancelifbackorder> <upc> </upc> <itemnumber>bhj23742</itemnumber> <custprice>5.27</custprice> <qty>12</qty> </poitem>- <poitem> <linenumber>11</linenumber> <iscancelled>0</iscancelled> <cancelifbackorder>0</cancelifbackorder> <upc> </upc> <itemnumber>llk2964</itemnumber> <custprice>101.32</custprice> <qty>7</qty> </poitem> </poitems> </purchaseorder> </dbiresponse> The minimum required fields for Option 2 and 3 above are: HEADER FIELDS Field Name: Notes: Trading Partner ID (partnrid_edinh) Required Bill to ID (billto_edinh) Required Except if Soldto on EDITPM is used. Ship-to ID (shipto_edinh) Required unless the Ship-to on customer ID is used. If Ship-to matches with the Sold -to ID, "SAME" will be assigned. Customer PO (cust_po_edinh) Required Number PO Date (podate_edinh) Required (ACF Option EDINDAY checks if date is over option value days from system date. If older the program will show error message. Required Date (reqdate_edinh) Required if not uploaded or if the default is blank the field is set by adding the number of days in ACF option OE022 to the system date. Ship Via Code (memo20_edinh) Required if blank the program will default to the shipvia code on the customer's record. For a list of other Header Fields that are available see table edinh. DETAIL FIELDS Field Name: Notes: Our Item ID (itemid_edind) Required Except if Customer Part ID (custpart1_edind, custpart2_edind) or UPC ID (upc_edind) is provided and Release NGS-7.00 EDI- 51

52 appropriate cross references have been set up on the Next Generation system. Customer Price (orgprice_edind) Required (with or without $ character) Except if option is set to use price generated by order entry or if our price (sell price_edind) is uploaded. Quantity Ordered (qtyord_edind) Required This must be in the stocking unit of measure else additional set up may be required (program EDIUOM sets up stocking, alternate UOM and conversion factor.) For a list of other Detail Fields that are available see table edind. B1 - UPLOAD/IMPORT ASCII/EXCEL FILE OPTION The following describes the logic used to process inbound transactions (i.e. EDI Purchase Order (850), EXCEL and other ASCII files) for each menu option. The Upload/Import ASCII/Excel File option provides the ability of uploading an ASCII file, generated in one of the standard ASCII file formats, into the EDI subsystem. Determine what type of ASCII input file you are working with, i.e. the 850 ASCII File format, or the EXCEL file. If you are importing an Excel file using method 3 above, use the From PC box. If you are importing the ASCII file that was imported to the Unix Server, use the From Main System box. Release NGS-7.00 EDI- 52

53 STEP 1 STEP 2 STEP 3 STEP 4 STEP 5 STEP 6 If you are importing an Excel file using Method 3 above, use the From PC box to choose where the input file is located on the PC by selecting the folder Icon then proceed to STEP 4. If you are importing the ASCII file in an 850 format or the shortened ASCII file, use the From Main System box to enter a valid starting directory where ASCII files on the UNIX server are located and where the log files will be output to (defaults to the value in the ACF "EDINDIR*" option series). Within this directory, 2 subdirectories, 1 named "data" and 1 named "pgm" must exist. The ASCII file to be uploaded must exist in this "data" directory before it can be uploaded. If these directories do not exist, the system will provide a warning message and return to the directory prompt. The 'pgm' subdirectory must contain scripts utilized by the EDI upload. ASCII data file name to upload (default to the value in the ACF "EDINDAT" option). This file must exist in the directory entered by the operator. The filename in the directory can now be up to 50 characters long. Previously there was a restriction of 18 characters. Printer to print log files (default to the value in the ACF "EDINPRT" option). The program will validate that the printer specified is a valid printer. Any errors which occur during the upload will be printed. An example of this type of error would be if the number of fields uploaded does not match the standard ASCII file definition. The system will display the batch number which will be assigned to the records uploaded from the ACF "EDINSEQ" option. This value will also be the value inserted before the ASCII file name when the ASCII file is renamed once the upload is complete. The ACF "EDINSEQ" batch number value will be incremented by 1 and updated to the ACF file. The value will be a 4 digit numeric which will assign numbers from 0001 to Enter "PROCEED" to continue or select Exit" to exit. Once the process is completed, the system will create a directory (if one is not already present) in the "data" directory of the starting directory specified. The directory will be named based on the current system date in the format "YYMMDD". Within this directory will be the renamed ASCII file in the format "BBBBNNNNNNNN" where BBBB represents the batch number and NNNNNNNN represents the original ASCII file name. A file with the same name with a ".h" suffix and a file with the same name with a ".d" suffix will also be created. These will be the upload error logs for the header and detail tables. If the size of the logs are 0, no upload errors occurred. Release NGS-7.00 EDI- 53

54 EDI Data Directory Maintenance. If you are using Method 1 or Method 2 for importing ASCII files to the UNIX server, (EDI purchase order transaction set (850) or the shortened ASCII file version), the ASCII file directories residing on the UNIX box should be cleared on a regular basis. To remove the ASCII files, use the UNIX recursive remove command. This command removes the directory or directories specified and all files and directories within them. USE EXTREME CAUTION WITH THE COMMANDS. - Enter the UNIX operating system. OSM <RETURN> - Change the directory to the directory containing the data files. cd /usr/mis/mis_edi/edin/data <RETURN> - Verify that the directory is correct. The result of the command should be the directory containing the directories to be deleted. If the wrong directory is chosen, files required by the system could be deleted by mistake! pwd <RETURN> - List the contents of the directory, if desired. ls al -Remove the directory or directories desired. rm -r <filename> For example, you may execute the following command to remove all directories and contents for September, 1998: rm -r 9809* USE EXTREME CAUTION WITH THE COMMAND. If executed without a filename, the command will remove all files within the specified directory. If executed with an incorrect file name, incorrect files may be deleted from the system. - Within the EDI inbound directory, 2 subdirectories are required: data and pgm. The data directory will contain the ASCII files as previously described. The pgm directory contains the following command files which are used during the upload process: mycut, mycut.c, order.exe, orderh.com and orderd.com. If the EDI inbound directory is changed, the setup must include the 2 subdirectories and the contents of the directories. Release NGS-7.00 EDI- 54

55 B2 - VALIDATION OPTION The validation option provides the ability of validating fields from the incoming transaction and determining the field values for standard Next Generation fields that will are required to generate the standard order tables. When operators choose the Validate Upload Data option, they will be prompted to enter selection criteria for the following fields: - Load Date - The date the ASCII file was uploaded to the system. - Batch Number - The EDI batch number assigned to the transactions. - Process Status - The status code of the transactions. - Trading Partner ID - The ID of the trading partner to process. - Sold To ID - The validated sold to customer ID to process. - Bill To ID - The EDI bill to ID. - Purchase Order Number - The purchase order number to process. The system will then validate the transactions which meet the criteria entered. B2-A. Header Validations. The following validations are performed for summary data associated with each transaction: Customer Sold To Validation. The trading partner id table will be accessed based on the trading partner / mailbox id on the transaction. If a record is not found, the system will set the status flag = "HC" (Header: Invalid Trading Partner). If a record is found but the order flag is not set to "Y" for the trading partner, the system will set the status flag = "HD" (Header: Invalid Partner Transaction). If a record is found and the trading partner sold to validation method is set to "1", the system will use the sold to id from the EDI transaction as the sold to customer id. Otherwise, if the sold to validation method is set to "0", the system will determine whether there is a

56 valued customer prefix defined for the trading partner. If this is the case, the system will access the standard customer table based on a customer ID of the prefix plus the bill to ID field from the incoming EDI Transaction. For example, if the prefix is set to "ABCD" and the incoming bill to ID is "0123", the system will access the customer table based on an id of "ABCD0123". If a record is not found, the system will set the status flag = "H2" (Header: Invalid Sold To). If the customer prefix is not valued, the sold to ID will be set to the customer ID defined in the trading partner table. Otherwise, if the sold to validation method for the trading partner is set to "2", the system will determine the sold to id based on the trading partner customer prefix and the ship to id. The system will select the applicable trading partner record (Table name: editp) based on the trading partner id defined in the EDI transaction (Table name: edinh; Field name: partnrid_editp = partnrid_edinh). The system will select the customer prefix defined for the trading partner (Field name: custprfx_editp). The system will access the Customer Master Table and Ship To Table based on the customer id (where the customer id (Field name: id_customer) matches the trading partner customer prefix (Field name: custprfx_editp) for the length of the trading partner prefix) and the ship to id (where the ship to id (Field name: id_shipto) matches the ship to id defined on the EDI transaction (Field name: shipto_edinh)). If no records are found or multiple records are found, the sold to validation will fail. If one record is found, the system will set the validated customer id (Field name: custid_edinh) to the customer id selected from the Ship To record (Field name: id_customer) and the validated ship to id (Field name: shipid_edinh) to the ship to id selected from the Ship To record (Field name: id_shipto). Note the following: This requires that only ONE customer prefix is defined for ALL the customer sold to records for a single trading partner and that NO other customers have a sold to id with the trading partner's prefix. This requires that a ship to id is unique for all the customers setup for a trading partner id. The system will not validate successfully if the same ship to id is defined for multiple customers of the same trading partner. In all cases, once the customer table is accessed, the branch will be set to the branch defined in the customer table. Customer Ship To Validation. If the ship to validation method defined for the trading partner is "1" the following method will be used: If the bslook flag is set to "BS" on the incoming transaction, the system will validate that a record exists in the standard ship to table for the validated customer sold to ID and the incoming ship to ID. If a record exists, the system will set the validated ship to ID to the ship to ID in the ship to table. If a record does not exist, the system will set the status flag to "H3" (Header: Invalid Ship To). If the bslook flag is not set to "BS", the system will validate that a record exists in the ship to table with a ship to id of "X". If a record is found, the system will set the ship to ID to "X". If a record is not found, the system will set the status flag to "H3" (Header: Invalid Ship To). By defining one ship to record with an id of "X" in the ship to table, the system can use this ship to with the ship to information on the EDI transaction rather than having to setup multiple ship to records. If the ship to validation method defined for the trading partner is "2" the following method will be used: If the EDI Bill to ID is equal to the EDI Ship to ID, the validated ship to ID will be set to "SAME".Otherwise, the system will validate that a record exists in the standard ship to table for the validated customer sold to ID and the incoming ship to ID. If a record exists, the system will set the validated ship to ID to the ship to ID in the ship to table. If a record does not exist, the system will set the status flag to "H3" (Header: Invalid Ship To). Release NGS-7.00 EDI- 56

57 If the branch id in the ship to record selected is valued, the system will set the branch id on the EDI transaction to the branch id of the ship to record, thereby overriding the customer record. Transaction Type Validation. If the transaction type is not set to "00" for regular orders or "W3" for WEB orders (see D'Artagnan system), the status flag will be set to "H1" (Header: Invalid Transaction Type). Transaction Type Codes. If the trading partner is defined to assign the transaction type from the EDI transaction, the system will verify that the transaction code is set to "OR" or "RM" or "DS" (if transtype on EDITPM table is a "2", then "DS" is a valid transaction type on the input PO file). If it is not, the status code will be set to "HF" (Header: Invalid transaction Code) Blank Purchase Order Number Validation. If the purchase order number is not valued, the status code will be set to "H7" (Header: Blank Cust PO Number). Duplicate Purchase Order Validation. If the purchase order duplicate override flag is set to "N", the following validations will occur if the duplicate PO check ACF option (oe011) is set to "Y". If another record exists with the same customer id and the same purchase order number in the EDI header table, the status code will be set to "H4" (Header: Duplicate Cust PO in EDI). If a record exists in the open order tables with the same customer id and the same purchase order number, the status code will be set to "H5" (Header: Duplicate Cust PO in Order). The validation will be limited to normal order transactions (OR, DS, QO, FO, SO, SI, BL). If a record exists in the sales analysis header table with the same customer sold to id and the same purchase order number, the status code will be set to "H6" (Header: Duplicate Cust PO in SA File). The system will only select records with a transaction date greater than or equal to the current system date less the number of days back to check defined in the ACF "edinpody" option. When performing the duplicate purchase order validation, if the trading partner's duplicate purchase order validation method is set to "1", the system will perform the duplicate purchase order validation based on the ship to id as well as the sold to id and the purchase order number. The following describes the validations that will occur when the duplicate purchase order ship to validation method is utilized: When validating whether the customer purchase order transmitted from EDI already exists in the EDI Table (Table name: edinh), select based on the ship to id as well as the sold to id, purchase order number and a different assigned serial number. Description Operation EDI Field Sold To ID = custid_edinh Customer PO # = cust_po_edinh Ship To ID = shipid_edinh Serial Number <> serial_edinh When validating whether the customer purchase order transmitted from EDI already exists in the Open Order Tables (Table names: ordera, orderb), select based on the ship to id as well as the sold to id, purchase order number and applicable transaction types defined. Description Ordera Field Name Orderb Field Name EDI Field Sold To ID soldto_ordera custid_edinh Customer PO # ust_po_orderb cust_po_edinh Ship To ID shipto_ordera shipid_edinh Release NGS-7.00 EDI- 57

58 Order Number ordnum_ordera ordnum_orderb (For Join) Transaction Types transtype_orderb OR, DS, QO, FO, SO, SI, BL. When validating whether the customer purchase order transmitted from EDI already exists in the Sales Analysis Table (Table names: sahdr), select based on the ship to id as well as the sold to id and purchase order number. Also, validate the transaction date based on the new ACF option (edinpody), defined in section E, which will indicate the number of days back to select Sales Analysis History records. Description SAHDR Field Name EDI Field Sold To ID soldto_ia_sahdr custid_edinh Customer PO # cust_po_ib_sahdr cust_po_edinh Ship To ID shipto_ia_sahdr shipid_edinh Transaction Date trandte_ib_sahdr (*) (*) TODAY - # of days defined in the new ACF 'edinpody' option. Note that if the number of days is set to '99999', the system will ignore the transaction date when doing the validation. If the number of days is set to "0", no validation against the sales history will occur. If the trading partner's duplicate purchase order validation method is set to "0", the system will perform the validation incorporating the number of days defined in the 'edinpody' option. Note that the duplicate purchase order validation only will occur if the contents of the existing ACF option for the purchase order check for duplicate P.O. number (oe011) is set to "Y". Duplicate Order Number If the system is defined to assign the order number from the purchase order number (based on the edipdoam option being set to "2"), the system will verify that no orders or sales analysis records have an order number that matches the first 10 characters of the customer purchase order number. If a duplicate order exists, the system will set the status code to "HG" (Header: Order number exist (from PO#)) Purchase Order Date Range Validation. If the purchase order date range override flag is set to "N" and the purchase order date is less than the current system date minus the purchase order number of days in the ACF "EDINDAY" option, the status code will be set to "HB" (Header: P/O Date Exceeded). Ship Via Code Validation. The first 4 characters of the header memo 20 field (memoh20_edinh) may be used to load the ship via code from the ASCII file. If the first 4 characters are not valued, the ship via validation will not be performed and the ship via of the order will be the default ship via from the customer or ship to record. If the first 4 characters are valued, the system will validate if a record exists in the Ship Via Table (shipvia) for the ship via code (based on svcode_shipvia = memoh20_edinh(1,4)). If a valid record is found, the validation will be passed and this ship via code will be loaded into the transaction when the order is created. If a valid record is not found, the system will set the status code to "H8" (Header: Invalid Shipping Method). B2-B. Detail Validations. The following validations are performed for detail line item data associated with each transaction: Detail Record Validation If no detail record is found for the purchase order, the transaction status will be set to "D0" (DETAIL - NO DETAIL RECORD FOUND). Item Validation. Release NGS-7.00 EDI- 58

59 Item ID validations occur based on the 2 customer part id fields, UPC fields and item id fields based on the methods defined in the trading partner record. If the trading partner lookup field is set to zero, that validation will not occur. Once a lookup is successful, the system will set the validated item id field. If any lookup fails, the system will then perform the next lookup. The system will first attempt to validate the item id field: - If the trading partner item lookup field is set to "0", the system will not perform any validation on the item id field. -If the trading partner item lookup field is set to "1", the system will access the item table based on the item id field being equal to the item id in the detail record. If a record is found, the system will set the validated item id to the item id found. - If the trading partner item lookup field is set to "2", the system will access the item table based on the item cross-reference being equal to the item id in the detail record. If ONE record is found, the system will set the validated item to the item id found. - If the trading partner item lookup field is set to "3", the system will access the customer part table based on the customer part id lookup field in the trading partner record and the item id field in the detail record. If the customer part id lookup field is <NULL>, the system will use the sold to customer ID. If ONE record is found, the system will validate that the item exists in the item table and set the validated item to the item id found. - If the trading partner item lookup field is set to "4", the system will access the Contract Pricing Table (Table name: conprice) based on the validated sold to id (Field name: custid_edinh) matching the contract's customer id (Field name: custid_conprice), the item id in the detail record (Field name: sellitem_edind) matching the contract's customer item id (Field name: custitem_conprice), the contract's effective date (Field name: effdte_conprice) being less than or equal to the transaction date on the EDI transaction (Field name: transdate_edinh) and the contract's expiration date (Field name: expdte_conprice) being greater than or equal to the transaction date on the EDI transaction (Field name: transdate_edinh). If no records are found, the validation will fail and the system will proceed with any additional item validations that have not yet been performed. If one or more contract records are selected, the system will set the validated item id (Field name: itemid_edinh) to the item id selected from the Contract Pricing record (Field name: itemid_conprice) for the first contract record selected in expiration date, contract price sequence (Field names: expdte_conprice, conprice_conprice). - If the trading partner item lookup field is set to '5", the system will access the Item Interchange Table maintained by the UPCLOAD program (Table name: cixref; rectype_cixref = "2"). The system will select the item id field (Field name: ouritemid_cixref) where the item id in the detail record (Field name: sellitem_edind) matches the UPC/Interchange id (Field name: interchgid_cixref). Note that if multiple records are defined with the same UPC/Interhchange id, the system will not be able to validate the record. The system will then attempt to validate the UPC code field: - If the trading partner UPC lookup field is set to "1", the system will access the item table based on the item id being equal to the UPC code in the detail record. If a record is found, the system will set the validated item to the item id found. - If the trading partner UPC lookup field is set to "2", the system will access the item table based on the item cross-reference field being equal to the UPC code on the detail record. If ONE record is found, the system will set the validated item id to the item id found. - If the trading partner UPC lookup field is set to "3", the system will access the customer part table based on the customer part id lookup field in the trading partner record and the UPC code in the detail record. If the customer part id lookup field is <NULL>, the system will use the sold to customer ID. If ONE Release NGS-7.00 EDI- 59

60 record is found, the system will validate that the item exists in the item table and set item to the item id found. the validated - If the trading partner UPC lookup field is set to "4", the system will access the Contract Pricing Table (Table name: conprice) based on the validated sold to id (Field name: custid_edinh) matching the contract's customer id (Field name: custid_conprice), the UPC code in the detail record (Field name: upc_edind) matching the contract's customer item id (Field name: custitem_conprice), the contract's effective date (Field name: effdte_conprice) being less than or equal to the transaction date on the EDI transaction (Field name: transdate_edinh) and the contract's expiration date (Field name: expdte_conprice) being greater than or equal to the transaction date on the EDI transaction (Field name: transdate_edinh). If no records are found, the validation will fail and the system will proceed with any additional item validations that have not yet been performed. If one or more contract records are selected, the system will set the validated item id (Field name: itemid_edinh) to the item id selected from the Contract Pricing record (Field name: itemid_conprice) for the first contract record selected in expiration date, contract price sequence (Field names: expdte_conprice, conprice_conprice). - If the trading partner UPC lookup field is set to '5", the system will access the Item Interchange Table maintained by the UPCLOAD program (Table name: cixref; rectype_cixref = "2"). The system will select the item id field (Field name: ouritemid_cixref) where the UPC code in the detail record (Field name: upc_edind) matches the UPC/Interchange id (Field name: interchgid_cixref). Note that if multiple records are defined with the same UPC/Interhchange id, the system will not be able to validate the record. The system will then determine the method to utilize the Customer Part ID for the trading partner: - If the trading partner customer part method field is set to "1", the system will use the customer part id 1 field. - If the trading partner customer part method field is set to "2", the system will use the customer part id 1 plus the customer part id 2 fields separated by a dash. (Note that if the customer part id 2 field is not valued, only the customer part id 1 field will be used without a dash). - If the trading partner customer part method field is set to "3", the system will use the combined customer part id 1 and customer part id 2 fields with no dash separator. The system will then attempt to validate the Customer Part ID field: - If the trading partner customer part lookup field is set to "1", the system will access the item table based on the item id field in the item record being equal to the customer part id used from the detail record. If a record is found, the system will set the validated item to the item id found. - If the trading partner customer part lookup field is set to "2", the system will access the item table based on the item cross-reference field in the item record being equal to the customer part id used from the detail record. If ONE record is found, the system will set the validated item to the item id found. - If the trading partner customer part lookup field is set to "3" the system will access the customer part table based on the Customer Part ID Lookup field in the trading partner record and the customer part id used from the detail record. If the Customer Part ID Lookup field is not valued, the system will use the validated Sold To ID. If ONE record is found, the system will validate that the item exists in the item table and set the validated item to the item id found. - If the trading partner customer part lookup field is set to "4", the system will access the Contract Pricing Table (Table name: conprice) based on the validated sold to id (Field name: custid_edinh) matching the contract's customer id (Field name: custid_conprice), the customer part id used from the detail record matching the contract's customer item id (Field name: custitem_conprice), the contract's effective date (Field name: effdte_conprice) being less than or equal to the transaction date on the EDI transaction (Field name: transdate_edinh) and the contract's expiration date (Field name: expdte_conprice) being greater than or equal to the transaction date on the EDI transaction (Field name: transdate_edinh). If no records are found, the validation will fail and the system will proceed with any additional item validations Release NGS-7.00 EDI- 60

61 that have not yet been performed. If one or more contract records are selected, the system will set the validated item id (Field name: itemid_edinh) to the item id selected from the Contract Pricing record (Field name: itemid_conprice) for the first contract record selected in expiration date, contract price sequence (Field names: expdte_conprice, conprice_conprice). - If the trading partner customer part lookup field is set to '5", the system will access the Item Interchange Table maintained by the UPCLOAD program (Table name: cixref; rectype_cixref = "2"). The system will select the item id field (Field name: ouritemid_cixref) where the customer part id used from the detail record matches the UPC/Interchange id (Field name: interchgid_cixref). Note that if multiple records are defined with the same UPC/Interhchange id, the system will not be able to validate the record. Once the item id is found, the system will set the validated item id, item description, alternate conversion factor, unit of measure, alternate unit of measure, pricing unit of measure and pricing unit of measure conversion factor fields in the EDI detail record. The system will also access the customer part id cross-reference table based on the trading partner Customer Part ID Lookup field and the validated item id. If the Customer Part ID Lookup field is not valued, the system will use the validated Sold To ID. The validated customer part number field will be set when a record is found. If all the item validations fail, the transaction status flag will be set to "D1" (DETAIL: INVALID ITEM ID). Unit of Measure Validation. If the ACF option to perform unit of measure validation (ediuomv) is set to "2", the system will validate the unit of measure code sent on EDI transactions to determine that it corresponds to the primary or alternate unit of measure in the item table or to a record in the EDI Unit of Measure Cross-reference table. The system will first access the EDI Trading Partner Unit of Measure Cross-Reference Table (ediuom) based on the following criteria: - partnerid_ediuom = partnrid_edinh. - itemid_ediuom = itemid_edind. - custuom_ediuom = uom_edind. If a record is found, the system will access the item table for the item being processed (id_item = itemid_edind). and determine if the unit of measure in the conversion table (uom_ediuom) matches the unit of measure in the item table (uom_item). If it matches, the system will leave the record as it is and the line item unit of measure will pass validation. If it does not match, the system will determine if the unit of measure in the conversion table (uom_ediuom) matches the alternate unit of measure in the item table (alteruom_item). If it matches, the system will set the alternate quantity ordered (altqtyord_edind) to the quantity ordered (qtyord_edind) and leave the quantity ordered as is. The line item unit of measure will pass validation. If no record is found in the cross-reference table or the unit of measure is not valid, the system will access the item table. The system will determine if the unit of measure in the EDI Detail Table record (uom_edind) matches the unit of measure in the item table (uom_item). If it matches, the system will leave the record as it is and the line item unit of measure will pass validation. If it does not match, the system will determine if the unit of measure in the EDI Detail Table record (uom_edind) matches the alternate unit of measure in the item table (alteruom_item). If it matches, the system will set the alternate quantity ordered (altqtyord_edind) to the quantity ordered (qtyord_edind) and leave the quantity ordered as is. This will indicate that the quantity in the detail record corresponds to and must be converted to the alternate unit of measure. The line item unit of measure will pass validation. If the unit of measure validation fails, the error status will be set to "D3" and the corresponding error message will be "DETAIL: INVALID UNIT OF MEASURE". Selling Price Validation. If the trading partner is defined to validate selling prices, the system will calculate the selling price for the Release NGS-7.00 EDI- 61

62 sold to customer, item id, quantity ordered and transaction date of the line item. If the EDI selling price is non-zero AND the EDI selling price is not equal to the selling price calculated, the system will set the status flag to "D2" (Detail: Invalid Selling Price). *Note* If you bring in a selling price of zero OR if the user overrides the selling price to zero, It will use the selling price calculated by the system. Logic behind this is if the Trading Partner sends in a zero price, they are accepting the price you calculated. When calculating and determining the selling price of the order, if the alternate quantity ordered is set to zero, the system will continue to calculate the line item extension based on the quantity ordered in the EDI detail table and an alternate quantity ordered of zero. If the alternate quantity ordered is not set to zero, the system will calculate the selling price by calculating the quantity ordered and alternate quantity ordered based on the alternate to stock conversion factor for the item. This condition would occur when the unit of measure is validated and the unit of measure corresponds to the item alternate unit of measure. Note that if the trading partner does no pricing validation, the selling price on the EDI transaction will be ignored. The system will use the standard pricing mechanisms to calculate the selling price on the order. If the trading partner is defined to set the selling price on the order to the selling price from the EDI record, based on trading partner sell price method being set to "O", the system will do this and also set the detail line as a manually priced line. If the contract pricing validation portion of the pricing validation logic fails and the validate selling price field in the trading partner record (Field name: pricemeth_editp) is set to "C" (indicating that the system will only validate the price against the customer's valid contracts), the record will fail the pricing validation. The status flag on the record (Field name: status_edind) will be set to "D2", indicating that the record has an invalid selling price. The system will NOT proceed with the remainder of the pricing logic (i.e. matrix pricing). Calculate Retail Price. If the retail price customer id in the trading partner record is valued, the system will access the customer table by the retail price id. If the customer exists, the system will calculate the selling price for the retail price customer for the item, quantity and transaction date and store this in the retail price field. If the retail price id is not valued, the system will leave the retail price as it was on the inbound transaction. B2-C. Summary Validations. The following validations are performed once the detail line item validations have been performed for the transaction: Order Maximum Value Validation. The system will calculate the net extension (netext_edind) on each detail line, based on the quantity ordered (qtyord_edind) and the selling price (sellprice_edind). When calculating the line item net extension, if the alternate quantity ordered is set to zero, the system will calculate the line item extension, based on the quantity ordered in the EDI detail table and an alternate quantity ordered of zero. If the alternate quantity ordered is not set to zero, the system will calculate the line item net extension, using the quantity ordered and alternate quantity ordered calculated based on the alternate to stock conversion factor of the item. This condition would occur if the unit of measure validation is performed and the unit of measure on the EDI transaction corresponds to the item alternate unit of measure. The system will calculate the net extension (netext_edinh) on the header, based on the sum of the net extension on the detail line for the header. If the value override flag is not set to "Y" and the maximum normal value defined in the trading partner record is not zero, the system will compare the header net extension to the maximum normal value in the trading partner record. If the net extension is greater than the maximum normal value, the system will set Release NGS-7.00 EDI- 62

63 the status flag to "H9" (Header: Netext is Over Normal Value). EDI HEADER and DETAIL COMMENTS RECORD CREATION Two new tables have been added and will be used by the EDIPOLD order creation option. They are EDINHC (header comments) and EDINDC (detail comments). They can only be created via a custom program using the EDIPOLD (U)pload exit program capability (acf option edipolxx). If data is present in these tables, the edipold (O)rder create option will create the appropriate order header and order detail comment records used in the standard Order Management system. edinhc table - edi uploaded header comments records serial_hdr_edinhc partnrid_edinhc cust_po_edinhc cseqid_edinhc prtflg_edinhc type_edinhc comm_edinhc trandate_edinhc sysdate_edinhc user_edinhc memoamt_edinhc memodate_edinhc autoxfer_cd_edinhc transtypes_edinhc edindc table edi uploaded detail comments records serial_hdr_edindc partnrid_edindc cust_po_edindc serial_det_edindc cseqid_edindc prtflg_edindc type_edindc comm_edindc trandate_edindc sysdate_edindc user_edindc memoamt_edindc memodate_edindc autoxfer_cd_edindc transtypes_edindc Release NGS-7.00 EDI- 63

64 B3 - MAINTENANCE OPTION The maintenance function will provide the capability will be provided to update, remove, query and view EDI transaction records. The maintenance function will provide the capability will be provided to update, remove, query and view EDI header transaction records. When the operator selects the Maintain Upload Data option on the EDI Processing Menu, the operator will be prompted for the menu option to perform. The system will allow you to prompt for search criteria on the maintainable detail fields on the first screen (validation fields screen). Release NGS-7.00 EDI- 64

65 Header Maintenance Screen 2. Header Maintenance Screen 3. Release NGS-7.00 EDI- 65

66 Header Maintenance Screen 4. Header Maintenance Screen 5. Once the operator selects records, the following options are provided: - U - Update - Access and maintain fields on the first header screen. - V - Validate - Perform all validation functions on the transaction. - C - Convert - Convert a successfully validated transaction to order. - D - Detail - Access the Detail Line Records for the transaction. - F - First Record - Access the first header record selected. - N - Next Record - Access the next header record. - P - Previous Record - Access the previous header record. - L - Last Record - Access the last header record selected Screen 1 - Access screen 1 of the transaction (validation fields) Screen 2 - Access screen 2 of the transaction (ship to address) Screen 3 - Access screen 3 of the transaction (flow through fields). Release NGS-7.00 EDI- 66

67 - H - Help - Access help. - E - Exit - Return to menu. When performing an update, the following will occur on the first header screen: - The operator will be prompted for the partner id. The system will validate that the trading partner ID is valid and that the trading partner is defined for order transactions. - The operator will be prompted for bill to id. If the trading partner prefix is set, this will be used in conjunction with the prefix to determine the sold to customer ID. - The operator will be prompted for sold to id. - The operator will be prompted for the sold to override flag. If the operator wants to override the validation fields and manually enter the Sold to customer ID, enter a "Y". - The operator will be prompted for the valid sold to id field. If a valid customer is found, the system will display the valid sold to id ("OUR SOLD TO"). Otherwise, the customer validation logic will be used to determine the sold to id. If a valid customer is found, the system will display the valid customer id ("OUR SOLD TO"). - If a valid customer is not found, the program will return to the trading partner id prompt and allow you to change the values in the customer validation fields. - The operator will be prompted for the bs ship to lookup designator. - The operator will be prompted for the ship to id. Based on the trading partner ship to method, this will be used to validate the ship to id. - The operator will be prompted for the ship to name. - The operator will be prompted for the ship to override flag. If the operator wants to override the validation fields and manually enter the Ship to ID, enter a "Y". - The operator will be prompted for the valid ship to id field. If a valid ship to is found, the system will display the valid ship to id ("OUR SHIP TO"). Otherwise, the ship to validation logic will be used to determine the ship to id. If a valid ship to is found, the system will display the valid ship to id ("OUR SHIP TO"). - If a valid ship to is not found, the program will return to the bs ship to lookup designator prompt and allow you to change the values in the ship to validation fields. - The branch id will default to the branch id in the customer record. If the ship to record contains a valid branch id, this will override the branch id. The operator will be prompted for a valid branch. - The operator will be prompted for a valid transaction type ("00"). - The operator will be prompted for the transaction code. - The operator will be prompted for the duplicate p/o override flag and the customer p/o number. The duplicate p/o validation logic will be used to determine if the p/o is a duplicate. If it is a duplicate and the duplicate p/o override flag is not set to "Y", the program will reprompt for duplicate p/o override flag and the customer purchase order number. - The operator will be prompted for the p/o date override flag and the purchase order date. The p/o date range validation logic will be used to determine if the p/o is outside the range. If it is out of range and the p/o date override flag is not set to "Y", the program will reprompt for the p/o date Release NGS-7.00 EDI- 67

68 override flag and the p/o date. - The operator will be prompted for the transaction date. - The operator will be prompted for the valid ship via code for the transaction. If the field is valued, the system will validate that a ship via record exists for the code. - The operator will be prompted for the required date and the cancel date. - The operator will be prompted for the over normal value override flag. If the operator sets the flag to "Y", the system will not compare the total value of the transaction to the maximum normal value setup in the trading partner record. - The system will display the total order value (net extension) based on the total extension of the validated detail line items and, if the normal value override flag is not set to "Y", validate the order value. - The operator will be prompted for the ship date. - If the operator selects "2" at the options prompt, the second header screen can be accessed. On the second screen (ship to fields), the validated sold to id, validated ship to id, trading partner id, customer purchase order number and ship to name will be displayed. The operator will be able to access the ship to address 1, ship to address 2, ship to address 3, ship to city, ship to state, ship to zip, ship to attention and ship to country. - If the operator selects "3" at the options prompt, the third header screen can be accessed. On the third screen (flow through fields), the validated sold to id, validated ship to id, trading partner id, customer purchase order number and ship to name will be displayed. The operator will be able to access the mark for, reference number, department, media event code, contract number, customer p/o batch number, terms code, routing, scac code, the memo 1 through 5 fields and the remarks. Query Menu Options Logic. The program will allow selection based on any of the fields on header screen 1 and provides options for Detail Screen, First record, Last record, Next record, Previous record, Screen 2 and Screen 3. Remove Menu Options Logic. Single Record Remove The program will allow selection based on any of the fields on header screen 1 and provides options for Remove record, First record, Last record, Next record, Previous record, Screen 2 and Screen 3. If the remove record option is selected, the system will prompt the operator to verify that the transaction should be removed. Mass Remove based on Batch #. Allows user to remove an entire batch. This will bypass records where the sales order was already generated. View Menu Options Logic. The program will allow selection based on any of the fields on header screen 1. The following sort options are provided: - By Batch Number, Trading Partner ID, Customer PO Number. - By Trading Partner ID, Batch Number, Customer PO Number. - By Customer PO Number, Trading Partner ID, Batch Number. - By Customer PO Number, Batch Number, Trading Partner ID. The program will prompt you to define the number of blank lines to appear between details. Release NGS-7.00 EDI- 68

69 The program will allow the report to be output to the screen, printer or hold file. B3-B. Detail Records Maintenance Logic: The maintenance function will provide the capability will be provided to add, update, remove and query detail lines. Detail Maintenance Screen 1. Detail Maintenance Screen 2. Release NGS-7.00 EDI- 69

70 Detail Maintenance Screen 3. Detail Maintenance Screen 4. When operators select the detail option, the system will display the validated sold to ID, validated ship to ID, the trading partner ID, the customer purchase order number and the ship to name from the header. The system will allow you to prompt for search criteria on the maintainable detail fields on the first screen. When performing an add or update, the following will occur: - The operator will be prompted for the customer's purchase order line number. - The operator will be prompted for customer part id 1. - The operator will be prompted for customer part id 2. - The operator will be prompted for the UPC code. Release NGS-7.00 EDI- 70

71 - The operator will be prompted for the item id. - The operator will be prompted for the item description. - The operator will be prompted for the item id override flag. If the operator wants to manually enter the item id, a "Y" should be entered here. - The operator will be prompted for the valid item id field. If a valid item id is found, the system will display the valid item id and item description ("OUR ITEM ID"). Otherwise, the item validation logic will be used to determine the item id. If a valid item id is found, the system will display the valid item id and item description ("OUR ITEM ID"). - If a valid item is not found, the program will return to the customer part id 1 prompt and allow you to access the item id validation fields. - The operator will be prompted for the quantity ordered and unit of measure. If the unit of measure validation option is set, the system will verify that the unit of measure entered matches either the trading partner unit of measure cross-reference, item primary unit of measure or item alternate unit of measure. If it does not match any of the fields, the system will display the message "Invalid Unit Of Measure" and return to the unit of measure prompt. - The operator will display the converted quantity if the UPC code on the edi input file is found in the UPCLOAD program table (cixref). The program will multiply the quantity ordered times the conversion factor from the UPCLOAD program table and show the converted quantity on the screen. The converted quantity and the conversion factor will be stored in the edind table and when the order is created, the converted quantity will become the quantity order in the orddet record. - The standard price calculation will be performed for the customer, item and quantity. The standard selling price ("OUR SELLING PRICE") and pricing unit of measure will be displayed. The net extension will be calculated and displayed, based on the standard selling price and the quantity ordered. - The operator will be prompted for the selling price. - If the trading partner is defined to validate selling prices and the selling price is non-zero and does not agree with the standard selling price, the system will display the message "Invalid Selling Price" and return to the quantity ordered prompt and allow you to enter the selling price validation fields. - The operator will be prompted for the freight, special instructions 1, and special instructions 2. - On screen 2, the operator can access the delivery note 1, delivery note 2 and memo 1 through 5 fields. Query Menu Options Logic. The program will allow selection based on any of the fields on detail screen 1 and provides options for First record, Last record, Next record, Previous record and Screen 2. Remove Menu Options Logic. The program will allow selection based on any of the fields on detail screen 1 and provides options for Remove record, First record, Last record, Next record, Previous record and Screen 2. If the remove record option is selected, the system will prompt the operator to verify that the transaction detail record should be removed. Release NGS-7.00 EDI- 71

72 B4 - ORDER CREATION OPTION. This option will generate orders for transactions that have been successfully validated. When operators select the order creation menu option, they will be prompted to enter selection criteria for the following fields: - Load Date - The date the ASCII file was uploaded to the system. - Batch Number - The EDI batch number assigned to the transactions. - Trading Partner ID - The ID of the trading partner to process. - Sold To ID - The validated sold to customer ID to process. - Ship To ID - The validated ship to ID to process. - Requested Date - The requested date to process. - Transaction Date - The transaction date to process. - Customer P/O Date - The purchase order date to process. - Purchase Order Number - The purchase order number to process. The system will then create orders in the standard order files for all successfully validated transactions that meet the selection criteria. The system will generate records in the temporary order tables based on the mapping. The ordtmpa, ordtmpb and ordtmpd tables will be generated. These records will passed through to the order entry program which will generate the actual open order records. If the system is defined to assign the order number to the purchase order number (based on the edipooam option being set to "2"), the system will set the order number to the first 10 characters of the customer purchase order number. Once the order has been generated, the system will generate the orderc record for the order transaction and an orddet2 record for each line item generated in the order detail table. These tables will contain the EDI fields to be saved through the system for outbound transaction generation. Once completed, the applicable fields in the EDI table will be set (i.e. the MIS order number field will be set in the EDI table, the status will be changed to "U" for updated, etc.). B4-A. Additional Mapping Requirements Date Processing If the ship date is not set, it will be set equal to the require date. If the cancel date is not set, it will be set to the require date Ship To Name And Address If the ship to id = "X", the name and address data will be taken from the EDI header fields. Any fields that are not valued will be set to "." to prevent the order entry program from inserting data from the ship to table. If either the ship to name, address1, address2, address3, city, state or zip code fields are valued, the entire ship to name and address data will be taken from the EDI header fields. Any fields not valued will be set to "." to prevent the order entry program from inserting data from the ship to table. If the BS look indicator is set to "BS", the system will pass the ship to id but will not pass the name and address data. This will be taken from the standard ship to table. Ship Via Code Requirements. If the header memo 20 field is valued, the first 4 characters will be validated to insure that the field matches a valid ship via code in the system. If the field is valued, it will be mapped to the ship via code on the order transaction. Release NGS-7.00 EDI- 72

73 Quantity / Unit Of Measure Requirements. When mapping the EDI Detail records (edind table) to the Order Temporary Detail Table (ordtmpd), if the alternate quantity ordered (altqtyord_edind) is set to zero, the program will continue to take the quantity ordered and move it to the order quantity ordered and set the alternate quantity ordered in the order table to zero (qtyord_orddet = qtyord_edind, altqtyord_orddet =0). If the alternate quantity ordered (altqtyord_edind) is not set to zero, the program will set the quantity ordered and alternate quantity ordered based on the alternate to stock conversion factor for the item. This condition would occur if the unit of measure validation is performed and the unit of measure on the EDI transaction corresponds to the item alternate unit of measure. Item Memo Fields. The first 16 characters of the detail memo 20 field will be updated to the item memo1 field in the order detail record. The first 16 characters of the detail memo 21 field will be updated to the item memo 2 field in the order detail record. Order Number If the system is defined to assign the order number to the purchase order number (based on the edipoam option being set to "2"), the system will verify that no orders or sales analysis records have an order number that matches the first 10 characters of the customer purchase order number. Original Taken By The original taken by field (Field name: otakenby_orderb) is set to "edi" rather than the user id of the user generating the sales orders. This will allow the user to select "edi" type orders in the ORDR Report. B4-B. Order Creation Error Codes The following error codes will be generated when there is a problem creating the order: Code Description O0 HEADER - NO MIS ORDER NUMBER O1 HEADER - CANNOT INSERT INTO ORDTMPA, ORDTMPB OA HEADER - CANNOT INSERT INTO ORDTMPA OB HEADER - CANNOT INSERT INTO ORDTMPB O2 HEADER - CANNOT INSERT INTO ORDTMPD O4 HEADER - ORDER NOT CREATED O5 HEADER - CANNOT ALLOCATE DETAIL LINE 06 HEADER ORDER NUMBER EXIST (FROM PO#) Release NGS-7.00 EDI- 73

74 *** NOTE *** you can automate the EDIPOLD process (upload validate order creation) by setting up a miscron *** (MISCRON)-- CRON JOB MAINTENANCE Program Name [edipold ] Parameter 1 : [AUTO ] Parameter 2 : [ ] Parameter 3 : [ ] Parameter 4 : [ ] Parameter 5 : [ ] Program Path : [EDIPROGS ] Military Time: [01:00] Daily Job : [Y] Mon [Y] Tues [Y] Wed [Y] Thur [Y] Fri [Y] Sat [Y] Sun [N] Selected Days: [N] Day 1 [ 0] Day 2 [ 0] Day 3 [ 0] Day 4 [ 0] Day 5 [ 0] Day 6 [ 0] Day 7 [ 0] Day 8 [ 0] Last Date Completed: [ ] Last Time Completed: [ ] Release NGS-7.00 EDI- 74

75 B5 - PURGE OPTION The purge option provides the ability to delete records in the EDI Inbound Header and Detail tables (edinh, edind) with an upload date equal to or less than an entered purge date.when operators select the Purge EDI Files option from the EDI Processing Menu, they will be prompted to enter a password. The password will be validated to see that it matches the value in the ACF "EDINPWD" option.the system will then prompt for the purge date. The purge date will default to the current system date minus the number of days to save the EDI Transaction Data files which is stored in the ACF "EDINPRG" option.the operator will then be prompted to enter "PROCEED" or select Exit" to exit. Purge Menu Option Password Screen. Purge Menu Option Screen. Release NGS-7.00 EDI- 75

76 This may also be set up to run automatically at a pre-determined date and time by adding a MISCRON record as shown. The purge date will default to the current system date minus the number of days to save the EDI Transaction Data files which is stored in the ACF "EDINPRG" option. Release NGS-7.00 EDI- 76

77 C - CUSTOM PROGRAM ROUTINE CAPABILITY The capability of calling custom subroutine programs from specific processes in the EDI Inbound program.is provided through the ACF "edipol " option that works in a manner similar to the "bill " ACF options. The following subroutine capabilities and options will be provided: edipol0x Execute programs in sequence after upload. This provides the capability of performing custom subroutines after the ASCII file has been uploaded in to the EDI tables. A new exit routine provides the capability to execute custom subroutines AFTER order temporary records are created but PRIOR to the order being generated based on ACF edipol series (edipol3_). The ACF Option key is broken into 3 segments. Example; edipolxy where 1st required seg = edipol X = 2nd segment. This number controls WHEN custom job will run from within EDIPOLD program. Y = 3rd segment. This number controls SEQUENCE of jobs to run AND allows for more than 1 job to run. IF X=0, run job after records have been uploaded through the upload option. X=1, run job after records have been validated through the validate or maintenance options. X=2, run job after order records have been created through the order creation or maintenance options. X=3, run job after order temporary records have been created but prior to the order creation through the order creation or maintenance options. ediin1x Execute programs in sequence after validation. This provides the capability of performing additional validations after the standard header, detail and summary validations are completed. Note that these functions will not occur during the actual maintenance of records but will occur during the validation menu option and the validation option in the maintenance menu option.. ediin2x Execute programs in sequence after order creation. This provides the capability of performing additional mapping and updating after the order transaction has been generated. Once the subroutine is completed, control will return to the main program, which will proceed with normal processing. Release NGS-7.00 EDI- 77

78 D - FILE AND FIELD LAYOUTS D1. EDINH - EDI INBOUND PURCHASE ORDER HEADER TABLE - this file is created after the ascii, excel or XML files are successfully (U)ploaded from the EDIPOLD program function. FIELD NAME SIZE TYPE DESCRIPTION serial_edinh 4 SERIAL SERIAL NUMBER batch_edinh 2 SMINT EDI BATCH NUMBER partnrid_edinh 27 CHAR TRADING PARTNER ID / MAILBOX NUMBER The trading partner ID or mailbox #. billto_edinh 35 CHAR BILL TO ID The ID of the unit to be invoiced. soldto_edinh 35 CHAR SOLD TO ID The ID of the unit that placed order. shipto_edinh 35 CHAR SHIP TO ID The ID of the unit where goods are to be shipped. bslook_edinh 35 CHAR SHIP TO ID INDICATOR The flag denoting whether or not to access customer ship to information. transdate_edinh 4 DATE TRANSACTION DATE The date the order came into the system and was processed converted to MM/DD/YYYY format. reqdate_edinh 4 DATE REQUESTED DATE The date the customer wants the goods converted to MM/DD/YYYY format. shipdate_edinh 4 DATE SHIP DATE The date the goods are to be shipped converted to MM/DD/YYYY format. canceldte_edinh 4 DATE CANCEL DATE The date the goods must be shipped before converted to MM/DD/YYYY format. podate_edinh 4 DATE PURCHASE ORDER DATE. The date of the customer purchase order converted to MM/DD/YYYY format. cust_po_edinh 22 CHAR CUSTOMER P/O NUMBER. pobatch_edinh 10 CHAR CUSTOMER PURCHASE ORDER BATCH. Customer denotion of a group of purchase orders. refno_edinh 30 CHAR REFERENCE NUMBER. Customer reference number for the order. dept_edinh 30 CHAR DEPARTMENT NUMBER. The buying department. remarks_edinh 80 CHAR REMARKS. Any remarks regarding the purchase order. media_edinh 2 CHAR MEDIA/EVENT CODE. shipname_edinh 35 CHAR SHIP TO NAME. shipaddr1_edinh 35 CHAR SHIP TO ADDRESS 1. shipaddr2_edinh 35 CHAR SHIP TO ADDRESS 2. shipaddr3_edinh 35 CHAR SHIP TO ADDRESS 3. shipcity_edinh 19 CHAR SHIP TO CITY. shipstate_edinh 4 CHAR SHIP TO STATE. shipzip_edinh 10 CHAR SHIP TO ZIP CODE. shipattn_edinh 27 CHAR SHIP TO ATTENTION. Release NGS-7.00 EDI- 78

79 FIELD NAME SIZE TYPE DESCRIPTION shipcntry_edinh 10 CHAR SHIP TO COUNTRY. shipphone_edinh 15 CHAR SHIP TO PHONE NUMBER. shipfax_edinh 15 CHAR SHIP TO FAX NUMBER. markfor_edinh 45 CHAR MARK FOR. terms_cd_edinh 4 CHAR TERMS CODE. transcd_edinh 2 CHAR TRANSACTION CODE. "OR, RM, DS" - *REQ D* depends on transtype assignment in EDITPM table transtype_edinh 2 CHAR TRANSACTION TYPE. 00 or W3 contract_edinh 12 CHAR CONTRACT ID. routing_edinh 2 CHAR ROUTING CODE. scac_edinh 4 CHAR SCAC CODE. memo1_edinh 30 CHAR MEMO 1 (ALPHA). memo2_edinh 30 CHAR MEMO 2 (ALPHA). memo3_edinh 10 CHAR MEMO 3 (ALPHA). memo4_edinh 10 DEC MEMO 4 (NUMERIC). memo5_edinh 4 DATE MEMO 5 (DATE). custid_edinh 10 CHAR VALIDATED CUSTOMER ID. shipid_edinh 10 CHAR VALIDATED SHIP TO ID. valueflag_edinh 2 CHAR VALUE OVER MAXIMUM OVERRIDE FLAG. poduplov_edinh 2 CHAR DUPLICATE P/O OVERRIDE FLAG. podateov_edinh 2 CHAR P/O DATE RANGE OVERRIDE FLAG. custidov_edinh 2 CHAR CUSTOMER ID MANUAL OVERRIDE FLAG. shipidov_edinh 2 CHAR SHIP TO ID MANUAL OVERRIDE FLAG. flag_edinh 4 CHAR EDI INTERNAL UPLOAD FLAG. status1_edinh 2 CHAR STATUS FLAG. status2_edinh 2 CHAR STATUS FLAG 2 (FUTURE USE). mis_ordnum_edinh 10 CHAR GENERATED ORDER NUMBER. edi_ordnum_edinh 10 CHAR TEMPORARY EDI ORDER NUMBER. division_edinh 4 CHAR DIVISION ID (FROM SHIP TO OR CUSTOMER TABLE). branch_edinh 8 CHAR BRANCH ID (FROM SHIP TO OR CUSTOMER TABLE; CAN BE OVERRIDDEN). netext_edinh 10 DEC NET EXTENSION grossext_edinh 10 DEC GROSS EXTENSION. loaddate_edinh 4 DATE DATE TRANSACTION UPLOADED. validdate_edinh 4 DATE DATE TRANSACTION LAST VALIDATED. createdate_edinh 4 DATE DATE ORDER CREATED. userid_edinh 8 CHAR USER ID. ttyname_edinh 16 CHAR DEVICE ID. sysdate_edinh 4 DATE DATE LAST MODIFIED. systime_edinh 8 CHAR TIME LAST MODIFIED. memoh1_edinh 30 CHAR HEADER MEMO 1. memoh2_edinh 30 CHAR HEADER MEMO 1. memoh3_edinh 30 CHAR HEADER MEMO 3. memoh4_edinh 30 CHAR HEADER MEMO 4. memoh5_edinh 30 CHAR HEADER MEMO 5. memoh6_edinh 30 CHAR HEADER MEMO 6. memoh7_edinh 30 CHAR HEADER MEMO 7. memoh8_edinh 30 CHAR HEADER MEMO 8. memoh9_edinh 30 CHAR HEADER MEMO 9. memoh10_edinh 30 CHAR HEADER MEMO 10. memoh11_edinh 30 CHAR HEADER MEMO 11. memoh12_edinh 30 CHAR HEADER MEMO 12. memoh13_edinh 30 CHAR HEADER MEMO 13. memoh14_edinh 30 CHAR HEADER MEMO 14. memoh15_edinh 30 CHAR HEADER MEMO 15. memoh16_edinh 30 CHAR HEADER MEMO 16. memoh17_edinh 30 CHAR HEADER MEMO 17. Release NGS-7.00 EDI- 79

80 FIELD NAME SIZE TYPE DESCRIPTION memoh18_edinh 30 CHAR HEADER MEMO 18. memoh19_edinh 30 CHAR HEADER MEMO 19. memoh20_edinh 30 CHAR HEADER MEMO 20 - SHIP VIA CODE. memoh21_edinh 30 CHAR HEADER MEMO 21. memoh22_edinh 30 CHAR HEADER MEMO 22. memoh23_edinh 30 CHAR HEADER MEMO 23. memoh24_edinh 30 CHAR HEADER MEMO 24. memoh25_edinh 30 CHAR HEADER MEMO 25. memoh26_edinh 30 CHAR HEADER MEMO 26. memoh27_edinh 30 CHAR HEADER MEMO 27. memoh28_edinh 30 CHAR HEADER MEMO 28. memoh29_edinh 30 CHAR HEADER MEMO 29. memoh30_edinh 30 CHAR HEADER MEMO 30. memoh31_edinh 30 CHAR HEADER MEMO 31. memoh32_edinh 30 CHAR HEADER MEMO 32. memoh33_edinh 30 CHAR HEADER MEMO 33. memoh34_edinh 30 CHAR HEADER MEMO 34. memoh35_edinh 30 CHAR HEADER MEMO 35. memoh36_edinh 30 CHAR HEADER MEMO 36. memoh37_edinh 30 CHAR HEADER MEMO 37. memoh38_edinh 30 CHAR HEADER MEMO 38. memoh39_edinh 30 CHAR HEADER MEMO 39. memoh40_edinh 30 CHAR HEADER MEMO 40. memohd01_edinh 4 DATE default 01/01/1980 memohd02_edinh 4 DATE default 01/01/1980 memohd03_edinh 4 DATE default 01/01/1980 memohd04_edinh 4 DATE default 01/01/1980 memohd05_edinh 4 DATE default 01/01/1980 memohd06_edinh 4 DATE default 01/01/1980 memohd07_edinh 4 DATE default 01/01/1980 memohd08_edinh 4 DATE default 01/01/1980 memohd09_edinh 4 DATE default 01/01/1980 memohd10_edinh 4 DATE default 01/01/1980 memohn01_edinh 10 DEC HEADER MEMO 1 memohn02_edinh 10 DEC HEADER MEMO 2 memohn03_edinh 10 DEC HEADER MEMO 3 memohn04_edinh 10 DEC HEADER MEMO 4 memohn05_edinh 10 DEC HEADER MEMO 5 memohn06_edinh 10 DEC HEADER MEMO 6 memohn07_edinh 10 DEC HEADER MEMO 7 memohn08_edinh 10 DEC HEADER MEMO 8 memohn09_edinh 10 DEC HEADER MEMO 9 memohn10_edinh 10 DEC HEADER MEMO10 branchimpt_edinh 1 CHAR BRANCH INPUT OVERRIDE FIELD NOTE: if the field is not included in the ascii or excel file (or is null), the system will set the branch id to the branch id in the customer master table of the sold to id or the branch id in the validated ship to master. Also, the branch id is not included in the fixed-format ascii file though it can be included in ascii files with a heading line (similar to the import). Indexes: Index on serial_edinh. Index on edi_ordnum_edinh. Index on soldto_edinh, edi_ordnum_edinh. Index on shipto_edinh, edi_ordnum_edinh. Index on partnrid_edinh, cust_po_edinh. Index on batch_edinh, edi_ordnum_edinh. Release NGS-7.00 EDI- 80

81 Index on flag_edinh. Index on status1_edinh. Index on custid_edinh, cust_po_edinh Release NGS-7.00 EDI- 81

82 D2. EDIND - EDI INBOUND PURCHASE ORDER DETAIL TABLE - this file is created after the ascii, excel or XML files are successfully (U)ploaded from the EDIPOLD program function. FIELD NAME SIZE TYPE DESCRIPTION serial_hdr_edind 4 INT SERIAL NUMBER ASSIGNED TO HEADER RECORD. serial_det_edind 4 SERIAL SERIAL NUMBER ASSIGNED TO DETAIL RECORD. batch_edind 2 SMINT EDI BATCH NUMBER. partnrid_edind 27 CHAR TRADING PARTNER'S ID OR MAILBOX NUMBER. ponumber_edind 22 CHAR CUSTOMER P/O NUMBER. polineno_edind 4 CHAR CUSTOMER P/O SEQUENCE NUMBER. The customer's p/o line item number. custpart1_edind 18 CHAR CUSTOMER PART ID. custpart2_edind 18 CHAR CUSTOMER PART ID 2. upc_edind 25 CHAR UPC CODE. sellitem_edind 25 CHAR ITEM ID. (The seller's item id.) desc_edind 18 CHAR ITEM DESCRIPTION. qtyord_edind 10 DEC QUANTITY ORDERED. altqtyord_edind 10 DEC ALTERNATE QUANTITY ORDERED. orgprice_edind 10 DEC SELLING PRICE. (price the customer wants to pay) altorgprc_edind 10 DEC ALTERNATE ORIGINAL PRICE. retailprc_edind 10 DEC RETAIL PRICE. (price cust. wants to sell the goods) freight_edind 10 DEC FREIGHT AMOUNT. ($ amt. cust allows for freight) spcsrv1_edind 8 CHAR SPECIAL INSTRUCTIONS - LINE 1. spcsrv2_edind 8 CHAR SPECIAL INSTRUCTIONS - LINE 2. delins1_edind 60 CHAR DELIVERY NOTES - LINE 1. delins2_edind 60 CHAR DELIVERY NOTES - LINE 2. memo1_edind 30 CHAR MEMO 1 (ALPHA). memo2_edind 30 CHAR MEMO 2 (ALPHA) memo3_edind 10 CHAR MEMO 3 (ALPHA) memo4_edind 10 DEC MEMO 4 (NUMERIC). memo5_edind 4 DATE MEMO 5 (DATE) itemidov_edind 2 CHAR ITEM ID MANUAL OVERRIDE FLAG. custpartid_edind 20 CHAR VALIDATED CUSTOMER PART ID. lineno_edind 4 INT EDI ASSIGNED LINE NUMBER (incremented by 10). subno_edind 4 CHAR EDI ASSIGNED INTERNAL SUB NUMBER. itemid_edind 18 CHAR VALIDATED ITEM ID. desc1_edind 30 CHAR VALIDATED ITEM DESCRIPTION uom_edind 2 CHAR UNIT OF MEASURE. altuom_edind 2 CHAR ALTERNATE UNIT OF MEASURE altconv_edind 10 DEC ALTERNATE CONVERSION FACTOR. sellprice_edind 10 DEC VALIDATED SELLING PRICE. altsellprc_edind 10 DEC ALTERNATE SELLING PRICE. grossext_edind 10 DEC GROSS EXTENSION. netext_edind 10 DEC NET EXTENSION. priceuom_edind 2 CHAR PRICING UNIT OF MEASURE. pruomcnv_edind 10 DEC PRICING UNIT OF MEASURE CONVERT FACTOR. ediordnum_edind 10 CHAR TEMPORARY EDI ORDER NUMBER misordnum_edind 10 CHAR ORDER NUMBER GENERATED flag_edind 4 CHAR INTERNAL UPLOAD FLAG. status_edind 2 CHAR LINE ITEM STATUS CODE. sysdate_edind 4 DATE SYSTEM DATE. systime_edind 8 CHAR SYSTEM TIME. memod1_edind 30 CHAR DETAIL MEMO 1. memod2_edind 30 CHAR DETAIL MEMO 2 memod3_edind 30 CHAR DETAIL MEMO 3. memod4_edind 30 CHAR DETAIL MEMO 4. memod5_edind 30 CHAR DETAIL MEMO 5. Release NGS-7.00 EDI- 82

83 FIELD NAME SIZE TYPE DESCRIPTION memod6_edind 30 CHAR DETAIL MEMO 6. memod7_edind 30 CHAR DETAIL MEMO 7. memod8_edind 30 CHAR DETAIL MEMO 8. memod9_edind 30 CHAR DETAIL MEMO 9. memod10_edind 30 CHAR DETAIL MEMO 10. memod11_edind 30 CHAR DETAIL MEMO 11. memod12_edind 30 CHAR DETAIL MEMO 12. memod13_edind 30 CHAR DETAIL MEMO 13. memod14_edind 30 CHAR DETAIL MEMO 14. memod15_edind 30 CHAR DETAIL MEMO 15. memod16_edind 30 CHAR DETAIL MEMO 16. memod17_edind 30 CHAR DETAIL MEMO 17. memod18_edind 30 CHAR DETAIL MEMO 18. memod19_edind 30 CHAR DETAIL MEMO 19. memod20_edind 30 CHAR DETAIL MEMO 20 - ITEM MEMO 1. memod21_edind 30 CHAR DETAIL MEMO 21 - ITEM MEMO 2. memod22_edind 30 CHAR DETAIL MEMO 22 DETAIL EDI SOLD TO ID. memod23_edind 30 CHAR DETAIL MEMO 23 DETAIL EDI SHIP TO ID. memod24_edind 30 CHAR DETAIL MEMO 24. memod25_edind 30 CHAR DETAIL MEMO 25. memod26_edind 30 CHAR DETAIL MEMO 26. memod27_edind 30 CHAR DETAIL MEMO 27. memod28_edind 30 CHAR DETAIL MEMO 28. memod29_edind 30 CHAR DETAIL MEMO 29. memod30_edind 30 CHAR DETAIL MEMO 30. memod31_edind 30 CHAR DETAIL MEMO 31. memod32_edind 30 CHAR DETAIL MEMO 32. memod33_edind 30 CHAR DETAIL MEMO 33. memod34_edind 30 CHAR DETAIL MEMO 34. memod35_edind 30 CHAR DETAIL MEMO 35. memod36_edind 30 CHAR DETAIL MEMO 36. memod37_edind 30 CHAR DETAIL MEMO 37. memod38_edind 30 CHAR DETAIL MEMO 38. memod39_edind 30 CHAR DETAIL MEMO 39. memod40_edind 30 CHAR DETAIL MEMO 40. memodd01_edind 4 DATE default 01/01/1980 memodd02_edind 4 DATE default 01/01/1980 memodd03_edind 4 DATE default 01/01/1980 memodd04_edind 4 DATE default 01/01/1980 memodd05_edind 4 DATE default 01/01/1980 memodd06_edind 4 DATE default 01/01/1980 memodd07_edind 4 DATE default 01/01/1980 memodd08_edind 4 DATE default 01/01/1980 memodd09_edind 4 DATE default 01/01/1980 memodd10_edind 4 DATE default 01/01/1980 memodn01_edind 10 DEC DETAIL MEMO 1 memodn02_edind 10 DEC DETAIL MEMO 2 memodn03_edind 10 DEC DETAIL MEMO 3 memodn04_edind 10 DEC DETAIL MEMO 4 memodn05_edind 10 DEC DETAIL MEMO 5 memodn06_edind 10 DEC DETAIL MEMO 6 memodn07_edind 10 DEC DETAIL MEMO 7 memodn08_edind 10 DEC DETAIL MEMO 8 memodn09_edind 10 DEC DETAIL MEMO 9 memodn10_edind 10 DEC DETAIL MEMO10 sellprcovrd_edind 1 CHAR [N] Release NGS-7.00 EDI- 83

84 upcload_qty_edind 10 DEC DETAIL MEMO 1 - converted quantity from UPCLOAD program upcload_cnv_edind 10 DEC DETAIL MEMO 2 - conversion factor from UPCLOAD program Indexes: Index on serial_hdr_edind. Index on ediordnum_edind, itemid_edind. Index on ediordnum_edind, lineno_edind, subno_edind. Index on partnrid_edind, ponumber_edind, polineno_edind. Index on misordnum_edind, lineo_edind. Index on serial_det_edind. Release NGS-7.00 EDI- 84

85 D3. ORDERC - EDI ORDER HEADER FILE. FIELD NAME SIZE TYPE DESCRIPTION invnum_orderc 10 CHAR INVOICE NUMBER ordnum_orderc 10 CHAR ORDER NUMBER batch_orderc 2 SMINT EDI BATCH NUMBER partnrid_orderc 27 CHAR TRADING PARTNER ID / MAILBOX NUMBER billto_orderc 35 CHAR BILL TO ID soldto_orderc 35 CHAR SOLD TO ID shipto_orderc 35 CHAR SHIP TO ID bslook_orderc 35 CHAR SHIP TO ID INDICATO Rtrandate_orderc 4 DATE TRANSACTION DATE reqdate_orderc 4 DATE REQUESTED DATE shipdate_orderc 4 DATE SHIP DATE canceldte_orderc 4 DATE CANCEL DATE podate_orderc 4 DATE PURCHASE ORDER DATE. cust_po_orderc 22 CHAR CUSTOMER P/O NUMBER. pobatch_orderc 10 CHAR CUSTOMER PURCHASE ORDER BATCH. refno_orderc 30 CHAR REFERENCE NUMBER. dept_orderc 30 CHAR DEPARTMENT NUMBER. remarks_orderc 80 CHAR REMARKS. media_orderc 2 CHAR MEDIA/EVENT CODE. shipname_orderc 35 CHAR SHIP TO NAME shipaddr1_orderc 35 CHAR SHIP TO ADDRESS 1. shipaddr2_orderc 35 CHAR SHIP TO ADDRESS 2. shipaddr3_orderc 35 CHAR SHIP TO ADDRESS 3. shipcity_orderc 19 CHAR SHIP TO CITY. shipstate_orderc 4 CHAR SHIP TO STATE. shipcntry_orderc 10 CHAR SHIP TO COUNTRY. shipzip_orderc 9 CHAR SHIP TO ZIP CODE. shipattn_orderc 27 CHAR SHIP TO ATTENTION. markfor_orderc 45 CHAR MARK FOR. terms_cd_orderc 4 CHAR TERMS CODE. transcd_orderc 2 CHAR TRANSACTION CODE transtype_orderc 2 CHAR TRANSACTION TYPE contract_orderc 12 CHAR CONTRACT NUMBER. routing_orderc 2 CHAR ROUTING CODE. scac_orderc 4 CHAR SCAC CODE. asnflag_orderc 2 CHAR ASN GENERATION FLAG. asndate_orderc 4 DATE ASN GENERATION DATE. asntime_orderc 8 CHAR ASN GENERATION TIME. asnuser_orderc 8 CHAR ASN GENERATION USER. asnbatch_orderc 4 INT ASN GENERATION BATCH NUMBER. invflag_orderc 2 CHAR INVOICE GENERATION FLAG. invdate_orderc 4 DATE INVOICE GENERATION DATE. invtime_orderc 8 CHAR INVOICE GENERATION TIME. invuser_orderc 8 CHAR INVOICE GENERATION USER. invbatch_orderc 10 CHAR INVOICE GENERATION BATCH NUMBER. memo1_orderc 30 CHAR MEMO 1 (ALPHA) memo2_orderc 30 CHAR MEMO 2 (ALPHA) memo3_orderc 10 CHAR MEMO 3 (ALPHA) memo4_orderc 10 DEC MEMO 4 (NUMERIC). memo5_orderc 4 DATE MEMO 5 (DATE). memoh1_orderc 30 CHAR HEADER MEMO 1. memoh2_orderc 30 CHAR HEADER MEMO 2. memoh3_orderc 30 CHAR HEADER MEMO 3. memoh4_orderc 30 CHAR HEADER MEMO 4. memoh5_orderc 30 CHAR HEADER MEMO 5. Release NGS-7.00 EDI- 85

86 FIELD NAME SIZE TYPE DESCRIPTION memoh6_orderc 30 CHAR HEADER MEMO 6. memoh7_orderc 30 CHAR HEADER MEMO 7. memoh8_orderc 30 CHAR HEADER MEMO 8. memoh9_orderc 30 CHAR HEADER MEMO 9. memoh10_orderc 30 CHAR HEADER MEMO 10. memoh11_orderc 30 CHAR HEADER MEMO 11. memoh12_orderc 30 CHAR HEADER MEMO 12. memoh13_orderc 30 CHAR HEADER MEMO 13. memoh14_orderc 30 CHAR HEADER MEMO 14. memoh15_orderc 30 CHAR HEADER MEMO 15. memoh16_orderc 30 CHAR HEADER MEMO 16. memoh17_orderc 30 CHAR HEADER MEMO 17. memoh18_orderc 30 CHAR HEADER MEMO 18. memoh19_orderc 30 CHAR HEADER MEMO 19. memoh20_orderc 30 CHAR HEADER MEMO 20 - SHIP VIA CODE. memoh21_orderc 30 CHAR HEADER MEMO 21. memoh22_orderc 30 CHAR HEADER MEMO 22. memoh23_orderc 30 CHAR HEADER MEMO 23. memoh24_orderc 30 CHAR HEADER MEMO 24. memoh25_orderc 30 CHAR HEADER MEMO 25. memoh26_orderc 30 CHAR HEADER MEMO 26. memoh27_orderc 30 CHAR HEADER MEMO 27. memoh28_orderc 30 CHAR HEADER MEMO 28. memoh29_orderc 30 CHAR HEADER MEMO 29. memoh30_orderc 30 CHAR HEADER MEMO 30. memoh31_orderc 30 CHAR HEADER MEMO 31. memoh32_orderc 30 CHAR HEADER MEMO 32. memoh33_orderc 30 CHAR HEADER MEMO 33. memoh34_orderc 30 CHAR HEADER MEMO 34. memoh35_orderc 30 CHAR HEADER MEMO 35. memoh36_orderc 30 CHAR HEADER MEMO 36. memoh37_orderc 30 CHAR HEADER MEMO 37. memoh38_orderc 30 CHAR HEADER MEMO 38. memoh39_orderc 30 CHAR HEADER MEMO 39. memoh40_orderc 30 CHAR HEADER MEMO 40. memohd01_orderc 4 DATE default 01/01/1980 memohd02_orderc 4 DATE default 01/01/1980 memohd03_orderc 4 DATE default 01/01/1980 memohd04_orderc 4 DATE default 01/01/1980 memohd05_orderc 4 DATE default 01/01/1980 memohd06_orderc 4 DATE default 01/01/1980 memohd07_orderc 4 DATE default 01/01/1980 memohd08_orderc 4 DATE default 01/01/1980 memohd09_orderc 4 DATE default 01/01/1980 memohd10_orderc 4 DATE default 01/01/1980 memohn01_orderc 10 DEC HEADER MEMO 1 memohn02_orderc 10 DEC HEADER MEMO 2 memohn03_orderc 10 DEC HEADER MEMO 3 memohn04_orderc 10 DEC HEADER MEMO 4 memohn05_orderc 10 DEC HEADER MEMO 5 memohn06_orderc 10 DEC HEADER MEMO 6 memohn07_orderc 10 DEC HEADER MEMO 7 memohn08_orderc 10 DEC HEADER MEMO 8 memohn09_orderc 10 DEC HEADER MEMO 9 memohn10_orderc 10 DEC HEADER MEMO10 Release NGS-7.00 EDI- 86

87 Indexes: Index on ordnum_orderc. Index on partnrid_orderc, cust_po_orderc. Index on batch_orderc, ordnum_orderc. Release NGS-7.00 EDI- 87

88 D4. ORDDET2 - EDI ORDER DETAIL FILE. FIELD NAME SIZE TYPE DESCRIPTION ordnum_orddet2 10 CHAR ORDER NUMBER. invnum_orddet2 10 CHAR INVOICE NUMBER. lineno_orddet2 4 INT LINE NUMBER. subno_orddet2 4 CHAR SUB NUMBER. batch_orddet2 2 SMINT EDI BATCH NUMBER. partnrid_orddet2 27 CHAR TRADING PARTNER'S ID OR MAILBOX NUMBER. ponumber_orddet2 22 CHAR CUSTOMER P/O NUMBER. polineno_orddet2 4 CHAR CUSTOMER P/O SEQUENCE NUMBER. custprt1_orddet2 18 CHAR CUSTOMER PART ID. custprt2_orddet2 18 CHAR CUSTOMER PART ID 2 upc_orddet2 25 CHAR UPC CODE. sellitem_orddet2 25 CHAR ITEM ID. desc_orddet2 18 CHAR ITEM DESCRIPTION. qtyord_orddet2 10 DEC QUANTITY ORDERED. altqtyord_orddet2 10 DEC ALTERNATE QUANTITY ORDERED. uom_orddet2 2 CHAR UNIT OF MEASURE. altuom_orddet2 2 CHAR ALTERNATE UNIT OF MEASURE. orgprice_orddet2 10 DEC ORIGINAL SELLING PRICE. altorgprc_orddet2 10 DEC ALTERNATE ORIGINAL SELLING PRICE. altsellpr_orddet2 10 DEC ALTERNATE SELLING PRICE. retailprc_orddet2 10 DEC RETAIL PRICE. freight_orddet2 10 DEC FREIGHT AMOUNT. spcsrv1_orddet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 1. spcsrv2_orddet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 2. delins1_orddet2 60 CHAR DELIVERY NOTES - LINE 1. delins2_orddet2 60 CHAR DELIVERY NOTES - LINE 2. memo1_orddet2 30 CHAR MEMO 1 (ALPHA). memo2_orddet2 30 CHAR MEMO 2 (ALPHA). memo3_orddet2 10 CHAR MEMO 3 (ALPHA). memo4_orddet2 10 DEC MEMO 4 (NUMERIC). memo5_orddet2 4 DATE MEMO 5 (DATE). memod1_orddet2 30 CHAR DETAIL MEMO 1. memod2_orddet2 30 CHAR DETAIL MEMO 2. memod3_orddet2 30 CHAR DETAIL MEMO 3. memod4_orddet2 30 CHAR DETAIL MEMO 4. memod5_orddet2 30 CHAR DETAIL MEMO 5. memod6_orddet2 30 CHAR DETAIL MEMO 6. memod7_orddet2 30 CHAR DETAIL MEMO 7. memod8_orddet2 30 CHAR DETAIL MEMO 8. memod9_orddet2 30 CHAR DETAIL MEMO 9. memod10_orddet2 30 CHAR DETAIL MEMO 10. memod11_orddet2 30 CHAR DETAIL MEMO 11. memod12_orddet2 30 CHAR DETAIL MEMO 12. memod13_orddet2 30 CHAR DETAIL MEMO 13. memod14_orddet2 30 CHAR DETAIL MEMO 14. memod15_orddet2 30 CHAR DETAIL MEMO 15. memod16_orddet2 30 CHAR DETAIL MEMO 16. memod17_orddet2 30 CHAR DETAIL MEMO 17. memod18_orddet2 30 CHAR DETAIL MEMO 18. memod19_orddet2 30 CHAR DETAIL MEMO 19. memod20_orddet2 30 CHAR DETAIL MEMO 20 - ITEM MEMO 1. memod21_orddet2 30 CHAR DETAIL MEMO 21 - ITEM MEMO 2. memod22_orddet2 30 CHAR DETAIL MEMO 22 DETAIL EDI SOLD TO ID. memod23_orddet2 30 CHAR DETAIL MEMO 23. memod24_orddet2 30 CHAR DETAIL MEMO 24. Release NGS-7.00 EDI- 88

89 FIELD NAME SIZE TYPE DESCRIPTION memod25_orddet2 30 CHAR DETAIL MEMO 25. memod26_orddet2 30 CHAR DETAIL MEMO 26. memod27_orddet2 30 CHAR DETAIL MEMO 27. memod28_orddet2 30 CHAR DETAIL MEMO 28. memod29_orddet2 30 CHAR DETAIL MEMO 29. memod30_orddet2 30 CHAR DETAIL MEMO 30. memod31_orddet2 30 CHAR DETAIL MEMO 31. memod32_orddet2 30 CHAR DETAIL MEMO 32. memod33_orddet2 30 CHAR DETAIL MEMO 33. memod34_orddet2 30 CHAR DETAIL MEMO 34. memod35_orddet2 30 CHAR DETAIL MEMO 35. memod36_orddet2 30 CHAR DETAIL MEMO 36. memod37_orddet2 30 CHAR DETAIL MEMO 37. memod38_orddet2 30 CHAR DETAIL MEMO 38. memod39_orddet2 30 CHAR DETAIL MEMO 39. memod40_orddet2 30 CHAR DETAIL MEMO 40. memodd01_orddet2 4 DATE default 01/01/1980 memodd02_orddet2 4 DATE default 01/01/1980 memodd03_orddet2 4 DATE default 01/01/1980 memodd04_orddet2 4 DATE default 01/01/1980 memodd05_orddet2 4 DATE default 01/01/1980 memodd06_orddet2 4 DATE default 01/01/1980 memodd07_orddet2 4 DATE default 01/01/1980 memodd08_orddet2 4 DATE default 01/01/1980 memodd09_orddet2 4 DATE default 01/01/1980 memodd10_orddet2 4 DATE default 01/01/1980 memodn01_orddet2 10 DEC DETAIL MEMO 1 memodn02_orddet2 10 DEC DETAIL MEMO 2 memodn03_orddet2 10 DEC DETAIL MEMO 3 memodn04_orddet2 10 DEC DETAIL MEMO 4 memodn05_orddet2 10 DEC DETAIL MEMO 5 memodn06_orddet2 10 DEC DETAIL MEMO 6 memodn07_orddet2 10 DEC DETAIL MEMO 7 memodn08_orddet2 10 DEC DETAIL MEMO 8 memodn09_orddet2 10 DEC DETAIL MEMO 9 memodn10_orddet2 10 DEC DETAIL MEMO10 sellprcovrd_orddet2 1 CHAR [N] upcload_qty_orddet2 10 DEC DETAIL MEMO 1 - converted quantity from UPCLOAD program upcload_cnv_orddet2 10 DEC DETAIL MEMO 2 - conversion factor from UPCLOAD program Indexes: Index on ordnum_orddet2, lineno_orddet2, subno_orddet2. Index on partnrid_orddet2, ponumber_orddet2, polineno_orddet2. Release NGS-7.00 EDI- 89

90 E - INBOUND CUSTOMER PURCHASE ORDER ASCII FILE DEFINITION (850) The following is a layout of the fields in the inbound ASCII file in field number sequence to be uploaded to the EDI uploaded file. All fields must be left justified. Fields 1 to 77 are header fields and will be mapped to the EDI Inbound Header Table (edinh). Fields 78 to 139 are detail fields and will be mapped to the EDI Inbound Detail Table (edind). For each trading partner / purchase order uploaded (based on the combination of fields 1 and 11), the first record will generate one EDI Inbound Header Table record. The assumption is that the header fields will be identical for all detail records with the same trading partner id / mailbox number and customer purchase order number. Once the header record is generated, the EDI Inbound Detail Table records will be generated for all lines with the same trading partner / purchase order number (based on header field 1 matching detail file 78 and header field 11 matching detail field 79). Also, depending on the setting for ACF option "edinfmt", records can also be generated on a trading partner / purchase order number / sold to id basis (based on header field 1 matching detail field 78, header field 11 matching detail field 79 and header field 3 matching detail field 121). This allows you to generate separate transactions for different sold to customers for the same purchase order. The assumption is that the header fields will be identical for all detail records with the same trading partner id / mailbox number, customer purchase order number and dsold to id. INBOUND ASCII FILE LAYOUT # FIELD DESCRIPTION TYPE SIZE NOTES 1. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 **REQUIRED**. 2. BILL TO ID. CHAR SOLD TO ID. CHAR SHIP TO ID. CHAR BS LOOK SHIP TO ID INDICATOR. CHAR TRANSACTION DATE. DATE 6 "MMDDYY". 7. REQUESTED DATE. DATE 6 "MMDDYY". 8. SHIP DATE. DATE 6 "MMDDYY". 9. CANCEL DATE. DATE 6 "MMDDYY". 10. PURCHASE ORDER DATE. DATE 6 "MMDDYY" **REQUIRED** 11. CUSTOMER P/O NUMBER. CHAR 22 **REQUIRED**. 12. CUSTOMER PURCHASE ORDER BATCH NBR CHAR REFERENCE NUMBER. CHAR DEPARTMENT. CHAR REMARKS. CHAR MEDIA/EVENT CODE. CHAR SHIP TO NAME. CHAR SHIP TO ADDRESS 1. CHAR SHIP TO ADDRESS 2. CHAR SHIP TO ADDRESS 3. CHAR SHIP TO CITY. CHAR SHIP TO STATE. CHAR SHIP TO COUNTRY. CHAR SHIP TO ZIP CODE. CHAR SHIP TO ATTENTION. CHAR MARK FOR. CHAR TERMS CODE. CHAR TRANSACTION CODE. CHAR 2 "OR, RM, DS" - *REQ D* depends on transtype assignment in EDITPM table for the TP 29. TRANSACTION TYPE. CHAR 2 "00" or "W3"" *REQUIRED* 30. CONTRACT NUMBER. CHAR 12 Release NGS-7.00 EDI- 90

91 # FIELD DESCRIPTION TYPE SIZE NOTES 31. ROUTING. CHAR SCAC. CHAR MEMO1. CHAR 30 phone# (W3) 34. MEMO2. CHAR MEMO3. CHAR MEMO4 (NUMERIC -XXXXXX.XX) DEC 10 Freight Charge (W3) 37. MEMO5 (DATE). DATE 6 "MMDDYY". 38. HEADER MEMO 1. CHAR 30 CC Authorization (W3) 39. HEADER MEMO 2. CHAR 30 CC Number (W3) 40. HEADER MEMO 3. CHAR 30 CC Expire Dt. MMYY (W3) 41. HEADER MEMO 4. CHAR 30 Name on CC (W3) 42. HEADER MEMO 5. CHAR 30 CC type (MC, Visa) (W3) 43. HEADER MEMO 6. CHAR 30 Sold to Name (W3) 44. HEADER MEMO 7. CHAR 30 Sold to Attn Line (W3) 45. HEADER MEMO 8. CHAR 30 Sold to Addr line 1 (W3) 46. HEADER MEMO 9. CHAR 30 Sold to Addr line 2 (W3) 47. HEADER MEMO 10. CHAR 30 Sold to City (W3) 48. HEADER MEMO 11. CHAR 30 Sold to State (W3) 49. HEADER MEMO 12. CHAR 30 Sold to Zip (W3) 50. HEADER MEMO 13. CHAR 30 Sold to Country Code (W3) 51. HEADER MEMO 14. CHAR HEADER MEMO 15. CHAR HEADER MEMO 16. CHAR HEADER MEMO 17. CHAR HEADER MEMO 18. CHAR HEADER MEMO 19. CHAR HEADER MEMO 20 CHAR 30 SHIP VIA CODE. 58. HEADER MEMO 21. CHAR 30 ROUTE CODE 59. HEADER MEMO 22. CHAR 30 Transaction ID web CC (W3) pre- approval 60. HEADER MEMO 23. CHAR 30 $ amt charged to card (W3) 61. HEADER MEMO 24. CHAR 30 Trade Disc $ amt. (W3) 62. HEADER MEMO 25. CHAR HEADER MEMO 26. CHAR HEADER MEMO 27. CHAR HEADER MEMO 28. CHAR HEADER MEMO 29. CHAR HEADER MEMO 30. CHAR HEADER MEMO 31. CHAR HEADER MEMO 32. CHAR HEADER MEMO 33. CHAR HEADER MEMO 34. CHAR HEADER MEMO 35. CHAR HEADER MEMO 36. CHAR HEADER MEMO 37. CHAR HEADER MEMO 38. CHAR HEADER MEMO 39. CHAR HEADER MEMO 40. CHAR 30 ************* field 78 thru 139 are the detail portion of the ascii input file ****************** 78. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 **REQUIRED** must be same as fld # CUSTOMER P/O NUMBER. CHAR 22 **REQUIRED** must be same as fld # CUSTOMER P/O SEQUENCE NUMBER. CHAR CUSTOMER PART ID. CHAR CUSTOMER PART ID 2. CHAR UPC CODE. CHAR 25 Release NGS-7.00 EDI- 91

92 84. ITEM ID. CHAR 25 # FIELD DESCRIPTION TYPE SIZE NOTE 85. ITEM DESCRIPTION. CHAR QUANTITY ORDERED. DEC 10 "-XXXXXX.XX" **Required** 87. UNIT OF MEASURE. CHAR SELLING PRICE. DEC 10 "-XXXXXX.XX" **Required** 89. RETAIL PRICE. DEC 10 Numeric "-XXXXXX.XX" 90. FREIGHT AMOUNT. DEC 10 Numeric "-XXXXXX.XX" 91. SPECIAL INSTRUCTIONS - LINE 1. CHAR SPECIAL INSTRUCTIONS - LINE 2. CHAR DELIVERY NOTES - LINE 1. CHAR DELIVERY NOTES - LINE 2. CHAR MEMO 1. CHAR MEMO 2. CHAR MEMO 3. CHAR MEMO 4 (NUMERIC). DEC 10 Numeric "-XXXXXX.XX" 99. MEMO 5 (DATE). DATE 6 Date "MMDDYY" DETAIL MEMO 1. CHAR DETAIL MEMO 2. CHAR DETAIL MEMO 3. CHAR DETAIL MEMO 4. CHAR DETAIL MEMO 5. CHAR DETAIL MEMO 6. CHAR DETAIL MEMO 7. CHAR DETAIL MEMO 8. CHAR DETAIL MEMO 9. CHAR DETAIL MEMO 10. CHAR DETAIL MEMO 11. CHAR DETAIL MEMO 12. CHAR DETAIL MEMO 13. CHAR DETAIL MEMO 14. CHAR DETAIL MEMO 15. CHAR DETAIL MEMO 16. CHAR DETAIL MEMO 17. CHAR DETAIL MEMO 18. CHAR DETAIL MEMO 19. CHAR DETAIL MEMO 20 - ITEM MEMO 1. CHAR DETAIL MEMO 21 - ITEM MEMO 2. CHAR DETAIL MEMO 22 - DETAIL EDI SOLDTO CHAR 30 See ACF 'edinfmt' for usage format codes = 0, 1, DETAIL MEMO 23. CHAR DETAIL MEMO 24. CHAR DETAIL MEMO 25. CHAR DETAIL MEMO 26. CHAR DETAIL MEMO 27. CHAR DETAIL MEMO 28. CHAR DETAIL MEMO 29. CHAR DETAIL MEMO 30. CHAR DETAIL MEMO 31. CHAR DETAIL MEMO 32. CHAR DETAIL MEMO 33. CHAR DETAIL MEMO 34. CHAR DETAIL MEMO 35. CHAR DETAIL MEMO 36. CHAR DETAIL MEMO 37. CHAR DETAIL MEMO 38. CHAR DETAIL MEMO 39. CHAR DETAIL MEMO 40. CHAR 30 Release NGS-7.00 EDI- 92

93 Field Types: CHAR - Character - Alpha-numeric characters. DATE - Date - Must be in format "MMDDYY". If field will not be used or is not valued, use the system default date ("010180"). DEC - Decimal - Numeric field with at least one position to the left and 2 positions to the right of the decimal point with leading minus sign (if applicable). General Requirements: - File must be in ASCII format. - All records must have each field delineated by a pipe symbol (<174> ASCII character which is represented as ). - All records must be terminated with a <CARRIAGE RETURN><LINE FEED> (<13><10>). - All dates must be in the format: "MMDDYY". For example, January 8, 1995 must be - "010895". - All date fields must be valued; if a date field is not valued or will not be used, set the date field to January 1, 1980 ("010180"). - All alphanumeric (CHAR) fields must be left-justified. - All quantities and prices must be in decimal format: "-XXXXXX.XX". Signed numeric fields must contain the sign in front of the number. Decimal point must be included and contain at least one digit to the left and two digits to the right of the decimal point (i.e ). Blanks before any number are assumed to be positive. Release NGS-7.00 EDI- 93

94 G - EDI INBOUND P. O. HEADER TABLE MAPPING (EDINH) TO ORDER TABLES FIELD NAME DESTINATION MAPPING serial_edinh None. batch_edinh batch_orderc. partnrid_edinh soldxref_ordera. 25 characters. partnrid_orderc. billto_edinh billto_orderc. soldto_edinh soldto_orderc. shipto_edinh shipto_orderc bslook_edinh bslook_orderc. transdate_edinh transdate_orderb. trandate_orderc. reqdate_edinh reqdate_orderb. reqdate_orderc. reqdate_orddet. shipdate_edinh shipdate_orderb. shipdate_orderc. canceldate_edinh canceldt_orderb. canceldate_orderc. podate_edinh podate_orderb. podate_orderc. cust_po_edinh cust_po_ordera. 20 characters. miscinf1_ordera. 22 characters. cust_po_orderc. pobatch_edinh pobatch_orderc refno_edinh refno_orderc. dept_edinh memo1_orderb. remarks_edinh remarks_orderb. 25 characters. remarks_orderc.media_edinh media_orderc. shipname_edinh shipname_ordera. 27 characters. shipname_orderc. shipaddr1_edinh shipadr1_ordera. 27 characters. shipaddr1_orderc. shipaddr2_edinh shipadr2_ordera. 27 characters. shipaddr2_orderc. shipaddr3_edinh shipadr3_ordera. 27 characters. shipaddr3_orderc. shipcity_edinh shipcity_ordera. 18 characters. shipcity_orderc. shipstate_edinh shipstate_ordera. 4 characters. shipstate_orderc. shipcntry_edinh shipcntry_ordera. 10 characters. shipcntry_orderc. shipzip_edinh shipzip_ordera. 10 characters. shipzip_orderc. shipattn_edinh shipattn_ordera. 27 characters. shipattn_orderc. shipphone_edinh None. shipfax_ediinh None. Release NGS-7.00 EDI- 94

95 FIELD NAME DESTINATION MAPPING markfor_edinh markfor_orderb. 25 characters. markfor_orderc. terms_cd_edinh terms_cd_orderc. transcd_edinh transcd_orderc. transtype_edinh trantype_orderc. contract_edinh contract_orderc. routing_edinh routing_orderc. scac_edinh scac_orderc. memo1_edinh memo1_orderc. memo2_edinh memo2_orderc. memo3_edinh memo3_orderc. memo4_edinh memo4_orderc. memo5_edinh memo5_orderc. custid_edinh soldto_ordera. shipid_edinh shipto_ordera. valueflag_edinh None. poduplov_edinh None. podateov_edinh None. custidov_edinh None. shipidov_edinh None. flag_edinh None. status1_edinh None. status2_edinh None. mis_ordnum_edinh ordnum_orderc. edi_ordnum_edinh None. division_edinh division_orderb. branch_edinh branch_orderb. branch_orddet. grossext_edinh None. netext_edinh None. loaddate_edinh None. validdate_edinh None. createdate_edinh None. sysdate_edinh None. systime_edinh None. userid_edinh None. ttyname_edinh None. memoh1_edinh memoh1_orderc memoh2_edinh memoh2_orderc memoh3_edinh memoh3_orderc memoh4_edinh memoh4_orderc memoh5_edinh memoh5_orderc memoh6_edinh memoh6_orderc memoh7_edinh memoh7_orderc memoh8_edinh memoh8_orderc memoh9_edinh memoh9_orderc memoh10_edinh memoh10_orderc memoh11_edinh memoh11_orderc memoh12_edinh memoh12_orderc memoh13_edinh memoh13_orderc memoh14_edinh memoh14_orderc Release NGS-7.00 EDI- 95

96 FIELD NAME DESTINATION MAPPING memoh15_edinh memoh15_orderc memoh16_edinh memoh16_orderc memoh17_edinh memoh17_orderc memoh18_edinh memoh18_orderc memoh19_edinh memoh19_orderc memoh20_edinh memoh20_orderc shipvia_orderb (4 characters). memoh21_edinh memoh21_orderc memoh22_edinh memoh22_orderc memoh23_edinh memoh23_orderc memoh24_edinh memoh24_orderc memoh25_edinh memoh25_orderc memoh26_edinh memoh26_orderc memoh27_edinh memoh27_orderc memoh28_edinh memoh28_orderc memoh29_edinh memoh29_orderc memoh30_edinh memoh30_orderc memoh31_edinh memoh31_orderc memoh32_edinh memoh32_orderc memoh33_edinh memoh33_orderc memoh34_edinh memoh34_orderc memoh35_edinh memoh35_orderc memoh36_edinh memoh36_orderc memoh37_edinh memoh37_orderc memoh38_edinh memoh38_orderc memoh39_edinh memoh39_orderc memoh40_edinh memoh40_orderc memohd01_edinh memohd01_orderc memohd02_ edinh memohd02_orderc memohd03_ edinh memohd03_orderc memohd04_ edinh memohd04_orderc memohd05_orderc memohd05_orderc memohd06_ edinh memohd06_orderc memohd07_ edinh memohd07_orderc memohd08_ edinh memohd08_orderc memohd09_ edinh memohd09_orderc memohd10_ edinh memohd10_orderc memohn01_ edinh memohn01_orderc memohn02_ edinh memohn02_orderc memohn03_ edinh memohn03_orderc memohn04_ edinh memohn04_orderc memohn05_ edinh memohn05_orderc memohn06_ edinh memohn06_orderc memohn07_ edinh memohn07_orderc memohn08_ edinh memohn08_orderc memohn09_ edinh memohn09_orderc memohn10_ edinh memohn10_orderc Release NGS-7.00 EDI- 96

97 H - EDI INBOUND P. O. DETAIL TABLE MAPPING (EDIND) TO ORDER TABLES FIELD NAME serial_hdr_edind serial_det_edind partnrid_edind ponumber_edind polineno_edind custpart1_edind custpart2_edind upc_edind sellitem_edind desc_edind qtyord_edind uom_edind orgprice_edind retailprc_edind freight_edind spcsrv1_edind spcsrv2_edind delins1_edind delins2_edind memo1_edind memo2_edind memo3_edind memo4_edind memo5_edind itemidov_edind custpartid_edind lineno_edind subno_edind itemid_edind desc1_edind sellprice_edind altqtyord_edind altconv_edind altuom_edind altorgprc_edind altsellprc_edind grossext_edind netext_edind priceuom_edind prcuomcnv_edind flag_edind status_edind sysdate_edind systime_edind edi_ordnum_edind DESTINATION MAPPING None. None. None. None. polineno_orddet2. custprt1_orddet2. custprt2_orddet2. upc_orddet2. sellitem_orddet2. desc_orddet2, not if original item is replaced via substitution logic in order creation, then the desc1_item will be used from substitute item. qtyord_orddet2. qtyord_orddet. altqtyord_orddet. uom_orddet2. orgprice_orddet2. retailprc_orddet2. freight_orddet2. spcsrv1_orddet2. spcsrv2_orddet2. delins1_orddet2. delins2_orddet2. memo1_orddet2. memo2_orddet2. memo3_orddet2. memo4_orddet2. memo5_orddet2. None. custpartid_orddet. lineno_orddet curmemo1_orddet (temporarily; then set to zero). lineno_orddet2 (from curmemo1_orddet before clear). None itemid_orddet. None. sellprice_orddet. altqtyord_orddet2. altconv_orddet2. altuom_orddet2. altorgprc_orddet2. altsellpr_orddet. None. None. priceuom_orddet. prcuomconv_orddet. None. None. None. None. None. Release NGS-7.00 EDI- 97

98 FIELD NAME DESTINATION MAPPING mis_ordnum_edind ordnum_orderc. memod1_edind memod1_orddet2 memod2_edind memod2_orddet2 memod3_edind memod3_orddet2 memod4_edind memod4_orddet2 memod5_edind memod5_orddet2 memod6_edind memod6_orddet2 memod7_edind memod7_orddet2 memod8_edind memod8_orddet2 memod9_edind memod9_orddet2 memod10_edind memod10_orddet2 memod11_edind memod11_orddet2 memod12_edind memod12_orddet2 memod13_edind memod13_orddet2 memod14_edind memod14_orddet2 memod15_edind memod15_orddet2 memod16_edind memod16_orddet2 memod17_edind memod17_orddet2 memod18_edind memod18_orddet2 memod19_edind memod19_orddet2 memod20_edind memod20_orddet2 imemo1_orddet 10 characters. memod21_edind memod21_orddet2 imemo2_orddet 10 characters. memod22_edind memod22_orddet2 memod23_edind memod23_orddet2 memod24_edind memod24_orddet2 memod25_edind memod25_orddet2 memod26_edind memod26_orddet2 memod27_edind memod27_orddet2 memod28_edind memod28_orddet2 memod29_edind memod29_orddet2 memod30_edind memod30_orddet2 memod31_edind memod31_orddet2 memod32_edind memod32_orddet2 memod33_edind memod33_orddet2 memod34_edind memod34_orddet2 memod35_edind memod35_orddet2 memod36_edind memod36_orddet2 memod37_edind memod37_orddet2 memod38_edind memod38_orddet2 memod39_edind memod39_orddet2 memod40_edind memod40_orddet2 memodd01_edind memodd01_orddet2 memodd02_edind memodd02_ orddet2 memodd03_edind memodd03_ orddet2 memodd04_edind memodd04_ orddet2 memodd05_edind memodd05_ orddet2 memodd06_edind memodd06_ orddet2 memodd07_edind memodd07_ orddet2 memodd08_edind memodd08_ orddet2 memodd09_edind memodd09_ orddet2 memodd10_edind memodd10_ orddet2 memodn01_edind memodn01_ orddet2 memodn02_edind memodn02_ orddet2 memodn03_edind memodn03_ orddet2 Release NGS-7.00 EDI- 98

99 memodn04_edind memodn05_edind memodn06_edind memodn07_edind memodn08_edind memodn09_edind memodn10_edind sellprcovrd_edind upcload_qty_edind upcload_cnv_edind memodn04_ orddet2 memodn05_ orddet2 memodn06_ orddet2 memodn07_ orddet2 memodn08_ orddet2 memodn09_ orddet2 memodn10_ orddet2 sellprcovrd_ orddet2 upcload_qty_orddet2 upcload_cnv_orddet2 I - ACF OPTIONS FOR THE EDI MODULE - *** view all edi options using edi* from the acf pgm *** Release NGS-7.00 EDI- 99

100 PROCESSING OUTBOUND TRANSACTIONS EDIASNG- EDI OUTBOUND ADVANCED SHIP NOTICES GENERATION A. Modification Summary. This program provides the optional ability to generate ASCII files for the purpose of generating EDI Advanced Shipment Notices through a third party product. B. Modification Detail. The following describes the logic used to process outbound EDI Advanced Shipment Notice transactions. B1. Program Flow. The operator will be prompted for the following options when generating the ASCII files. Once all the selections have been made, the operator will be prompted whether to proceed with the creation of the ASCII File. 1. Selection Options. Records will be selected from the applicable tables (shipment confirmation or invoice history) where the transaction was generated from and EDI purchase order (based on the existance of an orderc record) and where the advanced shipment notice flag (shipflag_editp) in the applicable trading partner record (based on partnerid_editp = partnrid_orderc) is set to 'Y'. The following header selection options will be available. The option will default to 'ALL' - By Selected Division ID. - By Selected Branch ID. - By Selected Department ID. - By Selected Trading Partner ID. - By Selected Sold To ID. - ALL. The following header transaction selection options will be available. The option will default to 'All Ungenerated Shipments'. - All Ungenerated Shipments. This selection will select all records from the ship tables where the asn generation flag in the order header table (asnflag_orderc) is not set to 'Y'. - Selected Ungenerated Shipment Reference Numbers. This selection will select records from the shipping confirmation tables based on the invoice reference number(s) entered where the asn generation flag in the order header table (asnflag_orderc) is not set to 'Y'. - Selected Generated Shipment Reference Numbers. This selection will select records from the shipping confirmation tables based on the invoice reference number(s) entered where the asn generation flag in the order header table (asnflag_orderc) is set to 'Y'. - Selected Generated Invoice History Reference Numbers. This selection will select records from the invoice history tables based on the invoice reference number(s) entered. - Selected Generated Date (Invoice History). This selection will select records from the invoice history tables based on the date criteria entered matching the asn generation date (asndate_invoicec). Release NGS-7.00 EDI- 100

101 The following detail transaction selection options will be available. The option will default to the contents of the ACF EDISDET option: - All Lines. This selection will include all detail lines in the file, whether or not a shipment is made against the line. - Only Lines Where Quantity Shipped Is Present. This selection will only include detail lines in the ASCII file if the quantity shipped (qtyship_invdet) is non-zero. 2. Sort Options. The following sort options will be available. The option will default to the contents of the ACF EDISSRT Option: - By Division ID, Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. - By Branch ID, Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. - By Trading Partner ID, Ship to ID, Master Bill of Lading # and Reference (Invoice) Number. - By Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. - By Master Bill of Lading # and Reference (Invoice) Number. - By Division ID, Department ID, Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. The Master Bill of Lading Number sort will only be incorporated if the ACF edismbl value is greater than '1'. 3. ASCII Files Options. The operator will be prompted for the following to define the ASCII file parameters: - Directory Path. This will be the VALID directory where the ASCII file will be generated. The default will be the contents of the ACF EDISDIR Option. If an invalid directory is selected, the program will display the message 'Invalid Directory', wait for a brief period and exit the program. - Prefix File Name. This will be the prefix for the ASCII file name to be generated. The default will be the contents of the ACF EDISPFX Option. By setting the default to 'TODAY', the system will use the month and day of the current date and the next edi asn sequence number (defined in ACF EDISSEQ) as the ASCII File Name Prefix in the format MMDDSSS where MM is the current month, DD is the current date and SSS is the current sequence number (between 001 and 999). If this method is used, the contents of the ACF EDISSEQ option will be incremented by 1 and updated. - ASCII File Name. This will be the ASCII file name to be generated. The default will be the contents of the ACF EDISFIL Option. The actual name assigned to the ASCII file will be in the following format: <PREFIX FILE NAME>.<ASCII FILE NAME> - Field Delimiter. This will be the field delimiter used in the ASCII file output. The default will be the contents of the EDISDEL Option which will be initially set to the pipe ( ) symbol. Once the selections have been made, the operator will be prompted whether to proceed with the creation of the ASCII File. If they proceed, the system will display the next EDI ASN Batch Number at the base of the screen. This number will be assigned to all records included in the file. The ACF value will be incremented by 1 and updated. Once the generation is completed, the program will go to program end. Release NGS-7.00 EDI- 101

102 B2. ASN Generation Update. The following fields will be set in the orderc table once the ASCII file has been created for the records included: - The ASN Generation Flag will be set to 'Y' (asnflag_orderc). - The ASN Generation Date will be set to the current date (asndate_orderc). - The ASN Generation Time will be set to the current time (asntime_orderc). - The ASN Generation User will be set to the user id performing the generation (asnuser_orderc). - The ASN Generation Batch Number will be set to the contents of the ACF EDISBAT option (asnbatch_orderc). B3. Download Logic. The following header fields will be selected from the original EDI inbound data (in the orderc or invc tables): - Trading Partner ID.- Scheduled Ship Date (from original ship date). - Customer P/O Number. - Customer P/O Date. - Customer P/O Batch Number. - Reference Number. - Department. - Sold to ID. - Bill to ID. - Ship to ID. - Ship to Name. - Mark For. - Remarks. - Memo Header Memo The following header fields will be selected from the standard tables (shipa, shipb, inva, invb): - Shipment Reference Number (Order Number - Number of Backorder Field). The format will be order number followed by a dash followed by the number of backorders field. - Invoice Number. - Order Number. - Actual Ship Date. - Order Weight. - Tracking Number (from miscellaneous information 3 field). - Master Bill of Lading Number (from miscellaneous information 3 field). The following header fields will be selected from the EDI Ship Via table (edisv) based on the sold to ID and the ship via code on the order: - Routing. - SCAC Code. - SCAC Description - Carrier Name field. - Carrier Reference Number (Tracking Number). - Transportation Method. The following header comment fields will be selected from the standard header comments tables (ordcomt, invhc): - Trailer Number (code of 'SH'). - Trailer Prefix (code of 'SX'). Release NGS-7.00 EDI- 102

103 The following header and detail fields will be selected from the EDI Trading Partner table (editp) based on the trading partner id in the orderc table: - Packing Code. - Unit of Measure Charged. The following detail fields will be selected from the original EDI inbound data (in the orddet2 or invd2 tables): - Customer P/O Sequence Number. - Quantity Ordered.- Retail Price. - Item ID. - Customer Part ID 1. - Customer Part ID 2. - UPC Code. - Unit of Measure. - Item Description. - Memo Detail Memo The following detail fields will be selected from the standard tables (shipd, invd): - Quantity Shipped. - Selling Price (+ Insurance if applicable). - Weight. - Unit of Measure Charged (if field in trading partner table is <NULL>). The following shipment fields will be summed for the master bill of lading number (misc. info. 3) if the value in the ACF edismbl option is '2'. If the value in the ACF edismbl option is set to '1' or the master bill of lading number is <NULL>, it will be summed for the invoice number: - Shipment Lading Quantity: Quantity Shipped. - Shipment Weight: Weight. The following order fields will be summed for the order number: - Order Lading Quantity: Quantity Shipped. The Ship From name and address information will be selected from the division file if the contents of the ACF EDISADR option is '1' (Default). If the contents of the ACF EDISADR option is '2', the information will be selected from the branch table. The line number will be an incremented field starting at 1 for each order. The following are the valid Ship Order Status Codes: Code Description CM SHIP COMPLETE. - CP PARTIAL SHIPMENT (FIRST SHIPMENT). - BP PARTIAL SHIPMENT (BACKORDERED ITEMS). - BK BACKORDERED. - CS SHIP COMPLETE WITH SUBSTITUTIONS. - IC ITEM CANCELLED. - IS ITEM SUBSTITUTIONS. These codes will be assigned in the following manner: Release NGS-7.00 EDI- 103

104 On the first shipment of the order: - If the original quantity on the order (qtyord_orddet2) is less than or equal to the quantity shipped (qtyship_invdet) AND the quantity backordered is zero (qtyback_invdet), the code will be set to 'CM' (SHIP COMPLETE). - Otherwise, the code will be set to 'CP' (PARTIAL SHIPMENT - FIRST SHIPMENT). On subsequent shipments of the order: - If the original quantity on the order (qtyord_orddet2) is less than or equal to the quantity shipped (qtyship_invdet) AND the quantity backordered is zero (qtyback_invdet), the code will be set to 'BP' (PARTIAL SHIPMENT - BACKORDER). - Otherwise, the code will be set to 'BK' (BACK ORDERED). B4. Price Formats. An ACF option (option code 'edisprcd') will allow the definition of the number of decimal positions of the selling price & retail price fields generated in the EDI Advanced Ship Notice ASCII file. The system will allow an option value of '2' or '4'. When generating the advanced ship notice, if the option value is '2', the system will output the retail price (field 88) and selling price (field 89) to 2 positions to the right of the decimal. This involves using a format of "&&&&&&&.&&". If the option value is '4', the system will output the the retail price (field 88) and selling price (field 89) to 4 positions to the right of the decimal. This involves using a format of "&&&&&.&&&&". Note that the maximum price capable of being output with this option is B5. Date Formats. An ACF option (option code 'edisdfmt') will allow the definition of the output date format for all the date fields generated in the EDI Advanced Ship Notice ASCII file. The system will allow an option value of "1" or "2" and default to "1". If the option value is set to "1", the system will output all dates in the EDI Advanced Ship Notice ASCII file in the format "YYMMDD". If the option value is set to "2", the system will output all dates in the EDI Advanced Ship Notice ASCII file in the format "MMDDYY". General Formats: - All dates will be downloaded in the format: "YYMMDD" or "MMDDYY", based on ACF option "edisdfmt". - All quantities will be downloaded in integer format: XXXXXXX. - All weights will be downloaded in Decimal Format: XXXXX.XX. - All prices will be downloaded in Decimal Format: XXXXXXX.XX or XXXXX.XXXX, based on ACF option "edisprcd". - All records will be terminated with a <CARRIAGE RETURN><LINE FEED>. - All fields will be output to their maximum length, not to the actual length of the field. Alphanumeric character fields will be left-justified with blanks following the data. Numeric fields will be right justified with leading zeroes. Release NGS-7.00 EDI- 104

105 C. Outbound ASCII File Layouts. The following is a layout of the fields in the outbound ASCII file in field number sequence to be downloaded to the EDI Advanced Ship Notice ASCII file. All fields will be left justified. Fields 1 to 83 are header fields. The remaining fields are detail fields. Outbound ASN ASCII File. # FIELD DESCRIPTION TYPE SIZE INFO 1. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 partnerid_orderc 2. SHIPMENT REFERENCE NUMBER. CHAR 17 ordnum - shipment # 3. INVOICE NUMBER. CHAR 10 invnum_invoiceb 4. SCHEDULED SHIP DATE. DATE 6 shipdate_orderc. 5. ACTUAL SHIP DATE. DATE 6 shipdate_invoiceb. 6. ORDER NUMBER. CHAR 10 ordnum_invoiceb. 7. CUSTOMER P/O NUMBER. CHAR 22 cust_po_orderc. 8. PURCHASE ORDER DATE. DATE 6 podate_orderc. 9. CUSTOMER PURCHASE ORDER BATCH NBR CHAR 10 pobatch_orderc. 10. REFERENCE NUMBER. CHAR 30 refno_orderc. 11. DEPARTMENT. CHAR 30 dept_orderc. 12. BILL TO ID. CHAR 35 billto_orderc. 13. SOLD TO ID. CHAR 35 soldto_orderc. 14. SHIP TO ID. CHAR 35 shipto_orderc. 15. SHIP TO NAME. CHAR 35 shipname_orderc. 16. MARK FOR. CHAR 45 markfor_orderc. 17. REMARKS. CHAR 80 remarks_orderc. 18. SHIPMENT LADING QUANTITY. DEC 10 sum (qtyshp_invdet) mstr bol #. 19. SHIPMENT WEIGHT. DEC 10 sum (weight_invoicea) mstr bol 20. MASTER BILL OF LADING NUMBER. CHAR 30 if acf edismbl = '1' ordnum_invoiceb if acf edismbl = '2' miscinf3_invoicea 21. ORDER LADING QUANTITY. DEC 10 sum (qtyshp_invdet) for order 22. ORDER WEIGHT. DEC 10 weight_invoicea. 23. PACKING CODE. CHAR 5 packcd_editp 24. ROUTING. CHAR 2 routing_edisv. 25. CARRIER REFERENCE NUMBER. CHAR 30 trackno_edisv. 26. SCAC CODE. CHAR 4 scac_edisv. 27. SCAC DESCRIPTION (CARRIER NAME). CHAR 35 carrier_edisv. 28. TRAILER NUMBER. CHAR 20 comm_ordcomt type_ordc = SH comm_invc (type_invc = 'SH'). 29. TRAILER PREFIX. CHAR 20 comm_ordc (type_ordc = 'SX'). comm_invc (type_invc = 'SX'). 30. TRACKING NUMBER. CHAR 30 miscinf3_ordera. 31. TRANSPORTATION METHOD. CHAR 2 trmethod_edisv. 32. SHIP FROM NAME. CHAR 30 name_division coname_branch. 33. SHIP FROM ADDRESS 1. CHAR 30 address1_division. address1_branch. 34. SHIP FROM ADDRESS 2. CHAR 30 address2_division. address2_branch. 35. SHIP FROM ADDRESS 3. CHAR 30 address3_division. address3_branch. 36. SHIP FROM CITY. CHAR 18 city_division. city_branch. 37. SHIP FROM STATE. CHAR 4 state_division. state_branch. 38. SHIP FROM ZIP. CHAR 10 zip_division. zip_branch. Release NGS-7.00 EDI- 105

106 39. MEMO 1. CHAR 30 memo1_orderc 40. MEMO 2. CHAR 30 memo2_orderc 41. MEMO 3. CHAR 10 memo3_orderc 42. MEMO 4 (NUMERIC). DEC 10 memo4_orderc 43. MEMO 5 (DATE). DATE 6 memo3_orderc 44. HEADER MEMO 1. CHAR 30 memoh1_orderc 45. HEADER MEMO 2. CHAR 30 memoh2_orderc 46. HEADER MEMO 3. CHAR 30 memoh3_orderc 47. HEADER MEMO 4. CHAR 30 memoh4_orderc 48. HEADER MEMO 5. CHAR 30 memoh5_orderc 49. HEADER MEMO 6. CHAR 30 memoh6_orderc 50. HEADER MEMO 7. CHAR 30 memoh7_orderc 51. HEADER MEMO 8. CHAR 30 memoh8_orderc 52. HEADER MEMO 9. CHAR 30 memoh9_orderc 53. HEADER MEMO 10. CHAR 30 memoh10_orderc 54. HEADER MEMO 11. CHAR 30 memoh11_orderc 55. HEADER MEMO 12. CHAR 30 memoh12_orderc 56. HEADER MEMO 13. CHAR 30 memoh13_orderc 57. HEADER MEMO 14. CHAR 30 memoh14_orderc 58. HEADER MEMO 15. CHAR 30 memoh15_orderc 59. HEADER MEMO 16. CHAR 30 memoh16_orderc 60. HEADER MEMO 17. CHAR 30 memoh17_orderc 61. HEADER MEMO 18. CHAR 30 memoh18_orderc 62. HEADER MEMO 19. CHAR 30 memoh19_orderc 63. HEADER MEMO 20. CHAR 30 memoh20_orderc 64. HEADER MEMO 21. CHAR 30 memoh21_orderc 65. HEADER MEMO 22. CHAR 30 memoh22_orderc 66. HEADER MEMO 23. CHAR 30 memoh23_orderc 67. HEADER MEMO 24. CHAR 30 memoh24_orderc 68. HEADER MEMO 25. CHAR 30 memoh25_orderc 69. HEADER MEMO 26. CHAR 30 memoh26_orderc 70. HEADER MEMO 27. CHAR 30 memoh27_orderc 71. HEADER MEMO 28. CHAR 30 memoh28_orderc 72. HEADER MEMO 29. CHAR 30 memoh29_orderc 73. HEADER MEMO 30. CHAR 30 memoh30_orderc 74. HEADER MEMO 31. CHAR 30 memoh31_orderc 75. HEADER MEMO 32. CHAR 30 memoh32_orderc 76. HEADER MEMO 33. CHAR 30 memoh33_orderc 77. HEADER MEMO 34. CHAR 30 memoh34_orderc 78. HEADER MEMO 35. CHAR 30 memoh35_orderc 79. HEADER MEMO 36. CHAR 30 memoh36_orderc 80. HEADER MEMO 37. CHAR 30 memoh37_orderc 81. HEADER MEMO 38. CHAR 30 memoh38_orderc 82. HEADER MEMO 39. CHAR 30 memoh39_orderc 83. HEADER MEMO 40. CHAR 30 memoh40_orderc 84. P/O LINE NUMBER. INT 6 current setting: sequential number assigned for each order detail line ucc128 setting: sequential number assigned to each record generated in ascii file 85. CUSTOMER P/O SEQUENCE NUMBER. CHAR 4 polineno_orddet QUANTITY ORDERED. DEC 10 qtyord_orddet QUANTITY SHIPPED. DEC 10 qtyshp_invdet. 88. RETAIL PRICE. DEC 10 retlpr_orddet SELLING PRICE. DEC 10 if acf edisprc = 1, sellprice_invdet if acf edisprc = 2, sellprice + insrrate 90. ITEM ID. CHAR 25 sellitem_orddet CUSTOMER PART ID. CHAR 18 cstpart1_orddet CUSTOMER PART ID 2. CHAR 18 cstpart2_orddet2. Release NGS-7.00 EDI- 106

107 # FIELD DESCRIPTION TYPE SIZE INFO 93. UPC CODE. CHAR 25 upc_orddet UNIT OF MEASURE. CHAR 2 uom_orddet UNIT OF MEASURE CHARGED. CHAR 2 uom_editp. uom_invdet. 96. ITEM DESCRIPTION. CHAR 18 desc_orddet WEIGHT. DEC 10 weight_invdet. 98. SHIP ORDER STATUS CODE. CHAR 2 ship order status code. 99. MEMO 1. CHAR 30 memo1_orddet MEMO 2. CHAR 30 memo2_orddet MEMO 3. CHAR 10 memo3_orddet MEMO 4 (NUMERIC). DEC 10 memo4_orddet MEMO 5 (DATE). DATE 6 memo5_orddet DETAIL MEMO 1. CHAR 30 memod1_orddet DETAIL MEMO 2. CHAR 30 memod2_orddet DETAIL MEMO 3. CHAR 30 memod3_orddet DETAIL MEMO 4. CHAR 30 memod4_orddet DETAIL MEMO 5. CHAR 30 memod5_orddet DETAIL MEMO 6. CHAR 30 memod6_orddet DETAIL MEMO 7. CHAR 30 memod7_orddet DETAIL MEMO 8. CHAR 30 memod8_orddet DETAIL MEMO 9. CHAR 30 memod9_orddet DETAIL MEMO 10. CHAR 30 memod10_orddet DETAIL MEMO 11. CHAR 30 memod11_orddet DETAIL MEMO 12. CHAR 30 memod12_orddet DETAIL MEMO 13. CHAR 30 memod13_orddet DETAIL MEMO 14. CHAR 30 memod14_orddet DETAIL MEMO 15. CHAR 30 memod15_orddet DETAIL MEMO 16. CHAR 30 memod16_orddet DETAIL MEMO 17. CHAR 30 memod17_orddet DETAIL MEMO 18. CHAR 30 memod18_orddet DETAIL MEMO 19. CHAR 30 memod19_orddet DETAIL MEMO 20. CHAR 30 memod20_orddet DETAIL MEMO 21. CHAR 30 memod21_orddet DETAIL MEMO 22. CHAR 30 memod22_orddet DETAIL MEMO 23. CHAR 30 memod23_orddet DETAIL MEMO 24. CHAR 30 memod24_orddet DETAIL MEMO 25. CHAR 30 memod25_orddet DETAIL MEMO 26. CHAR 30 memod26_orddet DETAIL MEMO 27. CHAR 30 memod27_orddet DETAIL MEMO 28. CHAR 30 memod28_orddet DETAIL MEMO 29. CHAR 30 memod29_orddet DETAIL MEMO 30. CHAR 30 memod30_orddet DETAIL MEMO 31. CHAR 30 memod31_orddet DETAIL MEMO 32. CHAR 30 memod32_orddet DETAIL MEMO 33. CHAR 30 memod33_orddet DETAIL MEMO 34. CHAR 30 memod34_orddet DETAIL MEMO 35. CHAR 30 memod35_orddet DETAIL MEMO 36. CHAR 30 if current setting: memod36_orddet2 if ucc128 setting: memo1_boxh 140. DETAIL MEMO 37. CHAR 30 memod37_orddet DETAIL MEMO 38. CHAR 30 memod38_orddet DETAIL MEMO 39. CHAR 30 memod39_orddet DETAIL MEMO 40. CHAR 30 memod40_orddet2 Release NGS-7.00 EDI- 107

108 D. Database Fields Updated. D1. ORDERC - EDI Open Order Header Table Layout. Update the following fields to the EDI Open Order Header Table: FIELD NAME SIZE TYPE DESCRIPTION asnflag_orderc 2 CHAR ASN GENERATION FLAG asndate_orderc 4 DATE ASN GENERATION DATE asntime_orderc 8 CHAR ASN GENERATION TIME asnuser_orderc 8 CHAR ASN GENERATION USER asnbatch_orderc 10 CHAR ASN GENERATION BATCH D2. ORMNTC - EDI Order Maintenance Header Table Layout. Maintain the following fields in the EDI Order Maintenance Header Table: FIELD NAME SIZE TYPE DESCRIPTION asnflag_orderc 2 CHAR ASN GENERATION FLAG asndate_orderc 4 DATE ASN GENERATION DATE asntime_orderc 8 CHAR ASN GENERATION TIME asnuser_orderc 8 CHAR ASN GENERATION USER asnbatch_orderc 10 CHAR ASN GENERATION BATCH D3. INVOICEC - EDI Open Invoice Header Table Layout. Maintain the following fields in the EDI Open Invoice Header Table: FIELD NAME SIZE TYPE DESCRIPTION asnflag_invoicec 2 CHAR ASN GENERATION FLAG asndate_invoicec 4 DATE ASN GENERATION DATE asntime_invoicec 8 CHAR ASN GENERATION TIME asnuser_invoicec 8 CHAR ASN GENERATION USER asnbatch_invoice 10 CHAR ASN GENERATION BATCH D4. INVC - EDI Invoice History Header Table Layout. Update the following fields to the EDI Invoice History Header Table: FIELD NAME SIZE TYPE DESCRIPTION asnflag_invoicec 2 CHAR ASN GENERATION FLAG asndate_invoicec 4 DATE ASN GENERATION DATE asntime_invoicec 8 CHAR ASN GENERATION TIME asnuser_invoicec 8 CHAR ASN GENERATION USER asnbatch_invoice 10 CHAR ASN GENERATION BATCH Release NGS-7.00 EDI- 108

109 E. Screen Layouts. E1. Option Selection Screen. E2. Sort/ASCII Parameters Screen. Release NGS-7.00 EDI- 109

110 F. ACF Options for ASN processing - *** view all edi options using edi* from the acf pgm *** Release NGS-7.00 EDI- 110

111 EDIINVCG- EDI OUTBOUND INVOICE ASCII FILE GENERATION A. Modification Summary. This program provides the ability to generate ASCII files for the purpose of generating EDI Invoices through a third party product. B. Modification Detail. The following describes the logic used to process outbound EDI Invoice transactions. B1. Program Flow. The operator will be prompted for the following options when generating the ASCII files. Once all the selections have been made, the operator will be prompted whether to proceed with the creation of the ASCII File. 1. Selection Options. Records will be selected from the applicable tables (open invoice or invoice history) where the transaction was generated from and EDI purchase order (based on the existence of an invoicec or invc record) and where the EDI invoice flag (invflag_editp) in the applicable trading partner record (based on partnerid_editp = partnrid_invoicec) is set to 'Y'. Note that if the EDI Invoice Header record is not found, the program will reject the transaction. The following header selection options will be available. The option will default to 'ALL'. - By Selected Division ID. - By Selected Branch ID. - By Selected Department ID. - By Selected Trading Partner ID. - By Selected A/R To ID. - By Selected Sold To ID. - ALL. The following header transaction selection options will be available. The option will default to 'All Ungenerated Invoices'. - All Ungenerated Invoices. This selection will select all records from the Open Invoice tables where the invoice generation flag in the EDI Invoice Header table (invflag_invoicec) is not set to 'Y'. - Selected Invoice Reference Numbers. This selection will select records from the Open Invoice tables based on the invoice reference number(s) entered where the invoice generation flag in the EDI Invoice Header table (invflag_invoicec) is not set to 'Y'. - Selected Invoice History Reference Numbers. This selection will select records from the Invoice History tables based on the invoice reference number(s) entered. - Selected Generated Date (Invoice History). This selection will select records from the Invoice History tables based on the date criteria entered matching the invoice generation date (invdate_invoicec) in the EDI Invoice Header table. Release NGS-7.00 EDI- 111

112 - All Invoices Open in A/R (Invoice History). This selection will select records from the Open A/R Table (aropnitm) where the total amount open on the invoice is not zero. The corresponding records in the Invoice History tables will be selected. - All Invoices matching a Customer s P.O. Number (Invoice History). This selection will select records from the Invoice History tables that match on purchase order number. The corresponding records in the Invoice History tables will be selected. The following detail transaction selection options will be available. The option will default to the contents of the ACF EDIIDET option: - All Lines. This selection will include all detail lines in the file, whether or not a shipment is made against the line. - Only Lines Where Quantity Shipped Is Present. This selection will only include detail lines in the ASCII file if the quantity shipped (qtyship_invdet) is non-zero. 2. Sort Options. The following sort options will be available. The option will default to the contents of the ACF EDIISRT. - By Division ID, Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. - By Branch ID, Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. - By Trading Partner ID, Ship to ID, Master Bill of Lading # and Reference (Invoice) Number. - By Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. - By Master Bill of Lading # and Reference (Invoice) Number. - By Division ID, Department ID, Trading Partner ID, Master Bill of Lading # and Reference (Invoice) Number. The Master Bill of Lading Nbr sort will only be incorporated if the ACF EDIIMBL value is greater than '1'. 3. ASCII Files Options. The operator will be prompted for the following to define the ASCII file parameters: - Directory Path. This will be the VALID directory where the ASCII file will be generated. The default will be the contents of the ACF EDIIDIR Option. If an invalid directory is selected, the program will display the message 'Invalid Directory', wait for a brief period and exit the program. - Prefix File Name. This will be the prefix for the ASCII file name to be generated. The default will be the contents of the ACF EDIIPFX Option. By setting the default to 'TODAY', the system will use the month and day of the current date and the next edi invoice sequence number (defined in ACF EDIISEQ) as the ASCII File Name Prefix in the format MMDDSSS where MM is the current month, DD is the current date and SSS is the current sequence number (between 001 and 999). If this method is used, the contents of the ACF EDIISEQ option will be incremented by 1 and updated. Release NGS-7.00 EDI- 112

113 - ASCII File Name. This will be the ASCII file name to be generated. The default will be the contents of the ACF EDIIFIL Option. The actual name assigned to the ASCII file will be in the following format: <PREFIX FILE NAME>.<ASCII FILE NAME> - Field Delimiter. This will be the field delimiter used in the ASCII file output. The default will be the contents of the ACF EDISDEL Option which will be initially set to the pipe ( ) symbol. - PROCEED WITH CREATING ASCII FILE. you can either create the ascii file and send later or ftp it immediately. When F (FTP) is selected, the program will prompt the user to select the configuration record to be used i.e. (where will you be sending this data). The configuration records are from the FTPSEND program. Once the configuration record is selected the system will pass Program name (EDIINVCG), configuration selected, file directory path and our file name to the FTPSEND Program. An acf option (ediifile) was added to use as a default for the proceed option. Y = create ascii file F = create ascii file and ftp immediately. Once the selections have been made, the operator will be prompted whether to proceed with the creation of the ASCII File. If they proceed, the system will display the next EDI Invoice Batch Number at the base of the screen. This number will be assigned to all records included in the file. The ACF value will be incremented by 1 and updated. Once the generation is completed, the program will go to program end. B2. Invoice Generation Update. The following fields will be set in the invoicec table and the invc table once the ASCII file has been created for the records included: - The Invoice Generation Flag will be set to 'Y' (invflag_invoicec) - The Invoice Generation Date will be set to the current date (invdate_invoicec) - The Invoice Generation Time will be set to the current time (invtime_invoicec) - The Invoice Generation User will be set to the user id performing the generation (invuser_invoicec). - The Invoice Generation Batch Number will be set to the contents of the ACF EDIIBAT option (invbatch_invoicec). If the trading partner invoice print flag is not set to 'Y' (invprt_editp), the following fields will be set in the standard Invoice Header table (invoiceb): - The invoice print flag will be set to 'N' (printflag_invoiceb). - The invoice print date will be set to the current date (invprtdt_invoiceb). - The invoice print time will be set to the current time (iprnttime_invoiceb). - The invoice print user will be set to the user performing the generation (iprntuser_invoiceb). Updating will only occur when processing Open Invoices, not invoice history records (print opt. 1 and 2). Release NGS-7.00 EDI- 113

114 B3. Download Logic. The following header fields will be selected from the original EDI inbound data (invoicec or invc tables): - Trading Partner ID. - Scheduled Ship Date (from original ship date). - Customer P/O Number. - Customer P/O Date. - Customer P/O Batch Number. - Reference Number. - Department. - Media/Event Code. - Sold to ID. - Bill to ID. - Ship to ID. - Ship to Name. - Ship to Address 1. - Ship to Address 2. - Ship to Address 3. - Ship to City. - Ship to State. - Ship to Zip Code. - Ship to Country. - Mark For. - Remarks. - Memo Header Memo The following header fields will be selected from the standard tables (invoicea, invoiceb, inva, invb): - Shipment Reference Number (Order Number - Number of Backorder Field). The format will be order number followed by a dash followed by the number of backorders field. - Invoice Number. - Invoice Date. - Order Number. - Actual Ship Date. - Order Weight. - Tracking Number (from miscellaneous information 3 field). - Master Bill of Lading Number (from miscellaneous information 3 field). - Invoice Total Amount. - Invoice Total Amount (without charges). - Special Charge Total. - Allowance Charge Total. - Terms Discount Percentage. - Terms Discount Amount. - Terms Discount Due Date. - Terms Net Due Date. - Percentage of Invoice Payable. Release NGS-7.00 EDI- 114

115 The following header fields will be selected from the EDI Ship Via table (edisv) based on the trading partner ID and the ship via code on the invoice: - Routing. - SCAC Code. - SCAC Description - Carrier Name field. - Carrier Reference Number (Tracking Number). - Transportation Method. - Special Services Code. The following header fields will be selected from the standard Terms table (terms) based on the terms code on the invoice: - Terms Net Days. - Terms Discount Days. - Terms Description. - Terms Discount Days Due. The following header fields will be selected from the EDI Terms table (editerm) based on the trading partner ID and the terms code on the invoice: - Terms Type Code. - Terms Basis Date Code. The following header comment fields will be selected from the standard header comments tables (invhcomt, invhc): - Trailer Number (code of 'SH'). - Trailer Prefix (code of 'SX'). The following header and detail fields will be selected from the EDI Trading Partner table (editp) based on the trading partner id in the EDI invoice table (invoicec, invc): - Remit To. - Packing Code. - Unit of Measure Charged. - Shipment Method of Payment. - Item Basis Unit Price Code. - Allowance Charge Indicator. - Allowance Charge Method. Release NGS-7.00 EDI- 115

116 The following detail fields will be selected from the original EDI inbound data (in the invdet2 or invd2 tables): - Customer P/O Sequence Number. - Quantity Ordered. - Retail Price. - Item ID. - Customer Part ID 1. - Customer Part ID 2. - UPC Code. - Unit of Measure. - Item Description. - Memo Detail Memo The following detail fields will be selected from the standard tables (invdet, invd): - Quantity Shipped. - Selling Price (+ Insurance if applicable). - Weight. - Unit of Measure Charged (if field in trading partner table is <NULL>). The following shipment fields will be summed for the master bill of lading number (misc. info. 3) if the value in the ACF EDIIMBL option is '2'. If the value in the ACF EDIIMBL option is set to '1' or the master bill of lading number is <NULL>, it will be summed for the invoice number: - Shipment Lading Quantity: Quantity Shipped. - Shipment Weight: Weight. The following order fields will be summed for the invoice number: - Order Lading Quantity: Quantity Shipped. The following invoice fields will be summed for the invoice number: - Number of Units Shipped: Quantity Shipped. The Ship From name and address information will be selected from the division file if the contents of the ACF EDIIADR option is '1' (Default). If the contents of the ACF EDIIADR option is '2', the information will be selected from the branch table. The line number will be an incremented field starting at 1 for each invoice. Release NGS-7.00 EDI- 116

117 The following are the valid Ship Order Status Codes: Code CM CP BP BK CS IC IS Description SHIP COMPLETE. PARTIAL SHIPMENT (FIRST SHIPMENT). PARTIAL SHIPMENT (BACKORDERED ITEMS). BACKORDERED. SHIP COMPLETE WITH SUBSTITUTIONS. ITEM CANCELLED. ITEM SUBSTITUTIONS. These codes will be assigned in the following manner: On the first shipment of the order: - If the original quantity on the order (qtyord_invdet2) is less than or equal to the quantity shipped (qtyship_invdet) AND the quantity backordered is zero (qtyback_invdet), the code will be set to 'CM' (SHIP COMPLETE). - Otherwise, the code will be set to 'CP' (PARTIAL SHIPMENT - FIRST SHIPMENT). On subsequent shipments of the order: - If the original quantity on the order (qtyord_invdet2) is less than or equal to the quantity shipped (qtyship_invdet) AND the quantity backordered is zero (qtyback_invdet), the code will be set to 'BP' (PARTIAL SHIPMENT - BACKORDER). - Otherwise, the code will be set to 'BK' (BACK ORDERED). B4. Price Formats. An ACF option (option code 'ediiprcd') will allow the definition of the number of decimal positions of the selling price & retail price fields generated in the EDI Invoice ASCII file. The system will allow an option value of '2' or '4'. When generating the invoice, if the option value is '2', the system will output the retail price (field 120) and selling price (field 121) to 2 positions to the right of the decimal. This involves using a format of "&&&&&&&.&&". If the option value is '4', the system will output the the retail price (field 120) and selling price (field 121) to 4 positions to the right of the decimal. This involves using a format of "&&&&&.&&&&". Note that the maximum price capable of being output with this option is B5. Date Formats. An ACF option (option code 'ediidfmt') will allow the definition of the output date format for all the date fields generated in the EDI Invoice ASCII file. The system will allow an option value of "1" or "2" and default to "1". If the option value is set to "1", the system will output all dates in the EDI Invoice ASCII file in the format "YYMMDD". If the option value is set to "2", the system will output all dates in the EDI Invoice ASCII file in the format "MMDDYY". Release NGS-7.00 EDI- 117

118 General Formats: - All dates will be downloaded in the format: "YYMMDD" or "MMDDYY", based on ACF option "ediidfmt". - All quantities will be downloaded in integer format: XXXXXXX. - All weights will be downloaded in Decimal Format: XXXXX.XX. - All prices will be downloaded in Decimal Format: XXXXXXX.XX or XXXXX.XXXX, based on ACF option "ediiprcd". - All terms percentages will be downloaded in Decimal Format: XXX.XX. - All terms days will be downloaded in Integer Format: XXX. - All amounts will be downloaded in Decimal Format: XXXXXXX.XX. - All records will be terminated with a <CARRIAGE RETURN><LINE FEED>. - All fields can either be output to their maximum length or to the actual length of the field, based on ACF option "ediinlen". When output to their maximum lengths, alpha-numeric character fields will be left-justified with blanks following the data; numeric fields will be right justified with leading zeroes. Release NGS-7.00 EDI- 118

119 C. Outbound Invoice ASCII File Layouts. The following is a layout of the fields in the outbound ASCII file in field number sequence to be downloaded to the EDI Invoice ASCII file. All fields will be left justified. Fields 1 to 115 are header fields. The remaining fields are detail fields. # FIELD DESCRIPTION TYPE SIZE INFO 1. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 partnerid_invoicec. 2. SHIPMENT REFERENCE NUMBER. CHAR 17 ordnum_invoiceb - no_bckord_invoiceb. 3. INVOICE NUMBER. CHAR 10 invnum_invoiceb. 4. INVOICE DATE. DATE 6 transdate_invoiceb. 5. SCHEDULED SHIP DATE. DATE 6 shipdate_invoicec. 6. ACTUAL SHIP DATE. DATE 6 shipdate_invoiceb. 7. ORDER NUMBER. CHAR 10 ordnum_invoiceb. 8. CUSTOMER P/O NUMBER. CHAR 22 cust_po_invoicec. 9. PURCHASE ORDER DATE. DATE 6 podate_invoicec. 10. CUSTOMER PURCHASE ORDER BATCH # CHAR 10 pobatch_invoicec. 11. REFERENCE NUMBER. CHAR 30 refno_invoicec. 12. DEPARTMENT. CHAR 30 dept_invoicec. 13. BILL TO ID. CHAR 35 billto_invoicec. 14. REMIT TO. CHAR 35 remitto_editp. 15. MEDIA/EVENT CODE. CHAR 2 media_invoicec. 16. SOLD TO ID. CHAR 35 soldto_invoicec. 17. SHIP TO ID. CHAR 35 shipto_invoicec. 18. SHIP TO NAME. CHAR 35 shipname_invoicec if blank, use shipname_invoicea. 19. SHIP TO ADDRESS 1. CHAR 35 shipaddr1_invoicec if blank, use shipadr1_invoicea. 20. SHIP TO ADDRESS 2. CHAR 35 shipaddr2_invoicec if blank, use shipadr2_invoicea. 21. SHIP TO ADDRESS 3. CHAR 35 shipaddr3_invoicec if blank, use shipadr3_invoicea. 22. SHIP TO CITY. CHAR 19 shipcity_invoicec if blank, use shipcity_invoicea. 23. SHIP TO STATE. CHAR 4 shipstate_invoicec if blank, use shipstate_invoicea. 24. SHIP TO ZIP CODE. CHAR 9 shipzip_invoicec if blank, use shipzip_invoicea. 25. SHIP TO COUNTRY. CHAR 10 shipcntry_invoicec. 26. MARK FOR. CHAR 45 markfor_invoicec. 27. REMARKS. CHAR 80 remarks_invoicec. 28. SHIPMENT LADING QUANTITY. INT 7 sum (qtyshp_invdet) for master bol #. 29. SHIPMENT WEIGHT. DEC 8 sum (weight_invoicea) for master bol #. 30. MASTER BILL OF LADING NUMBER. CHAR 30 If ACF ediimbl = '1' ordnum_invoiceb. If ACF ediimbl = '2' miscinf3_invoicea. 31. ORDER LADING QUANTITY. INT 7 sum (qtyshp_invdet) for invoice number. 32. ORDER WEIGHT. DEC 8 weight_invoicea. 33. PACKING CODE. CHAR 5 packcd_editp 34. ROUTING. CHAR 2 routing_edisv. 35. CARRIER REFERENCE NUMBER. CHAR 30 trackno_edisv. 36. SCAC CODE. CHAR 4 scac_edisv. 37. SCAC DESCRIPTION (CARRIER NAME). CHAR 35 carrier_edisv. Release NGS-7.00 EDI- 119

120 # FIELD DESCRIPTION TYPE SIZE INFO 38. TRAILER NUMBER. CHAR 20 comm_invc (type_invc = 'SH'). 39. TRAILER PREFIX. CHAR 20 comm_invc (type_invc = 'SX'). 40. TRACKING NUMBER. CHAR 30 miscinf3_invoicea. 41. TRANSPORTATION METHOD. CHAR 2 trmethod_edisv. 42. SHIP FROM NAME. CHAR 30 name_division (if ACF EDIIADR = 1). coname_branch (if ACF EDIIADR = 2). 43. SHIP FROM ADDRESS 1. CHAR 30 address1_division (if acf EDIIADR = 1). address1_branch (if acf EDIIADR = 2). 44. SHIP FROM ADDRESS 2. CHAR 30 address2_division (if acf EDIIADR = 1). address2_branch (if acf EDIIADR = 2). 45. SHIP FROM ADDRESS 3. CHAR 30 address3_division (if acf EDIIADR = 1). address3_branch (if acf EDIIADR = 2). 46. SHIP FROM CITY. CHAR 18 city_division (if acf EDIIADR = 1). city_branch (if acf EDIIADR = 2). 47. SHIP FROM STATE. CHAR 4 state_division (if acf EDIIADR = 1). state_branch (if acf EDIIADR = 2). 48. SHIP FROM ZIP. CHAR 10 zip_division (if acf EDIIADR = 1). zip_branch (if acf EDIIADR = 2). 49. SHIP METHOD OF PAYMENT. CHAR 2 pymethod_edisv. 50. NUMBER OF UNITS SHIPPED. INT 7 sum (qtyshp_invdet) for order number. 51. UNIT OF MEASURE. CHAR 2 uom_editp. 52. ITEM BASIS UNIT PRICE CODE. CHAR 2 pricebase_editp. 53. INVOICE TOTAL AMOUNT. DEC 10 total_invoicea. 54. INVOICE AMOUNT WITHOUT CHARGES. DEC 10 - zero + <addition> (if totalchg_editp = 0). - grossext_invoicea + <addition> (if totalchg_editp = 1). - netext_invoicea + <addition> (if totalchg_editp = 2). - grossext_invoicea - tradedisc_invoicea + <addition> (if totalchg_editp = 3). - netext_invoicea - tradedisc_invoicea + <addition> (if totalchg_editp = 4). <addition> defined as: - zero (if totaladd_editp = 0). - ins_invoicea (if totaladd_editp = 1). - handling_invoicea (if totaladd_editp = 2). - misc1_invoicea (if totaladd_editp = 3). - misc2_invoicea (if totaladd_editp = 4). - misc3_invoicea (if totaladd_editp = 5). - misc4_invoicea (if totaladd_editp = 6). - minsurch_invoicea (if totaladd_editp = 7). 55. SPECIAL SERVICES CODE. CHAR 5 spclsrv_edisv. Release NGS-7.00 EDI- 120

121 # FIELD DESCRIPTION TYPE SIZE INFO 56. SPECIAL CHARGE TOTAL. DEC 10 0 (if speclchg_editp = 0). frt_invoicea (if speclchg_editp = 1). handling_invoicea (if speclchg_editp = 2). ins_invoicea (if speclchg_editp = 3). misc1_invoicea (if speclchg_editp = 4). misc2_invoicea (if speclchg_editp = 5). misc3_invoicea (if speclchg_editp = 6). misc4_invoicea (if speclchg_editp = 7). minsurch_invoicea (if speclchg_editp = 8) tradedisc_invoicea (if speclchg_editp = 9). 57. ALLOWANCE CHARGE INDICATOR. CHAR 1 allowind_editp. 58. ALLOWANCE CHARGE METHOD. CHAR 2 allowmeth_editp. 59. ALLOWANCE CHARGE TOTAL. DEC 10 0 (if allowchg_editp = 0). frt_invoicea (if allowchg_editp = 1). handling_invoicea (if allowchg_editp = 2). ins_invoicea (if allowchg_editp = 3). misc1_invoicea (if allowchg_editp = 4). misc2_invoicea (if allowchg_editp = 5). misc3_invoicea (if allowchg_editp = 6). misc4_invoicea (if allowchg_editp = 7). minsurch_invoicea (if allowchg_editp = 8). tradedisc_invoicea (if allowchg_editp = 9) 60. TERMS NET DAYS. INT 3 due_days_terms. 61. TERMS DISCOUNT DAYS. INT 3 trm_days_terms. 62. TERMS DISCOUNT PERCENTAGE. DEC 5 termspct_invoiceb. 63. TERMS TYPE CODE. CHAR 2 termtype_editerm. 64. TERMS BASIS DATE. CHAR 2 termbase_editerm. 65. TERMS DESCRIPTION. CHAR 20 desc_terms. 66. TERMS DISCOUNT AMOUNT. DEC 10 AMOUNT WITHOUT CHARGES (54) * termspct_invoiceb / 100 (rounded). 67. TERMS DISCOUNT DAYS DUE. INT 3 trm_days_terms. 68. TERMS DISCOUNT DUE DATE. DATE 6 termsdate_invoiceb. 69. TERMS NET DUE DATE. DATE 6 duedate_invoiceb. 70. PERCENT INVOICE PAYABLE. DEC 6 ( termspct_invoiceb). 71. MEMO 1. CHAR 30 memo1_invoicec 72. MEMO 2. CHAR 30 memo2_invoicec 73. MEMO 3. CHAR 10 memo3_invoicec 74. MEMO 4 (NUMERIC). DEC 10 memo4_invoicec 75. MEMO 5 (DATE). DATE 6 memo5_invoicec 76. HEADER MEMO 1. CHAR 30 memoh1_invoicec 77. HEADER MEMO 2. CHAR 30 memoh2_invoicec 78. HEADER MEMO 3. CHAR 30 memoh3_invoicec 79. HEADER MEMO 4. CHAR 30 memoh4_invoicec 80. HEADER MEMO 5. CHAR 30 memoh5_invoicec 81. HEADER MEMO 6. CHAR 30 memoh6_invoicec 82. HEADER MEMO 7. CHAR 30 memoh7_invoicec 83. HEADER MEMO 8. CHAR 30 memoh8_invoicec 84. HEADER MEMO 9. CHAR 30 memoh9_invoicec 85. HEADER MEMO 10. CHAR 30 memoh10_invoicec 86. HEADER MEMO 11. CHAR 30 memoh11_invoicec 87. HEADER MEMO 12. CHAR 30 memoh12_invoicec 88. HEADER MEMO 13. CHAR 30 memoh13_invoicec Release NGS-7.00 EDI- 121

122 89. HEADER MEMO 14. CHAR 30 memoh14_invoicec 90. HEADER MEMO 15. CHAR 30 memoh15_invoicec 91. HEADER MEMO 16. CHAR 30 memoh16_invoicec # FIELD DESCRIPTION TYPE SIZE INFO 92. HEADER MEMO 17. CHAR 30 memoh17_invoicec 93. HEADER MEMO 18. CHAR 30 memoh18_invoicec 94. HEADER MEMO 19. CHAR 30 memoh19_invoicec 95. HEADER MEMO 20. CHAR 30 memoh20_invoicec 96. HEADER MEMO 21. CHAR 30 memoh21_invoicec 97. HEADER MEMO 22. CHAR 30 memoh22_invoicec 98. HEADER MEMO 23. CHAR 30 memoh23_invoicec 99. HEADER MEMO 24. CHAR 30 memoh24_invoicec 100. HEADER MEMO 25. CHAR 30 memoh25_invoicec 101. HEADER MEMO 26. CHAR 30 memoh26_invoicec 102. HEADER MEMO 27. CHAR 30 memoh27_invoicec 103. HEADER MEMO 28. CHAR 30 memoh28_invoicec 104. HEADER MEMO 29. CHAR 30 memoh29_invoicec 105. HEADER MEMO 30. CHAR 30 memoh30_invoicec 106. HEADER MEMO 31. CHAR 30 memoh31_invoicec 107. HEADER MEMO 32. CHAR 30 memoh32_invoicec 108. HEADER MEMO 33. CHAR 30 memoh33_invoicec 109. HEADER MEMO 34. CHAR 30 memoh34_invoicec 110. HEADER MEMO 35. CHAR 30 memoh35_invoicec 111. HEADER MEMO 36. CHAR 30 memoh36_invoicec 112. HEADER MEMO 37. CHAR 30 memoh37_invoicec 113. HEADER MEMO 38. CHAR 30 memoh38_invoicec 114. HEADER MEMO 39. CHAR 30 memoh39_invoicec 115. HEADER MEMO 40. CHAR 30 memoh40_invoicec 116. P/O LINE NUMBER. INT 6 Sequentially assign # 117. CUSTOMER P/O SEQUENCE NUMBER. CHAR 4 polineno_invdet QUANTITY ORDERED. INT 7 qtyord_invdet QUANTITY SHIPPED (INVOICED). INT 7 qtyshp_invdet RETAIL PRICE. DEC 10 retlpr_invdet SELLING PRICE. DEC 10 If ACF ediiprc = '1': sellprice_invdet. If ACF ediiprc = '2': sellprice_invdet + insrrate_invdet ITEM ID. CHAR 25 sellitem_invdet CUSTOMER PART ID. CHAR 18 cstpart1_invdet CUSTOMER PART ID 2. CHAR 18 cstpart2_invdet UPC CODE. CHAR 25 upc_invdet UNIT OF MEASURE. CHAR 2 uom_invdet UNIT OF MEASURE CHARGED. CHAR 2 uom_editp. uom_invdet (if uom_editp is <NULL>) ITEM DESCRIPTION. CHAR 18 desc_invdet WEIGHT. DEC 8 weight_invdet SHIP ORDER STATUS CODE. CHAR 2 Assigned ship order status code MEMO 1. CHAR 30 altconv_invdet 132. MEMO 2. CHAR 30 memo2_invdet MEMO 3. CHAR 10 memo3_invdet MEMO 4 (NUMERIC). DEC 10 memo4_invdet MEMO 5 (DATE). DATE 6 memo5_invdet DETAIL MEMO 1. CHAR 30 memod1_invdet DETAIL MEMO 2. CHAR 30 memod2_invdet DETAIL MEMO 3. CHAR 30 memod3_invdet DETAIL MEMO 4. CHAR 30 memod4_invdet DETAIL MEMO 5. CHAR 30 memod5_invdet2 Release NGS-7.00 EDI- 122

123 141. DETAIL MEMO 6. CHAR 30 memod6_invdet DETAIL MEMO 7. CHAR 30 memod7_invdet DETAIL MEMO 8. CHAR 30 memod8_invdet2 # FIELD DESCRIPTION TYPE SIZE INFO 144. DETAIL MEMO 9. CHAR 30 memod12_invdet DETAIL MEMO 13. CHAR 30 memod13_invdet DETAIL MEMO 14. CHAR 30 memod14_invdet DETAIL MEMO 15. CHAR 30 memod15_invdet DETAIL MEMO 16. CHAR 30 memod16_invdet DETAIL MEMO 17. CHAR 30 memod17_invdet DETAIL MEMO 18. CHAR 30 memod18_invdet DETAIL MEMO 19. CHAR 30 memod19_invdet DETAIL MEMO 20. CHAR 30 memod20_invdet DETAIL MEMO 21. CHAR 30 memod21_invdet DETAIL MEMO 22. CHAR 30 memod22_invdet DETAIL MEMO 23. CHAR 30 memod23_invdet DETAIL MEMO 24. CHAR 30 memod24_invdet DETAIL MEMO 25. CHAR 30 memod25_invdet DETAIL MEMO 26. CHAR 30 memod26_invdet DETAIL MEMO 27. CHAR 30 memod27_invdet DETAIL MEMO 28. CHAR 30 memod28_invdet DETAIL MEMO 29. CHAR 30 memod29_invdet DETAIL MEMO 30. CHAR 30 memod30_invdet DETAIL MEMO 31. CHAR 30 memod31_invdet DETAIL MEMO 32. CHAR 30 memod32_invdet DETAIL MEMO 33. CHAR 30 memod33_invdet DETAIL MEMO 34. CHAR 30 memod34_invdet DETAIL MEMO 35. CHAR 30 memod35_invdet DETAIL MEMO 36. CHAR 30 if current setting : use memod36_orddet2 if ucc128 setting : use memo1_boxh (pallet id) 172. DETAIL MEMO 37. CHAR 30 memod37_invdet DETAIL MEMO 38. CHAR 30 memod38_invdet DETAIL MEMO 39. CHAR 30 memod39_invdet DETAIL MEMO 40. CHAR 30 memod40_invdet2. Release NGS-7.00 EDI- 123

124 Database Fields Updated. 1. ORDERC - EDI Open Order Header Table Layout. Maintain the following field to the EDI Open Order Header Table: FIELD NAME SIZE TYPE DESCRIPTION invflag_orderc 2 CHAR INVOICE GENERATION FLAG invdate_orderc 4 DATE INVOICE GENERATION DATE invtime_orderc 8 CHAR INVOICE GENERATION TIME invuser_orderc 8 CHAR INVOICE GENERATION USER invbatch_orderc 10 CHAR INVOICE GENERATION BATCH 2. ORMNTC - EDI Order Maintenance Header Table Layout. Maintain the following fields in the EDI Order Maintenance Header Table: FIELD NAME SIZE TYPE DESCRIPTION invflag_ormntc 2 CHAR INVOICE GENERATION FLAG invdate_ormntc 4 DATE INVOICE GENERATION DATE invtime_ormntc 8 CHAR INVOICE GENERATION TIME invuser_ormntc 8 CHAR INVOICE GENERATION USER invbatch_ormntc 10 CHAR INVOICE GENERATION BATCH 3. INVOICEC - EDI Open Invoice Header Table Layout. Update the following fields in the EDI Open Invoice Header Table: FIELD NAME SIZE TYPE DESCRIPTION invflag_invoicec 2 CHAR INVOICE GENERATION FLAG invdate_invoicec 4 DATE INVOICE GENERATION DATE invtime_invoicec 8 CHAR INVOICE GENERATION TIME invuser_invoicec 8 CHAR INVOICE GENERATION USER invbatch_invoicec 10 CHAR INVOICE GENERATION BATCH 4. INVC - EDI Invoice History Header Table Layout. Update the following fields to the EDI Invoice History Header Table: FIELD NAME SIZE TYPE DESCRIPTION invflag_invoicec 2 CHAR INVOICE GENERATION FLAG invdate_invoicec 4 DATE INVOICE GENERATION DATE invtime_invoicec 8 CHAR INVOICE GENERATION TIME invuser_invoicec 8 CHAR INVOICE GENERATION USER invbatch_invoicec 10 CHAR INVOICE GENERATION BATCH Release NGS-7.00 EDI- 124

125 E. Screen Layouts. E1. Option Selection Screen. E2. Sort/ASCII Parameters Screen. Release NGS-7.00 EDI- 125

126 F. ACF Options. For an updated list of acf options use program acf and select edi* Release NGS-7.00 EDI- 126

127 EDIPOG - EDI PURCHASE ORDER ASCII FILE GENERATION A. Modification Summary. This program provides the capability to generate an ASCII file for the purpose of generating EDI Purchase Order transactions (850) to be transmitted to a vendor through a third party EDI mapping / translation / communications product. The edipog program can now run on an individual po and a batch basis. multiple users will be able to access the edipog program simultaneously. B. Modification Detail. The following describes the logic used to process outbound EDI Purchase Order transactions. B1. Program Flow. The operator will be prompted for the following options when generating the ASCII files. Once all the selections have been made, the operator will be prompted whether to proceed with the creation of the ASCII File. See Section C for the screen display formats for the program. 1. Selection Options Records will be selected from the open purchase order table (filename: pohdr) where the memo 4 field (field name: memo4_pohdr) is set to "EDI" (to indicate EDI transactions are utilized for the vendor) and where the EDI purchase order generation flag in the applicable EDI Trading Partner Vendor Master record (field name: poflag_editpv) is set to "Y". Once a purchase order is selected, the system will select the corresponding trading partner record from the EDI Trading Partner Vendor Master Table (editpv) which will be accessed by the division, department, branch and vendor id of each transaction. The system will select the first record meeting the conditions met in the following hierarchy: Division Department Branch Vendor division_pohdr dept_pohdr branch_pohdr vendor_pohdr division_pohdr dept_pohdr "ALL" vendor_pohdr division_pohdr "ALL" branch_pohdr vendor_pohdr division_pohdr "ALL" "ALL" vendor_pohdr Note that the memo 4 field is defined in the vendor record through the Vendor Maintenance program (VM) but may be overridden (if desired) on a purchase order basis. The following header selection options will be available for purchase order selection: 1- By Selected Division ID - selection based on division_pohdr. 2- By Selected Branch ID - selection based on branch_pohdr. 3- By Selected Department ID - selection based on dept_pohdr. 4- By Selected Trading Partner ID - selection based on partnrid_editpv. (where vendor_editpv = vendor_pohdr and division_editpv = division_pohdr and (dept_editpv = dept_pohdr OR dept_editpv = ALL) and (branch_editpv = branch_pohdr OR branch_editpv = ALL). 5- By selected Vendor ID - selection based on vendorid_pohdr. Release NGS-7.00 EDI- 127

128 The following header transaction selection options will be available. This option will default to "1-All Ungenerated Invoices". 1- All Ungenerated Purchase Orders. This selection option will select all records from the Open Purchase Order Header table where the purchase order EDI generation flag in the Open Purchase Order Header table (field name: crcardtp_pohdr) is not valued or not set to "Y" for the header selection options entered.. 2- Selected Ungenerated Purchase Order Numbers. This selection option will select records from the Open Purchase Order table based on the purchase order number(s) entered where the purchase order EDI generation flag in the Open Purchase Order table (field name: crcardtp_pohdr) is not valued or is not set to "Y" for the header selection option entered. 3- Selected Generated Purchase Order Numbers. This selection option will select records from the Open Purchase Order table based on the purchase order number(s) entered where the purchase order EDI generation flag in the Open Purchase Order table (field name: crcardtp_pohdr) is set to "Y" for the header selection options entered. 4-Selected Generated EDI Batch. This selection option will select records from the Open Purchase Order table based on the EDI purchase order batch criteria entered corresponding to the EDI purchase order batch number (field name: edicode_pohdr) and where the purchase order EDI generation flag in the Open Purchase Order table (field name: crcardtp_pohdr) is set to "Y" for the header selection options entered. 5- Selected Generated Date. This selection option will select records from the Open Purchase Order table based on the purchase order date criteria entered corresponding to the EDI generation date (field name: crexpirdt_pohdr) and where the purchase order EDI generation flag in the Open Purchase Order table (field name: crcardtp_pohdr) is set to "Y" for the header selection options entered. 2. Sort & Print Options The following sort options will be available. The option will default to the contents of the ACF EDIPOSRT Option (which will be initially set to 4): 1- By Division ID, Trading Partner ID, Purchase Order Number. (field names: division_edipoh, partnrid_edipoh, poid_edipoh). 2- By Department ID, Trading Partner ID, Purchase Order Number. (field names: dept_edipoh, partnrid_edipoh, poid_edipoh). 3- By Branch ID, Trading Partner ID, Purchase Order Number. (field names: branch_edipoh, partnrid_edipoh, poid_edipoh). 4- By Trading Partner ID, Purchase Order Number. (field names: partnrid_edipoh, poid_edipoh). 5- By Purchase Order Number. (field names: poid_edipoh). 6- By Division ID, Department ID, Trading Partner ID, Purchase Order Number. (field names: division_edipoh, dept_edipoh, partnrid_edipoh, poid_edipoh). 7- By Division ID, Branch ID, Trading Partner ID, Purchase Order Number. (field names: division_edipoh, branch_edipoh, partnrid_edipoh, poid_edipoh). Note that the detail records will have a line sequence number generated. This will be generated in purchase order line sequence (field name: line_podet). The detail records will be sorted by the line number generated (field name: seqno_edipod). Release NGS-7.00 EDI- 128

129 The following options will be available to define the detail records to include in the ASCII file: 1- Include all lines. 2- Include only lines where quantity ordered is present. The difference is that option 1 will include zero quantity detail lines. The default value will be the contents of the ACF EDIPOPRT option. 3. ASCII Files Options. The operator will be prompted for the following to define the ASCII file parameters: 1- ASCII File Field Delimiter. This will be the field delimiter used in the ASCII file output. The default will be the contents of the ACF EDIPODEL Option which will be initially set to the pipe ( ) symbol 2- ASCII File Name. This will be the ASCII file name to be generated for the file. The file name will be the format <PREFIX FILE NAME>.<SUFFIX FILE NAME>. The suffix file name will default to the contents of the ACF EDIPOFLS Option which should be defined as a 3 character name (i.e. dat). The prefix file name will default to the contents of the ACF EDIPOFLP Option. This option should either be set to a 1-8 character name (i.e. edi850po) or to "TODAY". If the option is set to TODAY, the system will use the month and day of the current date and the EDI batch number assigned to the transaction as the prefix file name in the format MMDDSSSS where MM is the current month, DD is the current date and SSSS are the last 4 characters of the batch number. 3- Directory Path. This will be the VALID directory on the Unix system where the ASCII file will be generated. The default will be the contents of the ACF EDIPODIR Option. If an invalid directory is selected, the program will display the message "Invalid Directory", wait for a brief period and exit the program. 4. General Processing Logic. Once the selections have been made, the operator will be prompted whether to proceed with the creation of the ASCII File. If they proceed, the system will display the next EDI Purchase Order Batch Number at the base of the screen. This number will be assigned to all purchase order records included in the file and will be set to the contents of the ACF "EDIPOBAT" option. The ACF value will be incremented by 1 and updated. The system will then select records from the purchase order header & detail tables and any corresponding files required and generate records in the EDI Purchase Order Work Files. Once these records are created, the system can perform any data manipulation required through a subroutine. The capability of executing a separate custom subroutine program once the work file is generated but before the ASCII file is generated should be provided. This will be provided through an ACF option (edipog_) that will work in the same manner as the "bill_" ACF options. Once the subroutine is completed, control will return to the main program, which will generate the ASCII file. The system will allow values of edipog00 - edipog09 for the routine. Once the data manipulation is completed, the system will generate the ASCII file. Once the generation is completed, the program will update the EDI PO generation fields in the purchase order tables and go to program end. The ASCII file generated may then be transferred to the PC using a standard PC transfer program (i.e. FTP). You will need to select the directory the ASCII file resides in and the ASCII file name. Once the ASCII file has been transferred to the PC, the third party PC software package must be used to map, translate, format and transfer the data in the ASCII file to the trading partners EDI format. The third party product must then be used to transfer the EDI file to the trading partner. Release NGS-7.00 EDI- 129

130 A new output option is available to allow the user to FTP the edi purchase orders to the trading partner directly from the EDIPOG program. This must be done prior to the printing of the Purchase Orders. When the following prompt appears the user will enter F to setup the FTP process. Proceed with creating ASCII file (Y/N/Ftp/E)? [ ] The program will retrieve the Trading partnerinfo from the 'editpv' table and send it via the FTPSEND program. 5. EDI PO Generation Update. The following fields in the purchase order table will be used to audit the creation of EDI ASCII files: Field Name Field Type Field Size Usage Description edicode_pohdr CHAR 10 EDI Batch Number. crcardtp_pohdr CHAR 4 EDI PO Generation Flag. crcardno_pohdr CHAR 19 EDI PO Generation User ID. crexpirdt_pohdr DATE 8 EDI PO Generation Date. crcardauth_pohdr CHAR 8 EDI PO Generation Time. jobrev_podet INT 4 EDI PO Line Number Assigned. The following fields will be set in the purchase order header table (pohdr) once the ASCII file has been created. Note that the updating will only occur when processing purchase orders not previously generated (header transaction selection options 1 and 2): - The EDI PO Generation Flag will be set to "Y" (crcardtp_pohdr). - The EDI PO Generation Date will be set to the current date (crexpirdt_pohdr). - The EDI PO Generation Time will be set to the current time (crcardauth_pohdr). - The EDI PO Generation User will be set to the user performing the generation (crcardno_pohdr). - The EDI PO Generation Batch Number will be set to the contents of the ACF "EDIPOBAT" option (edicode_pohdr). If the trading partner purchase order print flag is not set to "Y" (poprtflg_editpv), the following fields will be set in the Open Purchase Order Header table (pohdr) and Open Purchase Order Detail table (podet): - The purchase order print flag will be set to "N" (printflag_pohdr). - The purchase order revised flag will be set to "N" (porevised_pohdr). - The purchase order line print flag will be set to "N" on all detail lines for the purchase order (lineprint_podet). - The purchase order line revised flag will be set to "N" on all detail lines for the purchase order (linerevsd_podet). - The jobrev_podet field (representing the ASCII file line number assigned) will be set incrementally for each line in PO line number sequence, starting with 1. For example, if a PO has line numbers 10, 30 and 40, this field will be set to 1 on line 10, 2 on line 30 and 3 on line 40. Release NGS-7.00 EDI- 130

131 6. EDI Download Record Generation Detail Logic. The system will first remove all records from the EDI Purchase Order Download Tables (file names: edipoh, edipod). Note that this requires that only one user access the EDIPOG program at a time. Security will be setup to prevent multiple users from accessing the program. 6A. Purchase Order Header Logic. The system will select records from the Purchase Order Header Table (file name: pohdr) which meet the selection criteria defined above. Once a purchase order is selected, the system will select the corresponding trading partner record from the EDI Trading Partner Vendor Master Table (editpv) to access the Trading Partner information. The table will be accessed by the division, department, branch and vendor id of the transaction in the following hierarchy and will select the record of the first condition met: Division Department Branch Vendor division_pohdr dept_pohdr branch_pohdr vendor_pohdr division_pohdr dept_pohdr "ALL" vendor_pohdr division_pohdr "ALL" branch_pohdr vendor_pohdr division_pohdr "ALL" "ALL" vendor_pohdr The system will then select the freight payment method description (field name: fpdesc_frtpaymeth) from the Freight Payment Method Table (file name: frtpaymeth) for the freight payment method on the purchase order (criteria: where fpcode_frtpaymeth = frtpay_pohdr). The system will then select the Terms Table record (file name: terms) where the terms code corresponds to the terms code on the transaction (criteria: where code_terms = poterms_pohdr). The system will select the terms description, due days, discount days and discount percentage for the terms code selected (field names: desc_terms, due_days_terms, trm_days_terms, trm_pcnt_terms). The system will then select the EDI Terms Table record (file name: editerm) where the trading partner and terms codes correspond to those on the purchase order (criteria: where partnrid_editerm = partnrid_editp and terms_cd_editerm = poterms_pohdr). The system will select the terms type and terms basis date codes (field names: termtype_editerm, termbase_editerm). If a record is not found, the fields will not be valued in the ASCII file. The system will then select the EDI Ship Via record (filename: edisv) where the trading partner and ship via codes correspond to those on the transaction (criteria: where partnrid_edisv = partnrid_editp and svcode_edisv = shipvia_pohdr). The system will select the routing, carrier name/routing description and the SCAC code (field names: routing_edisv, carrier_edisv, scac_edisv). If a record is not found, the fields will not be valued in the ASCII file. The system will then select the buyer name from the buyer table (filename: buyer) where the buyer id matches the buyer id on the purchase order (id_buyer = buyer_pohdr). If the buyer record is not found, the system will use the buyer id on the purchase order instead of the buyer name. Release NGS-7.00 EDI- 131

132 The system will select the bill to name from the division, department or branch master table, based on the contents of the ACF "EDIPOADR" option and the corresponding field in the purchase order header: EDI Field Name Next-Generation Field Descr. Next-Generation Field Name. - Customer Name. Your Division name. name_division. - If ACF option = "1" - (based on division_division = division_pohdr). Your Department name. name_dept. - If ACF option = "2" - (based on deptid_dept = dept_pohdr). Your Branch name. name_branch. - If ACF option = "3" - (based on id_branch = branch_pohdr). If the trading partner output state format (field name: statefrm_editpv) is set to "1", the system will only output the first 2 characters of the 4 character state field. If set to "2", the full 4 character state field will be output. If the trading partner output zip format (field name: zipform_editpv) is set to "1", the system will only output the first 5 characters of the 10 character zip code field. If the format is set to "2", the system will only output the first 9 characters of the 10 character zip code field. If the format is set to "3", the system will output the full 10 character zip code field. If the trading partner output date format (field name: dateform_editpv) is set to "1", all dates will be output in the format "YYMMDD". Otherwise, the dates will be output in the format "MMDDYY". The system will then generate a record in the EDI Purchase Order Download Header Table (file name: edipoh). Release NGS-7.00 EDI- 132

133 6B. Purchase Order Detail Logic. The system will then select records from the Purchase Order Detail Table (file name: podet) for the purchase order entered (where poid_podet = poid_pohdr). For each line item of the purchase order, the system will assign and increment the purchase order line number on the purchase order starting with 1. For example, if there are 3 lines on the purchase order with line numbers 10, 30 and 40, ASCII file line "001" will be line 10, ASCII file line "002" will be line 30 and ASCII file line "003" will be line 40. The line number assigned will be updated to a Purchase Order Detail Table field (field name: jobrev_podet). The system will select the vendor part id (field name: venpart_vixref) from the Vendor Item Cross- Reference Table (file name: vixref) where the vendor id and item id correspond to the purchase order detail record and where the purchase order date is within the start and end date range (criteria: where vendorid_vixref = vendor_pohdr and itemid_vixref = itemid_podet and (effstart_vixref is NULL or effstart_vixref <= podate_pohdr) and (expdate_vixref is NULL or expdate_vixref >= podate_pohdr). UPC Codes may be defined in the Item Interchange Table through the Item Interchange Maintenance program, if desired (IIM). In order to designate the record as a UPC type record, enter the characters "UPC" EXACTLY in the memo 2 field. Note that only 1 UPC record should be setup per item id and that, if desired, the UPC code can be defined in an Item Master Table field (i.e. item cross-reference) instead, if desired. The system will determine if a corresponding UPC code exists by selecting a single record item interchange id (field name: interchgid_cixref) from the Item Interchange Table (file name: cixref) for the item id (criteria: where ouritemid_cixref = itemid_podet and rectype_cixref = "2" and memo2_cixref = "UPC"). Note that this will be selected only if there is ONE record in the table which meets the criteria. The system will then determine the total number of detail lines in the Purchase Order Detail Table (file name: podet; criteria: select count(*) from podet where poid_podet = poid_pohdr). The system will determine the quantity and unit of measure to send, based on the criteria defined below: If the trading partner unit of measure method (pouommth_editpv) is set to "0", the system will always send the primary (po_um_podet) or alternate unit of measure (alt_po_um_podet) in the purchase order detail table, based on the quantity ordered (po_qty_podet) on the purchase order line. If there is no alternate quantity ordered (alt_po_qty_podet), the system will use the quantity ordered and the primary unit of measure. If there is an alternate unit of measure quantity, the system will convert the quantity ordered plus the alternate quantity ordered to the alternate unit of measure (based on the po alternate conversion factor (po_alt_conv_podet)) and use the alternate unit of measure. This method assumes that your unit of measure codes will always match the trading partners. If the method is set to "1", the system will always use the default unit of measure from the trading partner record (pouom_editpv). This assumes that you are always utilizing a single unit of measure with the trading partner and that this is the primary unit of measure in the purchase order detail record. Release NGS-7.00 EDI- 133

134 If the method is set to "2", the system will first attempt to convert the unit of measure for the purchase order detail line (primary or alternate, based on the logic defined for method zero) by accessing the Trading Partner Unit Of Measure Cross-Reference Table (ediuom). If a record exists for the trading partner & item id & unit of measure code on the detail line (selected by the fields partnrid_ediuom, itemid_ediuom, uom_ediuom), the system will use the trading partners unit of measure code (custuom_ediuom). If a record does not exist for the trading partner & item id & unit of measure code on the detail line and the default unit of measure is valued for the trading partner, the system will use the trading partner default unit of measure (pouom_editpv). If a record does not exist for the trading partner & item id & unit of measure and there is no default unit of measure defined for the trading partner, the system will use the primary or alternate unit of measure in the purchase order detail record, based on the logic defined for method zero. The costing unit of measure to be sent will be determined based on the trading partner unit of measure method as well. If the trading partner unit of measure method (pouommth_editpv) is set to "0", the system will always send the costing unit of measure (costing_um_podet) in the purchase order detail record. This method assumes that your unit of measure codes will always match the trading partners. If the method is set to "1", the system will always use the default unit of measure from the EDI Trading Partner Vendor Master record (pouom_editpv). This assumes that you are always utilizing a single unit of measure with the trading partner and that this is the costing unit of measure on the purchase order detail line. If the method is set to "2", the system will first attempt to convert the costing unit of measure for the purchase order detail line by accessing the EDI Trading Partner Unit Of Measure Cross-Reference Table (ediuom). If a record exists for the trading partner & item id & unit of measure code on the detail line (selected by the fields partnrid_ediuom, itemid_ediuom, uom_ediuom), the system will use the trading partners unit of measure code (custuom_ediuom). If a record does not exist for the trading partner & item id & unit of measure code on the detail line and the default unit of measure is valued for the trading partner, the system will use the trading partner default unit of measure (pouom_editpv). If a record does not exist for the trading partner & item id & unit of measure and there is no default unit of measure defined for the trading partner, the system will use the po costing unit of measure on the purchase order detail line. If the trading partner output date format (field name: dateform_editpv) is set to "1", all dates will be output in the format "YYMMDD". Otherwise, the dates will be output in the format "MMDDYY". The system will then generate a record in the EDI Purchase Order Download Detail Table (file name: edipod). 6C. Purchase Order Header/Detail Summary Logic. For each purchase order in the EDI Purchase Order Download Header Table (file name: edipoh), the system will determine the total number of detail lines and the total quantity in the EDI Purchase Order Download Detail Table and update the corresponding fields in the header table (file name: edipodet; criteria: select count(*) from edipod where poid_edipod = poid=edipoh; quantity criteria: select sum(po_qty_edipod) from edipod where poid_edipod = poid_ edipoh). Options are provided for: - Generating separate header and detail records in the ASCII file. - A fixed format option with no delimiter between fields. - Allowing an option for implied decimal point in decimal fields. Release NGS-7.00 EDI- 134

135 C. Screen Display Layouts. 1. Option Selection Screen. 2. Sort/ASCII Parameters Screen. Release NGS-7.00 EDI- 135

136 ACF Options for edipog processing - *** view all edi options using edi* from the acf pgm *** Release NGS-7.00 EDI- 136

137 E. Outbound Vendor Purchase Order ASCII File Definition (850) - Header/Detail Combined Formt. The following is a layout of the fields in the outbound ASCII file in field number sequence which will be downloaded by the system. All fields will be left justified. Fields 1 to 107 are header fields and fields 108 to 175 are detail fields. Note that if there are multiple detail lines for a purchase order, the header information will be duplicated on all the applicable records. OUTBOUND Purchase Order ACSII FILE LAYOUT # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 1. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 partnrid_editpv partnrid_edipoh 2. P/O NUMBER. CHAR 10 poid_pohdr poid_edipoh. 3. EDI TRANSACTION DOCUMENT. CHAR 3 "850" poeditr_edipoh. 4. CUSTOMER PURCHASE ORDER EDI BATCH NO.CHAR 10 ACF: edipobat pobatch_edipoh 5. BILL TO NAME. CHAR 27 name_division billname_edipoh name_department. name_branch. 6. BILL TO ID. CHAR 35 billto_editpv billto_edipoh 7. SOLD TO ID. CHAR 35 soldto_editpv soldto_edipoh 8. SHIP TO ID. CHAR 35 shipto_editpv shipto_edipoh 9. BILL TO ID INDICATOR. CHAR 2 btlook_editpv btlook_edipoh 10. TRANSACTION DATE. DATE 6 TODAY - Generation Dt trandate_edipoh. 11. REQUESTED (WANTED) DATE. DATE 6 datewanted_pohdr. datewant_edipoh. 12. PROMISED DATE. DATE 6 dateprom_pohdr. dateprom_edipoh. 13. CANCEL BY DATE. DATE 6 cnclbydt_pohdr. canceldt_edipoh. 14. PURCHASE ORDER DATE. DATE 6 podate_pohdr. podate_edipoh. 15. NOT BEFORE DATE. DATE 6 notbeforedt_pohdr. notbefdt_edipoh. 16. REFERENCE NUMBER. CHAR 30 FUTURE USE reference_edipoh. 17. DEPARTMENT. CHAR 30 FUTURE USE department_edipoh. 18. REMARKS. CHAR 20 remarks_pohdr. remarks_edipoh. 19. SHIP TO INDICATOR. CHAR 2 bslook_editpv bslook_edipoh if trantype_pohdr = "DP" (Drop Ship) 20. SHIP TO NAME. CHAR 27 vsname_pohdr If trantype_pohdr = DP (Drop Ship) vsname_edipoh 21. SHIP TO ADDRESS 1. CHAR 27 vsaddr1_pohdr If trantype_pohdr = DP vsaddr1_edipoh 22. SHIP TO ADDRESS 2. CHAR 27 vsaddr2_pohdr (If trantype_pohdr = DP) vsaddr2_edipoh 23. SHIP TO ADDRESS 3. CHAR 27 vsaddr3_pohdr (If trantype_pohdr = DP) vsaddr3_edipoh 24. SHIP TO CITY. CHAR 18 vscity_pohdr. (If trantype_pohdr = DP) vscity_edipoh 25. SHIP TO STATE. CHAR 4 vsstate_pohdr (If trantype_pohdr = DP) vsstate_edipoh 26. SHIP TO COUNTRY. CHAR 10 vcountry_pohdr (If trantype_pohdr = DP) vscntry_edipoh 27. SHIP TO ZIP CODE. CHAR 10 vszip_pohdr (If trantype_pohdr = DP) vszip_edipoh Release NGS-7.00 EDI- 137

138 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 28. SHIP TO ATTENTION. CHAR 27 vsattn_pohdr (If trantype_pohdr = DP) vsattn_edipoh 29. SHIP TO PHONE NUMBER. CHAR 15 vsphone_pohdr (If trantype_pohdr = DP) vsphone_edipoh 30. VENDOR SHIP TO ID. CHAR 10 vshiptoid_pohdr (If trantype_pohdr = DP) vshipto_edipoh 31. TRANSACTION CODE. CHAR 2 potrancd_editpv transcd_edipoh. 32. TRANSACTION TYPE. CHAR 2 potranty_editpv transtype_edipoh. 33. CONTRACT NUMBER. CHAR 20 contract_pohdr contract_edipoh 34. ROUTING. CHAR 2 routing_edisv routing_edipoh 35. CARRIER / ROUTING DESCRIPTION. CHAR 35 carrier_edisv carrier_edipoh 36. SCAC. CHAR 4 scac_edisv scac_edipoh 37. TRANSPORTATION METHOD / TYPE CODE. CHAR 2 trmethod_edisv trmethod_edipoh 38. SHIPMENT METHOD OF PAYMENT. CHAR 4 frtpay_pohdr frtpay_edipoh 39. SHIPMENT METHOD OF PAYMENT DESCR. CHAR 20 fpdesc_frtpaymeth fpdesc_edipoh 40. TERMS CODE. CHAR 4 poterms_pohdr poterms_edipoh 41. TERMS TYPE CODE. CHAR 2 termtype_editerm termtype_edipoh 42. TERMS BASIS DATE CODE. CHAR 2 termbase_editerm termbase_edipoh 43. TERMS DISCOUNT PERCENT. DEC 6 trm_pcnt_terms trm_pcnt_edipoh Format: "xxx.xx". Impled: "xxxxx" 44. TERMS DISCOUNT DUE DATE. DATE 6 FUTURE USE. trmdiscdt_edipoh. 45. TERMS DISCOUNT DAYS DUE. INT 3 trm_days_terms trm_days_edipoh 46. TERMS NET DUE DATE. DATE 6 FUTURE USE. trmnetdt_edipoh 47. TERMS NET DAYS. INT 3 due_days_terms due_days_edipoh. 48. TERMS DISCOUNT AMOUNT. DEC 10 FUTURE USE. trm_disc_edipoh. 49. TERMS DESCRIPTION CHAR 20 desc_terms. trm_desc_edipoh. 50. ALLOWANCE / CHARGE INDICATOR. CHAR 1 FUTURE USE. allowind_edipoh. 51. SPECIAL SERVICES CODE. CHAR 10 FUTURE USE. spsrvcd_edipoh. 52. ALLOWANCE / CHARGE METHOD OF HANDLG. CHAR 2 FUTURE USE. allowmeth_edipoh. 53. ALLOWANCE OR CHARGE NUMBER. CHAR 16 FUTURE USE. allownum_edipoh. 54. ALLOWANCE OR CHARGE RATE. DEC 6 FUTURE USE. allowrate_edipoh. 55. ALLOWANCE OR CHARGE TOTAL AMOUNT. DEC 10 FUTURE USE. allowtot_edipoh. 56. ALLOWANCE OR CHARGE DESCRIPTION. CHAR 80 FUTURE USE. allowdesc_edipoh. 57. SPECIAL CHARGE OR ALLOWANCE CODE. CHAR 3 FUTURE USE. allowcd_edipoh. 58. PURCHASE ORDER QUANTITY. INT 7 (sum (po_qty_podet)). po_qty_edipoh. sum(po_qty_edipod). Release NGS-7.00 EDI- 138

139 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 59. PURCHASE ORDER NUMBER OF LINES. INT 4 count(podet records). po_lines_edipoh. 60. PURCHASE ORDER WEIGHT. DEC 8 poextwt_pohdr. poextwt_edipoh. 61. PURCHASE ORDER VOLUME. DEC 8 poextvol_pohdr. poextvl_edipoh. 62. PURCHASE ORDER TOTAL AMOUNT. DEC 10 totgrossext_pohdr. pototal_edipoh. 63. PURCHASE ORDER WEIGHT UNIT BASIS. CHAR 2 FUTURE USE. powtbase_edipoh. 64. PURCHASE ORDER VOLUME UNIT BASIS. CHAR 2 FUTURE USE. povlbase_edipoh. 65. DIVISION ID. CHAR 4 division_pohdr. division_edipoh. 66. DEPARTMENT ID. CHAR 5 dept_pohdr dept_edipoh 67. BRANCH ID. CHAR 8 branch_pohdr branch_edipoh. 68. CONFIRMATION PO FLAG CHAR 1 confirming_pohdr confirming_edipoh. 69. CONFIRM TO. CHAR 15 confirmto_pohdr. confirmto_edipoh 70. JOB NUMBER. CHAR 10 job_pohdr job_edipoh 71. MISCELLANEOUS INFORMATION 1. CHAR 25 miscinfo1_pohdr. miscinfo1_edipoh. 72. MISCELLANEOUS INFORMATION 2. CHAR 25 miscinfo2_pohdr. miscinfo2_edipoh. 73. MISCELLANEOUS INFORMATION 3. CHAR 25 miscinfo3_pohdr. miscinfo3_edipoh. 74. DELIVER TO. CHAR 15 deliverto_pohdr. deliverto_edipoh. 75. REQUESTED BY. CHAR 12 req_by_pohdr. req_by_edipoh. 76. BUYER NAME. CHAR 20 name_buyer buyer_edipoh. buyer_pohdr 77. WORK CENTER. CHAR 4 workcntr_pohdr workcntr_edipoh. 78. BACK ORDER FLAG. CHAR 1 backorder_pohdr. backorder_edipoh. 79. TAXABLE FLAG. CHAR 1 taxable_pohdr. taxable_edipoh. 80. PO REVISED FLAG. CHAR 1 porevised_pohdr. porevised_edipoh. 81. PO REVISION DATE. DATE 6 porevdate_pohdr. porevdate_edipoh. 82. PO REVISION CODE. CHAR 3 porevsn_pohdr. porevsn_edipoh. 83. VENDOR NOTE 1. CHAR 25 vendnote1_pohdr. vendnote1_edipoh. 84. VENDOR NOTE 2. CHAR 25 vendnote2_pohdr. vendnote2_edipoh. 85. VENDOR NOTE 3. CHAR 25 vendnote3_pohdr. vendnote3_edipoh. 86. VENDOR NOTE 4. CHAR 25 vendnote4_pohdr. vendnote4_edipoh. 87. VENDOR NOTE 5. CHAR 25 vendnote5_pohdr. vendnote5_edipoh. Release NGS-7.00 EDI- 139

140 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 88. MEMO1. CHAR 30 FUTURE USE memo1_edipoh. 89. MEMO2. CHAR 30 FUTURE USE memo2_edipoh. 90. MEMO3. CHAR 10 FUTURE USE memo3_edipoh. 91. MEMO4 (NUMERIC). DEC 10 FUTURE USE memo4_edipoh. 92. MEMO5 (DATE). DATE 6 FUTURE USE memo5_edipoh. 93. HEADER MEMO 1. CHAR 30 FUTURE USE hmemo1_edipoh. 94. HEADER MEMO 2. CHAR 30 FUTURE USE hmemo2_edipoh 95. HEADER MEMO 3. CHAR 30 FUTURE USE hmemo3_edipoh 96. HEADER MEMO 4. CHAR 30 FUTURE USE hmemo4_edipoh 97. HEADER MEMO 5. CHAR 30 FUTURE USE. hmemo5_edipoh 98. HEADER MEMO 6. CHAR 30 FUTURE USE. hmemo6_edipoh 99. HEADER MEMO 7. CHAR 30 FUTURE USE. hmemo7_edipoh 100. HEADER MEMO 8. CHAR 30 FUTURE USE. hmemo8_edipoh 101. HEADER MEMO 9. CHAR 30 FUTURE USE. hmemo9_edipoh 102. HEADER MEMO 10. CHAR 30 FUTURE USE. hmemo10_edipoh 103. HEADER MEMO 11. CHAR 30 FUTURE USE hmemo11_edipoh 104. HEADER MEMO 12. CHAR 30 FUTURE USE hmemo12_edipoh 105. HEADER MEMO 13. CHAR 30 FUTURE USE hmemo13_edipoh 106. HEADER MEMO 14. CHAR 30 FUTURE USE hmemo14_edipoh 107. HEADER MEMO 15. CHAR 30 FUTURE USE hmemo15_edipoh 108. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 partnrid_editp partnrid_edipod 109. P/O NUMBER. CHAR 10 poid_pohdr. poid_edipod 110. P/O LINE NUMBER. INT 4 line_podet poline_edipod Format: "XXXX" 111. VENDOR P/O LINE SEQUENCE NUMBER. INT 3 (System Assigned) (Zero filled). poseq_edipod Format: "XX" 112. VENDOR PART ID - PO. CHAR 18 vendpart_podet. vendpart_edipod VENDOR PART ID - VENDOR. CHAR 18 venpart_vixref vendpart2_edipod UPC CODE. CHAR 18 upc_edipod or interchgid_cixref ( if memo2_cixref = UPC and rectype_cixref = ITEM ID. CHAR 25 itemid_podet. itemid_edipod ITEM DESCRIPTION 1. CHAR 30 itemdesc_podet desc1_edipod 117. ITEM DESCRIPTION 2. CHAR 30 itemdesc2_podet desc2_edipod Release NGS-7.00 EDI- 140

141 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 118. ITEM CROSS-REFERENCE. CHAR 25 itemxref_podet. xref_edpod QUANTITY ORDERED. INT 7 po_qty_podet po_qty_edipod alt_po_qty_podet Format: "XXXXXX" 120. UNIT OF MEASURE. CHAR 2 po_um_podet po_um_edipod alt_po_um_podet. uom_ediuom. uom_editpv UNIT PRICE. DEC 10 po_cost_podet po_cost_edipod Format: "-XXXXXX.XX" Implied: -XXXXXXXX 122. UNIT PRICE - PRICING UNIT OF MEASURE. DEC 10 po_cost_podet * po_cost2_edipod. cost_conv_podet Format: "-XXXXXX.XX" Implied: -XXXXXXXX 123. ITEM BASIS OF UNIT PRICE. CHAR 2 FUTURE USE. pocstbase_edipod PRICING UNIT OF MEASURE. CHAR 2 costing_um_podet. cost_um_edipod uom_ediuom uom_editpv 125. EXTENDED COST. DEC 10 extcost_podet. extcost_edipod. Format: "-XXXXXX.XX" Implied: -XXXXXXXX 126. RETAIL PRICE. DEC 10 FUTURE USE retlprc_edipod FREIGHT AMOUNT. DEC 10 FUTURE USE frt_edipod REQUESTED (WANTED) DATE. DATE 6 datewanted_podet datewant_edipod PROMISED DATE. DATE 6 dateprom_pode dateprom_edipod CANCEL BY DATE. DATE 6 cancelby_podet. canceldt_edipod PURCHASE ORDER DATE. DATE 6 podate_podet. podate_edipod NOT BEFORE DATE. DATE 6 notbefore_podet notbefdt_edipod 133. PO UNIT WEIGHT. DEC 7 pounitwt_podet pounitwt_edipod Format: "-XXXXXX.XX" Implied: -XXXXXXXX 134. PO UNIT VOLUME. DEC 7 pounitvol_podet pounitvl_edipod Format: "-XXXXXX.XX" Implied: -XXXXXXXX 135. PO EXTENDED WEIGHT. DEC 7 poextwt_podet poextwt_edipod Format: "-XXXXXX.XX" Implied: -XXXXXXXX 136. PO EXTENDED VOLUME. DEC 7 poextvol_podet poextvl_edipod Format: "-XXXXXX.XX" Implied: -XXXXXXXX 137. DIVISION ID. CHAR 4 division_podet division_edipod 138. DEPARTMENT ID. CHAR 5 dept_podet dept_edipod 139. BRANCH ID. CHAR 8 branch_podet branch_edipod 140. JOB NUMBER. CHAR 10 job_podet job_edipod 141. DESTINATION. CHAR 10 destination_podet. destintn_edipod REQUISITION BY. CHAR 12 req_by_podet. req_by_edipod REQUESTED BY. CHAR 10 request_by_podet. request_by_edipod BUYER ID. CHAR 2 buyer_podet buyer_edipod 145. WORK CENTER. CHAR 4 workcntr_podet workcntr_edipod 146. TAXABLE FLAG. CHAR 1 taxable_podet taxable_edipod Release NGS-7.00 EDI- 141

142 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 147. PO LINE REVISED FLAG. CHAR 1 linerevsd_podet. linerevsd_edipod PO DETAIL MEMO 1. CHAR 15 memo1_podet. podmemo1_edipod PO DETAIL MEMO 2. CHAR 15 memo2_podet. podmemo2_edipod COMMODITY CODE. CHAR 6 commodity_podet. commodity_edipod CONTRACT NUMBER. CHAR 20 contract_no_podet. contract_edipod ITEM REVISION LEVEL. CHAR 4 itemrevlvl_podet. itemrevlv_edipod CUSTOMER ORDER NUMBER. CHAR 10 slsordnum_podet. slsordnum_edipod CUSTOMER ORDER LINE NUMBER. INT 4 slsordlin_podet. slsordlin_edipod. Format: "XXXX" CUSTOMER ORDER SUB LINE NUMBER. CHAR 4 slsordsub_podet. slsordsub_edipod MEMO 1. CHAR 30 FUTURE USE. memo1_edipod MEMO 2. CHAR 30 FUTURE USE. memo2_edipod MEMO 3. CHAR 10 FUTURE USE. memo3_edipod MEMO 4 (NUMERIC). DEC 10 FUTURE USE memo4_edipod Format: "-XXXXXX.XX" Implied: -XXXXXXXX 160. MEMO 5 (DATE). DATE 6 FUTURE USE. memo5_edipod DETAIL MEMO 1. CHAR 30 FUTURE USE dmemo1_edipod 162. DETAIL MEMO 2. CHAR 30 FUTURE USE dmemo2_edipod 163. DETAIL MEMO 3. CHAR 30 FUTURE USE dmemo3_edipod 164. DETAIL MEMO 4. CHAR 30 FUTURE USE dmemo4_edipod 165. DETAIL MEMO 5. CHAR 30 FUTURE USE dmemo5_edipod 166. DETAIL MEMO 6. CHAR 30 FUTURE USE dmemo6_edipod 167. DETAIL MEMO 7. CHAR 30 FUTURE USE dmemo7_edipod 168. DETAIL MEMO 8. CHAR 30 FUTURE USE dmemo8_edipod 169. DETAIL MEMO 9. CHAR 30 FUTURE USE dmemo9_edipod 170. DETAIL MEMO 10. CHAR 30 FUTURE USE. dmemo10_edipod 171. DETAIL MEMO 11. CHAR 30 FUTURE USE. dmemo11_edipod 172. DETAIL MEMO 12. CHAR 30 FUTURE USE. dmemo12_edipod 173. DETAIL MEMO 13. CHAR 30 FUTURE USE. dmemo13_edipod 174. DETAIL MEMO 14. CHAR 30 FUTURE USE. dmemo14_edipod DETAIL MEMO 15. CHAR 30 FUTURE USE. dmemo15_edipod. Release NGS-7.00 EDI- 142

143 Field Type Definitions: CHAR - Character - Alpha-numeric characters.date Date - Date field in format "YYMMDD" or "MMDDYY" format, based on a trading partner flag. DEC - Decimal - Numeric field with at least one position to the left and 2 positions to the right of the decimal point with leading minus sign (if applicable). INT Integer - Numeric fields with at least 1 position and leading minus sign (if applicable); no fractional parts included. General Format Requirements: - File generated will be in ASCII format. - All records will have each field delineated with a pipe symbol (<174> ASCII character which is represented as ). - All records will be terminated with a <CARRIAGE RETURN><LINE FEED> or <LINE FEED>, based on the ACF "EDIPORDL" option.- All dates will be downloaded in the format: "YYMMDD" or "MMDDYY", based on a trading partner flag.- All alphanumeric character fields will be left justified. - All quantities will be downloaded in integer format: XXXXXXX. - All weights will be downloaded in Decimal Format: XXXXX.XX. If implied decimal: XXXXXXX. - All prices will be downloaded in Decimal Format: XXXXXXX.XX. If Implied decimal: XXXXXXXXX - All terms percentages will be downloaded in Decimal Format: XXX.XX. If implied decimal: XXXXX. - All terms days will be downloaded in Integer Format: XXX. - All amounts will be downloaded in Decimal Format: XXXXXXX.XX If implied decimal: XXXXXXXXX. - All fields will be output to their maximum length, not to the actual length of the field based on ACF option EDIPOLEN. Alpha-numeric character fields will be left-justified with blank following the data. Numeric fields will be right justified with leading zeroes. Release NGS-7.00 EDI- 143

144 F. Outbound Vendor Purchase Order ASCII File Definition (850) - Separate Header/Detail Format. The following is a layout of the fields in the outbound ASCII files in field number sequence which will be downloaded by the system. All fields will be left justified. Fields 1 to 108 are header fields which will be output to the header records and fields 109 to 177 are detail fields which will be output to the detail records. Note that if there are multiple detail lines for a purchase order, the header information will print once followed by each detail record for that purchase order. OUTBOUND Purchase Order ASCII FILE HEADER RECORD LAYOUT # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 1. HEADER RECORD INDICATOR. CHAR 03 "HDR". 2. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 partnrid_editpv. partnrid_edipoh. 3. P/O NUMBER. CHAR 10 poid_pohdr. poid_edipoh. 4. EDI TRANSACTION DOCUMENT. CHAR 3 "850". poeditr_edipoh. 5. CUSTOMER PURCHASE ORDER EDI BATCH NO. CHAR 10 ACF: edipobat. pobatch_edipoh. 6. BILL TO NAME. CHAR 27 name_division. billname_edipoh. name_department. name_branch. 7. BILL TO ID. CHAR 35 billto_editpv. billto_edipoh. 8. SOLD TO ID. CHAR 35 soldto_editpv. soldto_edipoh. 9. SHIP TO ID. CHAR 35 shipto_editpv. shipto_edipoh. 10. BILL TO ID INDICATOR. CHAR 2 btlook_editpv. btlook_edipoh. 11. TRANSACTION DATE. DATE 6 TODAY - Generation Dt. trandate_edipoh. 12. REQUESTED (WANTED) DATE. DATE 6 datewanted_pohdr. datewant_edipoh. 13. PROMISED DATE. DATE 6 dateprom_pohdr. dateprom_edipoh. 14. CANCEL BY DATE. DATE 6 cnclbydt_pohdr. canceldt_edipoh. 15. PURCHASE ORDER DATE. DATE 6 podate_pohdr. podate_edipoh. 16. NOT BEFORE DATE. DATE 6 notbeforedt_pohdr. notbefdt_edipoh. 17. REFERENCE NUMBER. CHAR 30 FUTURE USE reference_edipoh. 18. DEPARTMENT. CHAR 30 FUTURE USE department_edipoh. 19. REMARKS. CHAR 20 remarks_pohdr. remarks_edipoh. 20. SHIP TO INDICATOR. CHAR 2 bslook_editpv. bslook_edipoh. Only if trantype_pohdr = "DP" (Drop Ship). 21. SHIP TO NAME. CHAR 27 vsname_pohdr. vsname_edipoh. (If trantype_pohdr = DP) 22. SHIP TO ADDRESS 1. CHAR 27 vsaddr1_pohdr. vsaddr1_edipoh. (If trantype_pohdr = DP) 23. SHIP TO ADDRESS 2. CHAR 27 vsaddr2_pohdr. vsaddr2_edipoh. (If trantype_pohdr = DP) 24. SHIP TO ADDRESS 3. CHAR 27 vsaddr3_pohdr. vsaddr3_edipoh. (If trantype_pohdr = DP) Release NGS-7.00 EDI- 144

145 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 25. SHIP TO CITY. CHAR 18 vscity_pohdr vscity_edipoh. (If trantype_pohdr = DP) 26. SHIP TO STATE. CHAR 4 vsstate_pohdr vsstate_edipoh (If trantype_pohdr = DP) 27. SHIP TO COUNTRY. CHAR 10 vcountry_pohdr vscntry_edipoh (If trantype_pohdr = DP) 28. SHIP TO ZIP CODE. CHAR 10 vszip_pohdr vszip_edipoh (If trantype_pohdr = DP) 29. SHIP TO ATTENTION. CHAR 27 vsattn_pohdr vsattn_edipoh (If trantype_pohdr = DP) 30. SHIP TO PHONE NUMBER. CHAR 15 vsphone_pohdrvsphone_edipoh (If trantype_pohdr = DP) 31. VENDOR SHIP TO ID. CHAR 10 vshiptoid_pohdr vshipto_edipoh (If trantype_pohdr = DP) 32. TRANSACTION CODE. CHAR 2 potrancd_editpv transcd_edipoh 33. TRANSACTION TYPE. CHAR 2 potranty_editpv transtype_edipoh 34. CONTRACT NUMBER. CHAR 20 contract_pohdr contract_edipoh 35. ROUTING. CHAR 2 routing_edisv routing_edipoh. 36. CARRIER / ROUTING DESCRIPTION. CHAR 35 carrier_edisv. carrier_edipoh. 37. SCAC. CHAR 4 scac_edisv scac_edipoh. 38. TRANSPORTATION METHOD / TYPE CODE. CHAR 2 trmethod_edisv trmethod_edipoh. 39. SHIPMENT METHOD OF PAYMENT. CHAR 4 frtpay_pohdr. frtpay_edipoh. 40. SHIPMENT METHOD OF PAYMENT DESCR. CHAR 20 fpdesc_frtpaymeth. fpdesc_edipoh. 41. TERMS CODE. CHAR 4 poterms_pohdr poterms_edipoh 42. TERMS TYPE CODE. CHAR 2 termtype_editerm. termtype_edipoh. 43. TERMS BASIS DATE CODE. CHAR 2 termbase_editerm. termbase_edipoh. 44. TERMS DISCOUNT PERCENT. DEC 6 trm_pcnt_terms. trm_pcnt_edipoh. Format: "xxx.xx". Impled: "xxxxx" 45. TERMS DISCOUNT DUE DATE. DATE 6 FUTURE USE. trmdiscdt_edipoh. 46. TERMS DISCOUNT DAYS DUE. INT 3 trm_days_terms. trm_days_edipoh. 47. TERMS NET DUE DATE. DATE 6 FUTURE USE. trmnetdt_edipoh. 48. TERMS NET DAYS. INT 3 due_days_terms due_days_edipoh. 49. TERMS DISCOUNT AMOUNT. DEC 10 FUTURE USE. trm_disc_edipoh. 50. TERMS DESCRIPTION CHAR 20 desc_terms. trm_desc_edipoh. 51. ALLOWANCE / CHARGE INDICATOR. CHAR 1 FUTURE USE. allowind_edipoh. 52. SPECIAL SERVICES CODE. CHAR 10 FUTURE USE. spsrvcd_edipoh. 53. ALLOWANCE / CHARGE METHOD OF HANDLG.CHAR 2 FUTURE USE. allowmeth_edipoh. 54. ALLOWANCE OR CHARGE NUMBER. CHAR 16 FUTURE USE. allownum_edipoh. 55. ALLOWANCE OR CHARGE RATE. DEC 6 FUTURE USE. allowrate_edipoh. Release NGS-7.00 EDI- 145

146 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 56. ALLOWANCE OR CHARGE TOTAL AMOUNT. DEC 10 FUTURE USE. allowtot_edipoh. 57. ALLOWANCE OR CHARGE DESCRIPTION. CHAR 80 FUTURE USE. allowdesc_edipoh. 58. SPECIAL CHARGE OR ALLOWANCE CODE. CHAR 3 FUTURE USE. allowcd_edipoh. 59. PURCHASE ORDER QUANTITY. INT 7 (sum (po_qty_podet)). po_qty_edipoh. sum(po_qty_edipod). 60. PURCHASE ORDER NUMBER OF LINES. INT 4 count(podet records). po_lines_edipoh. 61. PURCHASE ORDER WEIGHT. DEC 8 poextwt_pohdr. poextwt_edipoh. 62. PURCHASE ORDER VOLUME. DEC 8 poextvol_pohdr. poextvl_edipoh. 63. PURCHASE ORDER TOTAL AMOUNT. DEC 10 totgrossext_pohdr. pototal_edipoh. 64. PURCHASE ORDER WEIGHT UNIT BASIS. CHAR 2 FUTURE USE. powtbase_edipoh. 65. PURCHASE ORDER VOLUME UNIT BASIS. CHAR 2 FUTURE USE. povlbase_edipoh. 66. DIVISION ID. CHAR 4 division_pohdr. division_edipoh. 67. DEPARTMENT ID. CHAR 5 dept_pohdr. dept_edipoh. 68. BRANCH ID. CHAR 8 branch_pohdr. branch_edipoh. 69. CONFIRMATION PO FLAG CHAR 1 confirming_pohdr. confirming_edipoh. 70. CONFIRM TO. CHAR 15 confirmto_pohdr. confirmto_edipoh. 71. JOB NUMBER. CHAR 10 job_pohdr job_edipoh. 72. MISCELLANEOUS INFORMATION 1. CHAR 25 miscinfo1_pohdr. miscinfo1_edipoh. 73. MISCELLANEOUS INFORMATION 2. CHAR 25 miscinfo2_pohdr. miscinfo2_edipoh. 74. MISCELLANEOUS INFORMATION 3. CHAR 25 miscinfo3_pohdr. miscinfo3_edipoh. 75. DELIVER TO. CHAR 15 deliverto_pohdr. deliverto_edipoh. 76. REQUESTED BY. CHAR 12 req_by_pohdr. req_by_edipoh. 77. BUYER NAME. CHAR 20 name_buyer buyer_edipoh. buyer_pohdr 78. WORK CENTER. CHAR 4 workcntr_pohdr workcntr_edipoh. 79. BACK ORDER FLAG. CHAR 1 backorder_pohdr. backorder_edipoh. 80. TAXABLE FLAG. CHAR 1 taxable_pohdr. taxable_edipoh. 81. PO REVISED FLAG. CHAR 1 porevised_pohdr. porevised_edipoh. 82. PO REVISION DATE. DATE 6 porevdate_pohdr. porevdate_edipoh. 83. PO REVISION CODE. CHAR 3 porevsn_pohdr. porevsn_edipoh. Release NGS-7.00 EDI- 146

147 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 84. VENDOR NOTE 1. CHAR 25 vendnote1_pohdr. vendnote1_edipoh. 85. VENDOR NOTE 2. CHAR 25 vendnote2_pohdr. vendnote2_edipoh. 86. VENDOR NOTE 3. CHAR 25 vendnote3_pohdr. vendnote3_edipoh. 87. VENDOR NOTE 4. CHAR 25 vendnote4_pohdr. vendnote4_edipoh. 88. VENDOR NOTE 5. CHAR 25 vendnote5_pohdr. vendnote5_edipoh. 89. MEMO1. CHAR 30 FUTURE USE memo1_edipoh. 90. MEMO2. CHAR 30 FUTURE USE memo2_edipoh. 91. MEMO3. CHAR 10 FUTURE USE memo3_edipoh. 92. MEMO4 (NUMERIC). DEC 10 FUTURE USE memo4_edipoh. 93. MEMO5 (DATE). DATE 6 FUTURE USE memo5_edipoh. 94. HEADER MEMO 1. CHAR 30 FUTURE USE hmemo1_edipoh. 95. HEADER MEMO 2. CHAR 30 FUTURE USE hmemo2_edipoh 96. HEADER MEMO 3. CHAR 30 FUTURE USE hmemo3_edipoh 97. HEADER MEMO 4. CHAR 30 FUTURE USE hmemo4_edipoh 98. HEADER MEMO 5. CHAR 30 FUTURE USE hmemo5_edipoh 99. HEADER MEMO 6. CHAR 30 FUTURE USE hmemo6_edipoh 100. HEADER MEMO 7. CHAR 30 FUTURE USE hmemo7_edipoh 101. HEADER MEMO 8. CHAR 30 FUTURE USE hmemo8_edipoh 102. HEADER MEMO 9. CHAR 30 FUTURE USE hmemo9_edipoh 103. HEADER MEMO 10. CHAR 30 FUTURE use hmemo10_edipoh 104. HEADER MEMO 11. CHAR 30 FUTURE use hmemo11_edipoh 105. HEADER MEMO 12. CHAR 30 FUTURE use hmemo12_edipoh 106. HEADER MEMO 13. CHAR 30 FUTURE use hmemo13_edipoh 107. HEADER MEMO 14. CHAR 30 FUTURE use hmemo14_edipoh 108. HEADER MEMO 15. CHAR 30 FUTURE use hmemo15_edipoh 109. DETAIL RECORD INDICATOR. CHAR 03 "ITM" TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 partnrid_editp partnrid_edipod P/O NUMBER. CHAR 10 poid_pohdr. poid_edipod P/O LINE NUMBER. INT 4 line_podet poline_edipod. Format: "XXXX" 113. VENDOR P/O LINE SEQUENCE NUMBER. INT 3 (System Assign) poseq_edipod (Zero filled) Format: "XX" 114. VENDOR PART ID - PO. CHAR 18 vendpart_podet. vendpart_edipod VENDOR PART ID - VENDOR. CHAR 18 venpart_vixref vendpart2_edipod UPC CODE. CHAR 18 interchgid_cixref upc_edipod ITEM ID. CHAR 25 itemid_podet. itemid_edipod ITEM DESCRIPTION 1. CHAR 30 itemdesc_podet desc1_edipod ITEM DESCRIPTION 2. CHAR 30 itemdesc2_podet desc2_edipod ITEM CROSS-REFERENCE. CHAR 25 itemxref_podet. xref_edpod QUANTITY ORDERED. INT 7 po_qty_podet po_qty_edipod. alt_po_qty_podet Format: "XXXXXX" 122. UNIT OF MEASURE. CHAR 2 po_um_podet po_um_edipod alt_po_um_podet. uom_ediuom. uom_editpv UNIT PRICE. DEC 10 po_cost_podet po_cost_edipod Format: "-XXXXXX.XX" Implied: -XXXXXXXX Release NGS-7.00 EDI- 147

148 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 124. UNIT PRICE - PRICING UNIT OF MEASURE. DEC 10 po_cost_podet * po_cost2_edipod cost_conv_podet Format: "-XXXXXX.XX" Implied: -XXXXXXXX 125. ITEM BASIS OF UNIT PRICE. CHAR 2 FUTURE USE. pocstbase_edipod PRICING UNIT OF MEASURE. CHAR 2 costing_um_podet. cost_um_edipod. uom_ediuom uom_editpv EXTENDED COST. DEC 10 extcost_podet. extcost_edipod. Format: "-XXXXXX.XX" Implied: -XXXXXXXX 128. RETAIL PRICE. DEC 10 FUTURE USE. retlprc_edipod FREIGHT AMOUNT. DEC 10 FUTURE USE. frt_edipod REQUESTED (WANTED) DATE. DATE 6 datewanted_podet. datewant_edipod PROMISED DATE. DATE 6 dateprom_podet. dateprom_edipod CANCEL BY DATE. DATE 6 cancelby_podet. canceldt_edipod PURCHASE ORDER DATE. DATE 6 podate_podet. podate_edipod NOT BEFORE DATE. DATE 6 notbefore_podet. notbefdt_edipod PO UNIT WEIGHT. DEC 7 pounitwt_podet. pounitwt_edipod. Format: "-XXXXXX.XX" Implied: -XXXXXXXX 136. PO UNIT VOLUME. DEC 7 pounitvol_podet. pounitvl_edipod. Format: "-XXXXXX.XX" Implied: -XXXXXXXX 137. PO EXTENDED WEIGHT. DEC 7 poextwt_podet. poextwt_edipod. Format: "-XXXXXX.XX" Implied: -XXXXXXXX 138. PO EXTENDED VOLUME. DEC 7 poextvol_podet. poextvl_edipod. Format: "-XXXXXX.XX" Implied: -XXXXXXXX 139. DIVISION ID. CHAR 4 division_podet division_edipod DEPARTMENT ID. CHAR 5 dept_podet dept_edipod BRANCH ID. CHAR 8 branch_podet branch_edipod JOB NUMBER. CHAR 10 job_podet job_edipod DESTINATION. CHAR 10 destination_podet. destintn_edipod REQUISITION BY. CHAR 12 req_by_podet. req_by_edipod REQUESTED BY. CHAR 10 request_by_podet. request_by_edipod BUYER ID. CHAR 2 buyer_podet. buyer_edipod WORK CENTER. CHAR 4 workcntr_podet. workcntr_edipod TAXABLE FLAG. CHAR 1 taxable_podet. taxable_edipod PO LINE REVISED FLAG. CHAR 1 linerevsd_podet. linerevsd_edipod PO DETAIL MEMO 1. CHAR 15 memo1_podet. podmemo1_edipod PO DETAIL MEMO 2. CHAR 15 memo2_podet. podmemo2_edipod COMMODITY CODE. CHAR 6 commodity_podet. commodity_edipod CONTRACT NUMBER. CHAR 20 contract_no_podet. contract_edipod. Release NGS-7.00 EDI- 148

149 # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 154. ITEM REVISION LEVEL. CHAR 4 itemrevlvl_podet. itemrevlv_edipod CUSTOMER ORDER NUMBER. CHAR 10 slsordnum_podet. slsordnum_edipod CUSTOMER ORDER LINE NUMBER. INT 4 slsordlin_podet slsordlin_edipod Format: "XXXX" CUSTOMER ORDER SUB LINE NUMBER. CHAR 4 slsordsub_podet. slsordsub_edipod MEMO 1. CHAR 30 FUTURE USE. memo1_edipod MEMO 2. CHAR 30 FUTURE USE. memo2_edipod MEMO 3. CHAR 10 FUTURE USE. memo3_edipod MEMO 4 (NUMERIC). DEC 10 FUTURE USE memo4_edipod. Format: "-XXXXXX.XX" Implied: -XXXXXXXX 162. MEMO 5 (DATE). DATE 6 FUTURE USE. memo5_edipod DETAIL MEMO 1. CHAR 30 FUTURE USE dmemo1_edipod 164. DETAIL MEMO 2. CHAR 30 FUTURE USE dmemo2_edipod DETAIL MEMO 3. CHAR 30 FUTURE USE dmemo3_edipod DETAIL MEMO 4. CHAR 30 FUTURE USE dmemo4_edipod DETAIL MEMO 5. CHAR 30 FUTURE USE dmemo5_edipod DETAIL MEMO 6. CHAR 30 FUTURE USE dmemo6_edipod DETAIL MEMO 7. CHAR 30 FUTURE USE dmemo7_edipod DETAIL MEMO 8. CHAR 30 FUTURE USE dmemo8_edipod DETAIL MEMO 9. CHAR 30 FUTURE USE dmemo9_edipod DETAIL MEMO 10. CHAR 30 FUTURE use dmemo10_edipod 173. DETAIL MEMO 11. CHAR 30 FUTURE use dmemo11_edipod 174. DETAIL MEMO 12. CHAR 30 FUTURE use dmemo12_edipod 175. DETAIL MEMO 13. CHAR 30 FUTURE use dmemo13_edipod 176. DETAIL MEMO 14. CHAR 30 FUTURE use dmemo14_edipod 177. DETAIL MEMO 15. CHAR 30 FUTURE use dmemo15_edipod Release NGS-7.00 EDI- 149

150 G. Outbound ASCII File Layouts - Fixed Format - Implied Decimal - Separate Header / Details. The following layouts assume that the ASCII file is generated to the maximum size with no delimiter, that decimal fields will be in the implied decimal format and that header and detail records will be generated separately. Fixed Format - Implied Decimal - Header Record Format. Start End Position Position Field Description Field Type Field Size Record Designator. CHAR 3 (HDR) Trading Partner ID. CHAR PO Number. CHAR EDI Transaction Document. CHAR Customer PO EDI Batch #. CHAR Bill To Name. CHAR Bill To ID. CHAR ` 150 Sold To ID. CHAR Ship To ID. CHAR Bill To ID Indicator. CHAR Transaction Date. DATE Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE Reference Number CHAR 30 (Future Use) Department CHAR 30 (Future Use) Remarks. CHAR Ship To Indicator. CHAR Ship To Name. CHAR Ship To Address 1. CHAR Ship To Address 2. CHAR Ship To Address 3. CHAR Ship To City. CHAR Ship To State. CHAR ` Ship To Country CHAR Ship To Zip Code. CHAR Ship To Attention. CHAR Ship To Phone Number. CHAR Vendor Ship To ID. CHAR Transaction Code. CHAR Transaction Type. CHAR Contract Number. CHAR Routing. CHAR Carrier / Routing Description. CHAR SCAC. CHAR Transportation Method/Type Cd CHAR 2 Release NGS-7.00 EDI- 150

151 Start End Position Position Field Description Field Type Field Size Shipment Method Of Payment. CHAR Shipmnt Paymnt Method Desc CHAR Terms Code. CHAR Terms Type Code. CHAR Terms Basis Date Code. CHAR Terms Discount Percent. DECIMAL 5 (#####) Terms Discount Due Date DATE 6 (Future Use) Terms Discount Days Due. INTEGER 3 (###) Terms Net Due Date. DATE 6 (Future Use) Terms Net Days. INTEGER 3 (###) Terms Discount Amount DECIMAL 9 (#########) (Future Use) Terms Description CHAR Allowance / Charge Indicator CHAR 1 (Future Use) Special Services Code. CHAR 10 (Future Use) Allownce/Charge Hndlng Meth CHAR 2 (Future Use) Allowance or Charge Number. CHAR 16 (Future Use) Allowance or Charge Rate. DECIMAL 5 (#####) (Future Use) Allowance or Charge Total Amt DECIMAL 9 (#########) (Future Use) Allowance or Charge Desc CHAR 80 (Future Use) Special Charge / Allow Code CHAR 3 (Future Use) PO Total Quantity. INTEGER 7 (#######) PO # Of Lines. INTEGER 4 (####) PO Weight. DECIMAL 7 (#######) PO Volume. DECIMAL 7 (#######) PO Total Amount. DECIMAL 9 (#########) PO Weight Unit Basis. CHAR 2 (Future Use) PO Volume Unit Basis. CHAR 2 (Future Use) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Confirmation PO Flag. CHAR Confirmation To. CHAR Job Number. CHAR Misc. Info. 1. CHAR Misc. Info. 2. CHAR Misc. Info. 3. CHAR Deliver To. CHAR Requested By. CHAR Buyer Name. CHAR Work Center. CHAR Back Order Flag. CHAR Taxable Flag. CHAR 1 Release NGS-7.00 EDI- 151

152 Start End Position Position Field Description Field Type Field Siz PO Revised Flag. CHAR PO Revision Date. DATE PO Revision Code. CHAR Vendor Note 1. CHAR Vendor Note 2. CHAR Vendor Note 3. CHAR Vendor Note 4. CHAR Vendor Note 5. CHAR Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 9 (#########). (Future Use) Memo 5. DATE 6 (Future Use) Header Memo 1. CHAR 30 (Future Use) Header Memo 2. CHAR 30 (Future Use) Header Memo 3. CHAR 30 (Future Use) Header Memo 4. CHAR 30 (Future Use) Header Memo 5. CHAR 30 (Future Use) Header Memo 6. CHAR 30 (Future Use) Header Memo 7. CHAR 30 (Future Use) Header Memo 8. CHAR 30 (Future Use) Header Memo 9. CHAR 30 (Future Use) Header Memo 10. CHAR 30 (Future Use) Header Memo 11. CHAR 30 (Future Use) Header Memo 12. CHAR 30 (Future Use) Header Memo 13. CHAR 30 (Future Use) Header Memo 14. CHAR 30 (Future Use) Header Memo 15. CHAR 30 (Future Use). Release NGS-7.00 EDI- 152

153 Fixed Format - Implied Decimal - Detail Record Format. Start End Position Position Field Description Field Type Field Size Record Indicator. CHAR 3 (ITM) Trading Partner ID. CHAR PO Number. CHAR PO Line Number. INTEGER 4 (####) Vendor PO Line Sequence #. INTEGER 3 (###) Vendor Part ID - PO. CHAR Vendor Part ID - Vendor. CHAR UPC Code. CHAR Item ID. CHAR Item Description 1. CHAR Item Description 2. CHAR Item Cross-Reference. CHAR Quantity Ordered. INTEGER 7 (#######) Unit Of Measure. CHAR Unit Price. DECIMAL 9 (#########) Unit Price (Pricing U.O.M.) DECIMAL 9 (#########) Item Basis Of Unit Price. CHAR 2 (Future Use) Pricing Unit Of Measure. CHAR Extended Cost. DECIMAL 9 (#########) Retail Price DECIMAL 9 (#########) (Future Use) Freight Amount. DECIMAL 9 (#########) (Future Use) Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE PO Unit Weight. DECIMAL 6 (######) PO Unit Volume. DECIMAL 6 (######) PO Extended Weight. DECIMAL 6 (######) PO Extended Volume. DECIMAL 6 (######) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Job Number. CHAR Destination CHAR Requisition By. CHAR Requested By. CHAR Buyer ID. CHAR 2 Release NGS-7.00 EDI- 153

154 Start End Position Position Field Description Field Type Field Size Work Center. CHAR Taxable Flag. CHAR PO Line Revised Flag. CHAR PO Detail Memo 1. CHAR PO Detail Memo 2. CHAR Commodity Code. CHAR Contract Number. CHAR Item Revision Level. CHAR Customer Order Number. CHAR Customer Order Line Number. INTEGER 4 (####) Customer Order Sub Line No. CHAR Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 9 (#########). (Future Use) Memo 5. DATE 6 (Future Use) Detail Memo 1. CHAR 30 (Future Use) Detail Memo 2. CHAR 30 (Future Use) Detail Memo 3. CHAR 30 (Future Use) Detail Memo 4. CHAR 30 (Future Use) Detail Memo 5. CHAR 30 (Future Use) Detail Memo 6. CHAR 30 (Future Use) Detail Memo 7. CHAR 30 (Future Use Detail Memo 8. CHAR 30 (Future Use) Detail Memo 9. CHAR 30 (Future Use) Detail Memo 10. CHAR 30 (Future Use) Detail Memo 11. CHAR 30 (Future Use) Detail Memo 12. CHAR 30 (Future Use) Detail Memo 13. CHAR 30 (Future Use) Detail Memo 14. CHAR 30 (Future Use) Detail Memo 15. CHAR 30 (Future Use). Release NGS-7.00 EDI- 154

155 H. Outbound ASCII File Layout - Fixed Format - Include Decimal - Separate Header / Detail. The following layouts assume that the ASCII file is generated to the maximum size with no delimiter, that decimal fields will NOT be in the implied decimal format and that header and detail records will be generated separately. Fixed Format - Includes Decimal - Header Record Format. Start End Position Position Field Description Field Type Field Size Record Designator. CHAR 3 (HDR) Trading Partner ID. CHAR PO Number. CHAR EDI Transaction Document. CHAR Customer PO EDI Batch #. CHAR Bill To Name. CHAR Bill To ID. CHAR ` 150 Sold To ID. CHAR Ship To ID. CHAR Bill To ID Indicator. CHAR Transaction Date. DATE Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE Reference Number CHAR 30 (Future Use) Department CHAR 30 (Future Use) Remarks. CHAR Ship To Indicator. CHAR Ship To Name. CHAR Ship To Address 1. CHAR Ship To Address 2. CHAR Ship To Address 3. CHAR Ship To City. CHAR Ship To State. CHAR ` Ship To Country CHAR Ship To Zip Code. CHAR Ship To Attention. CHAR Ship To Phone Number. CHAR Vendor Ship To ID. CHAR Transaction Code. CHAR Transaction Type. CHAR Contract Number. CHAR Routing. CHAR Carrier / Routing Description. CHAR SCAC. CHAR Transportation Method/Type Cd.CHAR Shipment Method Of Payment. CHAR Shipment Payment Method DescCHAR 20 Release NGS-7.00 EDI- 155

156 Start End Position Position Field Description Field Type Field Size Terms Code. CHAR Terms Type Code. CHAR Terms Basis Date Code. CHAR Terms Discount Percent. DECIMAL 6 (###.##) Terms Discount Due Date DATE 6 (Future Use) Terms Discount Days Due. INTEGER 3 (###) Terms Net Due Date. DATE 6 (Future Use) Terms Net Days. INTEGER 3 (###) Terms Discount Amount DECIMAL 10 (#######.##) (Future Use) Terms Description CHAR Allowance / Charge Indicator CHAR 1 (Future Use) Special Services Code. CHAR 10 (Future Use) Allowance/Charge Handling MethCHAR 2 (Future Use) Allowance or Charge Number. CHAR 16 (Future Use) Allowance or Charge Rate. DECIMAL 6 (###.##) (Future Use) Allowance or Charge Total Amt.DECIMAL 10 (#######.##) (Future Use) Allowance or Charge Description.CHAR 80 (Future Use) Special Charge / Allowance Code.CHAR 3 (Future Use) PO Total Quantity. INTEGER 7 (#######) PO # Of Lines. INTEGER 4 (####) PO Weight. DECIMAL 8 (#####.##) PO Volume. DECIMAL 8 (#####.##) PO Total Amount. DECIMAL 10 (#######.##) PO Weight Unit Basis. CHAR 2 (Future Use) PO Volume Unit Basis. CHAR 2 (Future Use) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Confirmation PO Flag. CHAR Confirmation To. CHAR Job Number. CHAR Misc. Info. 1. CHAR Misc. Info. 2. CHAR Misc. Info. 3. CHAR Deliver To. CHAR Requested By. CHAR ` Buyer Name. CHAR Work Center. CHAR Back Order Flag. CHAR Taxable Flag. CHAR 1 Release NGS-7.00 EDI- 156

157 Start End Position Position Field Description Field Type Field Size PO Revised Flag. CHAR PO Revision Date. DATE PO Revision Code. CHAR Vendor Note 1. CHAR Vendor Note 2. CHAR Vendor Note 3. CHAR Vendor Note 4. CHAR Vendor Note 5. CHAR Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 10 (#######.##). (Future Use) Memo 5. DATE 6 (Future Use) Header Memo 1. CHAR 30 (Future Use) Header Memo 2. CHAR 30 (Future Use) Header Memo 3. CHAR 30 (Future Use) Header Memo 4. CHAR 30 (Future Use) Header Memo 5. CHAR 30 (Future Use) Header Memo 6. CHAR 30 (Future Use) Header Memo 7. CHAR 30 (Future Use) Header Memo 8. CHAR 30 (Future Use) Header Memo 9. CHAR 30 (Future Use) Header Memo 10. CHAR 30 (Future Use) Header Memo 11. CHAR 30 (Future Use) Header Memo 12. CHAR 30 (Future Use) Header Memo 13. CHAR 30 (Future Use) Header Memo 14. CHAR 30 (Future Use) Header Memo 15. CHAR 30 (Future Use). Release NGS-7.00 EDI- 157

158 Fixed Format - Implied Decimal - Detail Record Format. Start End Position Position Field Description Field Type Field Size Record Indicator. CHAR 3 (ITM) Trading Partner ID. CHAR PO Number. CHAR PO Line Number. INTEGER 4 (####) Vendor PO Line Sequence #. INTEGER 3 (###) Vendor Part ID - PO. CHAR Vendor Part ID - Vendor. CHAR UPC Code. CHAR Item ID. CHAR Item Description 1. CHAR Item Description 2. CHAR Item Cross-Reference. CHAR Quantity Ordered. INTEGER 7 (#######) Unit Of Measure. CHAR Unit Price. DECIMAL 10 (#######.##) Unit Price (Pricing Unit/Measure).DECIMAL 10 (#######.##) Item Basis Of Unit Price. CHAR 2 (Future Use) Pricing Unit Of Measure. CHAR Extended Cost. DECIMAL 10 (#######.##) Retail Price DECIMAL 10 (#######.##) (Future Use) Freight Amount. DECIMAL 10 (#######.##) (Future Use) Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE PO Unit Weight. DECIMAL 7 (####.##) PO Unit Volume. DECIMAL 7 (####.##) PO Extended Weight. DECIMAL 7 (####.##) PO Extended Volume. DECIMAL 7 (####.##) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Job Number. CHAR Destination CHAR Requisition By. CHAR Requested By. CHAR Buyer ID. CHAR 2 Release NGS-7.00 EDI- 158

159 Start End Position Position Field Description Field Type Field Size Work Center. CHAR Taxable Flag. CHAR PO Line Revised Flag. CHAR PO Detail Memo 1. CHAR PO Detail Memo 2. CHAR Commodity Code. CHAR Contract Number. CHAR Item Revision Level. CHAR Customer Order Number. CHAR Customer Order Line Number. INTEGER 4 (####) Customer Order Sub Line Number.CHAR Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 10 (#######.##). (Future Use) Memo 5. DATE 6 (Future Use) Detail Memo 1. CHAR 30 (Future Use) Detail Memo 2. CHAR 30 (Future Use) Detail Memo 3. CHAR 30 (Future Use) Detail Memo 4. CHAR 30 (Future Use) Detail Memo 5. CHAR 30 (Future Use) Detail Memo 6. CHAR 30 (Future Use) Detail Memo 7. CHAR 30 (Future Use Detail Memo 8. CHAR 30 (Future Use) Detail Memo 9. CHAR 30 (Future Use) Detail Memo 10. CHAR 30 (Future Use) Detail Memo 11. CHAR 30 (Future Use) Detail Memo 12. CHAR 30 (Future Use) Detail Memo 13. CHAR 30 (Future Use) Detail Memo 14. CHAR 30 (Future Use) Detail Memo 15. CHAR 30 (Future Use). Release NGS-7.00 EDI- 159

160 I. Outbound ASCII File Layouts - Fixed Format - Implied Decimal - Combined Header / Details. The following layouts assume that the ASCII file is generated to the maximum size with no delimiter, that decimal fields will be in the implied decimal format and that header and detail records will be generated together. Fixed Format - Implied Decimal - Combined Header / Detail Format. Start End Position Position Field Description Field Type Field Size Record Designator. CHAR 3 (HDR) Trading Partner ID. CHAR PO Number. CHAR EDI Transaction Document. CHAR Customer PO EDI Batch #. CHAR Bill To Name. CHAR Bill To ID. CHAR ` 150 Sold To ID. CHAR Ship To ID. CHAR Bill To ID Indicator. CHAR Transaction Date. DATE Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE Reference Number CHAR 30 (Future Use) Department CHAR 30 (Future Use) Remarks. CHAR Ship To Indicator. CHAR Ship To Name. CHAR Ship To Address 1. CHAR Ship To Address 2. CHAR Ship To Address 3. CHAR Ship To City. CHAR Ship To State. CHAR ` Ship To Country CHAR Ship To Zip Code. CHAR Ship To Attention. CHAR Ship To Phone Number. CHAR Vendor Ship To ID. CHAR Transaction Code. CHAR Transaction Type. CHAR Contract Number. CHAR Routing. CHAR Carrier / Routing Description. CHAR SCAC. CHAR Transportation Method/Type Cd.CHAR Shipment Method Of Payment. CHAR Shipment Payment Method Descr.CHAR 20 Release NGS-7.00 EDI- 160

161 Start End Position Position Field Description Field Type Field Size Terms Code. CHAR Terms Type Code. CHAR Terms Basis Date Code. CHAR Terms Discount Percent. DECIMAL 5 (#####) Terms Discount Due Date DATE 6 (Future Use) Terms Discount Days Due. INTEGER 3 (###) Terms Net Due Date. DATE 6 (Future Use) Terms Net Days. INTEGER 3 (###) Terms Discount Amount DECIMAL 9 (#########) (Future Use) Terms Description CHAR Allowance / Charge Indicator CHAR 1 (Future Use) Special Services Code. CHAR 10 (Future Use) Allowance/Charge Handling MethCHAR 2 (Future Use) Allowance or Charge Number. CHAR 16 (Future Use) Allowance or Charge Rate. DECIMAL 5 (#####) (Future Use) Allowance or Charge Total Amt.DECIMAL 9 (#########) (Future Use) Allowance or Charge Description.CHAR 80 (Future Use) Special Charge / Allowance Code.CHAR 3 (Future Use) PO Total Quantity. INTEGER 7 (#######) PO # Of Lines. INTEGER 4 (####) PO Weight. DECIMAL 7 (#######) PO Volume. DECIMAL 7 (#######) PO Total Amount. DECIMAL 9 (#########) PO Weight Unit Basis. CHAR 2 (Future Use) PO Volume Unit Basis. CHAR 2 (Future Use) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Confirmation PO Flag. CHAR Confirmation To. CHAR Job Number. CHAR Misc. Info. 1. CHAR Misc. Info. 2. CHAR Misc. Info. 3. CHAR Deliver To. CHAR Requested By. CHAR Buyer Name. CHAR Work Center. CHAR Back Order Flag. CHAR Taxable Flag. CHAR 1 Release NGS-7.00 EDI- 161

162 Start End Position Position Field Description Field Type Field Size PO Revised Flag. CHAR PO Revision Date. DATE PO Revision Code. CHAR Vendor Note 1. CHAR Vendor Note 2. CHAR Vendor Note 3. CHAR Vendor Note 4. CHAR Vendor Note 5. CHAR Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 9 (#########). (Future Use) Memo 5. DATE 6 (Future Use) Header Memo 1. CHAR 30 (Future Use) Header Memo 2. CHAR 30 (Future Use) Header Memo 3. CHAR 30 (Future Use) Header Memo 4. CHAR 30 (Future Use) Header Memo 5. CHAR 30 (Future Use) Header Memo 6. CHAR 30 (Future Use) Header Memo 7. CHAR 30 (Future Use) Header Memo 8. CHAR 30 (Future Use) Header Memo 9. CHAR 30 (Future Use) Header Memo 10. CHAR 30 (Future Use) Header Memo 11. CHAR 30 (Future Use) Header Memo 12. CHAR 30 (Future Use) Header Memo 13. CHAR 30 (Future Use) Header Memo 14. CHAR 30 (Future Use) Header Memo 15. CHAR 30 (Future Use) Record Indicator. CHAR 3 (ITM) Trading Partner ID. CHAR PO Number. CHAR PO Line Number. INTEGER 4 (####) Vendor PO Line Sequence #. INTEGER 3 (###) Vendor Part ID - PO. CHAR Vendor Part ID - Vendor. CHAR UPC Code. CHAR Item ID. CHAR Item Description 1. CHAR Item Description 2. CHAR 30 Release NGS-7.00 EDI- 162

163 Start End Position Position Field Description Field Type Field Size Item Cross-Reference. CHAR Quantity Ordered. INTEGER 7 (#######) Unit Of Measure. CHAR Unit Price. DECIMAL 9 (#########) Unit Price (Pricing Unit/Measure).DECIMAL 9 (#########) Item Basis Of Unit Price. CHAR 2 (Future Use) Pricing Unit Of Measure. CHAR Extended Cost. DECIMAL 9 (#########) Retail Price DECIMAL 9 (#########) (Future Use) Freight Amount. DECIMAL 9 (#########) (Future Use) Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE PO Unit Weight. DECIMAL 6 (######) PO Unit Volume. DECIMAL 6 (######) PO Extended Weight. DECIMAL 6 (######) PO Extended Volume. DECIMAL 6 (######) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Job Number. CHAR Destination CHAR Requisition By. CHAR Requested By. CHAR Buyer ID. CHAR Work Center. CHAR Taxable Flag. CHAR PO Line Revised Flag. CHAR PO Detail Memo 1. CHAR PO Detail Memo 2. CHAR Commodity Code. CHAR Contract Number. CHAR Item Revision Level. CHAR Customer Order Number. CHAR Customer Order Line Number. INTEGER 4 (####) Customer Order Sub Line Number.CHAR 4 Release NGS-7.00 EDI- 163

164 Start End Position Position Field Description Field Type Field Size Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 9 (#########). (Future Use) Memo 5. DATE 6 (Future Use) Detail Memo 1. CHAR 30 (Future Use) Detail Memo 2. CHAR 30 (Future Use) Detail Memo 3. CHAR 30 (Future Use) Detail Memo 4. CHAR 30 (Future Use) Detail Memo 5. CHAR 30 (Future Use) Detail Memo 6. CHAR 30 (Future Use) Detail Memo 7. CHAR 30 (Future Use Detail Memo 8. CHAR 30 (Future Use) Detail Memo 9. CHAR 30 (Future Use) Detail Memo 10. CHAR 30 (Future Use) Detail Memo 11. CHAR 30 (Future Use) Detail Memo 12. CHAR 30 (Future Use) Detail Memo 13. CHAR 30 (Future Use) Detail Memo 14. CHAR 30 (Future Use) Detail Memo 15. CHAR 30 (Future Use). Release NGS-7.00 EDI- 164

165 J. Outbound ASCII File Layout - Fixed Format - Include Decimal - Combined Header / Detail. The following layouts assume that the ASCII file is generated to the maximum size with no delimiter, that decimal fields will NOT be in the implied decimal format and that header and detail records will be generated together. Fixed Format - Includes Decimal - Combined Header / Detail Record Format. Start End Position Position Field Description Field Type Field Size Record Designator. CHAR 3 (HDR) Trading Partner ID. CHAR PO Number. CHAR EDI Transaction Document. CHAR Customer PO EDI Batch #. CHAR Bill To Name. CHAR Bill To ID. CHAR Sold To ID. CHAR Ship To ID. CHAR Bill To ID Indicator. CHAR Transaction Date. DATE Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE Reference Number CHAR 30 (Future Use) Department CHAR 30 (Future Use) Remarks. CHAR Ship To Indicator. CHAR Ship To Name. CHAR Ship To Address 1. CHAR Ship To Address 2. CHAR Ship To Address 3. CHAR Ship To City. CHAR Ship To State. CHAR ` Ship To Country CHAR Ship To Zip Code. CHAR Ship To Attention. CHAR Ship To Phone Number. CHAR Vendor Ship To ID. CHAR Transaction Code. CHAR Transaction Type. CHAR Contract Number. CHAR Routing. CHAR Carrier / Routing Description. CHAR SCAC. CHAR 4 Release NGS-7.00 EDI- 165

166 Start End Position Position Field Description Field Type Field Size Transportation Method/Type Cd.CHAR Shipment Method Of Payment. CHAR Shipment Payment Method Descr.CHAR Terms Code. CHAR Terms Type Code. CHAR Terms Basis Date Code. CHAR Terms Discount Percent. DECIMAL 6 (###.##) Terms Discount Due Date DATE 6 (Future Use) Terms Discount Days Due. INTEGER 3 (###) Terms Net Due Date. DATE 6 (Future Use) Terms Net Days. INTEGER 3 (###) Terms Discount Amount DECIMAL 10 (#######.##) (Future Use) Terms Description CHAR Allowance / Charge Indicator CHAR 1 (Future Use) Special Services Code. CHAR 10 (Future Use) Allowance/Charge Handling MethCHAR 2 (Future Use) Allowance or Charge Number. CHAR 16 (Future Use) Allowance or Charge Rate. DECIMAL 6 (###.##) (Future Use) Allowance or Charge Total Amt.DECIMAL 10 (#######.##) (Future Use) Allowance or Charge Description.CHAR 80 (Future Use) Special Charge / Allowance Code.CHAR 3 (Future Use) PO Total Quantity. INTEGER 7 (#######) PO # Of Lines. INTEGER 4 (####) PO Weight. DECIMAL 8 (#####.##) PO Volume. DECIMAL 8 (#####.##) PO Total Amount. DECIMAL 10 (#######.##) PO Weight Unit Basis. CHAR 2 (Future Use) PO Volume Unit Basis. CHAR 2 (Future Use) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Confirmation PO Flag. CHAR Confirmation To. CHAR Job Number. CHAR Misc. Info. 1. CHAR Misc. Info. 2. CHAR Misc. Info. 3. CHAR Deliver To. CHAR Requested By. CHAR 12 Release NGS-7.00 EDI- 166

167 Start End Position Position Field Description Field Type Field Size Buyer Name. CHAR Work Center. CHAR Back Order Flag. CHAR Taxable Flag. CHAR PO Revised Flag. CHAR PO Revision Date. DATE PO Revision Code. CHAR Vendor Note 1. CHAR Vendor Note 2. CHAR Vendor Note 3. CHAR Vendor Note 4. CHAR Vendor Note 5. CHAR Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 10 (#######.##). (Future Use) Memo 5. DATE 6 (Future Use) Header Memo 1. CHAR 30 (Future Use) Header Memo 2. CHAR 30 (Future Use) Header Memo 3. CHAR 30 (Future Use) Header Memo 4. CHAR 30 (Future Use) Header Memo 5. CHAR 30 (Future Use) Header Memo 6. CHAR 30 (Future Use) Header Memo 7. CHAR 30 (Future Use) Header Memo 8. CHAR 30 (Future Use) Header Memo 9. CHAR 30 (Future Use) Header Memo 10. CHAR 30 (Future Use) Header Memo 11. CHAR 30 (Future Use) Header Memo 12. CHAR 30 (Future Use) Header Memo 13. CHAR 30 (Future Use) Header Memo 14. CHAR 30 (Future Use) Header Memo 15. CHAR 30 (Future Use) Record Indicator. CHAR 3 (ITM) Trading Partner ID. CHAR PO Number. CHAR PO Line Number. INTEGER 4 (####) Vendor PO Line Sequence #. INTEGER 3 (###) Vendor Part ID - PO. CHAR Vendor Part ID - Vendor. CHAR 18 Release NGS-7.00 EDI- 167

168 Start End Position Position Field Description Field Type Field Size UPC Code. CHAR Item ID. CHAR Item Description 1. CHAR Item Description 2. CHAR Item Cross-Reference. CHAR Quantity Ordered. INTEGER 7 (#######) Unit Of Measure. CHAR Unit Price. DECIMAL 10 (#######.##) Unit Price (Pricing U.O.M.) DECIMAL 10 (#######.##) Item Basis Of Unit Price. CHAR 2 (Future Use) Pricing Unit Of Measure. CHAR Extended Cost. DECIMAL 10 (#######.##) Retail Price DECIMAL 10 (#######.##) (Future Use) Freight Amount. DECIMAL 10 (#######.##) (Future Use) Requested Date. DATE Promised Date. DATE Cancel By Date. DATE PO Date. DATE Not Before Date. DATE PO Unit Weight. DECIMAL 7 (####.##) PO Unit Volume. DECIMAL 7 (####.##) PO Extended Weight. DECIMAL 7 (####.##) PO Extended Volume. DECIMAL 7 (####.##) Division ID. CHAR Department ID. CHAR Branch ID. CHAR Job Number. CHAR Destination CHAR Requisition By. CHAR Requested By. CHAR Buyer ID. CHAR Work Center. CHAR Taxable Flag. CHAR PO Line Revised Flag. CHAR PO Detail Memo 1. CHAR PO Detail Memo 2. CHAR Commodity Code. CHAR Contract Number. CHAR Item Revision Level. CHAR Customer Order Number. CHAR Customer Order Line Number. INTEGER 4 (####) Release NGS-7.00 EDI- 168

169 Start End Position Position Field Description Field Type Field Size Cust. Order Sub Line Number. CHAR Memo 1. CHAR 30 (Future Use) Memo 2. CHAR 30 (Future Use) Memo 3. CHAR 10 (Future Use) Memo 4. DECIMAL 10 (#######.##). (Future Use) Memo 5. DATE 6 (Future Use) Detail Memo 1. CHAR 30 (Future Use) Detail Memo 2. CHAR 30 (Future Use) Detail Memo 3. CHAR 30 (Future Use) Detail Memo 4. CHAR 30 (Future Use) Detail Memo 5. CHAR 30 (Future Use) Detail Memo 6. CHAR 30 (Future Use) Detail Memo 7. CHAR 30 (Future Use Detail Memo 8. CHAR 30 (Future Use) Detail Memo 9. CHAR 30 (Future Use) Detail Memo 10. CHAR 30 (Future Use) Detail Memo 11. CHAR 30 (Future Use) Detail Memo 12. CHAR 30 (Future Use) Detail Memo 13. CHAR 30 (Future Use) Detail Memo 14. CHAR 30 (Future Use) Detail Memo 15. CHAR 30 (Future Use). K. Database File Formats. K1. EDIPOH - EDI Purchase Order Header Work Table. # Field Name Field Type Field Size 1 partnrid_edipoh char 27 2 poid_edipoh char 10 3 poeditr_edipoh char 3 4 pobatch_edipoh char 10 5 billname_edipoh char 27 6 billto_edipoh char 35 7 soldto_edipoh char 35 8 shipto_edipoh char 35 9 btlook_edipoh char 2 10 trandate_edipoh char 6 11 datewant_edipoh char 6 12 dateprom_edipoh char 6 13 canceldt_edipoh char 6 14 podate_edipoh char 6 15 notbefdt_edipoh char 6 16 reference_edipoh char department_edipoh char remarks_edipoh char bslook_edipoh char 2 20 vsname_edipoh char vsaddr1_edipoh char vsaddr2_edipoh char vsaddr3_edipoh char 27 Release NGS-7.00 EDI- 169

170 # Field Name Field Type Field Size 24 vscity_edipoh char vsstate_edipoh char 4 26 vscntry_edipoh char vszip_edipoh char vsattn_edipoh char vsphone_edipoh char vshipto_edipoh char transcd_edipoh char 2 32 transtype_edipoh char 2 33 contract_edipoh char routing_edipoh char 2 35 carrier_edipoh char scac_edipoh char 4 37 trmethod_edipoh char 2 38 frtpay_edipoh char 4 39 fpdesc_edipoh char poterms_edipoh char 4 41 termtype_edipoh char 2 42 termbase_edipoh char 2 43 trm_pcnt_edipoh decimal trmdiscdt_edipoh char 6 45 trm_days_edipoh smallint 2 46 trmnetdt_edipoh char 6 47 due_days_edipoh smallint 2 48 trm_disc_edipoh decimal trm_desc_edipoh char allowind_edipoh char 1 51 spsrvcd_edipoh char allowmeth_edipoh char 2 53 allownum_edipoh char allowrate_edipoh decimal allowtot_edipoh decimal allowdesc_edipoh char allowcd_edipoh char 3 58 po_qty_edipoh decimal po_lines_edipoh integer 4 60 poextwt_edipoh decimal poextvl_edipoh decimal pototal_edipoh decimal powtbase_edipoh char 2 64 povlbase_edipoh char 2 65 division_edipoh char 4 66 dept_edipoh char 5 67 branch_edipoh char 8 68 confirming_edipoh char 1 69 confirmto_edipoh char job_edipoh char miscinfo1_edipoh char miscinfo2_edipoh char miscinfo3_edipoh char deliverto_edipoh char req_by_edipoh char 12 Release NGS-7.00 EDI- 170

171 # Field Name Field Type Field Size 76 buyer_edipoh char workcntr_edipoh char 4 78 backorder_edipoh char 1 79 taxable_edipoh char 1 80 porevised_edipoh char 1 81 porevdate_edipoh char 6 82 porevsn_edipoh char 3 83 vendnote1_edipoh char vendnote2_edipoh char vendnote3_edipoh char vendnote4_edipoh char vendnote5_edipoh char memo1_edipoh char memo2_edipoh char memo3_edipoh char memo4_edipoh decimal memo5_edipoh char 6 93 hmemo1_edipoh char hmemo2_edipoh char hmemo3_edipoh char hmemo4_edipoh char hmemo5_edipoh char hmemo6_edipoh char hmemo7_edipoh char hmemo8_edipoh char hmemo9_edipoh char hmemo10_edipoh char hmemo11_edipoh char hmemo12_edipoh char hmemo13_edipoh char hmemo14_edipoh char hmemo15_edipoh char 30 Indexes: index edipoh_idx1 on edipoh(partnrid_edipoh)index edipoh_idx2 on edipoh(poid_edipoh) Release NGS-7.00 EDI- 171

172 K2. EDIPOD - EDI Purchase Order Detail Work Table. # Field Name Field Type Field Size 1 partnrid_edipod char 27 2 poid_edipod char 10 3 poline_edipod integer 4 4 pobatch_edipod char 10 5 poseq_edipod integer 4 6 vendpart_edipod char 18 7 vendpart2_edipod char 18 8 upc_edipod char 25 9 itemid_edipod char desc1_edipod char desc2_edipod char xref_edipod char po_qty_edipod decimal po_um_edipod char 2 15 po_cost_edipod decimal po_cost2_edipod decimal pocstbase_edipod char 2 18 cost_um_edipod char 2 19 extcost_edipod decimal retlprc_edipod decimal frt_edipod decimal datewant_edipod char 6 23 dateprom_edipod char 6 24 canceldt_edipod char 6 25 podate_edipod char 6 26 notbefdt_edipod char 6 27 pounitwt_edipod decimal pounitvl_edipod decimal poextwt_edipod decimal poextvl_edipod decimal division_edipod char 4 32 dept_edipod char 5 33 branch_edipod char 8 34 job_edipod char destintn_edipod char req_by_edipod char request_by_edipod char buyer_edipod char 2 39 workcntr_edipod char 4 40 taxable_edipod char 1 41 linerevsd_edipod char 1 42 podmemo1_edipod char podmemo2_edipod char commodity_edipod char 6 45 contract_edipod char itemrevlv_edipod char 4 47 slsordnum_edipod char slsordlin_edipod integer 4 49 slsordsub_edipod char 4 Release NGS-7.00 EDI- 172

173 # Field Name Field Type Field Size 50 memo1_edipod char memo2_edipod char memo3_edipod char memo4_edipod decimal memo5_edipod char 6 55 dmemo1_edipod char dmemo2_edipod char dmemo3_edipod char dmemo4_edipod char dmemo5_edipod char dmemo6_edipod char dmemo7_edipod char dmemo8_edipod char dmemo9_edipod char dmemo10_edipod char dmemo11_edipod char dmemo12_edipod char dmemo13_edipod char dmemo14_edipod char dmemo15_edipod char 30 Indexes: index edipod_idx1 on edipod(partnrid_edipod) index edipod_idx2 on edipod(poid_edipod,poline_edipod) G. SSM - System Security Maintenance (By Program). Program Name: EDIPOG Type Of Security: C (Conflict). Option Value: EDIPOG Release NGS-7.00 EDI- 173

174 EDIMNTU- EDI ORDER MAINTENANCE FILE UPDATE. A. Program Summary. The program will select any orders and/or order lines which have been deleted which were EDI orders, generate records in the EDI Order Maintenance Header and Detail tables for the transactions and remove the applicable records from the EDI Open Order Header and Detail tables. The program has the capability of being run interactively or as an MISCRON job. B. Program Detail. The operator will be prompted if they want to proceed with the program. The first pass of the program will determine Open Order Header records that have been deleted. The system will select all records in the EDI Open Order Header table (orderc) that do not have a corresponding record in the Open Order Header table (orderb). For each record selected, the system will access the Order Maintenance Header record (ormnta) for the transaction to determine the deleted record (based on the transaction having a status code of 'D' in the maint_code_ordera field). The system will then generate a record in the EDI Order Maintenance Header table (ormntc) with the data in the EDI Open Order Header record (orderc). The serial number assigned to the deletion record (maint_code_ordera) will be updated to the EDI Order Maintenance Header table as well. The system will generate records in the EDI Order Maintenance Detail table (ormntd2) with the data from all the records for the order in the EDI Open Order Detail table (orddet2) along with the serial number assigned to the deletion (maint_ser_ordera). If for any reason a corresponding record is not found in the Order Maintenance table (ormnta), the system will assign a serial number of ' ' to the EDI Order Maintenance Header record (ormntc) and the EDI Order Maintenance Detail records (ormntd2) in order to flag these records. The corresponding records in the EDI Order Header Table (orderc) and EDI Order Detail Table (orddet2) will be deleted after the maintenance records are generated. The second pass of the program will determine order detail lines that have been deleted. The system will select all records in the EDI Open Order Detail table (orddet2) that do not have a corresponding record in the Open Order Detail table (orddet). For each record selected, the system will access the Order Maintenance Detail record (ormntd) for the transaction which has a status code of 'D' in the maint_code_orddet field. The system will generate a record in the EDI Order Maintenance Detail table (ormntd2) with the data in the EDI Open Order Detail record (orddet2). The serial number assigned to the deletion record (maint_code_orddet) will be updated to the EDI Order Maintenance Detail table as well. If for any reason a corresponding record is not found in the Order Maintenance Detail table (ormntd), the system will assign a serial number of ' ' to the EDI Order Maintenance Detail record (ormntd2) in order to flag these records. The corresponding records in the EDI Order Detail Table (orddet2) will be deleted after the maintenance records are generated. Release NGS-7.00 EDI- 174

175 C. Screen Layout. Release NGS-7.00 EDI- 175

176 D. File & Field Layouts. D1. ORMNTC - EDI ORDER MAINTENANCE HEADER FILE. FIELD NAME SIZE TYPE DESCRIPTION ordnum_orderc 10 CHAR ORDER NUMBER batch_orderc 2 SMINT EDI BATCH NUMBER partnrid_orderc 27 CHAR TRADING PARTNER ID / MAILBOX NUMBER billto_orderc 35 CHAR BILL TO ID soldto_orderc 35 CHAR SOLD TO ID shipto_orderc 35 CHAR SHIP TO ID bslook_orderc 35 CHAR SHIP TO ID INDICATOR trandate_orderc 4 DATE TRANSACTION DATE reqdate_orderc 4 DATE REQUESTED DATE shipdate_orderc 4 DATE SHIP DATE canceldte_orderc 4 DATE CANCEL DATE podate_orderc 4 DATE PURCHASE ORDER DATE. cust_po_orderc 22 CHAR CUSTOMER P/O NUMBER. pobatch_orderc 10 CHAR CUSTOMER PURCHASE ORDER BATCH. refno_orderc 30 CHAR REFERENCE NUMBER. dept_orderc 30 CHAR DEPARTMENT NUMBER. remarks_orderc 80 CHAR REMARKS. media_orderc 2 CHAR MEDIA/EVENT CODE. shipname_orderc 35 CHAR SHIP TO NAME. shipaddr1_orderc 35 CHAR SHIP TO ADDRESS 1. shipaddr2_orderc 35 CHAR SHIP TO ADDRESS 2. shipaddr3_orderc 35 CHAR SHIP TO ADDRESS 3. shipcity_orderc 19 CHAR SHIP TO CITY. shipstate_orderc 4 CHAR SHIP TO STATE. shipcntry_orderc 10 CHAR SHIP TO COUNTRY. shipzip_orderc 9 CHAR SHIP TO ZIP CODE. shipattn_orderc 27 CHAR SHIP TO ATTENTION. markfor_orderc 45 CHAR MARK FOR. terms_cd_orderc 4 CHAR TERMS CODE. transcd_orderc 2 CHAR TRANSACTION CODE. trantype_orderc 2 CHAR TRANSACTION TYPE. contract_orderc 12 CHAR CONTRACT NUMBER. routing_orderc 2 CHAR ROUTING CODE. scac_orderc 4 CHAR SCAC CODE. asnflag_orderc 2 CHAR ASN GENERATION FLAG. asndate_orderc 4 DATE ASN GENERATION DATE. asntime_orderc 8 CHAR ASN GENERATION TIME. asnuser_orderc 8 CHAR ASN GENERATION USER. asnbatch_orderc 4 INT ASN GENERATION BATCH NUMBER. invflag_orderc 2 CHAR INVOICE GENERATION FLAG. invdate_orderc 4 DATE INVOICE GENERATION DATE. invtime_orderc 8 CHAR INVOICE GENERATION TIME. invuser_orderc 8 CHAR INVOICE GENERATION USER. invbatch_orderc 10 CHAR INVOICE GENERATION BATCH NUMBER. memo1_orderc 30 CHAR MEMO 1 (ALPHA). memo2_orderc 30 CHAR MEMO 2 (ALPHA). memo3_orderc 10 CHAR MEMO 3 (ALPHA). memo4_orderc 10 DEC MEMO 4 (NUMERIC). Release NGS-7.00 EDI- 176

177 FIELD NAME SIZE TYPE DESCRIPTION memo5_orderc 4 DATE MEMO 5 (DATE). maint_ser_orderc 4 INT MAINTENANCE SERIAL NUMBER. maint_code_orderc 2 CHAR MAINTENANCE CODE. maint_user_orderc 8 CHAR MAINTENANCE USER. maint_tty_orderc 16 CHAR MAINTENANCE TTY DEVICE. maint_time_orderc 8 DTTM MAINTENANCE DATE/TIME. memoh1_orderc 30 CHAR HEADER MEMO 1. memoh2_orderc 30 CHAR HEADER MEMO 2. memoh3_orderc 30 CHAR HEADER MEMO 3. memoh4_orderc 30 CHAR HEADER MEMO 4. memoh5_orderc 30 CHAR HEADER MEMO 5. memoh6_orderc 30 CHAR HEADER MEMO 6. memoh7_orderc 30 CHAR HEADER MEMO 7. memoh8_orderc 30 CHAR HEADER MEMO 8. memoh9_orderc 30 CHAR HEADER MEMO 9. memoh10_orderc 30 CHAR HEADER MEMO 10. memoh11_orderc 30 CHAR HEADER MEMO 11. memoh12_orderc 30 CHAR HEADER MEMO 12. memoh13_orderc 30 CHAR HEADER MEMO 13. memoh14_orderc 30 CHAR HEADER MEMO 14. memoh15_orderc 30 CHAR HEADER MEMO 15. memoh16_orderc 30 CHAR HEADER MEMO 16. memoh17_orderc 30 CHAR HEADER MEMO 17. memoh18_orderc 30 CHAR HEADER MEMO 18. memoh19_orderc 30 CHAR HEADER MEMO 19. memoh20_orderc 30 CHAR HEADER MEMO 20. memoh21_orderc 30 CHAR HEADER MEMO 21. memoh22_orderc 30 CHAR HEADER MEMO 22. memoh23_orderc 30 CHAR HEADER MEMO 23. memoh24_orderc 30 CHAR HEADER MEMO 24. memoh25_order 30 CHAR HEADER MEMO 25. memoh26_orderc 30 CHAR HEADER MEMO 26. memoh27_orderc 30 CHAR HEADER MEMO 27. memoh28_orderc 30 CHAR HEADER MEMO 28. memoh29_orderc 30 CHAR HEADER MEMO 29. memoh30_orderc 30 CHAR HEADER MEMO 30. memoh31_orderc 30 CHAR HEADER MEMO 31. memoh32_orderc 30 CHAR HEADER MEMO 32. memoh33_orderc 30 CHAR HEADER MEMO 33. memoh34_orderc 30 CHAR HEADER MEMO 34. memoh35_orderc 30 CHAR HEADER MEMO 35. memoh36_orderc 30 CHAR HEADER MEMO 36. memoh37_orderc 30 CHAR HEADER MEMO 37. memoh38_orderc 30 CHAR HEADER MEMO 38. memoh39_orderc 30 CHAR HEADER MEMO 39. memoh40_orderc 30 CHAR HEADER MEMO 40. Indexes: Unique index on ordnum_orderc. Index on maint_ser_orderc. Release NGS-7.00 EDI- 177

178 D2. ORMNTD2 - EDI ORDER MAINTENANCE DETAIL FILE. FIELD NAME SIZE TYPE DESCRIPTION. ordnum_orddet2 10 CHAR ORDER NUMBER. lineno_orddet2 4 INT LINE NUMBER. subno_orddet2 4 CHAR SUB NUMBER. batch_orddet2 2 SMINT EDI BATCH NUMBER. partnrid_orddet2 27 CHAR TRADING PARTNER'S ID OR MAILBOX NUMBER. ponumber_orddet2 22 CHAR CUSTOMER P/O NUMBER. polineno_orddet2 4 CHAR CUSTOMER P/O SEQUENCE NUMBER. custprt1_orddet2 18 CHAR CUSTOMER PART ID. custprt2_orddet2 18 CHAR CUSTOMER PART ID 2. upc_orddet2 25 CHAR UPC CODE. sellitem_orddet2 25 CHAR ITEM ID. desc_orddet2 1 CHAR ITEM DESCRIPTION. qtyord_orddet2 10 DEC QUANTITY ORDERED. altqtyord_orddet2 10 DEC ALTERNATE QUANTITY ORDERED. uom_orddet2 2 CHAR UNIT OF MEASURE. altuom_orddet2 2 CHAR ALTERNATE UNIT OF MEASURE. orgprice_orddet2 10 DEC ORIGINAL SELLING PRICE. altorgprc_orddet2 10 DEC ALTERNATE ORIGINAL SELLING PRICE. altsellpr_orddet2 10 DEC ALTERNATE SELLING PRICE. retailprc_orddet2 10 DEC RETAIL PRICE. freight_orddet2 10 DEC FREIGHT AMOUNT. spcsrv1_orddet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 1. spcsrv2_orddet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 2. delins1_orddet2 60 CHAR DELIVERY NOTES - LINE 1. delins2_orddet2 60 CHAR DELIVERY NOTES - LINE 2. memo1_orddet2 30 CHAR MEMO 1 (ALPHA). memo2_orddet2 30 CHAR MEMO 2 (ALPHA). memo3_orddet2 10 CHAR MEMO 3 (ALPHA). memo4_orddet2 10 DEC MEMO 4 (NUMERIC). memo5_orddet2 4 DATE MEMO 5 (DATE). maint_ser_orddet2 4 INT MAINTENANCE SERIAL NUMBER. maint_cde_orddet2 2 CHAR MAINTENANCE CODE. memod1_orddet2 30 CHAR DETAIL MEMO 1. memod2_orddet2 30 CHAR DETAIL MEMO 2. memod3_orddet2 30 CHAR DETAIL MEMO 3. memod4_orddet2 30 CHAR DETAIL MEMO 4. memod5_orddet2 30 CHAR DETAIL MEMO 5. memod6_orddet2 30 CHAR DETAIL MEMO 6. memod7_orddet2 30 CHAR DETAIL MEMO 7. memod8_orddet2 30 CHAR DETAIL MEMO 8. memod9_orddet2 30 CHAR DETAIL MEMO 9. memod10_orddet2 30 CHAR DETAIL MEMO 10. memod11_orddet2 30 CHAR DETAIL MEMO 11. memod12_orddet2 30 CHAR DETAIL MEMO 12. memod13_orddet2 30 CHAR DETAIL MEMO 13. memod14_orddet2 30 CHAR DETAIL MEMO 14. Release NGS-7.00 EDI- 178

179 FIELD NAME SIZE TYPE DESCRIPTION memod15_orddet2 30 CHAR DETAIL MEMO 15. memod16_orddet2 30 CHAR DETAIL MEMO 16. memod17_orddet2 30 CHAR DETAIL MEMO 17. memod18_orddet2 30 CHAR DETAIL MEMO 18. memod19_orddet2 30 CHAR DETAIL MEMO 19. memod20_orddet2 30 CHAR DETAIL MEMO 20. memod21_orddet2 30 CHAR DETAIL MEMO 21. memod22_orddet2 30 CHAR DETAIL MEMO 22. memod23_orddet2 30 CHAR DETAIL MEMO 23. memod24_orddet2 30 CHAR DETAIL MEMO 24. memod25_orddet2 30 CHAR DETAIL MEMO 25. memod26_orddet2 30 CHAR DETAIL MEMO 26. memod27_orddet2 30 CHAR DETAIL MEMO 27. memod28_orddet2 30 CHAR DETAIL MEMO 28. memod29_orddet2 30 CHAR DETAIL MEMO 29. memod30_orddet2 30 CHAR DETAIL MEMO 30. memod31_orddet2 30 CHAR DETAIL MEMO 31. memod32_orddet2 30 CHAR DETAIL MEMO 32. memod33_orddet2 30 CHAR DETAIL MEMO 33. memod34_orddet2 30 CHAR DETAIL MEMO 34. memod35_orddet2 30 CHAR DETAIL MEMO 35. memod36_orddet2 30 CHAR DETAIL MEMO 36. memod37_orddet2 30 CHAR DETAIL MEMO 37. memod38_orddet2 30 CHAR DETAIL MEMO 38. memod39_orddet2 30 CHAR DETAIL MEMO 39. memod40_orddet2 30 CHAR DETAIL MEMO 40. Indexes: Unique Index on ordnum_orddet2, lineno_orddet2. Index on maint_ser_orddet2. E. MISCRON - Cron Job Maintenance Setup Definition. Program Name: EDIMNTU Parameter 1: CRON Program Path: EDIPROGS Military Time: (Set to time desired). Daily Job: (Set to days desired). Selected Days: (Set to dates desired). Release NGS-7.00 EDI- 179

180 EDIBILU- EDI BILLING FILE UPDATE. A. Program Summary. The program will generate records in the EDI Open Invoice and Invoice History tables and remove records from the EDI Open Order tables for EDI transactions, which have been invoiced. This program should be setup to run from BILL as a subroutine. B. Program Detail. The program is designed to run from the BILL program after the billing update is completed (bill3*). This will be the last program run in the billing cycle. The program will first determine if the transaction being processed is for an EDI customer based on a record existing in the EDI order header table (orderc) for the invoice being processed. The process described below will occur for EDI customer transactions. For each of these transactions, the system will generate a record in the EDI Open Invoice Header table (invoicec) and the EDI Invoice History Header table (invc), based on the data in the EDI Order Header table (orderc) for each invoiced transaction header record. The system will generate records in the EDI Open Invoice Detail table (invdet2) and the EDI Invoice History Detail table (invd2) based on the data in the EDI Open Order Detail table (orddet2) for each invoiced transaction detail record. Once the records are generated, the program will determine if the order is still open in the Open Order table (orderb). If it is not, the EDI order record in the EDI Open Order table (orderc) for the transaction will be removed and all records for the transaction in the EDI Open Order Detail file (orddet2) will be removed. If the order is still open, the system will verify that each line number in the EDI Order Detail table (orddet2) is still open in the Order Detail table (orddet). For all lines which have been removed, the system will remove the lines in the EDI Order Detail table (orddet2). The advanced shipment notice fields in the EDI Order Header Table (orderc) will be cleared for shipments with backorders remaining on file. - The ASN Generation Flag will be set to 'N' (asnflag_orderc). - The ASN Generation Date will be set to '01/01/1980' (asndate_orderc). - The ASN Generation Time will be set to <NULL> (asntime_orderc). - The ASN Generation User will be set to <NULL> (asnuser_orderc). - The ASN Generation Batch # will be set to <NULL> (asnbatch_orderc). The invoice generation fields in the EDI Order Header Table (orderc) will be cleared for shipments with backorders remaining on file. - The Invoice Generation Flag will be set to 'N' (invflag_orderc). - The Invoice Generation Date will be set to '01/01/1980' (invdate_orderc). - The Invoice Generation Time will be set to <NULL> (invtime_orderc). - The Invoice Generation User will be set to <NULL> (invuser_orderc). - The Invoice Generation Batch # will be set to <NULL> (invbatch_orderc). Release NGS-7.00 EDI- 180

181 C. File & Field Layouts. C1. INVOICEC - EDI OPEN INVOICE HEADER FILE. FIELD NAME SIZE TYPE DESCRIPTION invnum_invoicec 10 CHAR INVOICE NUMBER. ordnum_invoicec 10 CHAR ORDER NUMBER. batch_invoicec 2 SMINT EDI BATCH NUMBER. partnrid_invoicec 27 CHAR TRADING PARTNER ID / MAILBOX NUMBER. billto_invoicec 35 CHAR BILL TO ID. soldto_invoicec 35 CHAR SOLD TO ID. shipto_invoicec 35 CHAR SHIP TO ID. bslook_invoicec 35 CHAR SHIP TO ID INDICATOR. trandate_invoicec 4 DATE TRANSACTION DATE. reqdate_invoice 4 DATE REQUESTED DATE. shipdate_invoicec 4 DATE SHIP DATE. canceldte_invoicec 4 DATE CANCEL DATE. podate_invoicec 4 DATE PURCHASE ORDER DATE. cust_po_invoicec 22 CHAR CUSTOMER P/O NUMBER. pobatch_invoicec 10 CHAR CUSTOMER PURCHASE ORDER BATCH. refno_invoicec 30 CHAR REFERENCE NUMBER. dept_invoicec 30 CHAR DEPARTMENT NUMBER. remarks_invoicec 80 CHAR REMARKS. media_invoicec 2 CHAR MEDIA/EVENT CODE. shipname_invoicec 35 CHAR SHIP TO NAME. shipaddr1_invoicec 35 CHAR SHIP TO ADDRESS 1. shipaddr2_invoicec 35 CHAR SHIP TO ADDRESS 2. shipaddr3_invoicec 35 CHAR SHIP TO ADDRESS 3. shipcity_invoicec 19 CHAR SHIP TO CITY. shipstate_invoicec 4 CHAR SHIP TO STATE. shipcntry_invoicec 10 CHAR SHIP TO COUNTRY. shipzip_invoicec 9 CHAR SHIP TO ZIP CODE. shipattn_invoicec 27 CHAR SHIP TO ATTENTION. markfor_invoicec 45 CHAR MARK FOR. terms_cd_invoicec 4 CHAR TERMS CODE. transcd_invoicec 2 CHAR TRANSACTION CODE. trantype_invoicec 2 CHAR TRANSACTION TYPE. contract_invoicec 12 CHAR CONTRACT NUMBER. routing_invoicec 2 CHAR ROUTING CODE. scac_invoicec 4 CHAR SCAC CODE. asnflag_invoicec 2 CHAR ASN GENERATION FLAG. asndate_invoicec 4 DATE ASN GENERATION DATE. asntime_invoicec 8 CHAR ASN GENERATION TIME. asnuser_invoicec 8 CHAR ASN GENERATION USER. asnbatch_invoicec 4 INT ASN GENERATION BATCH NUMBER. invflag_invoicec 2 CHAR INVOICE GENERATION FLAG. invdate_invoicec 4 DATE INVOICE GENERATION DATE. invtime_invoicec 8 CHAR INVOICE GENERATION TIME. invuser_invoicec 8 CHAR INVOICE GENERATION USER. invbtach_invoicec 10 CHAR INVOICE GENERATION BATCH NUMBER. Release NGS-7.00 EDI- 181

182 FIELD NAME SIZE TYPE DESCRIPTION memo1_invoicec 30 CHAR MEMO 1 (ALPHA). memo2_invoicec 30 CHAR MEMO 2 (ALPHA). memo3_invoicec 10 CHAR MEMO 3 (ALPHA). memo4_invoicec 10 DEC MEMO 4 (NUMERIC). memo5_invoicec 4 DATE MEMO 5 (DATE). memoh1_invoicec 30 CHAR HEADER MEMO 1. memoh2_invoicec 30 CHAR HEADER MEMO 1. memoh3_invoicec 30 CHAR HEADER MEMO 3. memoh4_invoicec 30 CHAR HEADER MEMO 4. memoh5_invoicec 30 CHAR HEADER MEMO 5. memoh6_invoicec 30 CHAR HEADER MEMO 6. memoh7_invoicec 30 CHAR HEADER MEMO 7. memoh8_invoicec 30 CHAR HEADER MEMO 8. memoh9_invoicec 30 CHAR HEADER MEMO 9. memoh10_invoicec 30 CHAR HEADER MEMO 10. memoh11_invoicec 30 CHAR HEADER MEMO 11. memoh12_invoicec 30 CHAR HEADER MEMO 12. memoh13_invoicec 30 CHAR HEADER MEMO 13. memoh14_invoicec 30 CHAR HEADER MEMO 14. memoh15_invoicec 30 CHAR HEADER MEMO 15. memoh16_invoicec 30 CHAR HEADER MEMO 16. memoh17_invoicec 30 CHAR HEADER MEMO 17. memoh18_invoicec 30 CHAR HEADER MEMO 18. memoh19_invoicec 30 CHAR HEADER MEMO 19. memoh20_invoicec 30 CHAR HEADER MEMO 20. memoh21_invoicec 30 CHAR HEADER MEMO 21. memoh22_invoicec 30 CHAR HEADER MEMO 22. memoh23_invoicec 30 CHAR HEADER MEMO 23. memoh24_invoicec 30 CHAR HEADER MEMO 24. memoh25_invoicec 30 CHAR HEADER MEMO 25. memoh26_invoicec 30 CHAR HEADER MEMO 26. memoh27_invoicec 30 CHAR HEADER MEMO 27. memoh28_invoicec 30 CHAR HEADER MEMO 28. memoh29_invoicec 30 CHAR HEADER MEMO 29. memoh30_invoicec 30 CHAR HEADER MEMO 30. memoh31_invoicec 30 CHAR HEADER MEMO 31. memoh32_invoicec 30 CHAR HEADER MEMO 32. memoh33_invoicec 30 CHAR HEADER MEMO 33. memoh34_invoicec 30 CHAR HEADER MEMO 34. memoh35_invoicec 30 CHAR HEADER MEMO 35. memoh36_invoicec 30 CHAR HEADER MEMO 36. memoh37_invoicec 30 CHAR HEADER MEMO 37. memoh38_invoicec 30 CHAR HEADER MEMO 38. memoh39_invoicec 30 CHAR HEADER MEMO 39. memoh40_invoicec 30 CHAR HEADER MEMO 40. Indexes: Index on invnum_invoicec. Index on ordnum_invoicec. Release NGS-7.00 EDI- 182

183 C2. INVDET2 - EDI OPEN INVOICE DETAIL FILE. FIELD NAME SIZE TYPE DESCRIPTION invnum_invdet2 10 CHAR INVOICE NUMBER. ordnum_invdet2 10 CHAR ORDER NUMBER lineno_invdet2 4 INT LINE NUMBER. subno_invdet2 4 CHAR SUB NUMBER. batch_invdet2 2 INT EDI BATCH NUMBER. partnrid_invdet2 27 CHAR TRADING PARTNER'S ID OR MAILBOX NUMBER. ponumber_invdet2 22 CHAR CUSTOMER P/O NUMBER. polineno_invdet2 4 CHAR CUSTOMER P/O SEQUENCE NUMBER custprt1_invdet2 18 CHAR CUSTOMER PART ID. custprt2_invdet2 18 CHAR CUSTOMER PART ID 2. upc_invdet2 25 CHAR UPC CODE. sellitem_invdet2 25 CHAR ITEM ID. desc_invdet2 18 CHAR ITEM DESCRIPTION. qtyord_invdet2 10 DEC QUANTITY ORDERED. altqtyord_invdet2 10 DEC ALTERNATE QUANTITY ORDERED. uom_invdet2 2 CHAR UNIT OF MEASURE. altuom_invdet2 2 CHAR ALTERNATE UNIT OF MEASURE. orgprice_invdet2 10 DEC ORIGINAL SELLING PRICE. altorgprc_invdet2 10 DEC ALTERNATE ORIGINAL SELLING PRICE. altsellprc_invdet2 10 DEC ALTERNATE SELLING PRICE. retailpr_invdet2 10 DEC RETAIL PRICE. freight_invdet2 10 DEC FREIGHT AMOUNT. spcsrv1_invdet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 1. spcsrv2_invdet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 2. delins1_invdet2 60 CHAR DELIVERY NOTES - LINE 1. delins2_invdet2 60 CHAR DELIVERY NOTES - LINE 2. memo1_invdet2 30 CHAR MEMO 1 (ALPHA). memo2_invdet2 30 CHAR MEMO 2 (ALPHA). memo3_invdet2 10 CHAR MEMO 3 (ALPHA). memo4_invdet2 10 DEC MEMO 4 (NUMERIC). memo5_invdet2 4 DATE MEMO 5 (DATE). memod1_invdet2 30 CHAR DETAIL MEMO 1. memod2_invdet2 30 CHAR DETAIL MEMO 2. memod3_invdet2 30 CHAR DETAIL MEMO 3. memod4_invdet2 30 CHAR DETAIL MEMO 4. memod5_invdet2 30 CHAR DETAIL MEMO 5. memod6_invdet2 30 CHAR DETAIL MEMO 6. memod7_invdet2 30 CHAR DETAIL MEMO 7. memod8_invdet2 30 CHAR DETAIL MEMO 8. memod9_invdet2 30 CHAR DETAIL MEMO 9. memod10_invdet2 30 CHAR DETAIL MEMO 10. memod11_invdet2 30 CHAR DETAIL MEMO 11. memod12_invdet2 30 CHAR DETAIL MEMO 12. memod13_invdet2 30 CHAR DETAIL MEMO 13. memod14_invdet2 30 CHAR DETAIL MEMO 14. Release NGS-7.00 EDI- 183

184 FIELD NAME SIZE TYPE DESCRIPTION memod15_invdet2 30 CHAR DETAIL MEMO 15. memod16_invdet2 30 CHAR DETAIL MEMO 16. memod17_invdet2 30 CHAR DETAIL MEMO 17. memod18_invdet2 30 CHAR DETAIL MEMO 18. memod19_invdet2 30 CHAR DETAIL MEMO 19. memod20_invdet2 30 CHAR DETAIL MEMO 20. memod21_invdet2 30 CHAR DETAIL MEMO 21. memod22_invdet2 30 CHAR DETAIL MEMO 22. memod23_invdet2 30 CHAR DETAIL MEMO 23. memod24_invdet2 30 CHAR DETAIL MEMO 24. memod25_invdet2 30 CHAR DETAIL MEMO 25. memod26_invdet2 30 CHAR DETAIL MEMO 26. memod27_invdet2 30 CHAR DETAIL MEMO 27. memod28_invdet2 30 CHAR DETAIL MEMO 28. memod29_invdet2 30 CHAR DETAIL MEMO 29. memod30_invdet2 30 CHAR DETAIL MEMO 30. memod31_invdet2 30 CHAR DETAIL MEMO 31. memod32_invdet2 30 CHAR DETAIL MEMO 32. memod33_invdet2 30 CHAR DETAIL MEMO 33. memod34_invdet2 30 CHAR DETAIL MEMO 34. memod35_invdet2 30 CHAR DETAIL MEMO 35. memod36_invdet2 30 CHAR DETAIL MEMO 36. memod37_invdet2 30 CHAR DETAIL MEMO 37. memod38_invdet2 30 CHAR DETAIL MEMO 38. memod39_invdet2 30 CHAR DETAIL MEMO 39. memod40_invdet2 30 CHAR DETAIL MEMO 40. Indexes: Index on invnum_invdet2. Index on ordnum_invdet2. Release NGS-7.00 EDI- 184

185 C3. INVC - EDI INVOICE HISTORY HEADER FILE. FIELD NAME SIZE TYPE DESCRIPTION invnum_invoicec 10 CHAR INVOICE NUMBER. ordnum_invoicec 10 CHAR ORDER NUMBER. batch_invoicec 2 SMINT EDI BATCH NUMBER. partnrid_invoicec 27 CHAR TRADING PARTNER ID / MAILBOX NUMBER. billto_invoicec 35 CHAR BILL TO ID. soldto_invoicec 35 CHAR SOLD TO ID. shipto_invoicec 35 CHAR SHIP TO ID. bslook_invoicec 35 CHAR SHIP TO ID INDICATOR. trandate_invoicec 4 DATE TRANSACTION DATE. reqdate_invoicec 4 DATE REQUESTED DATE. shipdate_invoicec 4 DATE SHIP DATE. canceldte_invoicec 4 DATE CANCEL DATE. podate_invoicec 4 DATE PURCHASE ORDER DATE. cust_po_invoicec 22 CHAR CUSTOMER P/O NUMBER. pobatch_invoicec 10 CHAR CUSTOMER PURCHASE ORDER BATCH. refno_invoicec 30 CHAR REFERENCE NUMBER. dept_invoicec 30 CHAR DEPARTMENT NUMBER. remarks_invoicec 80 CHAR REMARKS. media_invoicec 2 CHAR MEDIA/EVENT CODE. shipname_invoicec 35 CHAR SHIP TO NAME. shipaddr1_invoicec 35 CHAR SHIP TO ADDRESS 1. shipaddr2_invoicec 35 CHAR SHIP TO ADDRESS 2. shipaddr3_invoicec 35 CHAR SHIP TO ADDRESS 3. shipcity_invoicec 19 CHAR SHIP TO CITY. shipstate_invoicec 4 CHAR SHIP TO STATE. shipcntry_invoicec 10 CHAR SHIP TO COUNTRY. shipzip_invoicec 9 CHAR SHIP TO ZIP CODE. shipattn_invoicec 27 CHAR SHIP TO ATTENTION. markfor_invoicec 45 CHAR MARK FOR. terms_cd_invoicec 4 CHAR TERMS CODE. transcd_invoicec 2 CHAR TRANSACTION CODE. trantype_invoicec 2 CHAR TRANSACTION TYPE. contract_invoicec 12 CHAR CONTRACT NUMBER. routing_invoicec 2 CHAR ROUTING CODE. scac_invoicec 4 CHAR SCAC CODE. asnflag_invoicec 2 CHAR ASN GENERATION FLAG. asndate_invoicec 4 DATE ASN GENERATION DATE. asntime_invoicec 8 CHAR ASN GENERATION TIME. asnuser_invoicec 8 CHAR ASN GENERATION USER. asnbatch_invoicec 4 INT ASN GENERATION BATCH NUMBER. invflag_invoicec 2 CHAR INVOICE GENERATION FLAG. invdate_invoicec 4 DATE INVOICE GENERATION DATE. invtime_invoicec 8 CHAR INVOICE GENERATION TIME. invuser_invoicec 8 CHAR INVOICE GENERATION USER. invbatch_invoicec 10 CHAR INVOICE GENERATION BATCH NUMBER. Release NGS-7.00 EDI- 185

186 FIELD NAME SIZE TYPE DESCRIPTION memo1_invoicec 30 CHAR MEMO 1 (ALPHA). memo2_invoicec 30 CHAR MEMO 2 (ALPHA). memo3_invoicec 10 CHAR MEMO 3 (ALPHA). memo4_invoicec 10 DEC MEMO 4 (NUMERIC). memo5_invoicec 4 DATE MEMO 5 (DATE). memoh1_invoicec 30 CHAR HEADER MEMO 1. memoh2_invoicec 30 CHAR HEADER MEMO 1. memoh3_invoicec 30 CHAR HEADER MEMO 3. memoh4_invoicec 30 CHAR HEADER MEMO 4. memoh5_invoicec 30 CHAR HEADER MEMO 5. memoh6_invoicec 30 CHAR HEADER MEMO 6. memoh7_invoicec 30 CHAR HEADER MEMO 7. memoh8_invoicec 30 CHAR HEADER MEMO 8. memoh9_invoicec 30 CHAR HEADER MEMO 9. memoh10_invoicec 30 CHAR HEADER MEMO 10. memoh11_invoicec 30 CHAR HEADER MEMO 11. memoh12_invoicec 30 CHAR HEADER MEMO 12. memoh13_invoicec 30 CHAR HEADER MEMO 13. memoh14_invoicec 30 CHAR HEADER MEMO 14. memoh15_invoicec 30 CHAR HEADER MEMO 15. memoh16_invoicec 30 CHAR HEADER MEMO 16. memoh17_invoicec 30 CHAR HEADER MEMO 17. memoh18_invoicec 30 CHAR HEADER MEMO 18. memoh19_invoicec 30 CHAR HEADER MEMO 19. memoh20_invoicec 30 CHAR HEADER MEMO 20. memoh21_invoicec 30 CHAR HEADER MEMO 21. memoh22_invoicec 30 CHAR HEADER MEMO 22. memoh23_invoicec 30 CHAR HEADER MEMO 23. memoh24_invoicec 30 CHAR HEADER MEMO 24. memoh25_invoicec 30 CHAR HEADER MEMO 25. memoh26_invoicec 30 CHAR HEADER MEMO 26. memoh27_invoicec 30 CHAR HEADER MEMO 27. memoh28_invoicec 30 CHAR HEADER MEMO 28. memoh29_invoicec 30 CHAR HEADER MEMO 29. memoh30_invoicec 30 CHAR HEADER MEMO 30. memoh31_invoicec 30 CHAR HEADER MEMO 31. memoh32_invoicec 30 CHAR HEADER MEMO 32. memoh33_invoicec 30 CHAR HEADER MEMO 33. memoh34_invoicec 30 CHAR HEADER MEMO 34. memoh35_invoicec 30 CHAR HEADER MEMO 35. memoh36_invoicec 30 CHAR HEADER MEMO 36. memoh37_invoicec 30 CHAR HEADER MEMO 37. memoh38_invoicec 30 CHAR HEADER MEMO 38. memoh39_invoicec 30 CHAR HEADER MEMO 39. memoh40_invoicec 30 CHAR HEADER MEMO 40. Indexes: Index on invnum_invoicec. Index on ordnum_invoicec. Release NGS-7.00 EDI- 186

187 C4. INVD2 - EDI INVOICE HISTORY DETAIL FILE. FIELD NAME SIZE TYPE DESCRIPTION invnum_invdet2 10 CHAR INVOICE NUMBER. ordnum_invdet2 10 CHAR ORDER NUMBER lineno_invdet2 4 INT LINE NUMBER. subno_invdet2 4 CHAR SUB NUMBER. batch_invdet2 2 INT EDI BATCH NUMBER. partnrid_invdet2 27 CHAR TRADING PARTNER'S ID OR MAILBOX NUMBER. ponumber_invdet2 22 CHAR CUSTOMER P/O NUMBER. polineno_invdet2 4 CHAR CUSTOMER P/O SEQUENCE NUMBER. custprt1_invdet2 18 CHAR CUSTOMER PART ID. custprt2_invdet2 18 CHAR CUSTOMER PART ID 2. upc_invdet2 25 CHAR UPC CODE. sellitem_invdet2 25 CHAR ITEM ID. desc_invdet2 18 CHAR ITEM DESCRIPTION. qtyord_invdet2 10 DEC QUANTITY ORDERED. altqtyord_invdet2 10 DEC ALTERNATE QUANTITY ORDERED. uom_invdet2 2 CHAR UNIT OF MEASURE. altuom_invdet2 2 CHAR ALTERNATE UNIT OF MEASURE. orgprice_invdet2 10 DEC ORIGINAL SELLING PRICE. altorgprc_invdet2 10 DEC ALTERNATE ORIGINAL SELLING PRICE. altsellprc_invdet2 10 DEC ALTERNATE SELLING PRICE. retailpr_invdet2 10 DEC RETAIL PRICE. freight_invdet2 10 DEC FREIGHT AMOUNT. spcsrv1_invdet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 1. spcsrv2_invdet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 2. delins1_invdet2 60 CHAR DELIVERY NOTES - LINE 1. delins2_invdet2 60 CHAR DELIVERY NOTES - LINE 2. memo1_invdet2 30 CHAR MEMO 1 (ALPHA). memo2_invdet2 30 CHAR MEMO 2 (ALPHA). memo3_invdet2 10 CHAR MEMO 3 (ALPHA). memo4_invdet2 10 DEC MEMO 4 (NUMERIC). memo5_invdet2 4 DATE MEMO 5 (DATE). memod1_invdet2 30 CHAR DETAIL MEMO 1. memod2_invdet2 30 CHAR DETAIL MEMO 2. memod3_invdet2 30 CHAR DETAIL MEMO 3. memod4_invdet2 30 CHAR DETAIL MEMO 4. memod5_invdet2 30 CHAR DETAIL MEMO 5. memod6_invdet2 30 CHAR DETAIL MEMO 6. memod7_invdet2 30 CHAR DETAIL MEMO 7. memod8_invdet2 30 CHAR DETAIL MEMO 8. memod9_invdet2 30 CHAR DETAIL MEMO 9. memod10_invdet2 30 CHAR DETAIL MEMO 10. memod11_invdet2 30 CHAR DETAIL MEMO 11. memod12_invdet2 30 CHAR DETAIL MEMO 12. memod13_invdet2 30 CHAR DETAIL MEMO 13. memod14_invdet2 30 CHAR DETAIL MEMO 14. Release NGS-7.00 EDI- 187

188 FIELD NAME SIZE TYPE DESCRIPTION memod15_invdet2 30 CHAR DETAIL MEMO 15. memod16_invdet2 30 CHAR DETAIL MEMO 16. memod17_invdet2 30 CHAR DETAIL MEMO 17. memod18_invdet2 30 CHAR DETAIL MEMO 18. memod19_invdet2 30 CHAR DETAIL MEMO 19. memod20_invdet2 30 CHAR DETAIL MEMO 20. memod21_invdet2 30 CHAR DETAIL MEMO 21. memod22_invdet2 30 CHAR DETAIL MEMO 22. memod23_invdet2 30 CHAR DETAIL MEMO 23. memod24_invdet2 30 CHAR DETAIL MEMO 24. memod25_invdet2 30 CHAR DETAIL MEMO 25. memod26_invdet2 30 CHAR DETAIL MEMO 26. memod27_invdet2 30 CHAR DETAIL MEMO 27. memod28_invdet2 30 CHAR DETAIL MEMO 28. memod29_invdet2 30 CHAR DETAIL MEMO 29. memod30_invdet2 30 CHAR DETAIL MEMO 30. memod31_invdet2 30 CHAR DETAIL MEMO 31. memod32_invdet2 30 CHAR DETAIL MEMO 32. memod33_invdet2 30 CHAR DETAIL MEMO 33. memod34_invdet2 30 CHAR DETAIL MEMO 34. memod35_invdet2 30 CHAR DETAIL MEMO 35. memod36_invdet2 30 CHAR DETAIL MEMO 36. memod37_invdet2 30 CHAR DETAIL MEMO 37. memod38_invdet2 30 CHAR DETAIL MEMO 38. memod39_invdet2 30 CHAR DETAIL MEMO 39. memod40_invdet2 30 CHAR DETAIL MEMO 40. Indexes: Index on invnum_invdet2. Index on ordnum_invdet2. D. CTRLE - Multi-Process Program Parameter Maintenance. Program Name: EDIBILU Calling Program Name: BILL Sending Field 1: invnum_invoiceb Release NGS-7.00 EDI- 188

189 EDIPRG- EDI FILES PURGE. A. Program Summary. This program will clear records from the EDI order maintenance, EDI open invoice, and EDI invoice history tables once the corresponding order maintenance, open invoice and invoice history records have been removed. An option is provided to clear the EDI open invoice tables only or all the tables. The program has the capability of running interactively or as a scheduled job through MISCRON. If the edinhc and edindc (header and detail comments) records exist, they will be purged when the corresponding records are purged or deleted from the EDI Header or Detail Table. B. Program Detail. When accessing the program, the operator will be prompted to indicate whether they want to purge the open invoice tables only. The operator will then be prompted to verify that they want to proceed with the purge. The program will first examine the open invoice header and detail tables. If a record does not exist in the standard Open Invoice Header table (invoiceb) with the same invoice number as the EDI Open Invoice Header table (invoicec), the system will delete the records for the invoice in the EDI Open Invoice Header and Detail tables (invoicec, invdet2). If the program is not being run for the open invoice files only, the program will then examine the invoice history tables and the order maintenance files. If a record does not exist in the standard Invoice History Header table (invb) with the same invoice number as the EDI Invoice History Header table (invc), the system will delete the records for the invoice in the EDI Invoice History Header and Detail tables (invc, invd2). If a record does not exist in the standard Order Maintenance Header table (ormntb) with the same serial number as the EDI Order Maintenance Header table (ormntc), the system will delete the records for the serial number in the EDI Order Maintenance Header and Detail tables (ormntc, ormntd2). If a record does not exist in the standard Order Maintenance Detail table (ormntd) with the same serial number as the EDI Order Maintenance Detail table (ormntd2), the system will delete the records for the serial number in the EDI Order Maintenance Detail table (ormntd2). Release NGS-7.00 EDI- 189

190 C. Screen Layout. D. MISCRON - Cron Job Maintenance - Setup. Program Name: EDIPRG Parameter 1: CRON Program Path: EDIPROGS Military Time: (Set to time desired). Daily Job: (Set to days desired). Selected Days: (Set to dates desired). Release NGS-7.00 EDI- 190

191 EDITPMCM- EDI TRADING PARTNER MANUAL CUSTOMER MAINT. PROGRAM. A. Program Summary. This program will allow the user to add, update, remove, generate, query and view records in the Trading Partner Manual Customer table. The purpose of the table is to define the trading partners and customers that will be generating outbound EDI documents for manually entered transactions not originally received through an EDI purchase order. B. Program Detail. A new table has been added to the system to allow the definition of these customers. See section D for the file format for the EDI Trading Partner Manual Customer Table. See section C1 for the maintenance screen display format. The following describes the logic for each menu option. B1. Add Menu Options Logic. The program will prompt for the trading partner id / mailbox number and will validate that the trading partner is a valid trading partner and display the trading partner name below the trading partner id. The drop down window feature will allow the operator to select the trading partner based on the trading partner id or the trading partner name; see section C2 for the drop down window screen display format. The program will then prompt for the entry of a customer id and will validate that the customer is a valid customer and display the customer name to the right of the customer id. The drop down window feature will allow the operator to select the customer based on the customer id, customer name, customer crossreference or phone number; see section C3 for the drop down window screen display format. The program will prompt for the 30 character memo 1 field. The program will prompt for the 30 character memo 2 field. The program will prompt for the 10 character memo 3 field. The program will prompt for the memo 4 field, which allows decimal numeric values. An entry of <NULL> will not be permitted. The program will prompt for the memo 5 date field. An entry of <NULL> will not be permitted. B2. Update Menu Options Logic. The program will allow selection based on the trading partner id, customer id and memo fields within the trading partner manual customer table. The system will provide the options for Update, Next record, Previous record, Help and Exit. When utilizing the update option, the system will prompt for each memo field sequentially and allow the operator to override them. Release NGS-7.00 EDI- 191

192 B3. Query Menu Options Logic. The program will allow selection based on the trading partner id, customer id and memo fields within the trading partner manual customer table. The system will provide the options for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. The program will allow selection based on the trading partner id, customer id and memo fields within the trading partner manual customer table. The system will provide the options for Remove, Next record, Previous record, Help and Exit. B5. View Menu Options Logic. The program will allow selection based on the trading partner id, customer id and memo fields within the trading partner manual customer table. The program will allow you to sort by the trading partner id or the customer id with a different report format for each sort option and will allow the report to be output to screen, printer, or hold file. See section C4 for the view option sort selection screen format. See section E for the view report formats. B1-6. Generate Menu Options Logic. The program will allow you to generate multiple records in the table for a trading partner based on the criteria entered. The program will prompt for the trading partner id / mailbox number and will validate that the trading partner is a valid trading partner and display the trading partner name below the trading partner id. The drop down window feature will allow the operator to select the trading partner based on the trading partner id or the trading partner name; see section C2 for the drop down window screen display format. Once the trading partner is displayed, the program will prompt for the entry of the customer criteria (customer id, customer name, customer cross-reference and customer phone number) to utilize to select records to generate; see section C5 for the screen display format. Once the operator enters the criteria, the system will determine if any records meet the criteria in the customer master table. If no records meet the criteria, the system will display the message "No records found" and return to the customer criteria. If any records meet the criteria, the system will display the number of records which will be generated (based on the records existing in the Customer Master Table but not in the Trading Partner Manual Customer Table) and ask the operator if they want to proceed. Note that the prompt will require selection criteria to be entered. The system will then prompt for the 5 memo fields and then prompt the operator "Generate Records (Y/N)?". If the operator enters "Y", the system will generate records for all the customers selected with identical trading partner id and memo fields. If the operator enters "N", the system will return to the Trading Partner ID prompt. Release NGS-7.00 EDI- 192

193 C. Screen Layouts. C1. Maintenance Screen. C2. Trading Partner ID Option Screen Choose from the drop down window Release NGS-7.00 EDI- 193

194 C3. Customer ID Option choose from the drop down window. C4. View Report Sort Options Screen. Release NGS-7.00 EDI- 194