Table of Contents - Jason Industrial · The third party EDI communication, translation and mapping software package must receive EDI purchase order transactions (850), translate and

EDI PROCESSING INTERFACE MODULE

Table of Contents

EDI PROCESSING INTERFACE MODULE ........................................................... 1

EDI PROCESSING OVERVIEW ............................................................................................ 3

SETUP AND MAINTENANCE PROGRAMS .......................................................................... 15

EDITPM- ................. EDI TRADING PARTNER MAINTENANCE .............................................. 15 EDITPVM- .............. EDI TRADING PARTNER VENDOR MAINTENANCE. ................................ 28 EDISVM- ................ EDI TRADING PARTNER SHIP VIA MASTER TABLE MAINT.................... 36 EDITERM- .............. EDI TRADING PARTNER TERMS MASTER TABLE MAINT. ..................... 42 EDIUOM- ................ EDI TRADING PARTNER U.O.M. XREF TABLE MAINT. .......................... 45

PROCESSING INBOUND TRANSACTIONS .......................................................................... 49

EDIPOLD- ............... EDI PURCHASE ORDER UPLOAD PROGRAM......................................... 49 PROGRAM OVERVIEW .............................................................................................. 49 B1 - UPLOAD/IMPORT ASCII/EXCEL FILE OPTION ........................................................ 52 B2 - VALIDATION OPTION ........................................................................................ 55 B3 - MAINTENANCE OPTION ..................................................................................... 64 B4 - ORDER CREATION OPTION. ............................................................................... 70 B5 - PURGE OPTION ................................................................................................. 73 C - CUSTOM PROGRAM ROUTINE CAPABILITY ........................................................... 75 D - FILE AND FIELD LAYOUTS ................................................................................... 76 E - INBOUND CUSTOMER PURCHASE ORDER ASCII FILE DEFINITION (850) .................... 88 G - EDI INBOUND PURCHASE ORDER HEADER TABLE MAPPING (EDINH) TO ORDER TABLES92 H - EDI INBOUND PURCHASE ORDER DETAIL TABLE MAPPING (EDIND) TO ORDER TABLES95 I - ACF OPTIONS FOR THE EDI MODULE - ................................................................. 97

PROCESSING OUTBOUND TRANSACTIONS ...................................................................... 98

EDIASNG- .............. EDI OUTBOUND ADVANCED SHIP NOTICES GENERATION .................... 98 EDIINVCG- ............. EDI OUTBOUND INVOICE ASCII FILE GENERATION .............................. 111 EDIPOG- ................. EDI PURCHASE ORDER ASCII FILE GENERATION ................................. 130 EDIMNTU-.............. EDI ORDER MAINTENANCE FILE UPDATE. .......................................... 181 EDIBILU- ................ EDI BILLING FILE UPDATE. ................................................................ 187 EDIPRG- ................. EDI FILES PURGE. ............................................................................ 196 EDITPMCM- ........... EDI TRADING PARTNER MANUAL CUSTOMER MAINTENANCE PROGRAM.198 EDIMCG- ................ EDI MANUAL CUSTOMER TRANSACTION GENERATION. ..................... 204

Next Generat ion® EDI PROCESSING INTERFACE MODULE

Release NGS-6.30 EDI- 2

Proprietary Not ice This manual contains information w hich 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 w ithout the express w rit ten permission of Munics Information Systems, Inc. Disclaimer of Warranty The material contained herein is subject to change w ithout not ice. Munics Information Systems, Inc. makes no w arranty, express, implied or by descript ion, regarding the information set forth herein. Munics Information Systems, Inc. does not guarantee, warrant or make any representat ion regarding the use of, or the results of the use of, the programs in terms of correctness, accuracy, reliability, currency or otherw ise, and the purchaser relies on the programs and the results solely at his/her ow n risk. NEXT GENERATION® is a registered trademark of Munics Information Systems, Inc. Copyright 1987-2006 Munics Information Systems, Inc.



EDI PROCESSING OVERVIEW TRANSACTIONS PROCESSED: - Incoming Purchase Order Transact ions (850) from your customers. - Outgoing Advanced Ship Notices (856), Invoices (810) and Combined Advanced Ship Notices /

Invoices (857) to your customers. - Outgoing Purchase Order Transact ions (850) to your vendors. REQUIREMENTS: - The Next-Generat ionTM EDI Processing Subsystem. - A Third Party PC or UNIX based EDI communicat ion, translat ion and mapping package w ith the capabilit ies of sending and receiving the EDI transact ions from your trading partners, translat ing these documents into an ASCII format and mapping each trading partner document to the required Next- Generat ionTM standard ASCII f ile formats. - If you use a PC product, the PC must be interfaced to the UNIX system and have the capability of t ransferring ASCII f iles from the PC to the UNIX system and vice versa. CUSTOMER TRANSACTION FLOW: The third party EDI communicat ion, translat ion and mapping softw are package must receive EDI purchase order transact ions (850), t ranslate and map them to our standard EDI ASCII File Format, and upload them into a directory on the UNIX system so that the Next-Generat ionTM Software can access these f iles. Once the above is completed, the Next-Generat ionTM EDI Softw are w ill take over. The EDI Inbound Processing Program (EDIPOLD) w ill process the 850 transactions: - The UPLOAD opt ion w ill be processed to upload the ASCII f iles into Informix database f iles. This w ill generate data records in the EDI header and detail f iles on the Next -Generat ionTM system. - The VALIDATION opt ion w ill be processed once the f iles are uploaded to validate the data sent in and determine the customer and items to be processed. The system w ill f lag any invalid transact ions such as invalid trading partners, invalid ship to customers, invalid items, duplicate purchase orders and purchase orders outside of a def ined date range. - The MAINTENANCE opt ion must be processed for invalid transact ions to modify the invalid f ields manually or to remove the invalid records. - The VIEW opt ion may be processed to provide a report to the screen, printer or a hold f ile of the EDI t ransact ions. - The ORDER CREATION opt ion w ill be processed for validated records. The system w ill create temporary order f iles based on the information provided from the EDI f iles. The system w ill set addit ional f ields based on the default f ields def ined for the customer and item on the Next Generat ionTM database. As each record is processed, the system w ill generate an order in the standard order database tables from the temporary f iles.



- The PURGE opt ion may be ut ilized to remove records, w hich have been updated to the order tables, at regular intervals. Once the order has been generated, the Next-Generat ionTM order processing system is ut ilized to print forms, generate reports, provide inquiries and process the order. Once the order is ship conf irmed, the EDI Advanced Ship Notices Processing Program (EDIASNG) is ut ilized to generate an ASCII f ile in our standard format for Advanced Ship Notice documents (856). Once the order is billed, the EDI Invoice Processing Program (EDIINVCG) is ut ilized to generate ASCII f iles in our standard format for Invoice documents (810) or Combined Advanced Ship Notice / Invoice douments (857). Once the ASCII f iles are generated, the EDI processing on the Next-Generat ionTM system is completed. The ASCII f iles must then be dow nloaded to the PC, processed through the Third Party communicat ions, translat ion and mapping softw are and then transmitted to the trading partners. VENDOR TRANSACTION FLOW Once the purchase order has been entered, the EDI Purchase Order Generat ion Program (EDIPOG) is ut ilized to generate an ASCII f ile in our standard format for Purchase Order documents (850). Once the ASCII f ile is generated, the EDI processing on the Next-Generat ionTM system is completed. The ASCII f iles must then be dow nloaded to the PC, processed through the Third Party communicat ions, translat ion and mapping softw are and then transmitted to the trading partners. The third party EDI communicat ion, translat ion and mapping softw are package must map our standard EDI purchase order ASCII f ile format to the EDI purchase order document (850) based on the trading partner requirements, translate the data to the standard EDI Transact ion Document (850), and transmit the document to the trading partner mailbox. The Next-Generat ionTM purchase order processing system is ut ilized to print forms, generate reports, provide inquiries and process the purchase order and purchase order receipt.



SETUP PROCEDURE 1. The follow ing data f iles/f ields must be setup prior to ut ilizing EDI: - CM – If desired, a memo f ield may be def ined to f lag customers w hich w ill do EDI transact ions. - CICR - Setup applicable customer part numbers if customer part verif icat ion w ill be performed. - IM - If the customer w ill be using the UPC code, the UPC code may be setup in the item cross- reference f ield in the item master table. The UPC code may also be setup in the Item Interchange Table through the UPCLOAD program. As an alternat ive (or if different customers have dif ferent 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 w ill be using outbound transact ions (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 w ill 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 opt ions' default values (all of w hich have an opt ion code beginning w ith the characters ' edi' ) should be analyzed and, if necessary, changed. 3. If the trading partner w ill receive EDI Invoice transmissions, modif icat ions may be required to the Invoice Print program (INVP) to correspond to the customer' s need to send invoices to EDI customers. 4 .All f ields are brought into the EDI f iles themselves (edinh, edind). Records are generated as the t ransact ion 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 capabilit ies (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 transact ions. Analysis must be done of the EDI transact ions done by the customer to determine if any addit ional f ields sent need to be mapped to the standard order (and ship and invoice tables). If addit ional f ields, are required, addit ional customizat ion may be required. Note that the EDI Outbound transactions (advanced ship not ices and invoices) require that the



t ransact ions w ere originally added to the system through an EDI Inbound transact ion (purchase order).



TRANSFER PROCEDURE In order to ut ilize EDI, ASCII f iles need to be generated on the PC for the EDI transact ions. Once these f iles are generated, there are several methods to " transfer" these f iles to the Unix system. One method is to transfer the f ile using a diskette. This is the method that must be used if the PC is not netw orked w ith the Unix system. You w ould upload the f ile from the PC to the diskette and dow nload the f ile from the diskette to the Unix system. Another method is to create a " shared" directory betw een the PC and Unix system. When the EDI ASCII f ile is generated in this directory, it is immediately available for processing by the Unix system. Another method is to use a PC transfer ut ility (for example, FTP). If FTP is used, only the user w ho transferred the ASCII f ile w ill have suff icient access to upload the f ile on the Unix system. When FTP transfers a program, it t ransfers for the user and group of the user. The permissions are set to 640 (ow ner has read/w rite permission, group has read permission, others have no permission). Therefore, since read/w rite permission is required to upload the f ile, only the ow ner (the user that performed the transfer) can perform the upload. If it is desired for another user to have access, after transferring the f ile to the Unix system, go into the applicable directory (normally $EDIPROGS/edin/data) and change the permissions on the f ile so all users have access (normally by chmod 666 < f ilename> ). An example of FTP procedure session (make sure you follow your ow n FTP procedure): - w indows. - Start . - programs. - msdos prompt. - cd to directory in w hich ASCII f ile resides. - f tp (Unix system name> (i.e. f tp sco). - enter Unix user name (i.e. smith). - enter user passw ord (i.e. ???). - binary to transfer in binary mode. - put < source f ilename> < full pathname of dest inat ion f ilename> put edi850.dat /edi850/edi850.dat - quit to exit f tp. - exit to return to w indow s. A new method of receiving edi f iles via the f tp process is by using the FTPRECV pgm to connect w ith your 3rd party provider. Another new program to send edi f iles to your 3rd party provider is FTPSEND. The parameters for both programs are setup via the FTPCFGM program.



RETRIEVING FILES via FTP FTPRECV - note that these f ields are propagated from the matching external ID in the FTPCFGM program table.

External Id - name of the 3rd party provider you want to connect to to receive data From Server – IP address of the party you’ re connect ing w ith From Directory – the directory w here the data is stored on the external party’ s system From File Name – name of the f ile you are retrieving. Note: ‘ * ’ w ill retrieve all f iles in the above directory. Our Directory – the directory w here the data w ill be placed on the Munics sytem. Our File Name – f ilename stored in the above directory. Blank or ‘ * ’ w ill store as the same name of the f ile you are retrieving; w hich is probably w hat you want. PROCEED - enter “ PROCEED” to cont inue w ith the ftp process.



FTPCFGM - this is the program that stores the parameters for the FTP process

Program - name of the program to be used. e.g. “ FTPRECV” ID - generic name of the party you are connect ing to. e.g. VANTREE as a 3rd party EDI provider. REMOTE SERVER / CONNECT TO SETUP Receiving Directory - N/A Receiving File - N/A Sendng Directory - name of the directory on the remote system that you w ill be retrieving from. Sending File - name of the f ile you w ill be retrieving.



LOCAL FTP Client / CONNECT From SETUP Sendng Directory - N/A Sending File - N/A Receiving Directory - name of the directory on the local system that you w ill placing the data. Receiving File - name of the f ile you w ill be retrieving. If blank, the default is the retrieved f ilename. SENDING FILES via FTP FTPSEND - note that these fields are propagated from the matching external ID in the FTPCFGM program table.

External Id - name of the 3rd party provider you want to connect to to send data. To Server – IP address of the party you’ re connect ing w ith. To Directory – the directory w here the data w ill be stored on the external party’ s system To File Name – name of the f ile you are sending. Blank w ill store it as the same name. Our Directory – the directory w here the data is stored on the Munics sytem. Our File Name – f ilename that you are going to send. PROCEED - enter “ PROCEED” to cont inue w ith the ftp process.



Program - name of the program to be used. e.g. “ FTPSEND” ID - generic name of the party you are connect ing to. e.g. VANTREE as a 3rd party EDI provider. REMOTE SERVER / CONNECT TO SETUP Receiving Directory - name of the directory on the remote system that you w ill be sending to. Receiving File - name of the f ile you w ill be sending. This can be left blank. It w ill default to the name of the f ile you are sending. Sendng Directory - N/A Sending File - N/A LOCAL FTP Client / CONNECT From SETUP Sendng Directory - name of the directory on the local system that you w ill placing the data. Sending File - name of the f ile you w ill be sending. If blank, the default is the retrieved f ilename.



Receiving Directory - N/A Receiving File - N/A



Example of SENDING Purchase Order f iles via FTP FTPCFGM setup

When you execute the EDIPOG program to create the outgoing purhase order EDI f iles, ther is an opt ion to “ Ftp” the f ile. If selected the follow ing screen appears and the information of where to send the PO data is retrieved from the FTPCFGM program (program id = EDIPOG).





SETUP AND MAINTENANCE PROGRAMS EDITPM- EDI TRADING PARTNER MAINTENANCE A. Program Summary. This program w ill allow the user to add, update, remove, query and view records in the Trading Partner Master table. The purpose of the table is to def ine customers for EDI processing. B. Program Detail. The follow ing describes the logic for each menu opt ion. B1. Add Menu Options Logic.

• t rading partner id / mailbox number. This f ield w ill be unique and w ill be the key to the record.

• customer id and w ill validate that the customer is a valid customer and display the customer

name to the right of the customer id. The drop dow n w indow w ill allow the operator to select the customer based on the customer id, customer name, and customer cross-reference or phone number.

• t rading partner name. This f ield w ill default to the customer name.

• sold to validat ion method. The valid methods are def ined below :

0 – Use the customer id and pref ix (w hen applicable) def ined for the trading partner

to determine the customer sold to id. 1 - Use SOLD TO ID sent in direct ly from the EDI transmission as the customer sold

to id for the transact ion.

2 – Use the customer pref ix def ined for the trading partner and the SHIP TO ID sent in direct ly from the EDI transmission to determine the customer sold to id for the transact ion. The sold to id w ill be selected based on the trading partner customer pref ix matching the f irst characters of the customer id in the customer master and the ship to id exist ing in the ship to master for the customer.

3 - Use SOLD TO ID sent in direct ly from the EDI transmission and match it to the

customer cross-reference f ield in the Customer table to determine the customer sold to id for the transact ion.

• customer pref ix (w hich w ill be used to access the proper customer records w hen multiple

customer records are setup for the trading partner). For example, if t rading partner ' 123456789' has a main customer record of ' XXXX' setup in the system and all sold-to customer' s for the trading partner begin w ith ' XXXX' , the pref ix would be set to ' XXXX' . When a transact ion is validated, the system w ill use the ' XXXX' pref ix before the bill to ID passed from the EDI ASCII f ile as the sold to id. If this feature is not required for the trading partner, leave the f ield blank.

• ship to validat ion method. The valid methods are def ined below :

method " 1" - If the bslook f ield on the inbound transact ion is set to ' BS' , the system w ill 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 w ill be the ship to name and address in the ship to table.

If the bslook field on the inbound transact ion is not set to ' BS' , the validated ship to ID w ill 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 w ill be set to the EDI ship to name and address. This provides the ability to def ine a generic ship to record for the customer for EDI transact ions.

method " 2" - If the EDI bill to id is equal to the EDI ship to id, the validated ship to id w ill be set to ' SAME' .If the EDI bill to id is not equal to the EDI ship to id, the system w ill 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 w ill be the EDI ship to name and address. If all the EDI ship to name and address f ields are blank, the system w ill use the ship to name and address in the ship to table. method " 3" - If the Ship to Validat ion Method is set to a " 3" , the system w ill validate the shipto id from the EDI input f ile to the SHIPTO table in the standard system. The f ield that w ill be used for validat ion is the monitor_shipto f ield (program STM). This is a new opt ion added for customers such as Walmart w ho use a global distribut ion code as their shipto ident if ier.

• customer id to be used to obtain the item retail price. The f ield w ill be validated to insure that the code entered is a valid customer in the system. The drop dow n w indow w ill allow the operator to select the customer based on the customer id, customer name, customer cross-reference or phone number. If the f ield has a value, the system w ill calculate the retail price for the customer during the EDI validat ion and load the value into the table. If the f ield is blank, the system w ill leave the retail price as it is uploaded into the table. This f ield 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 not ices through EDI. A ' Y' or ' N' value must be entered. Note that only transact ions w hich have been created through the EDI process, from an 850 document, are available for outbound transact ions.

• if the trading partner requires processing of invoices through EDI. A ' Y' or 'N' value must

be entered. Note that only transact ions w hich have been created through the EDI process, from an 850 document, are available for outbound transact ions.

• if the trading partner requires processing of order status transact ions through EDI. A 'Y' or

' N' value must be entered. Note that this f ield is for future use.

• item lookup f ield method. The valid methods are def ined below :

1 - Use EDI item id f ield to access the item id f ield in the Item Master Table.

2 - Use EDI item id f ield to access the item cross-reference f ield in the Item Master Table (UPC method).

3 - Use EDI item f ield to access the customer part id in the Customer/Item Cross-reference Table (cixref).

4 – Use EDI item f ield to access the customer part id in the Contract Pricing Table for a valid



contract for the customer id.

5 – Use EDI item f ield to access the UPC/Interchange ID in the Item Interchange Table maintained by the UPCLOAD program.

• UPC lookup f ield method. The valid methods are def ined below :

1 - Use EDI item id f ield to access the item id f ield in the Item Master Table.

2 - Use EDI item id f ield to access the item cross-reference f ield in the Item Master Table (UPC method).

3 - Use EDI item f ield to access the customer part id in the Customer/Item Cross-reference Table (cixref).

4 – Use EDI item f ield to access the customer part id in the Contract Pricing Table for a valid contract for the customer id.

5 – Use EDI item f ield 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 def ined below :

1 - Use EDI customer part id f ield to access the item id f ield in the Item Master Table.

2 - Use EDI customer part id f ield to access the item cross-reference f ield in the Item Master Table (UPC method).

3 - Use EDI customer part id f ield to access the customer part id in the Customer/Item Cross-reference Table (cixref).

4 – Use EDI customer part id f ield 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 f ield to access the UPC/Interchange ID in the Item Interchange Table maintained by the UPCLOAD program.

• customer part id combine method. The valid methods are def ined below :

1 - Validate customer part id 1. If customer part id 1 fails validat ion, attempt to validate customer part id 2.

2 - Combine the customer part id 1 and part id 2 f ields w ith a dash (-) separat ing them and use this value for the customer part id validat ion.

3 - Combine the customer part id 1 and part id 2 f ields w ith no separator and use this value for the customer part id validat ion.

• The program w ill then prompt for the customer part id lookup (w hich w ill be the customer id

to ut ilize when accessing the Customer Part ID Cross-reference Table (cixref)). The f ield w ill be validated to insure that the code entered is a valid customer in the system. The drop dow n w indow w ill allow the operator to select the customer based on the customer id,



customer name, customer cross-reference or phone number. If the f ield is left blank, the system w ill use the sold to customer ID w hen 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 w ill not be ut ilized by any other programs in the system.

• sell price validat ion f lag to indicate w hether the selling price should be validated for the

trading partner' s transact ions. The follow ing 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 w ill

use the selling price calculated by the system. Logic behind this is if the Trading Partner sends in a zero price, they are accept ing the price you calculated.

N – Do not perform the validat ion of the selling price. The selling price on the transact ion w ill be the price calculated by the standard system.

O - Do not perform the validat ion of the selling price. The selling price from the EDI or w ebsite transmission file w ill be the selling price used in the standard system. The price origin code w ill be set to a ' 1' .

NOTE : Option ' O' means that the selling price from the EDI or w ebsite transmission f ile w ill 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) w ill be ut ilized.

E - The selling price from the EDI or w ebsite transmission f ile w ill be the selling price assigned to the sales order transact ion. The price origin code w ill be set to a value of ' 1' . Unlike opt ion ' O' , the system w ill st ill calculate the normal selling price based on the standard system calculat ions in order to determine if it varies from the price on the EDI transact ion. If the selling price calculated by the standard system is dif ferent than the selling price from the EDI transact ion, an Audit Trail record w ill be generated when the order is created w hich w ill include both the selling price calculated by the system and the selling price assigned to the sales order transact ion from the trading partner' s EDI transact ion.

• maximum normal order value. If this f ield is not zero, the system w ill validate that the total

order value of the EDI transact ion does not exceed this amount.

• unit of measure. This w ill be output to the Advanced Ship Notice. Leave the f ield blank if you w ant to output the sales order' s unit of measure instead.

• packaging code. This w ill be output to the Advanced Ship Notice.



• the transact ion type method for assigning transact ion types to the trading partner' s transact ions. The valid methods are def ined below :

0 – Alw ays assign transact ion type " OR" to EDI transact ions.

1 – Use the TRANSACTION CODE sent in direct ly from the EDI transmission. Valid transact ion

codes are " OR" for orders and " RM" for return merchandise.

2 – Use TRANSACTION CODE sent in direct ly from the EDI transmission. Valid transact ion code is " DS" w hich w ill be used for DROP SHIP orders and w ill create drop ship PO's in the system if acf parameters are setup to do so.

• duplicate purchase order validat ion method to use when verifying if a duplicate purchase

order exists for the trading partner' s transact ions:

0 - Perform the duplicate purchase order validat ion based on the validated sold to id. If a duplicate purchase order exists for the sold to id, the validat ion w ill fail.

1 - Perform the duplicate purchase order validat ion 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 validat ion w ill fail. If a duplicate purchase order exists for the sold to id for a dif ferent ship to id, the validat ion w ill not fail. 2 -l* * * * * * * * * * * * * IMPORTANT PLEASE READ BELOW* * * * * * * * * * * * * * * * * * * * * * * * No checking is done for duplicate purchase order numbers. The user must be aw are if this opt ion is chosen that no validat ion of duplicate batches for this Trading Partner is being performed.

• EDI Format.

EDIPOLD-EDI Inbound Record Format Definit ion This opt ion def ines the format to utilize w hen processing the EDI Inbound records for this trading partner. If this f ield is lef t blank, the format for this trading partner w ill be based on the value specif ied in acf opt ion edinfmt. Valid opt ion values are blank,0,1,2. 0 - Def ine transact ions based on the trading partner id and the purchase order number. 1 - Def ine transact ions based on the trading partner id, purchase order number and sold to for the EDI transact ion. 2 - Def ine transact ions based on the trading partner id, purchase order number and for assigning transact ion invoice



number (memoh23_edinh). The follow ing f ields w ill be prompted on screen 2 of the maintenance program. These f ields are ut ilized on the EDI Outbound Invoice ASCII File:

• remit to name.

• price basis code.

• allow ance charge indicator.



• allow ance charge method.

• allow ance charge def init ion. The follow ing values w ill be accepted:

0 - No allow ance charge applicable for trading partner. 1 - Allow ance charge w ill be freight amount. 2 - Allow ance charge w ill be handling amount. 3 - Allow ance charge w ill be insurance amount. 4 - Allow ance charge w ill be miscellaneous 1 amount. 5 - Allow ance charge w ill be miscellaneous 2 amount. 6 - Allow ance charge w ill be miscellaneous 3 amount. 7 - Allow ance charge w ill be miscellaneous 4 amount. 8 - Allow ance charge w ill be surcharge amount.

• special charge def init ion. The follow ing values w ill be accepted

0 - No special charge applicable for trading partner. 1 - Special charge w ill be freight amount. 2 - Special charge w ill be handling amount. 3 - Special charge w ill be insurance amount. 4 - Special charge w ill be miscellaneous 1 amount. 5 - Special charge w ill be miscellaneous 2 amount. 6 - Special charge w ill be miscellaneous 3 amount. 7 - Special charge w ill be miscellaneous 4 amount. 8 - Special charge w ill be surcharge amount.

• total charge def init ion. The follow ing values w ill be accepted:

0 - No total charge applicable for trading partner. 1 - Total charge w ill be based on the gross amount of t ransact ion. 2 - Total charge w ill be based on the net amount of t ransact ion. 3 - Total charge w ill be based on the gross amount - t rade discount. 4 - Total charge w ill be based on the net amount - t rade discount.

• total addit ional charge definit ion. The follow ing values w ill be accepted.

0 - No addit ional 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.



• The program w ill prompt for the invoice print f lag. The follow ing value w ill be accepted:

Y - Yes to print invoices in addit ion to generat ing EDI invoice transact ions. N - No to not print invoices in addit ion to generat ing EDI invoice transact ions.

• 2 character Bill through EDI BILL generat ion f ield

• 2 character Invoice / Order # assignment from EDI Memo f ields

• EMAIL Document Types - control w hat type of ordsend records to create / update to

for an order’ s email address w hen sent via EDI. Map Email Address from EDI Field To Transact ion Email Record. Provide the capability of generat ing or updat ing the order' s email address records based on a f ield recieved through EDI.

• Vendor ID - the FTP ID of the PARTNER you w ill be sending EDI Purchase Orders to.

This ID must be setup in the FTPCFGM program.

• 30 character memo 1 f ield.



• memo 4 f ield, w hich allow s decimal numeric values.

• memo 5 date f ield. B2. Update Menu Options Logic. The program w ill allow select ion based on any of the f ields w ithin the trading partner table. The system w ill provide the opt ions for Update, Next record, Previous record, Help and Exit . When ut ilizing the update opt ion, the system w ill prompt for each non-key f ield sequentially and allow the operator to override them. B2-A. Duplicate Menu Options Logic. The DUPLICATE opt ion is used to duplicate the values in one trading partner record to another trading partner record. User w ill be required to input the Trading Partner ID and Customer ID f ields for the new record being created. B3. Query Menu Options Logic. The program w ill allow select ion based on any of the f ields w ithin the trading partner table. B4. Remove Menu Options Logic. The program w ill allow select ion based on any of the f ields w ithin the trading partner table. When removing the trading partner record, the system w ill also delete any records in the EDI Manual Customer Table (Table name: editpmc; w here partnrid_editpmc = partnrid_editp). B5. View Menu Options Logic. The program w ill allow select ion based on any of the f ields w ithin the trading partner table.



The program w ill allow you to sort by the trading partner id or the customer id w ith a different report format for each sort opt ion and w ill allow the report to be output to screen, printer, or hold f ile. C. Screen Layouts. C1. Maintenance Screen 1.



C2. Maintenance Screen 2.



C3. View Sort Options Screen.



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. cust id_editp 10 CHAR CUSTOMER ID. custprfx_editp 10 CHAR SOLD TO ID PREFIX. custpart_editp 10 CHAR CUSTOMER PART ID LOOKUP. orderf lag_editp 2 CHAR PROCESS ORDERS. shipflag_editp 2 CHAR PROCESS ADVANCED SHIP NOTICES. invf lag_editp 2 CHAR PROCESS INVOICES. statf lag_editp 2 CHAR PROCESS STATUS. cashf lag_editp 2 CHAR < FUTURE USE> chgbkf lag_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. cpart look_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 allow ind_editp 1 CHAR ALLOWANCE CHARGE INDICATOR. allow meth_editp 2 CHAR ALLOWANCE CHARGE METHOD. allow chg_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 Definit ion ucc128fmt_editp 2 CHAR edibilltp_editp 2 CHAR Invoice / Order # assignment from EDI Memo f ields assignmeth_editp 2 CHAR Bill through EDI BILL generat ion f ield



emldoccd_editp 30 CHAR vendorid_editp 30 CHAR svialook_editp 2 CHAR Indexes: Unique index on partnrid_editp. Index on cust id_editp, partnrid_editp.



EDITPVM- EDI TRADING PARTNER VENDOR MAINTENANCE. A. Program Summary. The program w ill 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 def ine vendors, w hich w ill do EDI processing. B. Program Detail. The follow ing describes the logic used to maintain records in the Trading Partner Vendor Master Table for each menu opt ion. The screen display format is def ined in sect ion C. B1. Add Menu Options Logic. - The program w ill prompt for the division id. A valid division must be entered. A drop dow n

w indow opt ion is provided to select the division by the division id or division name. - The program w ill prompt for the department id. A valid department must be entered. A drop

dow n w indow opt ion is provided to select the department by the department id or department name. An entry of the constant " ALL" is permissible in this f ield.

- The program w ill prompt for the branch id. A valid branch must be entered. A drop dow n

w indow opt ion is provided to select the branch by the branch id or branch name. An entry of the constant " ALL" is permissible in this f ield.

- The program w ill prompt for the entry of the corresponding vendor id and w ill validate that the

vendor is a valid vendor and display the vendor name to the right of the vendor id. A drop dow n w indow opt ion is provided to select the vendor by vendor id, vendor name, vendor cross-reference, vendor city and vendor state. The vendor id, along w ith the division id, department id and branch id, is the unique " key" to the record.

- The program w ill prompt for the trading partner id / mailbox number. - The program w ill prompt for the entry of the trading partner name. This f ield w ill default to the

vendor name.

- The program w ill then prompt for the bill to code and id. The bill to code is the ident if ier code for the bill to w hich should be transmitted to the trading partner. The bill to id is the bill to id that the trading partner ident if ies you by.

- The program w ill then prompt for the sold to id. This is the sold to id that the trading partner

ident if ies you by. - The program w ill then prompt for the ship to code and id. The ship to code is the ident if ier code

for the ship to w hich should be transmitted to the trading partner. The ship to id is the ship to id that the trading partner ident if ies you by.

- The program w ill prompt w hether the trading partner processes purchase order (850) EDI

documents. A " Y" or "N" must be entered at this prompt. The f ield w ill default to "N" . - The program w ill then prompt for the PO print f lag. If you w ant the purchase order to be

available to print for the EDI transact ion after the EDI PO ASCII File has been generated, set the f ield to " Y" . If you do not w ant the purchase order to be available to print after the EDI PO ASCII f ile has been generated, set the f ield to " N" . A " Y" or " N" must be entered at this prompt. The f ield w ill default to " Y" . Please note that the purchase order w ill alw ays be



available to print prior to the EDI PO ASCII File generat ion.

- The program w ill then prompt for the output date format.

- An entry of " 1" indicates that all dates sent to the trading partner w ill be output in " YYMMDD" format.

- An entry of " 2" indicates that all dates sent to the trading partner w ill be output in " MMDDYY" format.

The f ield w ill default to " 1" and no other values w ill be accepted. - The program w ill prompt for the output ship to state format.

- An entry of " 1" indicates that the ship to state f ield on the purchase order w ill be truncated to 2 posit ions; only the f irst 2 characters w ill included in the EDI ASCII f ile generated.

- An entry of " 2" indicates that the ent ire 4 character state should be included in the EDI ASCII f ile generated.

The f ield w ill default to " 1" ; no other values w ill be accepted. - The program w ill prompt for the output ship to zip code format.

- An entry of " 1" indicates that the ship to zip code f ield on the purchase order w ill be truncated to 5 posit ions; only the f irst 5 characters w ill be included in the EDI ASCII f ile generated.

- An entry of " 2" indicates that the f ield w ill be truncated to 9 posit ions; only the f irst 9 characters w ill be included in the EDI ASCII f ile generated.

- An entry of " 3" indicates that the full 10 character f ield w ill be included in the EDI ASCII f ile generated.

The f ield w ill default to " 1" ; no other values w ill be accepted. - The program w ill prompt for the PO transact ion code. This is the transact ion set purpose for

the document and w ill default to " 00" . - The program w ill prompt for the PO transact ion type. This is the purchase order type for the

document and w ill default to " NE" . - The program w ill then prompt for the PO unit of measure method. If set to " 0" , the system w ill alw ays 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 w ill use the quantity ordered and the primary unit of measure. If there is an alternate unit of measure quantity, the system w ill 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 w ill alw ays match the trading partners. If the method is set to " 1" , the system w ill alw ays use the default unit of measure entered in the next f ield (trading partner PO default unit of measure). This assumes that you are alw ays ut ilizing a single unit of measure w ith 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 w ill f irst at tempt to convert the unit of measure for the po line (primary or alternate, based on the logic def ined for method zero) to the trading partner unit of measure xref f ile (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 f ield, the system w ill 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 def ined for the trading partner, the system w ill use the unit of measure in the purchase order detail table. - The program w ill then prompt for the PO trading partner default unit of measure. If you are only

dealing in a single unit of measure w ith the trading partner, their unit of measure code may be entered here (i.e. EA).

- The program w ill then prompt for the 2 character PO w eight basis code. This f ield is

information only at this t ime.



- The program w ill then prompt for the 2 character PO volume basis code. This f ield is information only

at this t ime. - The program w ill then prompt for the 2 character EDI Payment Handling Code - The program w ill then prompt for the 3 character Payment Reference Ident if icat ion - The program w ill then prompt for a FTP ID f ield that contains the EDI partner you w ill be

sending the data to. - The program w ill then prompt for the information only memo f ields. Once all the f ields are entered, the system w ill 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 w ill be generated in the EDI Trading Partner Master Table (editp) based on the mapping detailed in sect ion D2. This w ill 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 opt ion (including view) if the customer id (f ield name: cust id_editp) is set to the value " VENDORID" . B2. Update Menu Options Logic. - The program w ill allow select ion based on any of the trading partner vendor f ields on the

screen. - The system w ill provide the opt ions for Update record, Next record, Previous record, Help and

Exit . - When ut ilizing the update opt ion, the system w ill prompt for each f ield sequentially. B3. Query Menu Options Logic. - The program w ill allow select ion based on any of the trading partner vendor f ields on the

screen.

- The system w ill provide the opt ions for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. - The program w ill allow select ion based on any of the trading partner vendor f ields on the

screen. - The system w ill provide the opt ions for Remove record, Next record, Previous record, Help and

Exit . B5. View Menu Options Logic. - The program w ill allow select ion based on any of the trading partner vendor f ields on the

screen.

- The program w ill allow you to sort the report by the trading partner id or the vendor id.



- The program w ill allow the report to be output to the screen, printer or hold f ile. The view screen format is def ined in sect ion C.



C. Screen Layouts. C1. Maintenance Screen.




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. pof lag_editpv 2 CHAR PROCESS PURCHASE ORDERS (850) (Y/N). asnf lag_editpv 2 CHAR PROCESS ADVANCED SHIP NOTICES (856). * FUTURE USE* (DEFAULT TO " N" ). invf lag_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. bt look_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. poprtf lag_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. pow gt_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). payf lag_editpv 2 CHAR EDI PAYMENT HANDLING CODE payreftyp_editpv 3 CHAR EDI REFERENCE IDENTIFICATION TYPE f tpid_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.





EDISVM- EDI TRADING PARTNER SHIP VIA MASTER TABLE MAINT. A. Program Summary. The program w ill 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 transact ions. B. Program Detail. The follow ing describes the logic used to maintain records in the EDI Trading Partner Ship Via Master table for each menu opt ion. The screen display formats are def ined in sect ion C. B1. Add Menu Options Logic. - The program w ill prompt for the follow ing f ields: - t rading partner id and w ill validate that the trading partner is a valid trading partner in the

trading partner table (partnrid_editp). The trading partner name w ill be displayed. The drop dow n w indow opt ion w ill allow select ion by the trading partner id and the trading partner name f ields.

- ship via code and w ill validate that the ship via code is a valid ship via code in the hip via table

(svcode_shipvia). The ship via descript ion (svdesc_shipvia) w ill be displayed. The drop dow n w indow opt ion w ill allow select ion by the ship via code and ship via descript ion.

- 2 character rout ing code. - 4 character SCAC code. - 2 character transportat ion method code. - 35 character carrier name. - 2 character shipping reference qualif ier. - 30 character default t racking number. - 5 characters special services code. - 2 character ship method of payment. - alphanumeric memo 1 f ield. - alphanumeric memo 2 f ield. - alphanumeric memo 3 f ield. - numeric memo 4 f ield. - date memo 5 f ield. Once all the f ields are entered, the system w ill generate a record in the EDI Trading Partner Ship Via Master Table (table name: edisv).



B2. Update Menu Options Logic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Ship

Via Master table. - The system w ill provide the opt ions for Update, Next record, Previous record, Help and Exit . - When ut ilizing the update opt ion, the system w ill prompt for each f ield sequentially. B3. Query Menu Options Logic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Ship

Via Master table. - The system w ill provide the opt ions for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Ship

Via Master table. - The system w ill provide the opt ions for Remove, Next record, Previous record, Help and Exit . B5. View Menu Options Logic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Ship

Via Master table. - The program w ill allow sort opt ions by trading partner id or ship via code. - The program w ill allow the report to be output to the screen, printer, hold f ile, or exit.

The view screen format is def ined in sect ion C. B6. Count Menu OptionsLogic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Ship

Via Master table. - The program w ill 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 opt ion is selected, the system w ill display the trading partner source

duplicat ion entry criteria w indow . The operator may enter select ion criteria for the trading partner id, t rading partner name and customer id for the trading partner being duplicated from. The system w ill select records based on the respective f ields in the trading partner table (partnrid_editp, name_editp, cust id_editp). Applicable records w hich meet the select ion criteria w ill be displayed. The operator w ill have the opt ion of accept ing the current record on the screen, view ing the next record, view ing the previous record or exit ing the duplicat ion process.

- Once a source trading partner has been accepted, the system w ill display the trading partner

dest inat ion duplicat ion w indow . The operator may enter select ion criteria for the trading partner id, t rading partner name and customer id for the trading partner being duplicated to. The system w ill select records based on the respect ive f ields in the trading partner table (partnrid_editp, name_editp, cust id_editp). Applicable records w hich meet the select ion criteria w ill be displayed. The operator w ill have the opt ion of accept ing the current record on the screen, view ing the next record, view ing the previous record or exit ing the duplicate process.



- Once a dest inat ion trading partner has been accepted, the system w ill 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 dest inat ion trading partner EDI Trading Partner Ship Via records.

- The system w ill then delete all EDI Ship Via records for the dest inat ion trading partner. The

system w ill 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 f ields in each dest inat ion w ill match the f ields in the source record w ith the exception of the trading partner id. Once the process is completed, the system w ill display the complet ion message at the bottom of the screen and, once the operator enters a character, the program w ill return to the menu opt ion select ion.







C3. Duplicate Menu Option Window - Source Trading Partner Entry.

C4. Duplicate Menu Option Window - Dest inat ion Trading Partner Entry.



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. rout ing_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. 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). t rackno_edisv rout ing_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



EDITERM- EDI TRADING PARTNER TERMS MASTER TABLE MAINT. A. Program Summary. The program w ill 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 follow ing describes the logic used to maintain records in the EDI Trading Partner Terms Master table for each menu opt ion. The screen display format is def ined in sect ion C. B1. Add Menu Options Logic - The program w ill prompt for the follow ing f ields: - t rading partner id and w ill validate that the trading partner is a valid trading partner in the EDI

Trading Partner Table (partnrid_editp). The trading partner name (name_editp) w ill be displayed. The drop dow n w indow opt ion w ill allow select ion by the trading partner id and trading partner name f ields.

- terms code and w ill validate that the terms code is a valid terms code in the standard terms

table (code_terms). The terms descript ion (desc_terms) w ill be displayed. The drop dow n w indow opt ion w ill allow select ion by the terms code and terms descript ion.

- 2 character terms type code. - 2 character terms date basis code. - alphanumeric memo 1 f ield. - alphanumeric memo 2 f ield. - alphanumeric memo 3 f ield. - numeric memo 4 f ield. - date memo 5 f ield. Once all the f ields are entered, the system w ill generate a record in the EDI Trading Partner Terms Master Table (table name: editerm). B2. Update Menu Options Logic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Terms table. - The system w ill provide the opt ions for Update, Next record, Previous record, Help and Exit . - When ut ilizing the update opt ion, the system w ill prompt for each f ield sequentially. B3. Query Menu Logic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Terms

table. - The system w ill provide the opt ions for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic.



- The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Terms table.

- The system w ill provide the opt ions for Remove, Next record, Previous record, Help and Exit . B5. View Menu Options Logic. - The program w ill allow select ion based on any of the f ields w ithin the EDI Trading Partner Terms

table. - The program w ill allow you to sort the report by the trading partner id or the terms code. - The program w ill allow the report to be output to the screen, printer or hold f ile. The view screen format is def ined in sect ion C. C. Screen Layouts. C1. Maintenance 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: partnrid_editerm. terms_cd_editerm. termtype_editerm. termbase_editerm. memo1_editerm. Detail Line 2: name_editp (based on partnrid_editp = partnrid_editerm). desc_terms (based on code_terms = terms_cd_editerm). memo2_editerm. Detail Line 3: memo3_editerm. Detail Line 4: memo4_editerm. Detail Line 5: memo5_editerm.



EDIUOM- EDI TRADING PARTNER U.O.M. XREF TABLE MAINT. A. Program Summary. The program w ill 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 Validat ion purposes. All trading partner items that w ill have a unit of measure on incoming or outgoing EDI transact ions that differs from the primary or alternate unit of measure in the Item table must be setup here for the validat ion 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 w ill allow add, update, remove, query, view , help and exit opt ions. See Sect ion D for the screen display formats. B1. Add Menu Options Logic - The program w ill prompt for the trading partner id and allow drop dow n w indow to access the trading partner table. Select ion is provided by trading partner id and trading partner name. Once a valid trading partner id is entered or selected, the system w ill display the trading partner name. - The program w ill then prompt for the item id and allow drop dow n w indow access to the item table. Select ion is provided by item id, item cross-reference, item descript ion 1, item descript ion 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 w ill display the item descript ion 1 f ield, unit of measure code, alternate unit of measure code and the alternate to stock conversion factor. - The program w ill then prompt for the trading partner' s unit of measure code. Up to 2 characters of text may be entered. The system w ill do no verif icat ion of the unit of measure entered other than to verify that the f ield is not blank or < NULL> . - The program w ill then prompt for the unit of measure code. The entry w ill be verif ied 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 f ields are entered, the system w ill generate a record in the EDI Trading Partner Unit Of Measure Cross-Reference Table (table name: ediuom). B2. Update Menu Options Logic. - Record select ion w ill be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - The program w ill allow you to modify the item unit of measure code only (since the " key" to the f ile is trading partner, item and partner unit of measure code). The entry w ill be verif ied 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 w ill provide the opt ions for Update, Next record, Previous record, Help and Exit . B3. Query Menu Options Logic.



- Record select ion w ill be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - The system w ill provide the opt ions for Next record, Previous record, Help and Exit . B4. Remove Menu Options Logic. - Record select ion w ill be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - The system w ill provide the opt ions for Remove, Next record, Previous record, Help and Exit . B5. View Menu Options Logic. - Record select ion w ill be provided by trading partner id, item id, partner unit of measure code and item unit of measure code. - Report sort opt ions w ill be provided by trading partner id or item id. - The program w ill prompt w hether you w ant to output to the screen, printer or hold f ile. The view screen format is def ined in sect ion C.







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 Posit ion Field Condit ions 01 01 partnerid_ediuom 01 29 itemid_ediuom 01 68 custuom_ediuom 01 74 uom_ediuom 02 01 name_editpm Based on partner id. 02 29 desc1_item Based on item id. F. Fields To Display On Main Screen: Line Posit ion Field Name 05 22 partnerid_ediuom (validated from editpm). 05 51 name_editp (where partnrid_editp = partnerid_ediuom). 07 22 itemid_ediuom (validated from item). 07 41 desc1_item (w here id_item = itemid_ediuom). 08 41 desc2_item (w here id_item = itemid_ediuom). 10 65 uom_item (w here id_item = itemid_ediuom). 11 65 alteruom_item (w here id_item = itemid_ediuom). 12 65 altstkcnv_item (w here id_item = itemid_ediuom). 15 33 custuom_ediuom. 18 33 uom_ediuom (validated from item w here id_item = itemid_ediuom w here uom_ediuom = uom_item or uom_ediuom = alteruom_item).



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 f iles. ASCII is a standard that allow s ASCII-only plain text f iles (unlike most other f ile types) to be freely interchanged and readable on Unix, Macintosh, Microsoft Window s, DOS, and other systems. These f iles contain only ordinary textual characters w ith essent ially no formatt ing or no control characters. The ASCII f iles 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 transact ion set (850) and moved to the UNIX system w ith a ut ility 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 dif ferences are: (1) Method 1: If you are import ing the 850 tranact ion from a third party product, the ASCII f ile

must be mapped to the Next Generat ion f ile format, the ASCII f ile must be a f ixed length (139 f ields) delineated w ith a pipe sign (| ). Every f ield has to be accounted for, w hich means if no data is available for one of the f ields, you w ould have to put pipe signs together to accommodate for the missing data. The ASCII f ile is imported from a PC to the UNIX System.

An Example of this input f ile w ould be: 6670| 6670| 6670| DROP| | 02082007| 02082007| | | 02082007| T009| | | | | | ROBERT SMITH | 566 Garden

Pkw y.| | | CLIFTON| NJ| US| 07090| | | | | 00| | | | | | | | | | | | | | | | | | | | | | | | | | | | 0001| | | | | | | | | | | | | | | | | | | | | 6670| T009| | | | | ACR2272| | 1| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

6670| 6670| 6670| DROP| | 02082007| 02082007| | | 02082007| T009| | | | | | ROBERT SMITH | 555 Garden Pkw y.| | | CLIFTON| NJ| US| 07090| | | | | 00| | | | | | | | | | | | | | | | | | | | | | | | | | | | 0001| | | | | | | | | | | | | | | | | | | | | 6670| T009| | | | | ACR2273| | 1| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

Note: Each f ield has to be accounted for and must map to the precise f ield that is def inend in the Inbound ASCII f ile layout described at the end of this chapter. (2) Method 2: If you are import ing the transact ion from an ASCII f ile you created, you need to

supply the header (i.e. the name of the column) in the f irst row , follow ed by a pipe sign (| ) or comma (,). The pipe sign or comma must be included betw een each f ield in every row . With this method, you do not need to supply all 139 f ields that are available, but you do need to supply the minimum information required. The ASCII f ile is imported from a PC to the UNIX System. (See below for minimum f ields requirement.)

An Example of this input f ile w ould be: partnrid_edinh| shipto_edinh| cust_po_edinh| podate_edinh| sellitem_edind| orgprice_edind| qtyord_edind 004| 004| PO65998889| 1/23/08| 220022| 24.50| 10 004| 004| PO65998889| 1/23/08| 226630| 16.22| 20 004| 004| PO65998889| 1/23/08| 332200| 12.22| 30 004| 004| PO65998889| 1/23/08| 665522| 11.66| 40 004| 004| PO65998889| 1/23/08| 335522| 23.10| 50



Note: It does not matter w hat order the columns are in but the column names must be in the f irst line and be ident ical to the f ield name in the edihn and edind tables on the Next Generat ion System. (3) Method 3: If you are import ing from an EXCEL spreadsheet, the data on the spreadsheet

that is going to be used as input to this module must have each of the f ields 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 f ield names, w hich are def ined in the edinh and edind tables, of the columns that are to be uploaded must be listed across the f irst row of the spreadsheet (i.e. partnrid_edinh, shipto_edinh, cust_po_edinh, podate_edinh, sellitem_edind, orgprice_edind, qtyord_edind). These f ield names must correspond to the data that is in the column. Once this is def ined, the import funct ion w ill handle the rest. (See below for minimum f ields requirement.)

When loading data from a spreadsheet, if f ield names are supplied, the follow ing checks w ill 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 transact ion date is blank, set it to the system date If the required date is blank set it to the transact ion date + the value in ACF opt ion 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 transact ion 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 allow ing the system to accept the selling price " as is" based on a new selling price override f lag. If the user sets the selling price override f lag to " Y" , the system w ill accept the selling price on the EDI transact ion regardless of w hether it passes or fails the price validat ion rout ine. 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 transact ion. This also gives the user the capability of manually overriding the selling price on the EDI transact ion and using this manual price w hen the sales order is created.

An Example of w hat the EXCEL f ile w ould be: partnrid_edinh shipto_edinh cust_po_edinh podate_edinh sellitem_edind orgprice_edind qtyord_edind 004 004 PO65998889 1/23/08 220022 24.50 10 004 004 PO65998889 1/23/08 226630 16.22 20 004 004 PO65998889 1/23/08 332200 12.22 30 004 004 PO65998889 1/23/08 665522 11.66 40 004 004 PO65998889 1/23/08 335522 23.10 50 Note: It does not matter w hat order the columns are in but the column names must be in the f irst line and be ident ical to the f ield name in the edihn and edind tables on the Next Generat ion System.



(4) Method 4: If you are import ing from an XML f ile, the f ield names are embedded w ithin the

transmitted f ile follow ed by the data. For example, the city below is coded as < city> Cedar Knolls, an item number and quantity w ould come in as; < itemnumber> abc95497 < qty> 100.

An Example of w hat an XML f ile w ould 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> < descript ion> 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> 8002203838< /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> 800-2203838< /phone> < /billto> - < poitems> - < poitem> < linenumber> 1< /linenumber> < iscancelled> 0< /iscancelled> < cancelifbackorder> 0< /cancelifbackorder> < upc> 899178002925< /upc> < itemnumber> abc95497< /itemnumber> < custprice> 21.10< /custprice> < qty> 4< /qty> < /poitem> - < poitem> < linenumber> 10< /linenumber> < iscancelled> 0< /iscancelled> < cancelifbackorder> 0< /cancelifbackorder> < upc> 899178002933< /upc> < itemnumber> bhj23742< /itemnumber> < custprice> 5.27< /custprice> < qty> 12< /qty> < /poitem> - < poitem> < linenumber> 11< /linenumber> < iscancelled> 0< /iscancelled> < cancelifbackorder> 0< /cancelifbackorder> < upc> 899178002876< /upc> < itemnumber> llk2964< /itemnumber> < custprice> 101.32< /custprice> < qty> 7< /qty> < /poitem> < /poitems> < /purchaseorder> < /dbiresponse> The minimum required f ields 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 w ith the Sold -to ID, "SAME" w ill be assigned.

Customer PO Number

(cust_po_edinh) Required

PO Date (podate_edinh) Required (ACF Option EDINDAY checks if date is over opt ion value days from system date. If older the program w ill 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 opt ion OE022 to the system date.

Ship Via Code (memo20_edinh) Required if blank the program w ill 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 appropriate cross references have been set up on the Next Generat ion system.

Customer Price (orgprice_edind) Required (w ith or w ithout $ character) Except if opt ion 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 addit ional 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 follow ing describes the logic used to process inbound transact ions (i.e. EDI Purchase Order (850), EXCEL™ and other ASCII f iles) for each menu opt ion. The Upload/Import ASCII/Excel File opt ion provides the ability of uploading an ASCII f ile, generated in one of the standard ASCII f ile formats, into the EDI subsystem.



Determine w hat type of ASCII input f ile you are w orking w ith, i.e. the 850 ASCII File format, or the EXCEL f ile. If you are import ing an Excel f ile using method 3 above, use the From PC box. If you are import ing the ASCII f ile that w as imported to the Unix Server, use the From Main System box.

STEP 1 If you are import ing an Excel f ile using Method 3 above, use the From PC box to

choose w here the input f ile is located on the PC by select ing the folder Icon then proceed to STEP 4.

STEP 2 If you are import ing the ASCII f ile in an 850 format or the shortened ASCII f ile, use the From Main System box to enter a valid start ing directory w here ASCII f iles on the UNIX server are located and w here the log f iles w ill be output to (defaults to the value in the ACF " EDINDIR" opt ion). Within this directory, 2 subdirectories, 1 named " data" and 1 named "pgm" must exist . The ASCII f ile to be uploaded must exist in this " data" directory before it can be uploaded. If these directories do not exist , the system w ill provide a w arning message and return to the directory prompt. The ' pgm' subdirectory must contain scripts ut ilized by the EDI upload.

STEP 3 ASCII data f ile name to upload (default to the value in the ACF " EDINDAT" opt ion). This f ile must exist in the directory entered by the operator.

STEP 4 Printer to print log f iles (default to the value in the ACF " EDINPRT" opt ion). The program w ill validate that the printer specif ied is a valid printer. Any errors which occur during the upload w ill be printed. An example of this type of error w ould be if the number of f ields uploaded does not match the standard ASCII f ile def init ion.

STEP 5 The system w ill display the batch number w hich w ill be assigned to the records uploaded from the ACF " EDINSEQ" opt ion. This value w ill also be the value inserted before the ASCII f ile name w hen the ASCII f ile is renamed once the upload is complete. The ACF " EDINSEQ" batch number value w ill be incremented by 1 and updated to the ACF f ile. The value w ill be a 4 digit numeric w hich w ill assign numbers from 0001 to 9999.

STEP 6 Enter " PROCEED" to continue or select Exit " to exit . Once the process is completed, the system w ill create a directory (if one is not already present) in the " data" directory of the start ing directory specif ied. The directory w ill be named based on the current system date in the format " YYMMDD" . Within this directory w ill be the renamed ASCII f ile in the format " BBBBNNNNNNNN" w here BBBB represents the batch number and NNNNNNNN represents the original ASCII f ile name. A f ile w ith the same name w ith a " .h" suff ix and a f ile w ith the same name w ith a " .d" suff ix w ill also be created. These w ill be the upload error logs for the header and detail tables. If the size of the logs are 0, no upload errors occurred.



EDI Data Directory Maintenance. If you are using Method 1 or Method 2 for import ing ASCII f iles to the UNIX server, (EDI purchase order transaction set (850) or the shortened ASCII f ile version), the ASCII f ile directories residing on the UNIX box should be cleared on a regular basis. To remove the ASCII f iles, use the UNIX recursive remove command. This command removes the directory or directories specif ied and all f iles and directories w ithin them. USE EXTREME CAUTION WITH THE COMMANDS. - Enter the UNIX operat ing system.

OSM < RETURN> - Change the directory to the directory containing the data f iles. 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 w rong directory is chosen, f iles required by the system could be deleted by mistake !

pw d < RETURN> - List the contents of the directory, if desired.

ls –al -Remove the directory or directories desired.

rm -r < f ilename>

For example, you may execute the follow ing command to remove all directories and contents for September, 1998:

rm -r 9809*

USE EXTREME CAUTION WITH THE COMMAND. If executed w ithout a f ilename, the command w ill remove all f iles w ithin the specif ied directory. If executed w ith an incorrect f ile name, incorrect f iles may be deleted from the system. - Within the EDI inbound directory, 2 subdirectories are required: data and pgm. The data directory w ill contain the ASCII f iles as previously described. The pgm directory contains the follow ing command f iles w hich 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.

B2 - VALIDATION OPTION The validat ion opt ion provides the ability of validat ing f ields from the incoming transact ion and determining the f ield values for standard Next Generat ion™ f ields that w ill are required to generate the standard order tables.

When operators choose the Validate Upload Data opt ion, they w ill be prompted to enter select ion criteria for the follow ing f ields:

- Load Date - The date the ASCII f ile w as uploaded to the system. - Batch Number - The EDI batch number assigned to the transact ions. - Process Status - The status code of the transact ions. - 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 w ill then validate the transact ions w hich meet the criteria entered. B2-A. Header Validat ions. The follow ing validat ions are performed for summary data associated w ith each transact ion: Customer Sold To Validat ion. The trading partner id table w ill be accessed based on the trading partner / mailbox id on the transact ion. If a record is not found, the system w ill set the status f lag = " HC" (Header: Invalid Trading Partner). If a record is found but the order f lag is not set to " Y" for the trading partner, the system w ill set the status f lag = " HD" (Header: Invalid Partner Transact ion). If a record is found and the trading partner sold to validat ion method is set to " 1" , the system w ill use the sold to id from the EDI transact ion as the sold to customer id. Otherw ise, if the sold to validat ion method is set to " 0" , the system w ill determine w hether there is a valued customer pref ix def ined for the trading partner. If this is the case, the system w ill access the standard customer table based on a customer ID of the prefix plus the bill to ID f ield from the incoming EDI Transact ion. For example, if the pref ix is set to " ABCD" and the incoming bill to ID is " 0123" , the system w ill access the customer table based on an id of " ABCD0123" . If a record is



not found, the system w ill set the status f lag = " H2" (Header: Invalid Sold To). If the customer pref ix is not valued, the sold to ID w ill be set to the customer ID def ined in the trading partner table. Otherw ise, if the sold to validat ion method for the trading partner is set to " 2" , the system w ill determine the sold to id based on the trading partner customer pref ix and the ship to id. The system w ill select the applicable trading partner record (Table name: editp) based on the trading partner id defined in the EDI transact ion (Table name: edinh; Field name: partnrid_editp = partnrid_edinh). The system w ill select the customer pref ix def ined for the trading partner (Field name: custprfx_editp). The system w ill access the Customer Master Table and Ship To Table based on the customer id (w here the customer id (Field name: id_customer) matches the trading partner customer pref ix (Field name: custprfx_editp) for the length of the trading partner pref ix) and the ship to id (w here the ship to id (Field name: id_shipto) matches the ship to id def ined on the EDI transact ion (Field name: shipto_edinh)). If no records are found or mult iple records are found, the sold to validat ion w ill fail. If one record is found, the system w ill set the validated customer id (Field name: cust id_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 follow ing: • This requires that only ONE customer pref ix is def ined for ALL the customer sold to records

for a single trading partner and that NO other customers have a sold to id w ith the trading partner' s pref ix.

• This requires that a ship to id is unique for all the customers setup for a trading partner id.

The system w ill not validate successfully if the same ship to id is def ined for mult iple customers of the same trading partner.

In all cases, once the customer table is accessed, the branch w ill be set to the branch def ined in the customer table. Customer Ship To Validat ion. If the ship to validat ion method def ined for the trading partner is " 1" the follow ing method w ill be used: If the bslook flag is set to " BS" on the incoming transact ion, the system w ill 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 w ill set the validated ship to ID to the ship to ID in the ship to table. If a record does not exist , the system w ill set the status f lag to " H3" (Header: Invalid Ship To). If the bslook flag is not set to " BS" , the system w ill validate that a record exists in the ship to table w ith a ship to id of " X" . If a record is found, the system w ill set the ship to ID to " X" . If a record is not found, the system w ill set the status f lag to " H3" (Header: Invalid Ship To). By def ining one ship to record w ith an id of " X" in the ship to table, the system can use this ship to w ith the ship to information on the EDI transact ion rather than having to setup mult iple ship to records. If the ship to validat ion method def ined for the trading partner is " 2" the follow ing method w ill be used: If the EDI Bill to ID is equal to the EDI Ship to ID, the validated ship to ID w ill be set to " SAME" .Otherw ise, the system w ill 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 w ill set the validated ship to ID to the ship to ID in the ship to table. If a record does not exist, the system w ill set the status f lag to " H3" (Header: Invalid Ship To). If the branch id in the ship to record selected is valued, the system w ill set the branch id on the EDI transact ion to the branch id of the ship to record, thereby overriding the customer record. Transact ion Type Validat ion. If the transact ion type is not set to " 00" for regular orders or " W3" for WEB orders (see D' Artagnan system), the status f lag w ill be set to " H1" (Header: Invalid Transact ion Type). Transact ion Type Codes. If the trading partner is def ined to assign the transact ion type from the EDI transact ion, the system w ill verify that the transact ion code is set to " OR" or " RM" or " DS" (if t ranstype on EDITPM table is a " 2" , then " DS" is a valid transact ion type on the input PO f ile). If it is not, the status code w ill be set to " HF" (Header: Invalid transact ion Code) Blank Purchase Order Number Validat ion. If the purchase order number is not valued, the status code w ill be set to " H7" (Header: Blank Cust PO Number). Duplicate Purchase Order Validat ion. If the purchase order duplicate override f lag is set to " N" , the follow ing validat ions w ill occur if the duplicate PO check ACF opt ion (oe011) is set to "Y" . If another record exists w ith the same customer id and the same purchase order number in the EDI header table, the status code w ill be set to " H4" (Header: Duplicate Cust PO in EDI). If a record exists in the open order tables w ith the same customer id and the same purchase order number, the status code w ill be set to " H5" (Header: Duplicate Cust PO in Order). The validat ion w ill be limited to normal order transact ions (OR, DS, QO, FO, SO, SI, BL). If a record exists in the sales analysis header table w ith the same customer sold to id and the same purchase order number, the status code w ill be set to " H6" (Header: Duplicate Cust PO in SA File). The system w ill only select records w ith a transact ion date greater than or equal to the current system date less the number of days back to check def ined in the ACF " edinpody" opt ion. When performing the duplicate purchase order validat ion, if the trading partner' s duplicate purchase order validat ion method is set to " 1" , the system w ill perform the duplicate purchase order validat ion based on the ship to id as w ell as the sold to id and the purchase order number. The follow ing describes the validat ions that w ill occur w hen the duplicate purchase order ship to validat ion method is ut ilized: When validat ing w hether the customer purchase order transmitted from EDI already exists in the EDI Table (Table name: edinh), select based on the ship to id as w ell as the sold to id, purchase order number and a dif ferent assigned serial number. Descript ion Operat ion EDI Field Sold To ID = cust id_edinh Customer PO # = cust_po_edinh Ship To ID = shipid_edinh Serial Number < > serial_edinh



When validat ing w hether 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 w ell as the sold to id, purchase order number and applicable transact ion types def ined. Descript ion Ordera Field Name Orderb Field Name EDI Field Sold To ID soldto_ordera cust id_edinh Customer PO # ust_po_orderb cust_po_edinh Ship To ID shipto_ordera shipid_edinh Order Number ordnum_ordera ordnum_orderb (For Join) Transact ion Types t ranstype_orderb OR, DS, QO,

FO, SO, SI, BL.

When validat ing w hether 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 w ell as the sold to id and purchase order number. Also, validate the transact ion date based on the new ACF opt ion (edinpody), def ined in sect ion E, w hich w ill indicate the number of days back to select Sales Analysis History records. Descript ion SAHDR Field Name EDI Field Sold To ID soldto_ia_sahdr cust id_edinh Customer PO # cust_po_ib_sahdr cust_po_edinh Ship To ID shipto_ia_sahdr shipid_edinh Transact ion Date trandte_ib_sahdr (* ) (* ) TODAY - # of days def ined in the new ACF ' edinpody' opt ion. Note that

if the number of days is set to ' 99999' , the system w ill ignore the transact ion date w hen doing the validat ion. If the number of days is set to " 0" , no validat ion against the sales history w ill occur.

If the trading partner' s duplicate purchase order validat ion method is set to " 0" , the system w ill perform the validat ion incorporat ing the number of days defined in the ' edinpody' opt ion. Note that the duplicate purchase order validat ion only w ill occur if the contents of the exist ing ACF opt ion for the purchase order check for duplicate P.O. number (oe011) is set to "Y" . Duplicate Order Number If the system is def ined to assign the order number from the purchase order number (based on the edipdoam opt ion being set to " 2" ), the system w ill verify that no orders or sales analysis records have an order number that matches the f irst 10 characters of the customer purchase order number. If a duplicate order exists, the system w ill set the status code to " HG" (Header: Order number exist (from PO#)) Purchase Order Date Range Validat ion. If the purchase order date range override f lag 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" opt ion, the status code w ill be set to " HB" (Header: P/O Date Exceeded). Ship Via Code Validat ion. The f irst 4 characters of the header memo 20 f ield (memoh20_edinh) may be used to load the ship via code from the ASCII f ile. If the f irst 4 characters are not valued, the ship via validat ion w ill not be performed and the ship via of the order w ill be the default ship via from the customer or ship to record.



If the f irst 4 characters are valued, the system w ill 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 validat ion w ill be passed and this ship via code w ill be loaded into the transaction w hen the order is created. If a valid record is not found, the system w ill set the status code to " H8" (Header: Invalid Shipping Method). B2-B. Detail Validat ions . The follow ing validat ions are performed for detail line item data associated w ith each transact ion: Detail Record Validat ion If no detail record is found for the purchase order, the transact ion status w ill be set to " D0" (DETAIL - NO DETAIL RECORD FOUND). Item Validat ion. Item ID validations occur based on the 2 customer part id f ields, UPC f ields and item id f ields based on the methods def ined in the trading partner record. If the trading partner lookup f ield is set to zero, that validat ion w ill not occur. Once a lookup is successful, the system w ill set the validated item id f ield. If any lookup fails, the system w ill then perform the next lookup. The system w ill f irst attempt to validate the item id f ield: - If the trading partner item lookup f ield is set to " 0" , the system w ill not perform any validat ion on the item id f ield. -If the trading partner item lookup f ield is set to " 1" , the system w ill access the item table based on the item id f ield being equal to the item id in the detail record. If a record is found, the system w ill set the validated item id to the item id found. - If the trading partner item lookup f ield is set to " 2" , the system w ill 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 w ill set the validated item to the item id found. - If the trading partner item lookup f ield is set to " 3" , the system w ill access the customer part table based on the customer part id lookup f ield in the trading partner record and the item id f ield in the detail record. If the customer part id lookup f ield is < NULL> , the system w ill use the sold to customer ID. If ONE record is found, the system w ill 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 f ield is set to " 4" , the system w ill access the Contract Pricing Table (Table name: conprice) based on the validated sold to id (Field name: cust id_edinh) matching the contract ' s customer id (Field name: cust id_conprice), the item id in the detail record (Field name: sellitem_edind) matching the contract ' s customer item id (Field name: cust item_conprice), the contract ' s effect ive date (Field name: effdte_conprice) being less than or equal to the transact ion date on the EDI transact ion (Field name: t ransdate_edinh) and the contract ' s expirat ion date (Field name: expdte_conprice) being greater than or equal to the transact ion date on the EDI transact ion (Field name: transdate_edinh). If no records are found, the validation w ill fail and the system w ill proceed w ith any addit ional item validations that have not yet been performed. If one or more contract records are selected, the system w ill 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 f irst contract record selected in expirat ion date, contract price sequence (Field names: expdte_conprice, conprice_conprice). - If the trading partner item lookup f ield is set to ' 5" , the system w ill access the Item Interchange Table maintained by the UPCLOAD program (Table name: cixref; rectype_cixref = " 2" ). The



system w ill select the item id f ield (Field name: ouritemid_cixref) w here the item id in the detail record (Field name: sellitem_edind) matches the UPC/Interchange id (Field name: interchgid_cixref). Note that if mult iple records are def ined w ith the same UPC/Interhchange id, the system w ill not be able to validate the record. The system w ill then attempt to validate the UPC code f ield: - If the trading partner UPC lookup f ield is set to " 1" , the system w ill 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 w ill set the validated item to the item id found. - If the trading partner UPC lookup f ield is set to " 2" , the system w ill access the item table based on the item cross-reference f ield being equal to the UPC code on the detail record. If ONE record is found, the system w ill set the validated item id to the item id found. - If the trading partner UPC lookup f ield is set to " 3" , the system w ill access the customer part table based on the customer part id lookup f ield in the trading partner record and the UPC code in the detail record. If the customer part id lookup f ield is < NULL> , the system w ill use the sold to customer ID. If ONE record is found, the system w ill validate that the item exists in the item table and set the validated item to the item id found. - If the trading partner UPC lookup f ield is set to " 4" , the system w ill access the Contract Pricing Table (Table name: conprice) based on the validated sold to id (Field name: cust id_edinh) matching the contract ' s customer id (Field name: cust id_conprice), the UPC code in the detail record (Field name: upc_edind) matching the contract ' s customer item id (Field name: cust item_conprice), the contract' s effect ive date (Field name: effdte_conprice) being less than or equal to the transact ion date on the EDI transact ion (Field name: t ransdate_edinh) and the contract ' s expirat ion date (Field name: expdte_conprice) being greater than or equal to the transact ion date on the EDI transact ion (Field name: t ransdate_edinh). If no records are found, the validat ion w ill fail and the system w ill proceed w ith any addit ional item validat ions that have not yet been performed. If one or more contract records are selected, the system w ill 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 f irst contract record selected in expirat ion date, contract price sequence (Field names: expdte_conprice, conprice_conprice). - If the trading partner UPC lookup f ield is set to ' 5" , the system w ill access the Item Interchange Table maintained by the UPCLOAD program (Table name: cixref; rectype_cixref = " 2" ). The system w ill select the item id f ield (Field name: ouritemid_cixref) w here the UPC code in the detail record (Field name: upc_edind) matches the UPC/Interchange id (Field name: interchgid_cixref). Note that if mult iple records are def ined w ith the same UPC/Interhchange id, the system w ill not be able to validate the record. The system w ill then determine the method to ut ilize the Customer Part ID for the trading partner: - If the trading partner customer part method f ield is set to " 1" , the system w ill use the customer part id 1 f ield. - If the trading partner customer part method f ield is set to " 2" , the system w ill use the customer part id 1 plus the customer part id 2 f ields separated by a dash. (Note that if the customer part id 2 f ield is not valued, only the customer part id 1 f ield w ill be used w ithout a dash). - If the trading partner customer part method f ield is set to " 3" , the system w ill use the combined customer part id 1 and customer part id 2 f ields w ith no dash separator.



The system w ill then attempt to validate the Customer Part ID f ield: - If the trading partner customer part lookup f ield is set to " 1" , the system w ill access the item table based on the item id f ield in the item record being equal to the customer part id used from the detail record. If a record is found, the system w ill set the validated item to the item id found. - If the trading partner customer part lookup f ield is set to " 2" , the system w ill access the item table based on the item cross-reference f ield in the item record being equal to the customer part id used from the detail record. If ONE record is found, the system w ill set the validated item to the item id found. - If the trading partner customer part lookup f ield is set to " 3" the system w ill access the customer part table based on the Customer Part ID Lookup f ield in the trading partner record and the customer part id used from the detail record. If the Customer Part ID Lookup f ield is not valued, the system w ill use the validated Sold To ID. If ONE record is found, the system w ill 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 f ield is set to " 4" , the system w ill access the Contract Pricing Table (Table name: conprice) based on the validated sold to id (Field name: cust id_edinh) matching the contract ' s customer id (Field name: cust id_conprice), the customer part id used from the detail record matching the contract ' s customer item id (Field name: cust item_conprice), the contract' s effect ive date (Field name: effdte_conprice) being less than or equal to the transact ion date on the EDI transact ion (Field name: t ransdate_edinh) and the contract ' s expirat ion date (Field name: expdte_conprice) being greater than or equal to the transact ion date on the EDI transact ion (Field name: t ransdate_edinh). If no records are found, the validat ion w ill fail and the system w ill proceed w ith any addit ional item validat ions that have not yet been performed. If one or more contract records are selected, the system w ill 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 f irst contract record selected in expirat ion date, contract price sequence (Field names: expdte_conprice, conprice_conprice). - If the trading partner customer part lookup f ield is set to ' 5" , the system w ill access the Item Interchange Table maintained by the UPCLOAD program (Table name: cixref; rectype_cixref = " 2" ). The system w ill select the item id f ield (Field name: ouritemid_cixref) w here the customer part id used from the detail record matches the UPC/Interchange id (Field name: interchgid_cixref). Note that if mult iple records are def ined w ith the same UPC/Interhchange id, the system w ill not be able to validate the record. Once the item id is found, the system w ill set the validated item id, item descript ion, alternate conversion factor, unit of measure, alternate unit of measure, pricing unit of measure and pricing unit of measure conversion factor f ields in the EDI detail record. The system w ill also access the customer part id cross-reference table based on the trading partner Customer Part ID Lookup f ield and the validated item id. If the Customer Part ID Lookup f ield is not valued, the system w ill use the validated Sold To ID. The validated customer part number f ield w ill be set w hen a record is found. If all the item validat ions fail, the transact ion status f lag w ill be set to " D1" (DETAIL: INVALID ITEM ID). Unit of Measure Validat ion. If the ACF opt ion to perform unit of measure validation (ediuomv) is set to " 2" , the system w ill



validate the unit of measure code sent on EDI transact ions 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 w ill f irst access the EDI Trading Partner Unit of Measure Cross-Reference Table (ediuom) based on the follow ing criteria:

- partnerid_ediuom = partnrid_edinh. - itemid_ediuom = itemid_edind. - custuom_ediuom = uom_edind.

If a record is found, the system w ill 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 w ill leave the record as it is and the line item unit of measure w ill pass validat ion. If it does not match, the system w ill 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 w ill 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 w ill pass validat ion. If no record is found in the cross-reference table or the unit of measure is not valid, the system w ill access the item table. The system w ill 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 w ill leave the record as it is and the line item unit of measure w ill pass validat ion. If it does not match, the system w ill 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 w ill set the alternate quantity ordered (altqtyord_edind) to the quantity ordered (qtyord_edind) and leave the quantity ordered as is. This w ill 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 w ill pass validat ion. If the unit of measure validat ion fails, the error status w ill be set to " D3" and the corresponding error message w ill be " DETAIL: INVALID UNIT OF MEASURE" . Selling Price Validat ion. If the trading partner is def ined to validate selling prices, the system w ill calculate the selling price for the sold to customer, item id, quant ity 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 w ill set the status f lag 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 w ill use the selling price calculated by the system. Logic behind this is if the Trading Partner sends in a zero price, they are accept ing the price you calculated. When calculat ing and determining the selling price of the order, if the alternate quantity ordered is set to zero, the system w ill cont inue 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 w ill calculate the selling price by calculat ing the quantity ordered and alternate quantity ordered based on the alternate to stock conversion factor for the item. This condit ion w ould occur w hen 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 validat ion, the selling price on the EDI transact ion



w ill be ignored. The system w ill use the standard pricing mechanisms to calculate the selling price on the order. If the trading partner is def ined 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 w ill do this and also set the detail line as a manually priced line. If the contract pricing validat ion port ion of the pricing validat ion logic fails and the validate selling price f ield in the trading partner record (Field name: pricemeth_editp) is set to " C" (indicat ing that the system w ill only validate the price against the customer' s valid contracts), the record w ill fail the pricing validat ion. The status f lag on the record (Field name: status_edind) w ill be set to " D2" , indicat ing that the record has an invalid selling price. The system w ill NOT proceed w ith 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 w ill access the customer table by the retail price id. If the customer exists, the system w ill calculate the selling price for the retail price customer for the item, quantity and transact ion date and store this in the retail price f ield. If the retail price id is not valued, the system w ill leave the retail price as it w as on the inbound transact ion. B2-C. Summary Validat ions. The follow ing validat ions are performed once the detail line item validations have been performed for the transact ion: Order Maximum Value Validat ion. The system w ill calculate the net extension (netext_edind) on each detail line, based on the quantity ordered (qtyord_edind) and the selling price (sellprice_edind). When calculat ing the line item net extension, if the alternate quantity ordered is set to zero, the system w ill 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 w ill 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 condit ion w ould occur if the unit of measure validat ion is performed and the unit of measure on the EDI transact ion corresponds to the item alternate unit of measure. The system w ill 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 f lag is not set to " Y" and the maximum normal value def ined in the trading partner record is not zero, the system w ill 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 w ill set the status f lag to " H9" (Header: Netext is Over Normal Value).



B3 - MAINTENANCE OPTION The maintenance funct ion w ill provide the capability w ill be provided to update, remove, query and view EDI transact ion records.

The maintenance funct ion w ill provide the capability w ill be provided to update, remove, query and view EDI header transact ion records. When the operator selects the Maintain Upload Data opt ion on the EDI Processing Menu, the operator w ill be prompted for the menu opt ion to perform. The system w ill allow you to prompt for search criteria on the maintainable detail f ields on the f irst screen (validation f ields screen).



Header Maintenance Screen 2.

Header Maintenance Screen 3.

Once the operator selects records, the follow ing opt ions are provided: - U - Update - Access and maintain f ields on the f irst header screen. - V - Validate - Perform all validat ion funct ions on the transact ion. - C - Convert - Convert a successfully validated transact ion to order. - D - Detail - Access the Detail Line Records for the transact ion. - F - First Record - Access the f irst 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. - 1 - Screen 1 - Access screen 1 of the transact ion (validat ion f ields). - 2 - Screen 2 - Access screen 2 of the transact ion (ship to address). - 3 - Screen 3 - Access screen 3 of the transact ion (f low through fields). - H - Help - Access help. - E - Exit - Return to menu.



When performing an update, the follow ing w ill occur on the f irst header screen: - The operator w ill be prompted for the partner id. The system w ill validate that the trading

partner ID is valid and that the trading partner is defined for order transact ions. - The operator w ill be prompted for bill to id. If the trading partner pref ix is set, this w ill be used

in conjunct ion w ith the pref ix to determine the sold to customer ID. - The operator w ill be prompted for sold to id. - The operator w ill be prompted for the sold to override f lag. If the operator w ants to override

the validat ion f ields and manually enter the Sold to customer ID, enter a " Y" . - The operator w ill be prompted for the valid sold to id f ield. If a valid customer is found, the

system w ill display the valid sold to id (" OUR SOLD TO" ). Otherw ise, the customer validat ion logic w ill be used to determine the sold to id. If a valid customer is found, the system w ill display the valid customer id (" OUR SOLD TO" ).

- If a valid customer is not found, the program w ill return to the trading partner id prompt and

allow you to change the values in the customer validat ion f ields. - The operator w ill be prompted for the bs ship to lookup designator. - The operator w ill be prompted for the ship to id. Based on the trading partner ship to method,

this w ill be used to validate the ship to id. - The operator w ill be prompted for the ship to name. - The operator w ill be prompted for the ship to override f lag. If the operator w ants to override

the validat ion f ields and manually enter the Ship to ID, enter a " Y" . - The operator w ill be prompted for the valid ship to id f ield. If a valid ship to is found, the

system w ill display the valid ship to id (" OUR SHIP TO" ). Otherw ise, the ship to validat ion logic w ill be used to determine the ship to id. If a valid ship to is found, the system w ill display the valid ship to id (" OUR SHIP TO" ).

- If a valid ship to is not found, the program w ill return to the bs ship to lookup designator

prompt and allow you to change the values in the ship to validat ion f ields. - The branch id w ill default to the branch id in the customer record. If the ship to record contains

a valid branch id, this w ill override the branch id. The operator w ill be prompted for a valid branch.

- The operator w ill be prompted for a valid transact ion type (" 00" ). - The operator w ill be prompted for the transact ion code. - The operator w ill be prompted for the duplicate p/o override f lag and the customer p/o number.

The duplicate p/o validat ion logic w ill be used to determine if the p/o is a duplicate. If it is a duplicate and the duplicate p/o override f lag is not set to "Y" , the program w ill reprompt for duplicate p/o override f lag and the customer purchase order number.

- The operator w ill be prompted for the p/o date override f lag and the purchase order date. The



p/o date range validat ion logic w ill be used to determine if the p/o is outside the range. If it is out of range and the p/o date override f lag is not set to " Y" , the program w ill reprompt for the p/o date override f lag and the p/o date.

- The operator w ill be prompted for the transact ion date. - The operator w ill be prompted for the valid ship via code for the transact ion. If the f ield is

valued, the system w ill validate that a ship via record exists for the code. - The operator w ill be prompted for the required date and the cancel date. - The operator w ill be prompted for the over normal value override f lag. If the operator sets the

f lag to " Y" , the system w ill not compare the total value of the transact ion to the maximum normal value setup in the trading partner record.

- The system w ill display the total order value (net extension) based on the total extension of the

validated detail line items and, if the normal value override f lag is not set to "Y" , validate the order value.

- The operator w ill be prompted for the ship date. - If the operator selects " 2" at the opt ions prompt, the second header screen can be accessed. On the second screen (ship to f ields), the validated sold to id, validated ship to id, t rading partner id, customer purchase order number and ship to name w ill be displayed. The operator w ill 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 attent ion and ship to country. - If the operator selects " 3" at the opt ions prompt, the third header screen can be accessed. On the third screen (f low through f ields), the validated sold to id, validated ship to id, t rading partner id, customer purchase order number and ship to name w ill be displayed. The operator w ill be able to access the mark for, reference number, department, media event code, contract number, customer p/o batch number, terms code, rout ing, scac code, the memo 1 through 5 f ields and the remarks. Query Menu Options Logic. The program w ill allow select ion based on any of the f ields on header screen 1 and provides opt ions 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 w ill allow select ion based on any of the f ields on header screen 1 and provides opt ions for Remove record, First record, Last record, Next record, Previous record, Screen 2 and Screen 3. If the remove record opt ion is selected, the system w ill prompt the operator to verify that the transact ion should be removed. Mass Remove based on Batch #. Allow s user to remove an ent ire batch. This w ill bypass records w here the sales order w as already generated. View Menu Options Logic. The program w ill allow select ion based on any of the f ields on header screen 1. The follow ing sort opt ions 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 w ill prompt you to def ine the number of blank lines to appear betw een details. The program w ill allow the report to be output to the screen, printer or hold f ile. B3-B. Detail Records Maintenance Logic: The maintenance funct ion w ill provide the capability w ill be provided to add, update, remove and query detail lines. Detail Maintenance Screen 1.

Detail Maintenance Screen 2.

When operators select the detail opt ion, the system w ill 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 w ill allow you to prompt for search criteria on the maintainable detail f ields on the f irst screen. When performing an add or update, the follow ing w ill occur: - The operator w ill be prompted for the customer' s purchase order line number. - The operator w ill be prompted for customer part id 1. - The operator w ill be prompted for customer part id 2. - The operator w ill be prompted for the UPC code. - The operator w ill be prompted for the item id. - The operator w ill be prompted for the item descript ion. - The operator w ill be prompted for the item id override f lag. If the operator w ants to manually

enter the item id, a " Y" should be entered here. - The operator w ill be prompted for the valid item id f ield. If a valid item id is found, the system

w ill display the valid item id and item descript ion ("OUR ITEM ID" ). Otherw ise, the item validat ion logic w ill be used to determine the item id. If a valid item id is found, the system w ill display the valid item id and item descript ion (" OUR ITEM ID" ). - If a valid item is not found, the program w ill return to the customer part id 1 prompt and allow

you to access the item id validat ion f ields. - The operator w ill be prompted for the quantity ordered and unit of measure. If the unit of

measure validat ion opt ion is set, the system w ill 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 f ields, the system w ill display the message " Invalid Unit Of Measure" and return to the unit of measure prompt.

- The operator w ill display the converted quantity if the UPC code on the edi input f ile is found in

the UPCLOAD program table (cixref). The program w ill mult iply the quantity ordered t imes the conversion factor from the UPCLOAD program table and show the converted quantity on the screen. The converted quantity and the conversion factor w ill be stored in the edind table and w hen the order is created, the converted quantity w ill become the quantity order in the orddet record.

- The standard price calculat ion w ill be performed for the customer, item and quantity. The

standard selling price (" OUR SELLING PRICE" ) and pricing unit of measure w ill be displayed. The net extension w ill be calculated and displayed, based on the standard selling price and the quantity ordered.

- The operator w ill be prompted for the selling price. - If the trading partner is def ined to validate selling prices and the selling price is non-zero and

does not agree w ith the standard selling price, the system w ill display the message " Invalid



Selling Price" and return to the quantity ordered prompt and allow you to enter the selling price validat ion f ields.

- The operator w ill be prompted for the freight, special instruct ions 1, and special instruct ions 2. - On screen 2, the operator can access the delivery note 1, delivery note 2 and memo 1 through

5 f ields. Query Menu Options Logic. The program w ill allow select ion based on any of the f ields on detail screen 1 and provides opt ions for First record, Last record, Next record, Previous record and Screen 2. Remove Menu Options Logic. The program w ill allow select ion based on any of the f ields on detail screen 1 and provides opt ions for Remove record, First record, Last record, Next record, Previous record and Screen 2. If the remove record opt ion is selected, the system w ill prompt the operator to verify that the transact ion detail record should be removed.

B4 - ORDER CREATION OPTION. This opt ion w ill generate orders for transact ions that have been successfully validated. When operators select the order creat ion menu opt ion, they w ill be prompted to enter select ion criteria for the follow ing f ields: - Load Date - The date the ASCII f ile w as uploaded to the system. - Batch Number - The EDI batch number assigned to the transact ions. - 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. - Transact ion Date - The transact ion date to process. - Customer P/O Date - The purchase order date to process. - Purchase Order Number - The purchase order number to process. The system w ill then create orders in the standard order f iles for all successfully validated transact ions that meet the select ion criteria. The system w ill generate records in the temporary order tables based on the mapping. The ordtmpa, ordtmpb and ordtmpd tables w ill be generated. These records w ill passed through to the order entry program w hich w ill generate the actual open order records. If the system is def ined to assign the order number to the purchase order number (based on the edipooam opt ion being set to " 2" ), the system w ill set the order number to the f irst 10 characters of the customer purchase order number. Once the order has been generated, the system w ill generate the orderc record for the order transact ion and an orddet2 record for each line item generated in the order detail table. These tables w ill contain the EDI f ields to be saved through the system for outbound transact ion generat ion.



Once completed, the applicable f ields in the EDI table w ill be set (i.e. the MIS order number f ield w ill be set in the EDI table, the status w ill be changed to " U" for updated, etc.). B4-A. Addit ional Mapping Requirements Date Processing If the ship date is not set, it w ill be set equal to the require date. If the cancel date is not set, it w ill be set to the require date + 30. Ship To Name And Address If the ship to id = " X" , the name and address data w ill be taken from the EDI header f ields. Any f ields that are not valued w ill be set to " ." to prevent the order entry program from insert ing data from the ship to table. If either the ship to name, address1, address2, address3, city, state or zip code f ields are valued, the ent ire ship to name and address data w ill be taken from the EDI header f ields. Any f ields not valued w ill be set to " ." to prevent the order entry program from insert ing data from the ship to table. If the BS look indicator is set to " BS" , the system w ill pass the ship to id but w ill not pass the name and address data. This w ill be taken from the standard ship to table. Ship Via Code Requirements. If the header memo 20 f ield is valued, the f irst 4 characters w ill be validated to insure that the f ield matches a valid ship via code in the system. If the f ield is valued, it w ill be mapped to the ship via code on the order transact ion. 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 w ill cont inue 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 w ill set the quantity ordered and alternate quantity ordered based on the alternate to stock conversion factor for the item. This condit ion w ould occur if the unit of measure validat ion is performed and the unit of measure on the EDI transact ion corresponds to the item alternate unit of measure. Item Memo Fields. The f irst 16 characters of the detail memo 20 f ield w ill be updated to the item memo1 f ield in the order detail record. The f irst 16 characters of the detail memo 21 f ield w ill be updated to the item memo 2 f ield in the order detail record. Order Number If the system is def ined to assign the order number to the purchase order number (based on the edipoam opt ion being set to " 2" ), the system w ill verify that no orders or sales analysis records have an order number that matches the f irst 10 characters of the customer purchase order number. Original Taken By The original taken by f ield (Field name: otakenby_orderb) is set to " edi" rather than the user id of the user generat ing the sales orders. This w ill allow the user to select " edi" type orders in the Open



Order Report (ORDR). B4-B. Order Creat ion Error Codes The follow ing error codes w ill be generated when there is a problem creat ing the order: Code Descript ion 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#)



B5 - PURGE OPTION The purge opt ion provides the ability to delete records in the EDI Inbound Header and Detail tables (edinh, edind) w ith an upload date equal to or less than an entered purge date.When operators select the Purge EDI Files opt ion from the EDI Processing Menu, they w ill be prompted to enter a passw ord. The password w ill be validated to see that it matches the value in the ACF " EDINPWD" opt ion.The system w ill then prompt for the purge date. The purge date w ill default to the current system date minus the number of days to save the EDI Transact ion Data f iles w hich is stored in the ACF " EDINPRG" option.The operator w ill then be prompted to enter " PROCEED" or select Exit" to exit . Purge Menu Option Passw ord Screen.

Purge Menu Option Screen.



This may also be set up to run automatically at a pre-determined date and t ime by adding a MISCRON record as show n. The purge date w ill default to the current system date minus the number of days to save the EDI Transact ion Data f iles w hich is stored in the ACF " EDINPRG" opt ion.



C - CUSTOM PROGRAM ROUTINE CAPABILITY The capability of calling custom subrout ine programs from specif ic processes in the EDI Inbound program.is provided through the ACF "edipol__" option that w orks in a manner similar to the " bill__" ACF opt ions. The follow ing subrout ine capabilit ies and opt ions w ill be provided: edipol0x Execute programs in sequence after upload. This provides the capability of performing custom subrout ines after the ASCII f ile has been uploaded in to the EDI tables. ediin1x Execute programs in sequence after validat ion. This provides the capability of performing addit ional validat ions after the standard header, detail and summary validat ions are completed. Note that these funct ions w ill not occur during the actual maintenance of records but w ill occur during the validat ion menu opt ion and the validat ion option in the maintenance menu opt ion.. ediin2x Execute programs in sequence after order creat ion. This provides the capability of performing addit ional mapping and updating after the order transact ion has been generated. Once the subrout ine is completed, control w ill return to the main program, which w ill proceed w ith normal processing.



D - FILE AND FIELD LAYOUTS D1. EDINH - EDI INBOUND PURCHASE ORDER HEADER TABLE - this f ile is created after the ascii, excel or XML f iles are successfully (U)ploaded from the EDIPOLD program funct ion. 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 w here goods are to be shipped. bslook_edinh 35 CHAR SHIP TO ID INDICATOR The f lag denot ing w hether or not to access customer ship

to information. transdate_edinh 4 DATE TRANSACTION DATE The date the order came into the system and w as

processed converted to MM/DD/YYYY format. reqdate_edinh 4 DATE REQUESTED DATE The date the customer w ants 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 denot ion 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. 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. t ranscd_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. rout ing_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). cust id_edinh 10 CHAR VALIDATED CUSTOMER ID. shipid_edinh 10 CHAR VALIDATED SHIP TO ID. valuef lag_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. cust idov_edinh 2 CHAR CUSTOMER ID MANUAL OVERRIDE FLAG. shipidov_edinh 2 CHAR SHIP TO ID MANUAL OVERRIDE FLAG. f lag_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. t tyname_edinh 16 CHAR DEVICE ID. sysdate_edinh 4 DATE DATE LAST MODIFIED. syst ime_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. 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



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. Index on f lag_edinh. Index on status1_edinh. Index on cust id_edinh, cust_po_edinh



D2. EDIND - EDI INBOUND PURCHASE ORDER DETAIL TABLE - this f ile is created after the ascii, excel or XML f iles are successfully (U)ploaded from the EDIPOLD program funct ion. 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 w ants to pay) altorgprc_edind 10 DEC ALTERNATE ORIGINAL PRICE. retailprc_edind 10 DEC RETAIL PRICE. (price cust. w ants to sell the goods) freight_edind 10 DEC FREIGHT AMOUNT. ($ amt. cust allow s 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. custpart id_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 f lag_edind 4 CHAR INTERNAL UPLOAD FLAG. status_edind 2 CHAR LINE ITEM STATUS CODE. sysdate_edind 4 DATE SYSTEM DATE. syst ime_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. 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. 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] upcload_qty_edind 10 DEC DETAIL MEMO 1 - converted quantity from UPCLOAD program upcload_cnv_edind 10 DEC DETAIL MEMO 2 - conversion factor f rom 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.



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. rout ing_orderc 2 CHAR ROUTING CODE. scac_orderc 4 CHAR SCAC CODE. asnf lag_orderc 2 CHAR ASN GENERATION FLAG. asndate_orderc 4 DATE ASN GENERATION DATE. asnt ime_orderc 8 CHAR ASN GENERATION TIME. asnuser_orderc 8 CHAR ASN GENERATION USER. asnbatch_orderc 4 INT ASN GENERATION BATCH NUMBER. invf lag_orderc 2 CHAR INVOICE GENERATION FLAG. invdate_orderc 4 DATE INVOICE GENERATION DATE. invt ime_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. 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 Indexes: Index on ordnum_orderc. Index on partnrid_orderc, cust_po_orderc. Index on batch_orderc, ordnum_orderc.



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. 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 f rom UPCLOAD program Indexes: Index on ordnum_orddet2, lineno_orddet2, subno_orddet2. Index on partnrid_orddet2, ponumber_orddet2, polineno_orddet2.



E - INBOUND CUSTOMER PURCHASE ORDER ASCII FILE DEFINITION (850) The follow ing is a layout of the f ields in the inbound ASCII f ile in f ield number sequence to be uploaded to the EDI uploaded f ile. All f ields must be left just if ied. Fields 1 to 77 are header f ields and w ill be mapped to the EDI Inbound Header Table (edinh). Fields 78 to 139 are detail f ields and w ill be mapped to the EDI Inbound Detail Table (edind). For each trading partner / purchase order uploaded (based on the combinat ion of f ields 1 and 11), the f irst record w ill generate one EDI Inbound Header Table record. The assumption is that the header f ields w ill be ident ical for all detail records w ith the same trading partner id / mailbox number and customer purchase order number. Once the header record is generated, the EDI Inbound Detail Table records w ill be generated for all lines w ith the same trading partner / purchase order number (based on header f ield 1 matching detail f ile 78 and header f ield 11 matching detail f ield 79). Also, depending on the sett ing for ACF opt ion "edinfmt" , records can also be generated on a trading partner / purchase order number / sold to id basis (based on header f ield 1 matching detail f ield 78, header f ield 11 matching detail f ield 79 and header f ield 3 matching detail f ield 121). This allow s you to generate separate transact ions for dif ferent sold to customers for the same purchase order. The assumption is that the header f ields w ill be ident ical for all detail records w ith 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 35 3. SOLD TO ID. CHAR 35 4. SHIP TO ID. CHAR 35 5. BS LOOK SHIP TO ID INDICATOR. CHAR 35 6. 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 10 13. REFERENCE NUMBER. CHAR 30 14. DEPARTMENT. CHAR 30 15. REMARKS. CHAR 80 16. MEDIA/EVENT CODE. CHAR 2 17. SHIP TO NAME. CHAR 35 18. SHIP TO ADDRESS 1. CHAR 35 19. SHIP TO ADDRESS 2. CHAR 35 20. SHIP TO ADDRESS 3. CHAR 35 21. SHIP TO CITY. CHAR 19 22. SHIP TO STATE. CHAR 2 23. SHIP TO COUNTRY. CHAR 2 24. SHIP TO ZIP CODE. CHAR 9 25. SHIP TO ATTENTION. CHAR 27 26. MARK FOR. CHAR 45 27. TERMS CODE. CHAR 4 28. 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 # FIELD DESCRIPTION TYPE SIZE NOTES 31. ROUTING. CHAR 2 32. SCAC. CHAR 4 33. MEMO1. CHAR 30 phone# (W3) 34. MEMO2. CHAR 30 35. MEMO3. CHAR 10 36. MEMO4 (NUMERIC -XXXXXX.XX) DEC 10 Freight Charge (W3) 37. MEMO5 (DATE). DATE 6 " MMDDYY" . 38. HEADER MEMO 1. CHAR 30 CC Authorizat ion (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 30 52. HEADER MEMO 15. CHAR 30 53. HEADER MEMO 16. CHAR 30 54. HEADER MEMO 17. CHAR 30 55. HEADER MEMO 18. CHAR 30 56. HEADER MEMO 19. CHAR 30 57. HEADER MEMO 20 CHAR 30 SHIP VIA CODE. 58. HEADER MEMO 21. CHAR 30 ROUTE CODE 59. HEADER MEMO 22. CHAR 30 Transact ion ID w eb 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 30 63. HEADER MEMO 26. CHAR 30 64. HEADER MEMO 27. CHAR 30 65. HEADER MEMO 28. CHAR 30 66. HEADER MEMO 29. CHAR 30 67. HEADER MEMO 30. CHAR 30 68. HEADER MEMO 31. CHAR 30 69. HEADER MEMO 32. CHAR 30 70. HEADER MEMO 33. CHAR 30 71. HEADER MEMO 34. CHAR 30 72. HEADER MEMO 35. CHAR 30 73. HEADER MEMO 36. CHAR 30 74. HEADER MEMO 37. CHAR 30 75. HEADER MEMO 38. CHAR 30 76. HEADER MEMO 39. CHAR 30 77. HEADER MEMO 40. CHAR 30 * * * * * * * * * * * * * f ield 78 thru 139 are the detail port ion of the ascii input f ile



* * * * * * * * * * * * * * * * * * 78. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 * * REQUIRED* * must be same as f ld # 1 79. CUSTOMER P/O NUMBER. CHAR 22 * * REQUIRED* * must be same as f ld # 11 80. CUSTOMER P/O SEQUENCE NUMBER. CHAR 4 81. CUSTOMER PART ID. CHAR 18 82. CUSTOMER PART ID 2. CHAR 18 83. UPC CODE. CHAR 25 84. ITEM ID. CHAR 25 # FIELD DESCRIPTION TYPE SIZE NOTE 85. ITEM DESCRIPTION. CHAR 18 86. QUANTITY ORDERED. DEC 10 " -XXXXXX.XX" * * Required* * 87. UNIT OF MEASURE. CHAR 2 88. 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 8 92. SPECIAL INSTRUCTIONS - LINE 2. CHAR 8 93. DELIVERY NOTES - LINE 1. CHAR 60 94. DELIVERY NOTES - LINE 2. CHAR 60 95. MEMO 1. CHAR 30 96. MEMO 2. CHAR 30 97. MEMO 3. CHAR 10 98. MEMO 4 (NUMERIC). DEC 10 Numeric " -XXXXXX.XX" 99. MEMO 5 (DATE). DATE 6 Date " MMDDYY" . 100. DETAIL MEMO 1. CHAR 30 101. DETAIL MEMO 2. CHAR 30 102. DETAIL MEMO 3. CHAR 30 103. DETAIL MEMO 4. CHAR 30 104. DETAIL MEMO 5. CHAR 30 105. DETAIL MEMO 6. CHAR 30 106. DETAIL MEMO 7. CHAR 30 107. DETAIL MEMO 8. CHAR 30 108. DETAIL MEMO 9. CHAR 30 109. DETAIL MEMO 10. CHAR 30 110. DETAIL MEMO 11. CHAR 30 111. DETAIL MEMO 12. CHAR 30 112. DETAIL MEMO 13. CHAR 30 113. DETAIL MEMO 14. CHAR 30 114. DETAIL MEMO 15. CHAR 30 115. DETAIL MEMO 16. CHAR 30 116. DETAIL MEMO 17. CHAR 30 117. DETAIL MEMO 18. CHAR 30 118. DETAIL MEMO 19. CHAR 30 119. DETAIL MEMO 20 - ITEM MEMO 1. CHAR 30 120. DETAIL MEMO 21 - ITEM MEMO 2. CHAR 30 121. DETAIL MEMO 22 - DETAIL EDI SOLDTO CHAR 30 See ACF ' edinfmt' for usage format codes = 0, 1, 2.



122. DETAIL MEMO 23. CHAR 30 123. DETAIL MEMO 24. CHAR 30 124. DETAIL MEMO 25. CHAR 30 125. DETAIL MEMO 26. CHAR 30 126. DETAIL MEMO 27. CHAR 30 127. DETAIL MEMO 28. CHAR 30 128. DETAIL MEMO 29. CHAR 30 129. DETAIL MEMO 30. CHAR 30 130. DETAIL MEMO 31. CHAR 30 131. DETAIL MEMO 32. CHAR 30 132. DETAIL MEMO 33. CHAR 30 133. DETAIL MEMO 34. CHAR 30 134. DETAIL MEMO 35. CHAR 30 135. DETAIL MEMO 36. CHAR 30 136. DETAIL MEMO 37. CHAR 30 137. DETAIL MEMO 38. CHAR 30 138. DETAIL MEMO 39. CHAR 30 139. DETAIL MEMO 40. CHAR 30 Field Types: CHAR - Character - Alpha-numeric characters. DATE - Date - Must be in format " MMDDYY" . If f ield w ill not be used or is not valued, use the system default date (" 010180" ). DEC - Decimal - Numeric f ield w ith at least one posit ion to the left and 2 posit ions to the right of the decimal point w ith leading minus sign (if applicable). General Requirements: - File must be in ASCII format. - All records must have each f ield delineated by a pipe symbol (< 174> ASCII character w hich is

represented as | ). - All records must be terminated w ith 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 f ields must be valued; if a date f ield is not valued or w ill not be used, set the date f ield

to January 1, 1980 (" 010180" ). - All alphanumeric (CHAR) fields must be lef t -just if ied. - All quant it ies and prices must be in decimal format: " -XXXXXX.XX" . Signed numeric f ields

must contain the sign in front of the number. Decimal point must be included and contain at least one digit to the lef t and tw o digits to the right of the decimal point (i.e. -323.25). Blanks before any number are assumed to be posit ive.



G - EDI INBOUND PURCHASE ORDER 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.

t randate_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.



FIELD NAME DESTINATION MAPPING markfor_edinh markfor_orderb. 25 characters.

markfor_orderc. terms_cd_edinh terms_cd_orderc. t ranscd_edinh transcd_orderc. transtype_edinh trantype_orderc. contract_edinh contract_orderc. rout ing_edinh rout ing_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. cust id_edinh soldto_ordera. shipid_edinh shipto_ordera. valuef lag_edinh None. poduplov_edinh None. podateov_edinh None. cust idov_edinh None. shipidov_edinh None. f lag_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. syst ime_edinh None. userid_edinh None. t tyname_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



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



H - EDI INBOUND PURCHASE ORDER DETAIL TABLE MAPPING (EDIND) TO ORDER TABLES FIELD NAME DESTINATION MAPPING serial_hdr_edind None. serial_det_edind None. partnrid_edind None. ponumber_edind None. polineno_edind polineno_orddet2. custpart1_edind custprt1_orddet2. custpart2_edind custprt2_orddet2. upc_edind upc_orddet2. sellitem_edind sellitem_orddet2. desc_edind desc_orddet2. qtyord_edind qtyord_orddet2. qtyord_orddet. altqtyord_orddet. uom_edind uom_orddet2. orgprice_edind orgprice_orddet2. retailprc_edind retailprc_orddet2. freight_edind freight_orddet2. spcsrv1_edind spcsrv1_orddet2. spcsrv2_edind spcsrv2_orddet2. delins1_edind delins1_orddet2. delins2_edind delins2_orddet2. memo1_edind memo1_orddet2. memo2_edind memo2_orddet2. memo3_edind memo3_orddet2. memo4_edind memo4_orddet2. memo5_edind memo5_orddet2. itemidov_edind None. custpart id_edind custpart id_orddet. lineno_edind lineno_orddet

curmemo1_orddet (temporarily; then set to zero). lineno_orddet2 (from curmemo1_orddet before clear).

subno_edind None itemid_edind itemid_orddet. desc1_edind None. sellprice_edind sellprice_orddet. altqtyord_edind altqtyord_orddet2. altconv_edind altconv_orddet2. altuom_edind altuom_orddet2. altorgprc_edind altorgprc_orddet2. altsellprc_edind altsellpr_orddet. grossext_edind None. netext_edind None. priceuom_edind priceuom_orddet. prcuomcnv_edind prcuomconv_orddet. f lag_edind None. status_edind None. sysdate_edind None. syst ime_edind None. edi_ordnum_edind None.



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 memodn04_edind memodn04_ orddet2 memodn05_edind memodn05_ orddet2 memodn06_edind memodn06_ orddet2 memodn07_edind memodn07_ orddet2 memodn08_edind memodn08_ orddet2 memodn09_edind memodn09_ orddet2 memodn10_edind memodn10_ orddet2 sellprcovrd_edind sellprcovrd_ orddet2 upcload_qty_edind upcload_qty_orddet2 upcload_cnv_edind upcload_cnv_orddet2

I - ACF OPTIONS FOR THE EDI MODULE -

* * * view all edi opt ions using edi* from the acf pgm * * *



PROCESSING OUTBOUND TRANSACTIONS EDIASNG- EDI OUTBOUND ADVANCED SHIP NOTICES GENERATION A. Modif icat ion Summary. This program provides the opt ional ability to generate ASCII f iles for the purpose of generat ing EDI Advanced Shipment Notices through a third party product. B. Modif icat ion Detail. The follow ing describes the logic used to process outbound EDI Advanced Shipment Notice transact ions. B1. Program Flow . The operator w ill be prompted for the follow ing opt ions when generat ing the ASCII f iles. Once all the select ions have been made, the operator w ill be prompted w hether to proceed w ith the creat ion of the ASCII File. 1. Select ion Options. Records w ill be selected from the applicable tables (shipment conf irmation or invoice history) w here the transact ion w as generated from and EDI purchase order (based on the existance of an orderc record) and w here the advanced shipment not ice f lag (shipf lag_editp) in the applicable trading partner record (based on partnerid_editp = partnrid_orderc) is set to ' Y' . The follow ing header select ion opt ions w ill be available. The opt ion w ill 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 follow ing header transact ion select ion opt ions w ill be available. The opt ion w ill default to ' All Ungenerated Shipments' . - All Ungenerated Shipments.

This select ion w ill select all records from the ship tables w here the asn generat ion f lag in the order header table (asnf lag_orderc) is not set to ' Y' .

- Selected Ungenerated Shipment Reference Numbers.

This select ion w ill select records from the shipping conf irmation tables based on the invoice reference number(s) entered w here the asn generat ion f lag in the order header table (asnf lag_orderc) is not set to ' Y' .

- Selected Generated Shipment Reference Numbers.

This select ion w ill select records from the shipping conf irmation tables based on the invoice reference number(s) entered w here the asn generat ion f lag in the order header table (asnf lag_orderc) is set to 'Y' .

- Selected Generated Invoice History Reference Numbers.

This select ion w ill select records from the invoice history tables based on the invoice reference number(s) entered.



- Selected Generated Date (Invoice History). This select ion w ill select records from the invoice history tables based on the date criteria entered matching the asn generat ion date (asndate_invoicec).

The follow ing detail t ransact ion select ion opt ions w ill be available. The opt ion w ill default to the contents of the ACF EDISDET opt ion: - All Lines.

This select ion w ill include all detail lines in the f ile, w hether or not a shipment is made against the line.

- Only Lines Where Quantity Shipped Is Present.

This select ion w ill only include detail lines in the ASCII f ile if the quantity shipped (qtyship_invdet) is non-zero.

2. Sort Options. The follow ing sort opt ions w ill be available. The option w ill 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 w ill only be incorporated if the ACF edismbl value is greater than ' 1' . 3. ASCII Files Options. The operator w ill be prompted for the follow ing to def ine the ASCII f ile parameters: - Directory Path.

This w ill be the VALID directory where the ASCII f ile w ill be generated. The default w ill be the contents of the ACF EDISDIR Option. If an invalid directory is selected, the program w ill display the message ' Invalid Directory' , wait for a brief period and exit the program.

- Pref ix File Name.

This w ill be the pref ix for the ASCII f ile name to be generated. The default w ill be the contents of the ACF EDISPFX Option. By sett ing the default to ' TODAY' , the system w ill use the month and day of the current date and the next edi asn sequence number (def ined

in ACF EDISSEQ) as the ASCII File Name Pref ix in the format MMDDSSS w here MM is the current month, DD is the current date and SSS is the current sequence number (betw een

001 and 999). If this method is used, the contents of the ACF EDISSEQ opt ion w ill be incremented by 1 and updated.

- ASCII File Name.

This w ill be the ASCII f ile name to be generated. The default w ill be the contents of the ACF

EDISFIL Option. The actual name assigned to the ASCII f ile w ill be in the follow ing format: < PREFIX FILE NAME> .< ASCII FILE NAME>



- Field Delimiter.

This w ill be the f ield delimiter used in the ASCII f ile output. The default w ill be the contents of the EDISDEL Option which w ill be init ially set to the pipe (| ) symbol.

Once the select ions have been made, the operator w ill be prompted w hether to proceed w ith the creat ion of the ASCII File. If they proceed, the system w ill display the next EDI ASN Batch Number at the base of the screen. This number w ill be assigned to all records included in the f ile. The ACF value w ill be incremented by 1 and updated. Once the generat ion is completed, the program w ill go to program end.

B2. ASN Generat ion Update. The follow ing f ields w ill be set in the orderc table once the ASCII f ile has been created for the records included: - The ASN Generat ion Flag w ill be set to ' Y' (asnf lag_orderc). - The ASN Generat ion Date w ill be set to the current date (asndate_orderc). - The ASN Generat ion Time w ill be set to the current t ime (asnt ime_orderc). - The ASN Generat ion User w ill be set to the user id performing the generat ion (asnuser_orderc). - The ASN Generat ion Batch Number w ill be set to the contents of the ACF EDISBAT opt ion (asnbatch_orderc).

B3. Dow nload Logic. The follow ing header f ields w ill 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 1 - 5. - Header Memo 1 - 40. - The follow ing header f ields w ill be selected from the standard tables (shipa, shipb, inva, invb): - Shipment Reference Number (Order Number - Number of Backorder Field). The format w ill be order number followed by a dash follow ed by the number of backorders f ield. - Invoice Number. - Order Number. - Actual Ship Date. - Order Weight. - Tracking Number (from miscellaneous information 3 f ield). - Master Bill of Lading Number (from miscellaneous informat ion 3 f ield).



The follow ing header f ields w ill be selected from the EDI Ship Via table (edisv) based on the sold to ID and the ship via code on the order: - Rout ing. - SCAC Code. - SCAC Descript ion - Carrier Name f ield. - Carrier Reference Number (Tracking Number). - Transportat ion Method. The follow ing header comment f ields w ill be selected from the standard header comments tables

(ordcomt, invhc): - Trailer Number (code of ' SH' ). - Trailer Pref ix (code of ' SX' ). The follow ing header and detail f ields w ill 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 follow ing detail f ields w ill 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 Descript ion. - Memo 1 - 5. - Detail Memo 1 - 40. The follow ing detail f ields w ill be selected from the standard tables (shipd, invd): - Quant ity Shipped. - Selling Price (+ Insurance if applicable). - Weight. - Unit of Measure Charged (if f ield in trading partner table is < NULL> ). The follow ing shipment f ields w ill be summed for the master bill of lading number (misc. info. 3) if the value in the ACF edismbl opt ion is ' 2' . If the value in the ACF edismbl opt ion is set to ' 1' or the master bill of lading number is < NULL> , it w ill be summed for the invoice number: - Shipment Lading Quantity: Quantity Shipped. - Shipment Weight: Weight. The follow ing order f ields w ill be summed for the order number: - Order Lading Quantity: Quantity Shipped.



The Ship From name and address information w ill be selected from the division f ile if the contents of the ACF EDISADR opt ion is ' 1' (Default). If the contents of the ACF EDISADR opt ion is ' 2' , the information w ill be selected from the branch table. The line number w ill be an incremented f ield start ing at 1 for each order. The follow ing are the valid Ship Order Status Codes: Code Descript ion ---- ----------- - 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 w ill be assigned in the follow ing manner: On the f irst shipment of the order: - If the original quant ity 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 w ill be set to ' CM' (SHIP COMPLETE). - Otherw ise, the code w ill be set to ' CP' (PARTIAL SHIPMENT - FIRST SHIPMENT). On subsequent shipments of the order: - If the original quant ity 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 w ill be set to ' BP' (PARTIAL SHIPMENT - BACKORDER). - Otherw ise, the code w ill be set to ' BK' (BACK ORDERED). B4. Price Formats. An ACF opt ion (opt ion code ' edisprcd' ) w ill allow the def init ion of the number of decimal posit ions of the selling price & retail price f ields generated in the EDI Advanced Ship Notice ASCII f ile. The system w ill allow an opt ion value of ' 2' or ' 4' . When generat ing the advanced ship not ice, if the opt ion value is ' 2' , the system w ill output the retail price (f ield 88) and selling price (f ield 89) to 2 posit ions to the right of the decimal. This involves using a format of " &&&&&&&.&&" . If the opt ion value is ' 4' , the system w ill output the the retail price (f ield 88) and selling price (f ield 89) to 4 posit ions to the right of the decimal. This involves using a format of " &&&&&.&&&&" . Note that the maximum price capable of being output w ith this opt ion is 99999.9999. B5. Date Formats. An ACF opt ion (opt ion code ' edisdfmt' ) w ill allow the def init ion of the output date format for all the



date f ields generated in the EDI Advanced Ship Notice ASCII f ile. The system w ill allow an opt ion value of " 1" or " 2" and default to " 1" . If the opt ion value is set to " 1" , the system w ill output all dates in the EDI Advanced Ship Notice ASCII f ile in the format " YYMMDD" . If the opt ion value is set to " 2" , the system w ill output all dates in the EDI Advanced Ship Notice ASCII f ile in the format " MMDDYY" . General Formats: - All dates w ill be dow nloaded in the format: " YYMMDD" or " MMDDYY" , based on ACF opt ion " edisdfmt" . - All quant it ies w ill be dow nloaded in integer format: XXXXXXX. - All w eights w ill be downloaded in Decimal Format: XXXXX.XX. - All prices w ill be dow nloaded in Decimal Format: XXXXXXX.XX or XXXXX.XXXX, based on ACF opt ion " edisprcd" . - All records w ill be terminated w ith a < CARRIAGE RETURN> < LINE FEED> . - All f ields w ill be output to their maximum length, not to the actual length of the f ield. Alpha- numeric character f ields w ill be lef t-just if ied w ith blanks follow ing the data. Numeric f ields w ill be right just if ied w ith leading zeroes.



C. Outbound ASCII File Layouts. The follow ing is a layout of the f ields in the outbound ASCII f ile in f ield number sequence to be dow nloaded to the EDI Advanced Ship Notice ASCII f ile. All f ields w ill be lef t just if ied. Fields 1 to 83 are header f ields. The remaining f ields are detail f ields. 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 (w eight_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 w eight_invoicea. 23. PACKING CODE. CHAR 5 packcd_editp 24. ROUTING. CHAR 2 rout ing_edisv. 25. CARRIER REFERENCE NUMBER. CHAR 30 t rackno_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. 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 sett ing: sequential number assigned for each order detail line ucc128 sett ing: sequential number assigned to each record generated in ascii

f ile 85. CUSTOMER P/O SEQUENCE NUMBER. CHAR 4 polineno_orddet2. 86. QUANTITY ORDERED. DEC 10 qtyord_orddet2. 87. QUANTITY SHIPPED. DEC 10 qtyshp_invdet. 88. RETAIL PRICE. DEC 10 ret lpr_orddet2. 89. SELLING PRICE. DEC 10 if acf edisprc = 1, sellprice_invdet if acf edisprc = 2, sellprice + insrrate 90. ITEM ID. CHAR 25 sellitem_orddet2. 91. CUSTOMER PART ID. CHAR 18 cstpart1_orddet2. 92. CUSTOMER PART ID 2. CHAR 18 cstpart2_orddet2. # FIELD DESCRIPTION TYPE SIZE INFO 93. UPC CODE. CHAR 25 upc_orddet2. 94. UNIT OF MEASURE. CHAR 2 uom_orddet2. 95. UNIT OF MEASURE CHARGED. CHAR 2 uom_editp. uom_invdet. 96. ITEM DESCRIPTION. CHAR 18 desc_orddet2. 97. WEIGHT. DEC 10 w eight_invdet. 98. SHIP ORDER STATUS CODE. CHAR 2 ship order status code. 99. MEMO 1. CHAR 30 memo1_orddet2 100. MEMO 2. CHAR 30 memo2_orddet2 101. MEMO 3. CHAR 10 memo3_orddet2 102. MEMO 4 (NUMERIC). DEC 10 memo4_orddet2 103. MEMO 5 (DATE). DATE 6 memo5_orddet2 104. DETAIL MEMO 1. CHAR 30 memod1_orddet2 105. DETAIL MEMO 2. CHAR 30 memod2_orddet2 106. DETAIL MEMO 3. CHAR 30 memod3_orddet2 107. DETAIL MEMO 4. CHAR 30 memod4_orddet2 108. DETAIL MEMO 5. CHAR 30 memod5_orddet2 109. DETAIL MEMO 6. CHAR 30 memod6_orddet2 110. DETAIL MEMO 7. CHAR 30 memod7_orddet2 111. DETAIL MEMO 8. CHAR 30 memod8_orddet2 112. DETAIL MEMO 9. CHAR 30 memod9_orddet2 113. DETAIL MEMO 10. CHAR 30 memod10_orddet2 114. DETAIL MEMO 11. CHAR 30 memod11_orddet2 115. DETAIL MEMO 12. CHAR 30 memod12_orddet2 116. DETAIL MEMO 13. CHAR 30 memod13_orddet2 117. DETAIL MEMO 14. CHAR 30 memod14_orddet2 118. DETAIL MEMO 15. CHAR 30 memod15_orddet2 119. DETAIL MEMO 16. CHAR 30 memod16_orddet2 120. DETAIL MEMO 17. CHAR 30 memod17_orddet2 121. DETAIL MEMO 18. CHAR 30 memod18_orddet2 122. DETAIL MEMO 19. CHAR 30 memod19_orddet2 123. DETAIL MEMO 20. CHAR 30 memod20_orddet2 124. DETAIL MEMO 21. CHAR 30 memod21_orddet2 125. DETAIL MEMO 22. CHAR 30 memod22_orddet2



126. DETAIL MEMO 23. CHAR 30 memod23_orddet2 127. DETAIL MEMO 24. CHAR 30 memod24_orddet2 128. DETAIL MEMO 25. CHAR 30 memod25_orddet2 129. DETAIL MEMO 26. CHAR 30 memod26_orddet2 130. DETAIL MEMO 27. CHAR 30 memod27_orddet2 131. DETAIL MEMO 28. CHAR 30 memod28_orddet2 132. DETAIL MEMO 29. CHAR 30 memod29_orddet2 133. DETAIL MEMO 30. CHAR 30 memod30_orddet2 134. DETAIL MEMO 31. CHAR 30 memod31_orddet2 135. DETAIL MEMO 32. CHAR 30 memod32_orddet2 136. DETAIL MEMO 33. CHAR 30 memod33_orddet2 137. DETAIL MEMO 34. CHAR 30 memod34_orddet2 138. DETAIL MEMO 35. CHAR 30 memod35_orddet2 139. DETAIL MEMO 36. CHAR 30 if current sett ing: memod36_orddet2 if ucc128 sett ing: memo1_boxh 140. DETAIL MEMO 37. CHAR 30 memod37_orddet2 141. DETAIL MEMO 38. CHAR 30 memod38_orddet2 142. DETAIL MEMO 39. CHAR 30 memod39_orddet2 143. DETAIL MEMO 40. CHAR 30 memod40_orddet2



D. Database Fields Updated. D1. ORDERC - EDI Open Order Header Table Layout. Update the follow ing f ields to the EDI Open Order Header Table: FIELD NAME SIZE TYPE DESCRIPTION

asnf lag_orderc 2 CHAR ASN GENERATION FLAG asndate_orderc 4 DATE ASN GENERATION DATE asnt ime_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 follow ing f ields in the EDI Order Maintenance Header Table: FIELD NAME SIZE TYPE DESCRIPTION

asnf lag_orderc 2 CHAR ASN GENERATION FLAG asndate_orderc 4 DATE ASN GENERATION DATE asnt ime_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 follow ing f ields in the EDI Open Invoice Header Table: FIELD NAME SIZE TYPE DESCRIPTION

asnf lag_invoicec 2 CHAR ASN GENERATION FLAG asndate_invoicec 4 DATE ASN GENERATION DATE asnt ime_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 follow ing f ields to the EDI Invoice History Header Table: FIELD NAME SIZE TYPE DESCRIPTION

asnf lag_invoicec 2 CHAR ASN GENERATION FLAG asndate_invoicec 4 DATE ASN GENERATION DATE asnt ime_invoicec 8 CHAR ASN GENERATION TIME asnuser_invoicec 8 CHAR ASN GENERATION USER asnbatch_invoice 10 CHAR ASN GENERATION BATCH



E. Screen Layouts. E1. Option Selection Screen.

E2. Sort /ASCII Parameters Screen.



F. ACF Options for ASN processing - * * * view all edi opt ions using edi* from the acf pgm

* * *



EDIINVCG- EDI OUTBOUND INVOICE ASCII FILE GENERATION A. Modif icat ion Summary. This program provides the ability to generate ASCII f iles for the purpose of generat ing EDI Invoices through a third party product. B. Modif icat ion Detail. The follow ing describes the logic used to process outbound EDI Invoice transact ions. B1. Program Flow . The operator w ill be prompted for the follow ing opt ions when generat ing the ASCII f iles. Once all the select ions have been made, the operator w ill be prompted w hether to proceed w ith the creat ion of the ASCII File. 1. Select ion Options. Records w ill be selected from the applicable tables (open invoice or invoice history) w here the transact ion w as generated from and EDI purchase order (based on the existence of an invoicec or invc record) and w here the EDI invoice f lag (invf lag_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 w ill reject the transact ion. The follow ing header select ion opt ions w ill be available. The opt ion w ill 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 follow ing header transact ion select ion opt ions w ill be available. The opt ion w ill default to ' All Ungenerated Invoices' . - All Ungenerated Invoices.

This select ion w ill select all records from the Open Invoice tables w here the invoice generat ion f lag in the EDI Invoice Header table (invf lag_invoicec) is not set to ' Y' .

- Selected Invoice Reference Numbers.

This select ion w ill select records from the Open Invoice tables based on the invoice reference number(s) entered w here the invoice generat ion f lag in the EDI Invoice Header table (invf lag_invoicec) is not set to ' Y' .

- Selected Invoice History Reference Numbers.

This select ion w ill select records from the Invoice History tables based on the invoice reference number(s) entered.

- Selected Generated Date (Invoice History).

This select ion w ill select records from the Invoice History tables based on the date criteria entered matching the invoice generat ion date (invdate_invoicec) in the EDI Invoice Header table.



- All Invoices Open in A/R (Invoice History). This select ion w ill select records from the Open A/R Table (aropnitm) w here the total amount open on the invoice is not zero. The corresponding records in the Invoice History tables w ill be selected.

- All Invoices matching a Customer’ s P.O. Number (Invoice History). This select ion w ill select records from the Invoice History tables that match on purchase order number. The corresponding records in the Invoice History tables w ill be selected.

The follow ing detail t ransact ion select ion opt ions w ill be available. The opt ion w ill default to the contents of the ACF EDIIDET opt ion: - All Lines.

This select ion w ill include all detail lines in the f ile, w hether or not a shipment is made against the line.

- Only Lines Where Quantity Shipped Is Present.

This select ion w ill only include detail lines in the ASCII f ile if the quantity shipped (qtyship_invdet) is non-zero.

2. Sort Options. The follow ing sort opt ions w ill be available. The option w ill 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 w ill only be incorporated if the ACF EDIIMBL value is greater than ' 1' . 3. ASCII Files Options. The operator w ill be prompted for the follow ing to def ine the ASCII f ile parameters: - Directory Path.

This w ill be the VALID directory where the ASCII f ile w ill be generated. The default w ill be the contents of the ACF EDIIDIR Option. If an invalid directory is selected, the program w ill display the message ' Invalid Directory' , w ait for a brief period and exit the program.

- Pref ix File Name.

This w ill be the pref ix for the ASCII f ile name to be generated. The default w ill be the contents of the ACF EDIIPFX Option. By sett ing the default to ' TODAY' , the system w ill use the month and day of the current date and the next edi invoice sequence number (def ined in ACF EDIISEQ) as the ASCII File Name Pref ix in the format MMDDSSS w here 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 opt ion w ill be incremented by 1 and updated.



- ASCII File Name. This w ill be the ASCII f ile name to be generated. The default w ill be the contents of the ACF EDIIFIL Option. The actual name assigned to the ASCII f ile w ill be in the follow ing format: < PREFIX FILE NAME> .< ASCII FILE NAME> - Field Delimiter.

This w ill be the f ield delimiter used in the ASCII f ile output. The default w ill be the contents of the ACF EDISDEL Option w hich w ill be init ially set to the pipe (| ) symbol.

Once the select ions have been made, the operator w ill be prompted w hether to proceed w ith the creat ion of the ASCII File. If they proceed, the system w ill display the next EDI Invoice Batch Number at the base of the screen. This number w ill be assigned to all records included in the f ile. The ACF value w ill be incremented by 1 and updated. Once the generat ion is completed, the program w ill go to program end. B2. Invoice Generat ion Update. The follow ing f ields w ill be set in the invoicec table and the invc table once the ASCII f ile has been created for the records included: - The Invoice Generat ion Flag w ill be set to ' Y' (invf lag_invoicec) - The Invoice Generat ion Date w ill be set to the current date (invdate_invoicec) - The Invoice Generat ion Time w ill be set to the current t ime (invt ime_invoicec) - The Invoice Generat ion User w ill be set to the user id performing the generat ion

(invuser_invoicec). - The Invoice Generat ion Batch Number w ill be set to the contents of the ACF EDIIBAT opt ion (invbatch_invoicec). If the trading partner invoice print f lag is not set to 'Y' (invprt_editp), the follow ing f ields w ill be set in the standard Invoice Header table (invoiceb): - The invoice print f lag w ill be set to ' N' (print f lag_invoiceb). - The invoice print date w ill be set to the current date (invprtdt_invoiceb). - The invoice print t ime w ill be set to the current t ime (iprnt t ime_invoiceb). - The invoice print user w ill be set to the user performing the generat ion (iprntuser_invoiceb). Updating w ill only occur w hen processing Open Invoices, not invoice history records (print opt . 1 and 2).



B3. Dow nload Logic. The follow ing header f ields w ill 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 1 - 5. - Header Memo 1 - 40. The follow ing header f ields w ill be selected from the standard tables (invoicea, invoiceb, inva, invb): - Shipment Reference Number (Order Number - Number of Backorder Field). The format w ill be order number follow ed by a dash follow ed by the number of backorders f ield. - Invoice Number. - Invoice Date. - Order Number. - Actual Ship Date. - Order Weight. - Tracking Number (from miscellaneous information 3 f ield). - Master Bill of Lading Number (from miscellaneous information 3 f ield). - Invoice Total Amount. - Invoice Total Amount (w ithout charges). - Special Charge Total. - Allow ance Charge Total. - Terms Discount Percentage. - Terms Discount Amount. - Terms Discount Due Date. - Terms Net Due Date. - Percentage of Invoice Payable.



The follow ing header f ields w ill be selected from the EDI Ship Via table (edisv) based on the trading partner ID and the ship via code on the invoice: - Rout ing. - SCAC Code. - SCAC Descript ion - Carrier Name f ield. - Carrier Reference Number (Tracking Number). - Transportat ion Method. - Special Services Code. The follow ing header f ields w ill be selected from the standard Terms table (terms) based on the terms code on the invoice: - Terms Net Days. - Terms Discount Days. - Terms Descript ion. - Terms Discount Days Due. The follow ing header f ields w ill 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 follow ing header comment f ields w ill be selected from the standard header comments tables (invhcomt, invhc): - Trailer Number (code of 'SH' ). - Trailer Pref ix (code of ' SX' ). The follow ing header and detail f ields w ill 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. - Allow ance Charge Indicator. - Allow ance Charge Method.



The follow ing detail f ields w ill 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 Descript ion. - Memo 1 - 5. - Detail Memo 1 - 40. The follow ing detail f ields w ill be selected from the standard tables (invdet, invd): - Quantity Shipped. - Selling Price (+ Insurance if applicable). - Weight. - Unit of Measure Charged (if f ield in trading partner table is < NULL> ). The follow ing shipment f ields w ill be summed for the master bill of lading number (misc. info. 3) if the value in the ACF EDIIMBL opt ion is ' 2' . If the value in the ACF EDIIMBL opt ion is set to ' 1' or the master bill of lading number is < NULL> , it w ill be summed for the invoice number: - Shipment Lading Quantity: Quantity Shipped. - Shipment Weight: Weight. The follow ing order f ields w ill be summed for the invoice number: - Order Lading Quantity: Quantity Shipped. The follow ing invoice f ields w ill be summed for the invoice number: - Number of Units Shipped: Quantity Shipped. The Ship From name and address information w ill be selected from the division f ile if the contents of the ACF EDIIADR opt ion is ' 1' (Default). If the contents of the ACF EDIIADR opt ion is ' 2' , the information w ill be selected from the branch table. The line number w ill be an incremented f ield start ing at 1 for each invoice.



The follow ing are the valid Ship Order Status Codes: Code Descript ion 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 w ill be assigned in the follow ing manner: On the f irst shipment of the order: - If the original quant ity 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 w ill be set to ' CM' (SHIP COMPLETE). - Otherw ise, the code w ill be set to ' CP' (PARTIAL SHIPMENT - FIRST SHIPMENT). On subsequent shipments of the order: - If the original quant ity 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 w ill be set to ' BP' (PARTIAL SHIPMENT - BACKORDER). - Otherw ise, the code w ill be set to ' BK' (BACK ORDERED). B4. Price Formats. An ACF opt ion (opt ion code ' ediiprcd' ) w ill allow the def init ion of the number of decimal posit ions of the selling price & retail price f ields generated in the EDI Invoice ASCII f ile. The system w ill allow an opt ion value of ' 2' or ' 4' . When generat ing the invoice, if the opt ion value is ' 2' , the system w ill output the retail price (f ield 120) and selling price (f ield 121) to 2 posit ions to the right of the decimal. This involves using a format of " &&&&&&&.&&" . If the opt ion value is ' 4' , the system w ill output the the retail price (f ield 120) and selling price (f ield 121) to 4 posit ions to the right of the decimal. This involves using a format of " &&&&&.&&&&" . Note that the maximum price capable of being output w ith this opt ion is 99999.9999. B5. Date Formats. An ACF opt ion (opt ion code ' ediidfmt ' ) w ill allow the def init ion of the output date format for all the date f ields generated in the EDI Invoice ASCII f ile. The system w ill allow an opt ion value of " 1" or " 2" and default to " 1" . If the opt ion value is set to " 1" , the system w ill output all dates in the EDI Invoice ASCII f ile in the format " YYMMDD" . If the opt ion value is set to " 2" , the system w ill output all dates in the EDI Invoice ASCII f ile in the format " MMDDYY" .



General Formats: - All dates w ill be dow nloaded in the format: "YYMMDD" or " MMDDYY" , based on ACF opt ion

" ediidfmt" . - All quant it ies w ill be downloaded in integer format: XXXXXXX. - All w eights w ill be dow nloaded in Decimal Format: XXXXX.XX. - All prices w ill be dow nloaded in Decimal Format: XXXXXXX.XX or XXXXX.XXXX, based on

ACF opt ion " ediiprcd" . - All terms percentages w ill be dow nloaded in Decimal Format: XXX.XX. - All terms days w ill be dow nloaded in Integer Format: XXX. - All amounts w ill be dow nloaded in Decimal Format: XXXXXXX.XX. - All records w ill be terminated w ith a < CARRIAGE RETURN> < LINE FEED> . - All f ields can either be output to their maximum length or to the actual length of the f ield, based

on ACF opt ion " ediinlen" . When output to their maximum lengths, alpha-numeric character f ields w ill be lef t-just if ied w ith blanks follow ing the data; numeric f ields w ill be right just if ied w ith leading zeroes.



C. Outbound Invoice ASCII File Layouts. The follow ing is a layout of the f ields in the outbound ASCII f ile in f ield number sequence to be dow nloaded to the EDI Invoice ASCII f ile. All f ields w ill be lef t just if ied. Fields 1 to 115 are header f ields. The remaining fields are detail f ields. # 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. 19. SHIP TO ADDRESS 1. CHAR 35 shipaddr1_invoicec. 20. SHIP TO ADDRESS 2. CHAR 35 shipaddr2_invoicec. 21. SHIP TO ADDRESS 3. CHAR 35 shipaddr3_invoicec. 22. SHIP TO CITY. CHAR 19 shipcity_invoicec. 23. SHIP TO STATE. CHAR 4 shipstate_invoicec. 24. SHIP TO ZIP CODE. CHAR 9 shipzip_invoicec. 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 (w eight_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 w eight_invoicea. 33. PACKING CODE. CHAR 5 packcd_editp 34. ROUTING. CHAR 2 rout ing_edisv. 35. CARRIER REFERENCE NUMBER. CHAR 30 t rackno_edisv. 36. SCAC CODE. CHAR 4 scac_edisv.



37. SCAC DESCRIPTION (CARRIER NAME). CHAR 35 carrier_edisv. 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. # FIELD DESCRIPTION TYPE SIZE INFO 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 + < addit ion> (if totalchg_editp = 0). - grossext_invoicea + < addit ion> (if totalchg_editp = 1). - netext_invoicea + < addit ion> (if totalchg_editp = 2). - grossext_invoicea - tradedisc_invoicea + < addit ion> (if

totalchg_editp = 3). - netext_invoicea - tradedisc_invoicea + < addit ion> (if totalchg_editp = 4).



< addit ion> 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. 56. SPECIAL CHARGE TOTAL. DEC 10

0 (if speclchg_editp = 0). f rt_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).

# FIELD DESCRIPTION TYPE SIZE NOTES 57. ALLOWANCE CHARGE INDICATOR. CHAR 1 allow ind_editp. 58. ALLOWANCE CHARGE METHOD. CHAR 2 allow meth_editp. 59. ALLOWANCE CHARGE TOTAL. DEC 10

0 (if allow chg_editp = 0). f rt_invoicea (if allow chg_editp = 1). handling_invoicea (if allowchg_editp = 2). ins_invoicea (if allowchg_editp = 3). misc1_invoicea (if allow chg_editp = 4). misc2_invoicea (if allow chg_editp = 5). misc3_invoicea (if allow chg_editp = 6). misc4_invoicea (if allow chg_editp = 7). minsurch_invoicea (if allow chg_editp = 8).

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

(100.00 - 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 89. HEADER MEMO 14. CHAR 30 memoh14_invoicec 90. HEADER MEMO 15. CHAR 30 memoh15_invoicec 91. HEADER MEMO 16. CHAR 30 memoh16_invoicec 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



# FIELD DESCRIPTION TYPE SIZE INFO 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 Sequent ially assign # 117. CUSTOMER P/O SEQUENCE NUMBER. CHAR 4 polineno_invdet2. 118. QUANTITY ORDERED. INT 7 qtyord_invdet2. 119. QUANTITY SHIPPED (INVOICED). INT 7 qtyshp_invdet. 120. RETAIL PRICE. DEC 10 ret lpr_invdet2. 121. SELLING PRICE. DEC 10

If ACF ediiprc = ' 1' : sellprice_invdet. If ACF ediiprc = ' 2' : sellprice_invdet + insrrate_invdet. 122. ITEM ID. CHAR 25 sellitem_invdet2. 123. CUSTOMER PART ID. CHAR 18 cstpart1_invdet2. 124. CUSTOMER PART ID 2. CHAR 18 cstpart2_invdet2. 125. UPC CODE. CHAR 25 upc_invdet2. 126. UNIT OF MEASURE. CHAR 2 uom_invdet2. 127. UNIT OF MEASURE CHARGED. CHAR 2 uom_editp.

uom_invdet (if uom_editp is < NULL> ). 128. ITEM DESCRIPTION. CHAR 18 desc_invdet2. 129. WEIGHT. DEC 8 w eight_invdet. 130. SHIP ORDER STATUS CODE. CHAR 2

Assigned ship order status code. 131. MEMO 1. CHAR 30 altconv_invdet 132. MEMO 2. CHAR 30 memo2_invdet2 133. MEMO 3. CHAR 10 memo3_invdet2 134. MEMO 4 (NUMERIC). DEC 10 memo4_invdet2 135. MEMO 5 (DATE). DATE 6 memo5_invdet2 136. DETAIL MEMO 1. CHAR 30 memod1_invdet2 137. DETAIL MEMO 2. CHAR 30 memod2_invdet2 138. DETAIL MEMO 3. CHAR 30 memod3_invdet2 139. DETAIL MEMO 4. CHAR 30 memod4_invdet2 140. DETAIL MEMO 5. CHAR 30 memod5_invdet2 141. DETAIL MEMO 6. CHAR 30 memod6_invdet2 142. DETAIL MEMO 7. CHAR 30 memod7_invdet2 143. DETAIL MEMO 8. CHAR 30 memod8_invdet2





# FIELD DESCRIPTION TYPE SIZE INFO 144. DETAIL MEMO 9. CHAR 30 memod12_invdet2 148. DETAIL MEMO 13. CHAR 30 memod13_invdet2 149. DETAIL MEMO 14. CHAR 30 memod14_invdet2 150. DETAIL MEMO 15. CHAR 30 memod15_invdet2 151. DETAIL MEMO 16. CHAR 30 memod16_invdet2 152. DETAIL MEMO 17. CHAR 30 memod17_invdet2 153. DETAIL MEMO 18. CHAR 30 memod18_invdet2 154. DETAIL MEMO 19. CHAR 30 memod19_invdet2 155. DETAIL MEMO 20. CHAR 30 memod20_invdet2 156. DETAIL MEMO 21. CHAR 30 memod21_invdet2 157. DETAIL MEMO 22. CHAR 30 memod22_invdet2 158. DETAIL MEMO 23. CHAR 30 memod23_invdet2 159. DETAIL MEMO 24. CHAR 30 memod24_invdet2 160. DETAIL MEMO 25. CHAR 30 memod25_invdet2 161. DETAIL MEMO 26. CHAR 30 memod26_invdet2 162. DETAIL MEMO 27. CHAR 30 memod27_invdet2 163. DETAIL MEMO 28. CHAR 30 memod28_invdet2 164. DETAIL MEMO 29. CHAR 30 memod29_invdet2 165. DETAIL MEMO 30. CHAR 30 memod30_invdet2 166. DETAIL MEMO 31. CHAR 30 memod31_invdet2 167. DETAIL MEMO 32. CHAR 30 emod32_invdet2 168. DETAIL MEMO 33. CHAR 30 memod33_invdet2 169. DETAIL MEMO 34. CHAR 30 memod34_invdet2 170. DETAIL MEMO 35. CHAR 30 memod35_invdet2 171. DETAIL MEMO 36. CHAR 30 memod36_invdet2 172. DETAIL MEMO 37. CHAR 30 memod37_invdet2 173. DETAIL MEMO 38. CHAR 30



memod38_invdet2 174. DETAIL MEMO 39. CHAR 30 memod39_invdet2 175. DETAIL MEMO 40. CHAR 30 memod40_invdet2.



D. Database Fields Updated. 1. ORDERC - EDI Open Order Header Table Layout. Maintain the follow ing f ield to the EDI Open Order Header Table: FIELD NAME SIZE TYPE DESCRIPTION

invf lag_orderc 2 CHAR INVOICE GENERATION FLAG invdate_orderc 4 DATE INVOICE GENERATION DATE invt ime_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 follow ing f ields in the EDI Order Maintenance Header Table: FIELD NAME SIZE TYPE DESCRIPTION

invf lag_ormntc 2 CHAR INVOICE GENERATION FLAG invdate_ormntc 4 DATE INVOICE GENERATION DATE invt ime_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 follow ing f ields in the EDI Open Invoice Header Table: FIELD NAME SIZE TYPE DESCRIPTION

invf lag_invoicec 2 CHAR INVOICE GENERATION FLAG invdate_invoicec 4 DATE INVOICE GENERATION DATE invt ime_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 follow ing f ields to the EDI Invoice History Header Table: FIELD NAME SIZE TYPE DESCRIPTION

invf lag_invoicec 2 CHAR INVOICE GENERATION FLAG invdate_invoicec 4 DATE INVOICE GENERATION DATE invt ime_invoicec 8 CHAR INVOICE GENERATION TIME invuser_invoicec 8 CHAR INVOICE GENERATION USER invbatch_invoicec 10 CHAR INVOICE GENERATION BATCH



E. Screen Layouts. E1. Option Selection Screen.

E2. Sort /ASCII Parameters Screen.



F. ACF Options. For an updated list of acf opt ions use program acf and select edi*



EDIPOG- EDI PURCHASE ORDER ASCII FILE GENERATION A. Modif icat ion Summary. This program provides the capability to generate an ASCII f ile for the purpose of generat ing EDI Purchase Order transact ions (850) to be transmit ted to a vendor through a third party EDI mapping / t ranslat ion / communicat ions product. B. Modif icat ion Detail. The follow ing describes the logic used to process outbound EDI Purchase Order transact ions. B1. Program Flow . The operator w ill be prompted for the follow ing opt ions when generat ing the ASCII f iles. Once all the select ions have been made, the operator w ill be prompted w hether to proceed w ith the creat ion of the ASCII File. See Sect ion C for the screen display formats for the program. 1. Select ion Options Records w ill be selected from the open purchase order table (f ilename: pohdr) w here the memo 4 f ield (f ield name: memo4_pohdr) is set to " EDI" (to indicate EDI transact ions are ut ilized for the vendor) and w here the EDI purchase order generat ion f lag in the applicable EDI Trading Partner Vendor Master record (f ield name: pof lag_editpv) is set to " Y" . Once a purchase order is selected, the system w ill select the corresponding trading partner record from the EDI Trading Partner Vendor Master Table (editpv) w hich w ill be accessed by the division, department, branch and vendor id of each transact ion. The system w ill select the f irst record meeting the condit ions met in the follow ing 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 f ield is def ined in the vendor record through the Vendor Maintenance program (VM) but may be overridden (if desired) on a purchase order basis. The follow ing header select ion opt ions w ill be available for purchase order select ion: 1- By Selected Division ID - select ion based on division_pohdr. 2- By Selected Branch ID - select ion based on branch_pohdr. 3- By Selected Department ID - select ion based on dept_pohdr. 4- By Selected Trading Partner ID - select ion based on partnrid_editpv. (w here 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 - select ion based on vendorid_pohdr.



The follow ing header transact ion select ion opt ions w ill be available. This option w ill default to " 1-All Ungenerated Invoices" .

1- All Ungenerated Purchase Orders. This select ion opt ion w ill select all records from the Open Purchase Order Header table w here the purchase order EDI generat ion f lag in the Open Purchase Order Header table (f ield name: crcardtp_pohdr) is not valued or not set to " Y" for the header select ion opt ions entered.. 2- Selected Ungenerated Purchase Order Numbers. This select ion opt ion w ill select records from the Open Purchase Order table based on the purchase order number(s) entered w here the purchase order EDI generat ion f lag in the Open Purchase Order table (f ield name: crcardtp_pohdr) is not valued or is not set to " Y" for the header select ion opt ion entered. 3- Selected Generated Purchase Order Numbers. This select ion opt ion w ill select records from the Open Purchase Order table based on the purchase order number(s) entered w here the purchase order EDI generat ion f lag in the Open Purchase Order table (f ield name: crcardtp_pohdr) is set to "Y" for the header select ion opt ions entered. 4-Selected Generated EDI Batch. This select ion opt ion w ill 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 (f ield name: edicode_pohdr) and w here the purchase order EDI generat ion f lag in the Open Purchase Order table (f ield name: crcardtp_pohdr) is set to "Y" for the header select ion opt ions entered. 5- Selected Generated Date. This select ion opt ion w ill select records from the Open Purchase Order table based on the purchase order date criteria entered corresponding to the EDI generat ion date (f ield name: crexpirdt_pohdr) and where the purchase order EDI generat ion f lag in the Open Purchase Order table (f ield name: crcardtp_pohdr) is set to "Y" for the header select ion opt ions entered. 2. Sort & Print Options The follow ing sort opt ions w ill be available. The option w ill default to the contents of the ACF EDIPOSRT Option (w hich w ill be init ially set to 4): 1- By Division ID, Trading Partner ID, Purchase Order Number. (f ield names: division_edipoh, partnrid_edipoh, poid_edipoh). 2- By Department ID, Trading Partner ID, Purchase Order Number. (f ield names: dept_edipoh, partnrid_edipoh, poid_edipoh). 3- By Branch ID, Trading Partner ID, Purchase Order Number. (f ield names: branch_edipoh, partnrid_edipoh, poid_edipoh). 4- By Trading Partner ID, Purchase Order Number. (f ield names: partnrid_edipoh, poid_edipoh). 5- By Purchase Order Number. (f ield names: poid_edipoh). 6- By Division ID, Department ID, Trading Partner ID, Purchase Order Number. (f ield names: division_edipoh, dept_edipoh, partnrid_edipoh, poid_edipoh). 7- By Division ID, Branch ID, Trading Partner ID, Purchase Order Number. (f ield names: division_edipoh, branch_edipoh, partnrid_edipoh, poid_edipoh). Note that the detail records w ill have a line sequence number generated. This w ill be generated in purchase order line sequence (f ield name: line_podet). The detail records w ill be sorted by the line number generated (f ield name: seqno_edipod).



The follow ing opt ions w ill be available to def ine the detail records to include in the ASCII f ile: 1- Include all lines. 2- Include only lines w here quantity ordered is present. The dif ference is that opt ion 1 w ill include zero quantity detail lines. The default value w ill be the contents of the ACF EDIPOPRT opt ion. 3. ASCII Files Options. The operator w ill be prompted for the follow ing to def ine the ASCII f ile parameters:

1- ASCII File Field Delimiter. This w ill be the f ield delimiter used in the ASCII f ile output. The default w ill be the contents of the ACF EDIPODEL Option w hich w ill be init ially set to the pipe (| ) symbol 2- ASCII File Name. This w ill be the ASCII f ile name to be generated for the f ile. The f ile name w ill be the format < PREFIX FILE NAME> .< SUFFIX FILE NAME> . The suff ix f ile name w ill default to the contents of the ACF EDIPOFLS Option w hich should be def ined as a 3 character name (i.e. dat). The pref ix f ile name w ill default to the contents of the ACF EDIPOFLP Option. This opt ion should either be set to a 1-8 character name (i.e. edi850po) or to " TODAY" . If the opt ion is set to TODAY, the system w ill use the month and day of the current date and the EDI batch number assigned to the transact ion as the pref ix f ile 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 w ill be the VALID directory on the Unix system w here the ASCII f ile w ill be generated. The default w ill be the contents of the ACF EDIPODIR Option. If an invalid directory is selected, the program w ill display the message " Invalid Directory" , w ait for a brief period and exit the program.

4. General Processing Logic. Once the select ions have been made, the operator w ill be prompted w hether to proceed w ith the creat ion of the ASCII File. If they proceed, the system w ill display the next EDI Purchase Order Batch Number at the base of the screen. This number w ill be assigned to all purchase order records included in the f ile and w ill be set to the contents of the ACF " EDIPOBAT" option. The ACF value w ill be incremented by 1 and updated. The system w ill then select records from the purchase order header & detail tables and any corresponding f iles required and generate records in the EDI Purchase Order Work Files. Once these records are created, the system can perform any data manipulat ion required through a subrout ine. The capability of execut ing a separate custom subrout ine program once the w ork f ile is generated but before the ASCII f ile is generated should be provided. This w ill be provided through an ACF opt ion (edipog_) that w ill w ork in the same manner as the " bill_" ACF opt ions. Once the subrout ine is completed, control w ill return to the main program, w hich w ill generate the ASCII f ile. The system w ill allow values of edipog00 - edipog09 for the rout ine. Once the data manipulat ion is completed, the system w ill generate the ASCII f ile. Once the generat ion is completed, the program w ill update the EDI PO generat ion f ields in the purchase order



tables and go to program end. The ASCII f ile generated may then be transferred to the PC using a standard PC transfer program (i.e. FTP). You w ill need to select the directory the ASCII f ile resides in and the ASCII f ile name. Once the ASCII f ile 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 f ile to the trading partners EDI format. The third party product must then be used to transfer the EDI f ile to the trading partner. A new output opt ion is available to allow the user to FTP the edi purchase orders to the trading partner direct ly from the EDIPOG program. This must be done prior to the print ing of the Purchase Orders. When the follow ing prompt appears the user w ill enter “ F” to setup the FTP process. Proceed w ith creat ing ASCII f ile (Y/N/Ftp/E) ? [ ] The program w ill retrieve the Trading partnerINFO from the ' editpv' table and send it via the FTPSEND program. 5. EDI PO Generat ion Update. The follow ing f ields in the purchase order table w ill be used to audit the creat ion of EDI ASCII f iles: Field Name Field Type Field Size Usage Descript ion edicode_pohdr CHAR 10 EDI Batch Number. crcardtp_pohdr CHAR 4 EDI PO Generat ion Flag. crcardno_pohdr CHAR 19 EDI PO Generat ion User ID. crexpirdt_pohdr DATE 8 EDI PO Generat ion Date. crcardauth_pohdr CHAR 8 EDI PO Generat ion Time. jobrev_podet INT 4 EDI PO Line Number Assigned. The follow ing f ields w ill be set in the purchase order header table (pohdr) once the ASCII f ile has been created. Note that the updating w ill only occur w hen processing purchase orders not previously generated (header transact ion selection opt ions 1 and 2):

- The EDI PO Generat ion Flag w ill be set to " Y" (crcardtp_pohdr). - The EDI PO Generat ion Date w ill be set to the current date (crexpirdt_pohdr). - The EDI PO Generat ion Time w ill be set to the current t ime (crcardauth_pohdr). - The EDI PO Generat ion User w ill be set to the user performing the generat ion

(crcardno_pohdr). - The EDI PO Generat ion Batch Number w ill be set to the contents of the ACF

" EDIPOBAT" opt ion (edicode_pohdr). If the trading partner purchase order print f lag is not set to " Y" (poprt f lg_editpv), the follow ing f ields w ill be set in the Open Purchase Order Header table (pohdr) and Open Purchase Order Detail table (podet): - The purchase order print f lag w ill be set to " N" (print f lag_pohdr). - The purchase order revised f lag w ill be set to " N" (porevised_pohdr). - The purchase order line print f lag w ill be set to " N" on all detail lines for the purchase order (lineprint_podet). - The purchase order line revised f lag w ill be set to "N" on all detail lines for the purchase order (linerevsd_podet). - The jobrev_podet f ield (represent ing the ASCII f ile line number assigned) w ill be set incrementally for each line in PO line number sequence, start ing w ith 1. For example, if a PO has line numbers 10, 30 and 40, this f ield w ill be set to 1 on line 10, 2 on line 30 and 3 on line 40.





6. EDI Dow nload Record Generat ion Detail Logic. The system w ill f irst remove all records from the EDI Purchase Order Dow nload Tables (f ile names: edipoh, edipod). Note that this requires that only one user access the EDIPOG program at a t ime. Security w ill be setup to prevent mult iple users from accessing the program. 6A. Purchase Order Header Logic. The system w ill select records from the Purchase Order Header Table (f ile name: pohdr) w hich meet the select ion criteria def ined above. Once a purchase order is selected, the system w ill select the corresponding trading partner record from the EDI Trading Partner Vendor Master Table (editpv) to access the Trading Partner information. The table w ill be accessed by the division, department, branch and vendor id of the transact ion in the follow ing hierarchy and w ill select the record of the f irst condit ion 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 w ill then select the freight payment method descript ion (f ield name: fpdesc_frtpaymeth) from the Freight Payment Method Table (f ile name: f rtpaymeth) for the freight payment method on the purchase order (criteria: where fpcode_frtpaymeth = frtpay_pohdr). The system w ill then select the Terms Table record (f ile name: terms) w here the terms code corresponds to the terms code on the transact ion (criteria: w here code_terms = poterms_pohdr). The system w ill select the terms description, due days, discount days and discount percentage for the terms code selected (f ield names: desc_terms, due_days_terms, trm_days_terms, trm_pcnt_terms). The system w ill then select the EDI Terms Table record (f ile name: editerm) w here the trading partner and terms codes correspond to those on the purchase order (criteria: w here partnrid_editerm = partnrid_editp and terms_cd_editerm = poterms_pohdr). The system w ill select the terms type and terms basis date codes (f ield names: termtype_editerm, termbase_editerm). If a record is not found, the f ields w ill not be valued in the ASCII f ile. The system w ill then select the EDI Ship Via record (f ilename: edisv) w here the trading partner and ship via codes correspond to those on the transact ion (criteria: where partnrid_edisv = partnrid_editp and svcode_edisv = shipvia_pohdr). The system w ill select the rout ing, carrier name/rout ing descript ion and the SCAC code (f ield names: rout ing_edisv, carrier_edisv, scac_edisv). If a record is not found, the f ields w ill not be valued in the ASCII f ile. The system w ill then select the buyer name from the buyer table (f ilename: buyer) w here the buyer id matches the buyer id on the purchase order (id_buyer = buyer_pohdr). If the buyer record is not found, the system w ill use the buyer id on the purchase order instead of the buyer name.



The system w ill select the bill to name from the division, department or branch master table, based on the contents of the ACF " EDIPOADR" opt ion and the corresponding f ield in the purchase order header: EDI Field Name Next-Generat ion Field Descr. Next-Generat ion Field Name. - Customer Name. Your Division name. name_division. - If ACF opt ion = " 1" - (based on division_division = division_pohdr). Your Department name. name_dept. - If ACF opt ion = " 2" - (based on dept id_dept = dept_pohdr). Your Branch name. name_branch. - If ACF opt ion = " 3" - (based on id_branch = branch_pohdr). If the trading partner output state format (f ield name: statefrm_editpv) is set to " 1" , the system w ill only output the f irst 2 characters of the 4 character state f ield. If set to " 2" , the full 4 character state f ield w ill be output. If the trading partner output zip format (f ield name: zipform_editpv) is set to " 1" , the system w ill only output the f irst 5 characters of the 10 character zip code f ield. If the format is set to " 2" , the system w ill only output the f irst 9 characters of the 10 character zip code f ield. If the format is set to " 3" , the system w ill output the full 10 character zip code f ield. If the trading partner output date format (f ield name: dateform_editpv) is set to " 1" , all dates w ill be output in the format "YYMMDD" . Otherw ise, the dates w ill be output in the format " MMDDYY" . The system w ill then generate a record in the EDI Purchase Order Dow nload Header Table (f ile name: edipoh).



6B. Purchase Order Detail Logic. The system w ill then select records from the Purchase Order Detail Table (f ile name: podet) for the purchase order entered (w here poid_podet = poid_pohdr). For each line item of the purchase order, the system w ill assign and increment the purchase order line number on the purchase order starting w ith 1. For example, if there are 3 lines on the purchase order w ith line numbers 10, 30 and 40, ASCII f ile line " 001" w ill be line 10, ASCII f ile line " 002" w ill be line 30 and ASCII f ile line " 003" w ill be line 40. The line number assigned w ill be updated to a Purchase Order Detail Table f ield (f ield name: jobrev_podet). The system w ill select the vendor part id (f ield name: venpart_vixref) f rom the Vendor Item Cross-Reference Table (f ile name: vixref) w here the vendor id and item id correspond to the purchase order detail record and w here the purchase order date is w ithin 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 def ined 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 f ield. 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 f ield (i.e. item cross-reference) instead, if desired. The system w ill determine if a corresponding UPC code exists by select ing a single record item interchange id (f ield name: interchgid_cixref) f rom the Item Interchange Table (f ile name: cixref) for the item id (criteria: where ouritemid_cixref = itemid_podet and rectype_cixref = " 2" and memo2_cixref = "UPC" ). Note that this w ill be selected only if there is ONE record in the table w hich meets the criteria. The system w ill then determine the total number of detail lines in the Purchase Order Detail Table (f ile name: podet; criteria: select count(* ) f rom podet w here poid_podet = poid_pohdr). The system w ill determine the quantity and unit of measure to send, based on the criteria def ined below : If the trading partner unit of measure method (pouommth_editpv) is set to " 0" , the system w ill alw ays 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 w ill use the quantity ordered and the primary unit of measure. If there is an alternate unit of measure quantity, the system w ill 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 w ill alw ays match the trading partners. If the method is set to " 1" , the system w ill alw ays use the default unit of measure from the trading partner record (pouom_editpv). This assumes that you are always ut ilizing a single unit of measure w ith the trading partner and that this is the primary unit of measure in the purchase order detail record.



If the method is set to " 2" , the system w ill f irst at tempt to convert the unit of measure for the purchase order detail line (primary or alternate, based on the logic def ined 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 f ields partnrid_ediuom, itemid_ediuom, uom_ediuom), the system w ill 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 w ill 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 def ined for the trading partner, the system w ill use the primary or alternate unit of measure in the purchase order detail record, based on the logic def ined for method zero. The cost ing unit of measure to be sent w ill be determined based on the trading partner unit of measure method as w ell. If the trading partner unit of measure method (pouommth_editpv) is set to " 0" , the system w ill alw ays send the cost ing unit of measure (cost ing_um_podet) in the purchase order detail record. This method assumes that your unit of measure codes w ill alw ays match the trading partners. If the method is set to " 1" , the system w ill alw ays use the default unit of measure from the EDI Trading Partner Vendor Master record (pouom_editpv). This assumes that you are alw ays ut ilizing a single unit of measure w ith the trading partner and that this is the cost ing unit of measure on the purchase order detail line. If the method is set to " 2" , the system w ill f irst at tempt to convert the cost ing 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 f ields partnrid_ediuom, itemid_ediuom, uom_ediuom), the system w ill 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 w ill 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 def ined for the trading partner, the system w ill use the po cost ing unit of measure on the purchase order detail line. If the trading partner output date format (f ield name: dateform_editpv) is set to " 1" , all dates w ill be output in the format "YYMMDD" . Otherw ise, the dates w ill be output in the format " MMDDYY" . The system w ill then generate a record in the EDI Purchase Order Dow nload Detail Table (f ile name: edipod). 6C. Purchase Order Header/Detail Summary Logic. For each purchase order in the EDI Purchase Order Dow nload Header Table (f ile name: edipoh), the system w ill determine the total number of detail lines and the total quant ity in the EDI Purchase Order Dow nload Detail Table and update the corresponding f ields in the header table (f ile name: edipodet; criteria: select count(* ) f rom edipod w here poid_edipod = poid= edipoh; quant ity criteria: select sum(po_qty_edipod) from edipod w here poid_edipod = poid_ edipoh). Options are provided for: - Generat ing separate header and detail records in the ASCII f ile. - A f ixed format opt ion w ith no delimiter between f ields. - Allow ing an opt ion for implied decimal point in decimal f ields.



C. Screen Display Layouts. 1. Option Select ion Screen.

2. Sort/ASCII Parameters Screen.



ACF Options for edipog processing - * * * view all edi opt ions using edi* from the acf pgm * * *



E. Outbound Vendor Purchase Order ASCII File Definit ion (850) - Header/Detail Combined Formt. The follow ing is a layout of the f ields in the outbound ASCII f ile in f ield number sequence w hich w ill be dow nloaded by the system. All f ields w ill be lef t just if ied. Fields 1 to 107 are header f ields and f ields 108 to 175 are detail f ields. Note that if there are mult iple detail lines for a purchase order, the header information w ill 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 bt look_editpv bt look_edipoh 10. TRANSACTION DATE. DATE 6 TODAY - Generat ion Dt t randate_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 t rantype_pohdr = " DP" (Drop Ship) 20. SHIP TO NAME. CHAR 27 vsname_pohdr If t rantype_pohdr = “ DP” (Drop Ship) vsname_edipoh 21. SHIP TO ADDRESS 1. CHAR 27 vsaddr1_pohdr If t rantype_pohdr = DP vsaddr1_edipoh 22. SHIP TO ADDRESS 2. CHAR 27 vsaddr2_pohdr (If t rantype_pohdr = DP) vsaddr2_edipoh 23. SHIP TO ADDRESS 3. CHAR 27 vsaddr3_pohdr (If t rantype_pohdr = DP) vsaddr3_edipoh



24. SHIP TO CITY. CHAR 18 vscity_pohdr. (If t rantype_pohdr = DP) vscity_edipoh

25. SHIP TO STATE. CHAR 4 vsstate_pohdr (If t rantype_pohdr = DP) vsstate_edipoh 26. SHIP TO COUNTRY. CHAR 10 vcountry_pohdr (If t rantype_pohdr = DP) vscntry_edipoh 27. SHIP TO ZIP CODE. CHAR 10 vszip_pohdr (If t rantype_pohdr = DP) vszip_edipoh # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 28. SHIP TO ATTENTION. CHAR 27 vsattn_pohdr (If t rantype_pohdr = DP) vsattn_edipoh 29. SHIP TO PHONE NUMBER. CHAR 15 vsphone_pohdr (If t rantype_pohdr = DP) vsphone_edipoh 30. VENDOR SHIP TO ID. CHAR 10 vshiptoid_pohdr

(If t rantype_pohdr = DP) vshipto_edipoh 31. TRANSACTION CODE. CHAR 2 potrancd_editpv transcd_edipoh. 32. TRANSACTION TYPE. CHAR 2 potranty_editpv t ranstype_edipoh. 33. CONTRACT NUMBER. CHAR 20 contract_pohdr contract_edipoh 34. ROUTING. CHAR 2 rout ing_edisv rout ing_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 t rmethod_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 t rm_pcnt_terms trm_pcnt_edipoh Format: " xxx.xx" . Impled: " xxxxx" 44. TERMS DISCOUNT DUE DATE. DATE 6 FUTURE USE. t rmdiscdt_edipoh. 45. TERMS DISCOUNT DAYS DUE. INT 3 trm_days_terms t rm_days_edipoh 46. TERMS NET DUE DATE. DATE 6 FUTURE USE. t rmnetdt_edipoh 47. TERMS NET DAYS. INT 3 due_days_terms due_days_edipoh. 48. TERMS DISCOUNT AMOUNT. DEC 10 FUTURE USE. t rm_disc_edipoh. 49. TERMS DESCRIPTION CHAR 20 desc_terms. t rm_desc_edipoh. 50. ALLOWANCE / CHARGE INDICATOR. CHAR 1 FUTURE USE. allow ind_edipoh.



51. SPECIAL SERVICES CODE. CHAR 10 FUTURE USE. spsrvcd_edipoh. 52. ALLOWANCE / CHARGE METHOD OF HANDLG. CHAR 2 FUTURE USE. allow meth_edipoh. 53. ALLOWANCE OR CHARGE NUMBER. CHAR 16 FUTURE USE. allow num_edipoh. 54. ALLOWANCE OR CHARGE RATE. DEC 6 FUTURE USE. allow rate_edipoh. 55. ALLOWANCE OR CHARGE TOTAL AMOUNT. DEC 10 FUTURE USE. allow tot_edipoh. 56. ALLOWANCE OR CHARGE DESCRIPTION. CHAR 80 FUTURE USE. allow desc_edipoh. 57. SPECIAL CHARGE OR ALLOWANCE CODE. CHAR 3 FUTURE USE. allow cd_edipoh. 58. PURCHASE ORDER QUANTITY. INT 7 (sum (po_qty_podet)). po_qty_edipoh. sum(po_qty_edipod). # 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 poextw t_pohdr. poextw t_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. pow tbase_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 conf irming_pohdr conf irming_edipoh. 69. CONFIRM TO. CHAR 15 conf irmto_pohdr. conf irmto_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 w orkcntr_pohdr w orkcntr_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.



# 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 f illed). poseq_edipod Format: "XX" 112. VENDOR PART ID - PO. CHAR 18 vendpart_podet. vendpart_edipod. 113. VENDOR PART ID - VENDOR. CHAR 18 venpart_vixref vendpart2_edipod. 114. UPC CODE. CHAR 18 upc_edipod or interchgid_cixref ( if memo2_cixref = “ UPC” and rectype_cixref = ‘ 2’



115. ITEM ID. CHAR 25 itemid_podet. itemid_edipod. 116. ITEM DESCRIPTION 1. CHAR 30 itemdesc_podet desc1_edipod 117. ITEM DESCRIPTION 2. CHAR 30 itemdesc2_podet desc2_edipod # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 118. ITEM CROSS-REFERENCE. CHAR 25 itemxref_podet. xref_edpod. 119. 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. 121. 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. 124. PRICING UNIT OF MEASURE. CHAR 2 cost ing_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 ret lprc_edipod. 127. FREIGHT AMOUNT. DEC 10 FUTURE USE frt_edipod. 128. REQUESTED (WANTED) DATE. DATE 6 datew anted_podet

datewant_edipod. 129. PROMISED DATE. DATE 6 dateprom_pode

dateprom_edipod. 130. CANCEL BY DATE. DATE 6 cancelby_podet. canceldt_edipod. 131. PURCHASE ORDER DATE. DATE 6 podate_podet. podate_edipod. 132. NOT BEFORE DATE. DATE 6 notbefore_podet notbefdt_edipod 133. PO UNIT WEIGHT. DEC 7 pounitw t_podet pounitw t_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 poextw t_podet poextw t_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 dest inat ion_podet. dest intn_edipod. 142. REQUISITION BY. CHAR 12 req_by_podet. req_by_edipod. 143. REQUESTED BY. CHAR 10 request_by_podet. request_by_edipod. 144. BUYER ID. CHAR 2 buyer_podet buyer_edipod 145. WORK CENTER. CHAR 4 w orkcntr_podet

w orkcntr_edipod 146. TAXABLE FLAG. CHAR 1 taxable_podet taxable_edipod # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 147. PO LINE REVISED FLAG. CHAR 1 linerevsd_podet. linerevsd_edipod. 148. PO DETAIL MEMO 1. CHAR 15 memo1_podet. podmemo1_edipod. 149. PO DETAIL MEMO 2. CHAR 15 memo2_podet. podmemo2_edipod. 150. COMMODITY CODE. CHAR 6 commodity_podet. commodity_edipod. 151. CONTRACT NUMBER. CHAR 20 contract_no_podet. contract_edipod. 152. ITEM REVISION LEVEL. CHAR 4 itemrevlvl_podet. itemrevlv_edipod. 153. CUSTOMER ORDER NUMBER. CHAR 10 slsordnum_podet. slsordnum_edipod. 154. CUSTOMER ORDER LINE NUMBER. INT 4 slsordlin_podet. slsordlin_edipod. Format: " XXXX" . 155. CUSTOMER ORDER SUB LINE NUMBER. CHAR 4 slsordsub_podet. slsordsub_edipod. 156. MEMO 1. CHAR 30 FUTURE USE. memo1_edipod. 157. MEMO 2. CHAR 30 FUTURE USE. memo2_edipod. 158. MEMO 3. CHAR 10 FUTURE USE. memo3_edipod. 159. MEMO 4 (NUMERIC). DEC 10 FUTURE USE memo4_edipod Format: " -XXXXXX.XX" Implied: -XXXXXXXX 160. MEMO 5 (DATE). DATE 6 FUTURE USE. memo5_edipod. 161. 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. 175. DETAIL MEMO 15. CHAR 30 FUTURE USE. dmemo15_edipod. Field Type Definit ions: CHAR - Character - Alpha-numeric characters.DATE – Date - Date f ield in format " YYMMDD" or " MMDDYY" format, based on a trading partner f lag. DEC - Decimal - Numeric f ield w ith at least one posit ion to the left and 2 posit ions to the right of the decimal point w ith leading minus sign (if applicable). INT – Integer - Numeric f ields w ith at least 1 posit ion and leading minus sign (if applicable); no fract ional parts included. General Format Requirements: - File generated w ill be in ASCII format. - All records w ill have each f ield delineated w ith a pipe symbol (< 174> ASCII character w hich is represented as | ). - All records w ill be terminated w ith a < CARRIAGE RETURN> < LINE FEED> or < LINE FEED> , based on the ACF " EDIPORDL" opt ion.- All dates w ill be dow nloaded in the format: " YYMMDD" or " MMDDYY" , based on a trading partner f lag.- All alphanumeric character f ields w ill be lef t just if ied. - All quant it ies w ill be dow nloaded in integer format: XXXXXXX. - All w eights w ill be downloaded in Decimal Format: XXXXX.XX. If implied decimal: XXXXXXX. - All prices w ill be dow nloaded in Decimal Format: XXXXXXX.XX. If Implied decimal: XXXXXXXXX - All terms percentages w ill be dow nloaded in Decimal Format: XXX.XX. If implied decimal: XXXXX. - All terms days w ill be dow nloaded in Integer Format: XXX. - All amounts w ill be downloaded in Decimal Format: XXXXXXX.XX If implied decimal: XXXXXXXXX. - All f ields w ill be output to their maximum length, not to the actual length of the f ield based on



ACF opt ion EDIPOLEN. Alpha-numeric character f ields w ill be lef t-just if ied w ith blank follow ing the data. Numeric f ields w ill be right just if ied w ith leading zeroes.



F. Outbound Vendor Purchase Order ASCII File Definit ion (850) - Separate Header/Detail Format. The follow ing is a layout of the f ields in the outbound ASCII f iles in f ield number sequence which w ill be dow nloaded by the system. All f ields w ill be lef t just if ied. Fields 1 to 108 are header f ields w hich w ill be output to the header records and f ields 109 to 177 are detail f ields w hich w ill be output to the detail records. Note that if there are mult iple detail lines for a purchase order, the header information w ill print once follow ed 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 bt look_editpv. bt look_edipoh. 11. TRANSACTION DATE. DATE 6 TODAY - Generat ion Dt. t randate_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 t rantype_pohdr = " DP" (Drop Ship). 21. SHIP TO NAME. CHAR 27 vsname_pohdr. vsname_edipoh. (If t rantype_pohdr = DP) 22. SHIP TO ADDRESS 1. CHAR 27 vsaddr1_pohdr. vsaddr1_edipoh. (If t rantype_pohdr = DP) 23. SHIP TO ADDRESS 2. CHAR 27 vsaddr2_pohdr. vsaddr2_edipoh. (If t rantype_pohdr = DP)



24. SHIP TO ADDRESS 3. CHAR 27 vsaddr3_pohdr. vsaddr3_edipoh. (If t rantype_pohdr = DP) # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 25. SHIP TO CITY. CHAR 18 vscity_pohdr vscity_edipoh. (If t rantype_pohdr = DP) 26. SHIP TO STATE. CHAR 4 vsstate_pohdr vsstate_edipoh (If t rantype_pohdr = DP) 27. SHIP TO COUNTRY. CHAR 10 vcountry_pohdr vscntry_edipoh (If t rantype_pohdr = DP) 28. SHIP TO ZIP CODE. CHAR 10 vszip_pohdr vszip_edipoh (If t rantype_pohdr = DP) 29. SHIP TO ATTENTION. CHAR 27 vsattn_pohdr vsattn_edipoh (If t rantype_pohdr = DP) 30. SHIP TO PHONE NUMBER. CHAR 15 vsphone_pohdrvsphone_edipoh (If t rantype_pohdr = DP) 31. VENDOR SHIP TO ID. CHAR 10 vshiptoid_pohdr vshipto_edipoh (If t rantype_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 rout ing_edisv rout ing_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 t rmethod_edipoh. 39. SHIPMENT METHOD OF PAYMENT. CHAR 4 frtpay_pohdr. f rtpay_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. t rm_pcnt_edipoh. Format: " xxx.xx" . Impled: " xxxxx" 45. TERMS DISCOUNT DUE DATE. DATE 6 FUTURE USE. t rmdiscdt_edipoh. 46. TERMS DISCOUNT DAYS DUE. INT 3 trm_days_terms. t rm_days_edipoh. 47. TERMS NET DUE DATE. DATE 6 FUTURE USE. t rmnetdt_edipoh. 48. TERMS NET DAYS. INT 3 due_days_terms due_days_edipoh.



49. TERMS DISCOUNT AMOUNT. DEC 10 FUTURE USE. t rm_disc_edipoh. 50. TERMS DESCRIPTION CHAR 20 desc_terms. t rm_desc_edipoh. 51. ALLOWANCE / CHARGE INDICATOR. CHAR 1 FUTURE USE. allow ind_edipoh. 52. SPECIAL SERVICES CODE. CHAR 10 FUTURE USE. spsrvcd_edipoh. 53. ALLOWANCE / CHARGE METHOD OF HANDLG.CHAR 2 FUTURE USE. allow meth_edipoh. 54. ALLOWANCE OR CHARGE NUMBER. CHAR 16 FUTURE USE. allow num_edipoh. 55. ALLOWANCE OR CHARGE RATE. DEC 6 FUTURE USE. allow rate_edipoh. # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 56. ALLOWANCE OR CHARGE TOTAL AMOUNT. DEC 10 FUTURE USE. allow tot_edipoh. 57. ALLOWANCE OR CHARGE DESCRIPTION. CHAR 80 FUTURE USE. allow desc_edipoh. 58. SPECIAL CHARGE OR ALLOWANCE CODE. CHAR 3 FUTURE USE. allow cd_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 poextw t_pohdr. poextw t_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. pow tbase_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 conf irming_pohdr. conf irming_edipoh. 70. CONFIRM TO. CHAR 15 conf irmto_pohdr. conf irmto_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 w orkcntr_pohdr w orkcntr_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. # 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" . 110. TRADING PARTNER ID / MAILBOX NUMBER. CHAR 27 partnrid_editp partnrid_edipod. 111. P/O NUMBER. CHAR 10 poid_pohdr. poid_edipod. 112. 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 f illed) Format: " XX" 114. VENDOR PART ID - PO. CHAR 18 vendpart_podet. vendpart_edipod. 115. VENDOR PART ID - VENDOR. CHAR 18 venpart_vixref vendpart2_edipod. 116. UPC CODE. CHAR 18 interchgid_cixref upc_edipod. 117. ITEM ID. CHAR 25 itemid_podet. itemid_edipod. 118. ITEM DESCRIPTION 1. CHAR 30 itemdesc_podet desc1_edipod. 119. ITEM DESCRIPTION 2. CHAR 30 itemdesc2_podet desc2_edipod. 120. ITEM CROSS-REFERENCE. CHAR 25 itemxref_podet. xref_edpod. 121. 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. 123. UNIT PRICE. DEC 10 po_cost_podet po_cost_edipod Format: " -XXXXXX.XX" Implied: -XXXXXXXX # 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. 126. PRICING UNIT OF MEASURE. CHAR 2 cost ing_um_podet. cost_um_edipod. uom_ediuom uom_editpv. 127. EXTENDED COST. DEC 10 extcost_podet. extcost_edipod. Format: " -XXXXXX.XX" Implied: -XXXXXXXX 128. RETAIL PRICE. DEC 10 FUTURE USE. ret lprc_edipod. 129. FREIGHT AMOUNT. DEC 10 FUTURE USE. f rt_edipod. 130. REQUESTED (WANTED) DATE. DATE 6 datewanted_podet. datewant_edipod. 131. PROMISED DATE. DATE 6 dateprom_podet. dateprom_edipod. 132. CANCEL BY DATE. DATE 6 cancelby_podet. canceldt_edipod. 133. PURCHASE ORDER DATE. DATE 6 podate_podet.



podate_edipod. 134. NOT BEFORE DATE. DATE 6 notbefore_podet. notbefdt_edipod. 135. PO UNIT WEIGHT. DEC 7 pounitw t_podet. pounitw t_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 poextw t_podet. poextw t_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. 140. DEPARTMENT ID. CHAR 5 dept_podet dept_edipod. 141. BRANCH ID. CHAR 8 branch_podet branch_edipod. 142. JOB NUMBER. CHAR 10 job_podet job_edipod. 143. DESTINATION. CHAR 10 dest inat ion_podet. dest intn_edipod. 144. REQUISITION BY. CHAR 12 req_by_podet. req_by_edipod. 145. REQUESTED BY. CHAR 10 request_by_podet. request_by_edipod. 146. BUYER ID. CHAR 2 buyer_podet. buyer_edipod. 147. WORK CENTER. CHAR 4 w orkcntr_podet. w orkcntr_edipod. 148. TAXABLE FLAG. CHAR 1 taxable_podet. taxable_edipod. 149. PO LINE REVISED FLAG. CHAR 1 linerevsd_podet. linerevsd_edipod. 150. PO DETAIL MEMO 1. CHAR 15 memo1_podet. podmemo1_edipod. 151. PO DETAIL MEMO 2. CHAR 15 memo2_podet. podmemo2_edipod. 152. COMMODITY CODE. CHAR 6 commodity_podet. commodity_edipod. 153. CONTRACT NUMBER. CHAR 20 contract_no_podet. contract_edipod. # FIELD DESCRIPTION / DESTINATION FIELD TYPE SIZE SOURCE FIELD NAME 154. ITEM REVISION LEVEL. CHAR 4 itemrevlvl_podet. itemrevlv_edipod. 155. CUSTOMER ORDER NUMBER. CHAR 10 slsordnum_podet. slsordnum_edipod. 156. CUSTOMER ORDER LINE NUMBER. INT 4 slsordlin_podet slsordlin_edipod Format: " XXXX" . 157. CUSTOMER ORDER SUB LINE NUMBER. CHAR 4 slsordsub_podet. slsordsub_edipod. 158. MEMO 1. CHAR 30 FUTURE USE. memo1_edipod.



159. MEMO 2. CHAR 30 FUTURE USE. memo2_edipod. 160. MEMO 3. CHAR 10 FUTURE USE. memo3_edipod. 161. MEMO 4 (NUMERIC). DEC 10 FUTURE USE memo4_edipod. Format: " -XXXXXX.XX" Implied: -XXXXXXXX 162. MEMO 5 (DATE). DATE 6 FUTURE USE. memo5_edipod. 163. DETAIL MEMO 1. CHAR 30 FUTURE USE dmemo1_edipod 164. DETAIL MEMO 2. CHAR 30 FUTURE USE dmemo2_edipod. 165. DETAIL MEMO 3. CHAR 30 FUTURE USE dmemo3_edipod. 166. DETAIL MEMO 4. CHAR 30 FUTURE USE dmemo4_edipod. 167. DETAIL MEMO 5. CHAR 30 FUTURE USE dmemo5_edipod. 168. DETAIL MEMO 6. CHAR 30 FUTURE USE dmemo6_edipod. 169. DETAIL MEMO 7. CHAR 30 FUTURE USE dmemo7_edipod. 170. DETAIL MEMO 8. CHAR 30 FUTURE USE dmemo8_edipod. 171. DETAIL MEMO 9. CHAR 30 FUTURE USE dmemo9_edipod. 172. 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



G. Outbound ASCII File Layouts - Fixed Format - Implied Decimal - Separate Header / Details. The follow ing layouts assume that the ASCII f ile is generated to the maximum size w ith no delimiter, that decimal f ields w ill be in the implied decimal format and that header and detail records w ill be generated separately.

Fixed Format - Implied Decimal - Header Record Format.

Start End Posit ion Posit ion Field Descript ion Field Type Field Size 001 003 Record Designator. CHAR 3 (HDR) 004 030 Trading Partner ID. CHAR 27 031 040 PO Number. CHAR 10 041 043 EDI Transact ion Document. CHAR 3 044 053 Customer PO EDI Batch #. CHAR 10 054 080 Bill To Name. CHAR 27 081 115 Bill To ID. CHAR 35 116 ` 150 Sold To ID. CHAR 35 151 185 Ship To ID. CHAR 35 186 187 Bill To ID Indicator. CHAR 2 188 193 Transact ion Date. DATE 6 194 199 Requested Date. DATE 6 200 205 Promised Date. DATE 6 206 211 Cancel By Date. DATE 6 212 217 PO Date. DATE 6 218 223 Not Before Date. DATE 6 224 253 Reference Number CHAR 30 (Future Use) 254 283 Department CHAR 30 (Future Use) 284 303 Remarks. CHAR 20 304 305 Ship To Indicator. CHAR 2 306 332 Ship To Name. CHAR 27 333 359 Ship To Address 1. CHAR 27 360 386 Ship To Address 2. CHAR 27 387 413 Ship To Address 3. CHAR 27 414 431 Ship To City. CHAR 18 432 435 Ship To State. CHAR ` 4 436 445 Ship To Country CHAR 10 446 455 Ship To Zip Code. CHAR 10 456 482 Ship To Attent ion. CHAR 27 483 497 Ship To Phone Number. CHAR 15 498 507 Vendor Ship To ID. CHAR 10 508 509 Transact ion Code. CHAR 2 510 511 Transact ion Type. CHAR 2 512 531 Contract Number. CHAR 20 532 533 Routing. CHAR 2 534 568 Carrier / Rout ing Descript ion. CHAR 35 569 572 SCAC. CHAR 4 573 574 Transportat ion Method/Type Cd CHAR 2



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 575 578 Shipment Method Of Payment. CHAR 4 579 598 Shipmnt Paymnt Method Desc CHAR 20 599 602 Terms Code. CHAR 4 603 604 Terms Type Code. CHAR 2 605 606 Terms Basis Date Code. CHAR 2 607 611 Terms Discount Percent. DECIMAL 5 (#####) 612 617 Terms Discount Due Date DATE 6 (Future Use). 618 620 Terms Discount Days Due. INTEGER 3 (###) 621 626 Terms Net Due Date. DATE 6 (Future Use). 627 629 Terms Net Days. INTEGER 3 (###) 630 638 Terms Discount Amount DECIMAL 9 (#########) (Future Use). 639 658 Terms Descript ion CHAR 20 659 659 Allow ance / Charge Indicator CHAR 1 (Future Use). 660 669 Special Services Code. CHAR 10 (Future Use). 670 671 Allow nce/Charge Hndlng Meth CHAR 2 (Future Use). 672 687 Allow ance or Charge Number. CHAR 16 (Future Use). 688 692 Allow ance or Charge Rate. DECIMAL 5 (#####) (Future Use). 693 701 Allow ance or Charge Total Amt DECIMAL 9 (#########) (Future Use). 702 781 Allow ance or Charge Desc CHAR 80 (Future Use). 782 784 Special Charge / Allow Code CHAR 3 (Future Use). 785 791 PO Total Quantity. INTEGER 7 (#######) 792 795 PO # Of Lines. INTEGER 4 (####) 796 802 PO Weight. DECIMAL 7 (#######) 803 809 PO Volume. DECIMAL 7 (#######) 810 818 PO Total Amount. DECIMAL 9 (#########) 819 820 PO Weight Unit Basis. CHAR 2 (Future Use). 821 822 PO Volume Unit Basis. CHAR 2 (Future Use). 823 826 Division ID. CHAR 4 827 831 Department ID. CHAR 5 832 839 Branch ID. CHAR 8 840 840 Confirmation PO Flag. CHAR 1 841 855 Confirmation To. CHAR 15 856 865 Job Number. CHAR 10 866 890 Misc. Info. 1. CHAR 25 891 915 Misc. Info. 2. CHAR 25 916 940 Misc. Info. 3. CHAR 25 941 955 Deliver To. CHAR 15 956 967 Requested By. CHAR 12 968 987 Buyer Name. CHAR 20 988 991 Work Center. CHAR 4 992 992 Back Order Flag. CHAR 1 993 993 Taxable Flag. CHAR 1



Start End Posit ion Posit ion Field Descript ion Field Type Field Siz 994 994 PO Revised Flag. CHAR 1 995 1000 PO Revision Date. DATE 6 1001 1002 PO Revision Code. CHAR 2 1003 1027 Vendor Note 1. CHAR 25 1028 1052 Vendor Note 2. CHAR 25 1053 1077 Vendor Note 3. CHAR 25 1078 1102 Vendor Note 4. CHAR 25 1103 1127 Vendor Note 5. CHAR 25 1128 1157 Memo 1. CHAR 30 (Future Use). 1158 1187 Memo 2. CHAR 30 (Future Use). 1188 1197 Memo 3. CHAR 10 (Future Use). 1198 1206 Memo 4. DECIMAL 9 (#########). (Future Use). 1207 1212 Memo 5. DATE 6 (Future Use). 1213 1242 Header Memo 1. CHAR 30 (Future Use). 1243 1272 Header Memo 2. CHAR 30 (Future Use). 1273 1302 Header Memo 3. CHAR 30 (Future Use). 1303 1332 Header Memo 4. CHAR 30 (Future Use). 1333 1362 Header Memo 5. CHAR 30 (Future Use). 1363 1392 Header Memo 6. CHAR 30 (Future Use). 1393 1422 Header Memo 7. CHAR 30 (Future Use). 1423 1452 Header Memo 8. CHAR 30 (Future Use). 1453 1482 Header Memo 9. CHAR 30 (Future Use). 1483 1512 Header Memo 10. CHAR 30 (Future Use). 1513 1542 Header Memo 11. CHAR 30 (Future Use). 1543 1572 Header Memo 12. CHAR 30 (Future Use). 1573 1602 Header Memo 13. CHAR 30 (Future Use). 1603 1632 Header Memo 14. CHAR 30 (Future Use). 1633 1662 Header Memo 15. CHAR 30 (Future Use).



Fixed Format - Implied Decimal - Detail Record Format. Start End Posit ion Posit ion Field Descript ion Field Type Field Size 001 003 Record Indicator. CHAR 3 (ITM) 004 030 Trading Partner ID. CHAR 27 031 040 PO Number. CHAR 10 041 044 PO Line Number. INTEGER 4 (####) 045 047 Vendor PO Line Sequence #. INTEGER 3 (###) 048 065 Vendor Part ID - PO. CHAR 18 066 083 Vendor Part ID - Vendor. CHAR 18 084 108 UPC Code. CHAR 25 109 133 Item ID. CHAR 25 134 163 Item Descript ion 1. CHAR 30 164 193 Item Descript ion 2. CHAR 30 194 218 Item Cross-Reference. CHAR 25 219 225 Quantity Ordered. INTEGER 7 (#######) 226 227 Unit Of Measure. CHAR 2 228 236 Unit Price. DECIMAL 9 (#########) 237 245 Unit Price (Pricing U.O.M.) DECIMAL 9 (#########) 246 247 Item Basis Of Unit Price. CHAR 2 (Future Use). 248 249 Pricing Unit Of Measure. CHAR 2 250 258 Extended Cost. DECIMAL 9 (#########) 259 267 Retail Price DECIMAL 9 (#########) (Future Use). 268 276 Freight Amount. DECIMAL 9 (#########) (Future Use). 277 282 Requested Date. DATE 6 283 288 Promised Date. DATE 6 289 294 Cancel By Date. DATE 6 295 300 PO Date. DATE 6 301 306 Not Before Date. DATE 6 307 312 PO Unit Weight. DECIMAL 6 (######) 313 318 PO Unit Volume. DECIMAL 6 (######) 319 320 PO Extended Weight. DECIMAL 6 (######) 325 330 PO Extended Volume. DECIMAL 6 (######) 331 334 Division ID. CHAR 4 335 339 Department ID. CHAR 5 340 347 Branch ID. CHAR 8 348 357 Job Number. CHAR 10 358 367 Dest inat ion CHAR 10 368 379 Requisit ion By. CHAR 12 380 389 Requested By. CHAR 10 390 391 Buyer ID. CHAR 2



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 392 395 Work Center. CHAR 4 396 396 Taxable Flag. CHAR 1 397 397 PO Line Revised Flag. CHAR 1 398 412 PO Detail Memo 1. CHAR 15 413 427 PO Detail Memo 2. CHAR 15 428 433 Commodity Code. CHAR 6 434 453 Contract Number. CHAR 20 454 457 Item Revision Level. CHAR 4 458 467 Customer Order Number. CHAR 10 468 471 Customer Order Line Number. INTEGER 4 (####) 472 475 Customer Order Sub Line No. CHAR 4 476 505 Memo 1. CHAR 30 (Future Use). 506 535 Memo 2. CHAR 30 (Future Use). 536 545 Memo 3. CHAR 10 (Future Use). 546 554 Memo 4. DECIMAL 9 (#########). (Future Use). 555 560 Memo 5. DATE 6 (Future Use). 561 590 Detail Memo 1. CHAR 30 (Future Use). 591 620 Detail Memo 2. CHAR 30 (Future Use). 621 650 Detail Memo 3. CHAR 30 (Future Use). 651 680 Detail Memo 4. CHAR 30 (Future Use). 681 710 Detail Memo 5. CHAR 30 (Future Use). 711 740 Detail Memo 6. CHAR 30 (Future Use). 741 770 Detail Memo 7. CHAR 30 (Future Use. 771 800 Detail Memo 8. CHAR 30 (Future Use). 801 830 Detail Memo 9. CHAR 30 (Future Use). 831 860 Detail Memo 10. CHAR 30 (Future Use). 861 890 Detail Memo 11. CHAR 30 (Future Use). 891 920 Detail Memo 12. CHAR 30 (Future Use). 921 950 Detail Memo 13. CHAR 30 (Future Use). 951 980 Detail Memo 14. CHAR 30 (Future Use). 981 1010 Detail Memo 15. CHAR 30 (Future Use).



H. Outbound ASCII File Layout - Fixed Format - Include Decimal - Separate Header / Detail. The follow ing layouts assume that the ASCII f ile is generated to the maximum size w ith no delimiter, that decimal f ields w ill NOT be in the implied decimal format and that header and detail records w ill be generated separately.

Fixed Format - Includes Decimal - Header Record Format.

Start End Posit ion Posit ion Field Descript ion Field Type Field Size 001 003 Record Designator. CHAR 3 (HDR) 004 030 Trading Partner ID. CHAR 27 031 040 PO Number. CHAR 10 041 043 EDI Transact ion Document. CHAR 3 044 053 Customer PO EDI Batch #. CHAR 10 054 080 Bill To Name. CHAR 27 081 115 Bill To ID. CHAR 35 116 ` 150 Sold To ID. CHAR 35 151 185 Ship To ID. CHAR 35 186 187 Bill To ID Indicator. CHAR 2 188 193 Transact ion Date. DATE 6 194 199 Requested Date. DATE 6 200 205 Promised Date. DATE 6 206 211 Cancel By Date. DATE 6 212 217 PO Date. DATE 6 218 223 Not Before Date. DATE 6 224 253 Reference Number CHAR 30 (Future Use) 254 283 Department CHAR 30 (Future Use) 284 303 Remarks. CHAR 20 304 305 Ship To Indicator. CHAR 2 306 332 Ship To Name. CHAR 27 333 359 Ship To Address 1. CHAR 27 360 386 Ship To Address 2. CHAR 27 387 413 Ship To Address 3. CHAR 27 414 431 Ship To City. CHAR 18 432 435 Ship To State. CHAR ` 4 436 445 Ship To Country CHAR 10 446 455 Ship To Zip Code. CHAR 10 456 482 Ship To Attent ion. CHAR 27 483 497 Ship To Phone Number . CHAR 15 498 507 Vendor Ship To ID. CHAR 10 508 509 Transact ion Code. CHAR 2 510 511 Transact ion Type. CHAR 2 512 531 Contract Number. CHAR 20 532 533 Routing. CHAR 2 534 568 Carrier / Rout ing Descript ion. CHAR 35 569 572 SCAC. CHAR 4 573 574 Transportat ion Method/Type Cd.CHAR 2 575 578 Shipment Method Of Payment. CHAR 4 579 598 Shipment Payment Method DescCHAR 20



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 599 602 Terms Code. CHAR 4 603 604 Terms Type Code. CHAR 2 605 606 Terms Basis Date Code. CHAR 2 607 612 Terms Discount Percent. DECIMAL 6 (###.##) 613 619 Terms Discount Due Date DATE 6 (Future Use). 619 621 Terms Discount Days Due. INTEGER 3 (###) 622 627 Terms Net Due Date. DATE 6 (Future Use). 628 630 Terms Net Days. INTEGER 3 (###) 631 640 Terms Discount Amount DECIMAL 10 (#######.##) (Future Use). 641 660 Terms Descript ion CHAR 20 661 661 Allow ance / Charge Indicator CHAR 1 (Future Use). 662 671 Special Services Code. CHAR 10 (Future Use). 672 673 Allow ance/Charge Handling MethCHAR 2 (Future Use). 674 689 Allow ance or Charge Number. CHAR 16 (Future Use). 690 695 Allow ance or Charge Rate. DECIMAL 6 (###.##) (Future Use). 696 705 Allow ance or Charge Total Amt.DECIMAL 10 (#######.##) (Future Use). 706 785 Allow ance or Charge Descript ion.CHAR 80 (Future Use). 786 788 Special Charge / Allow ance Code.CHAR 3 (Future Use). 789 795 PO Total Quantity. INTEGER 7 (#######) 796 799 PO # Of Lines. INTEGER 4 (####) 800 807 PO Weight. DECIMAL 8 (#####.##) 808 815 PO Volume. DECIMAL 8 (#####.##) 816 825 PO Total Amount. DECIMAL 10 (#######.##) 826 827 PO Weight Unit Basis. CHAR 2 (Future Use). 828 829 PO Volume Unit Basis. CHAR 2 (Future Use). 830 833 Division ID. CHAR 4 834 838 Department ID. CHAR 5 839 839 Branch ID. CHAR 8 847 847 Confirmation PO Flag. CHAR 1 848 862 Confirmation To. CHAR 15 863 872 Job Number. CHAR 10 873 897 Misc. Info. 1. CHAR 25 898 922 Misc. Info. 2. CHAR 25 923 947 Misc. Info. 3. CHAR 25 948 962 Deliver To. CHAR 15 963 974 Requested By. CHAR ` 12 975 994 Buyer Name. CHAR 20 995 998 Work Center. CHAR 4 999 999 Back Order Flag. CHAR 1 1000 1000 Taxable Flag. CHAR 1



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 1001 1001 PO Revised Flag. CHAR 1 1002 1009 PO Revision Date. DATE 6 1009 1010 PO Revision Code. CHAR 2 1011 1035 Vendor Note 1. CHAR 25 1036 1059 Vendor Note 2. CHAR 25 1060 1083 Vendor Note 3. CHAR 25 1084 1107 Vendor Note 4. CHAR 25 1108 1132 Vendor Note 5. CHAR 25 1133 1162 Memo 1. CHAR 30 (Future Use). 1163 1193 Memo 2. CHAR 30 (Future Use). 1194 1203 Memo 3. CHAR 10 (Future Use). 1204 1213 Memo 4. DECIMAL 10 (#######.##). (Future Use). 1214 1219 Memo 5. DATE 6 (Future Use). 1220 1249 Header Memo 1. CHAR 30 (Future Use). 1250 1279 Header Memo 2. CHAR 30 (Future Use). 1280 1309 Header Memo 3. CHAR 30 (Future Use). 1310 1339 Header Memo 4. CHAR 30 (Future Use). 1340 1369 Header Memo 5. CHAR 30 (Future Use). 1370 1399 Header Memo 6. CHAR 30 (Future Use). 1400 1429 Header Memo 7. CHAR 30 (Future Use). 1430 1459 Header Memo 8. CHAR 30 (Future Use). 1460 1489 Header Memo 9. CHAR 30 (Future Use). 1490 1519 Header Memo 10. CHAR 30 (Future Use). 1520 1549 Header Memo 11. CHAR 30 (Future Use). 1550 1579 Header Memo 12. CHAR 30 (Future Use). 1580 1609 Header Memo 13. CHAR 30 (Future Use). 1610 1639 Header Memo 14. CHAR 30 (Future Use). 1640 1669 Header Memo 15. CHAR 30 (Future Use).



Fixed Format - Implied Decimal - Detail Record Format. Start End Posit ion Posit ion Field Descript ion Field Type Field Size 001 003 Record Indicator. CHAR 3 (ITM) 004 030 Trading Partner ID. CHAR 27 031 040 PO Number. CHAR 10 041 044 PO Line Number. INTEGER 4 (####) 045 047 Vendor PO Line Sequence #. INTEGER 3 (###) 048 065 Vendor Part ID - PO. CHAR 18 066 083 Vendor Part ID - Vendor. CHAR 18 084 108 UPC Code. CHAR 25 109 133 Item ID. CHAR 25 134 163 Item Descript ion 1. CHAR 30 164 193 Item Descript ion 2. CHAR 30 194 218 Item Cross-Reference. CHAR 25 219 225 Quantity Ordered. INTEGER 7 (#######) 226 227 Unit Of Measure. CHAR 2 228 237 Unit Price. DECIMAL 10 (#######.##) 238 247 Unit Price (Pricing Unit /Measure).DECIMAL 10 (#######.##) 248 249 Item Basis Of Unit Price. CHAR 2 (Future Use). 250 251 Pricing Unit Of Measure. CHAR 2 252 261 Extended Cost. DECIMAL 10 (#######.##) 262 271 Retail Price DECIMAL 10 (#######.##) (Future Use). 272 281 Freight Amount. DECIMAL 10 (#######.##) (Future Use). 282 287 Requested Date. DATE 6 288 293 Promised Date. DATE 6 294 299 Cancel By Date. DATE 6 300 305 PO Date. DATE 6 306 311 Not Before Date. DATE 6 312 318 PO Unit Weight. DECIMAL 7 (####.##) 319 325 PO Unit Volume. DECIMAL 7 (####.##) 326 332 PO Extended Weight. DECIMAL 7 (####.##) 333 339 PO Extended Volume. DECIMAL 7 (####.##) 340 343 Division ID. CHAR 4 344 348 Department ID. CHAR 5 349 356 Branch ID. CHAR 8 357 366 Job Number. CHAR 10 367 376 Dest inat ion CHAR 10 377 388 Requisit ion By. CHAR 12 389 398 Requested By. CHAR 10 399 400 Buyer ID. CHAR 2



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 401 404 Work Center. CHAR 4 405 405 Taxable Flag. CHAR 1 406 406 PO Line Revised Flag. CHAR 1 407 421 PO Detail Memo 1. CHAR 15 422 436 PO Detail Memo 2. CHAR 15 437 442 Commodity Code. CHAR 6 443 462 Contract Number. CHAR 20 463 466 Item Revision Level. CHAR 4 467 476 Customer Order Number. CHAR 10 477 480 Customer Order Line Number. INTEGER 4 (####) 481 484 Customer Order Sub Line Number.CHAR 4 485 514 Memo 1. CHAR 30 (Future Use). 515 544 Memo 2. CHAR 30 (Future Use). 545 554 Memo 3. CHAR 10 (Future Use). 555 564 Memo 4. DECIMAL 10 (#######.##). (Future Use). 565 570 Memo 5. DATE 6 (Future Use). 571 600 Detail Memo 1. CHAR 30 (Future Use). 601 630 Detail Memo 2. CHAR 30 (Future Use). 631 660 Detail Memo 3. CHAR 30 (Future Use). 661 690 Detail Memo 4. CHAR 30 (Future Use). 691 720 Detail Memo 5. CHAR 30 (Future Use). 721 750 Detail Memo 6. CHAR 30 (Future Use). 751 780 Detail Memo 7. CHAR 30 (Future Use. 781 810 Detail Memo 8. CHAR 30 (Future Use). 811 840 Detail Memo 9. CHAR 30 (Future Use). 841 870 Detail Memo 10. CHAR 30 (Future Use). 871 900 Detail Memo 11. CHAR 30 (Future Use). 901 930 Detail Memo 12. CHAR 30 (Future Use). 931 960 Detail Memo 13. CHAR 30 (Future Use). 961 990 Detail Memo 14. CHAR 30 (Future Use). 991 1020 Detail Memo 15. CHAR 30 (Future Use).



I. Outbound ASCII File Layouts - Fixed Format - Implied Decimal - Combined Header / Details. The follow ing layouts assume that the ASCII f ile is generated to the maximum size w ith no delimiter, that decimal f ields w ill be in the implied decimal format and that header and detail records w ill be generated together.

Fixed Format - Implied Decimal - Combined Header / Detail Format. Start End Posit ion Posit ion Field Descript ion Field Type Field Size 001 003 Record Designator. CHAR 3 (HDR) 004 030 Trading Partner ID. CHAR 27 031 040 PO Number. CHAR 10 041 043 EDI Transact ion Document. CHAR 3 044 053 Customer PO EDI Batch #. CHAR 10 054 080 Bill To Name. CHAR 27 081 115 Bill To ID. CHAR 35 116 ` 150 Sold To ID. CHAR 35 151 185 Ship To ID. CHAR 35 186 187 Bill To ID Indicator. CHAR 2 188 193 Transact ion Date. DATE 6 194 199 Requested Date. DATE 6 200 205 Promised Date. DATE 6 206 211 Cancel By Date. DATE 6 212 217 PO Date. DATE 6 218 223 Not Before Date. DATE 6 224 253 Reference Number CHAR 30 (Future Use) 254 283 Department CHAR 30 (Future Use) 284 303 Remarks. CHAR 20 304 305 Ship To Indicator. CHAR 2 306 332 Ship To Name. CHAR 27 333 359 Ship To Address 1. CHAR 27 360 386 Ship To Address 2. CHAR 27 387 413 Ship To Address 3. CHAR 27 414 431 Ship To City. CHAR 18 432 435 Ship To State. CHAR ` 4 436 445 Ship To Country CHAR 10 446 455 Ship To Zip Code. CHAR 10 456 482 Ship To Attent ion. CHAR 27 483 497 Ship To Phone Number. CHAR 15 498 507 Vendor Ship To ID. CHAR 10 508 509 Transact ion Code. CHAR 2 510 511 Transact ion Type. CHAR 2 512 531 Contract Number. CHAR 20 532 533 Routing. CHAR 2 534 568 Carrier / Rout ing Descript ion. CHAR 35 569 572 SCAC. CHAR 4 573 574 Transportat ion Method/Type Cd.CHAR 2 575 578 Shipment Method Of Payment. CHAR 4 579 598 Shipment Payment Method Descr.CHAR 20



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 599 602 Terms Code. CHAR 4 603 604 Terms Type Code. CHAR 2 605 606 Terms Basis Date Code. CHAR 2 607 611 Terms Discount Percent. DECIMAL 5 (#####) 612 617 Terms Discount Due Date DATE 6 (Future Use). 618 620 Terms Discount Days Due. INTEGER 3 (###) 621 626 Terms Net Due Date. DATE 6 (Future Use). 627 629 Terms Net Days. INTEGER 3 (###) 630 638 Terms Discount Amount DECIMAL 9 (#########) (Future Use). 639 658 Terms Descript ion CHAR 20 659 659 Allow ance / Charge Indicator CHAR 1 (Future Use). 660 669 Special Services Code. CHAR 10 (Future Use). 670 671 Allow ance/Charge Handling MethCHAR 2 (Future Use). 672 687 Allow ance or Charge Number. CHAR 16 (Future Use). 688 692 Allow ance or Charge Rate. DECIMAL 5 (#####) (Future Use). 693 701 Allow ance or Charge Total Amt.DECIMAL 9 (#########) (Future Use). 702 781 Allow ance or Charge Descript ion.CHAR 80 (Future Use). 782 784 Special Charge / Allow ance Code.CHAR 3 (Future Use). 785 791 PO Total Quantity. INTEGER 7 (#######) 792 795 PO # Of Lines. INTEGER 4 (####) 796 802 PO Weight. DECIMAL 7 (#######) 803 809 PO Volume. DECIMAL 7 (#######) 810 818 PO Total Amount. DECIMAL 9 (#########) 819 820 PO Weight Unit Basis. CHAR 2 (Future Use). 821 822 PO Volume Unit Basis. CHAR 2 (Future Use). 823 826 Division ID. CHAR 4 827 831 Department ID. CHAR 5 832 839 Branch ID. CHAR 8 840 840 Confirmation PO Flag. CHAR 1 841 855 Confirmation To. CHAR 15 856 865 Job Number. CHAR 10 866 890 Misc. Info. 1. CHAR 25 891 915 Misc. Info. 2. CHAR 25 916 940 Misc. Info. 3. CHAR 25 941 955 Deliver To. CHAR 15 956 967 Requested By. CHAR 12 968 987 Buyer Name. CHAR 20 988 991 Work Center. CHAR 4 992 992 Back Order Flag. CHAR 1 993 993 Taxable Flag. CHAR 1



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 994 994 PO Revised Flag. CHAR 1 995 1000 PO Revision Date. DATE 6 1001 1002 PO Revision Code. CHAR 2 1003 1027 Vendor Note 1. CHAR 25 1028 1052 Vendor Note 2. CHAR 25 1053 1077 Vendor Note 3. CHAR 25 1078 1102 Vendor Note 4. CHAR 25 1103 1127 Vendor Note 5. CHAR 25 1128 1157 Memo 1. CHAR 30 (Future Use). 1158 1187 Memo 2. CHAR 30 (Future Use). 1188 1197 Memo 3. CHAR 10 (Future Use). 1198 1206 Memo 4. DECIMAL 9 (#########). (Future Use). 1207 1212 Memo 5. DATE 6 (Future Use). 1213 1242 Header Memo 1. CHAR 30 (Future Use). 1243 1272 Header Memo 2. CHAR 30 (Future Use). 1273 1302 Header Memo 3. CHAR 30 (Future Use). 1303 1332 Header Memo 4. CHAR 30 (Future Use). 1333 1362 Header Memo 5. CHAR 30 (Future Use). 1363 1392 Header Memo 6. CHAR 30 (Future Use). 1393 1422 Header Memo 7. CHAR 30 (Future Use). 1423 1452 Header Memo 8. CHAR 30 (Future Use). 1453 1482 Header Memo 9. CHAR 30 (Future Use). 1483 1512 Header Memo 10. CHAR 30 (Future Use). 1513 1542 Header Memo 11. CHAR 30 (Future Use). 1543 1572 Header Memo 12. CHAR 30 (Future Use). 1573 1602 Header Memo 13. CHAR 30 (Future Use). 1603 1632 Header Memo 14. CHAR 30 (Future Use). 1633 1662 Header Memo 15. CHAR 30 (Future Use). 1663 1665 Record Indicator. CHAR 3 (ITM) 1666 1692 Trading Partner ID. CHAR 27 1693 1702 PO Number. CHAR 10 1703 1706 PO Line Number. INTEGER 4 (####) 1707 1709 Vendor PO Line Sequence #. INTEGER 3 (###) 1710 1727 Vendor Part ID - PO. CHAR 18 1728 1745 Vendor Part ID - Vendor. CHAR 18 1746 1770 UPC Code. CHAR 25 1771 1795 Item ID. CHAR 25 1796 1825 Item Descript ion 1. CHAR 30 1826 1855 Item Descript ion 2. CHAR 30



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 1856 1880 Item Cross-Reference. CHAR 25 1881 1887 Quantity Ordered. INTEGER 7 (#######) 1888 1889 Unit Of Measure. CHAR 2 1890 1898 Unit Price. DECIMAL 9 (#########) 1899 1907 Unit Price (Pricing Unit /Measure).DECIMAL 9 (#########) 1908 1909 Item Basis Of Unit Price. CHAR 2 (Future Use). 1910 1911 Pricing Unit Of Measure. CHAR 2 1912 1920 Extended Cost. DECIMAL 9 (#########) 1921 1929 Retail Price DECIMAL 9 (#########) (Future Use). 1930 1938 Freight Amount. DECIMAL 9 (#########) (Future Use). 1939 1944 Requested Date. DATE 6 1945 1950 Promised Date. DATE 6 1951 1956 Cancel By Date. DATE 6 1957 1962 PO Date. DATE 6 1963 1968 Not Before Date. DATE 6 1969 1974 PO Unit Weight. DECIMAL 6 (######) 1975 1980 PO Unit Volume. DECIMAL 6 (######) 1981 1986 PO Extended Weight. DECIMAL 6 (######) 1987 1992 PO Extended Volume. DECIMAL 6 (######) 1993 1996 Division ID. CHAR 4 1997 2001 Department ID. CHAR 5 2002 2009 Branch ID. CHAR 8 2010 2019 Job Number. CHAR 10 2020 2029 Dest inat ion CHAR 10 2030 2041 Requisit ion By. CHAR 12 2042 2051 Requested By. CHAR 10 2052 2053 Buyer ID. CHAR 2 2054 2057 Work Center. CHAR 4 2058 2058 Taxable Flag. CHAR 1 2059 2059 PO Line Revised Flag. CHAR 1 2060 2074 PO Detail Memo 1. CHAR 15 2075 2089 PO Detail Memo 2. CHAR 15 2090 2095 Commodity Code. CHAR 6 2096 2115 Contract Number. CHAR 20 2116 2119 Item Revision Level. CHAR 4 2120 2129 Customer Order Number. CHAR 10 2130 2133 Customer Order Line Number. INTEGER 4 (####) 2134 2137 Customer Order Sub Line Number.CHAR 4



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 2138 2167 Memo 1. CHAR 30 (Future Use). 2168 2197 Memo 2. CHAR 30 (Future Use). 2198 2207 Memo 3. CHAR 10 (Future Use). 2208 2216 Memo 4. DECIMAL 9 (#########). (Future Use). 2217 2222 Memo 5. DATE 6 (Future Use). 2223 2252 Detail Memo 1. CHAR 30 (Future Use). 2253 2282 Detail Memo 2. CHAR 30 (Future Use). 2283 2312 Detail Memo 3. CHAR 30 (Future Use). 2313 2342 Detail Memo 4. CHAR 30 (Future Use). 2343 2372 Detail Memo 5. CHAR 30 (Future Use). 2373 2402 Detail Memo 6. CHAR 30 (Future Use). 2403 2432 Detail Memo 7. CHAR 30 (Future Use. 2433 2462 Detail Memo 8. CHAR 30 (Future Use). 2463 2492 Detail Memo 9. CHAR 30 (Future Use). 2493 2522 Detail Memo 10. CHAR 30 (Future Use). 2523 2552 Detail Memo 11. CHAR 30 (Future Use). 2553 2582 Detail Memo 12. CHAR 30 (Future Use). 2583 2612 Detail Memo 13. CHAR 30 (Future Use). 2613 2642 Detail Memo 14. CHAR 30 (Future Use). 2643 2672 Detail Memo 15. CHAR 30 (Future Use).



J. Outbound ASCII File Layout - Fixed Format - Include Decimal - Combined Header / Detail. The follow ing layouts assume that the ASCII f ile is generated to the maximum size w ith no delimiter, that decimal f ields w ill NOT be in the implied decimal format and that header and detail records w ill be generated together.

Fixed Format - Includes Decimal - Combined Header / Detail Record Format.

Start End Posit ion Posit ion Field Descript ion Field Type Field Size 001 003 Record Designator. CHAR 3 (HDR) 004 030 Trading Partner ID. CHAR 27 031 040 PO Number. CHAR 10 041 043 EDI Transact ion Document. CHAR 3 044 053 Customer PO EDI Batch #. CHAR 10 054 080 Bill To Name. CHAR 27 081 115 Bill To ID. CHAR 35 116 150 Sold To ID. CHAR 35 151 185 Ship To ID. CHAR 35 186 187 Bill To ID Indicator. CHAR 2 188 193 Transact ion Date. DATE 6 194 199 Requested Date. DATE 6 200 205 Promised Date. DATE 6 206 211 Cancel By Date. DATE 6 212 217 PO Date. DATE 6 218 223 Not Before Date. DATE 6 224 253 Reference Number CHAR 30 (Future Use) 254 283 Department CHAR 30 (Future Use) 284 303 Remarks. CHAR 20 304 305 Ship To Indicator. CHAR 2 306 332 Ship To Name. CHAR 27 333 359 Ship To Address 1. CHAR 27 360 386 Ship To Address 2. CHAR 27 387 413 Ship To Address 3. CHAR 27 414 431 Ship To City. CHAR 18 432 435 Ship To State. CHAR ` 4 436 445 Ship To Country CHAR 10 446 455 Ship To Zip Code. CHAR 10 456 482 Ship To Attent ion. CHAR 27 483 497 Ship To Phone Number. CHAR 15 498 507 Vendor Ship To ID. CHAR 10 508 509 Transact ion Code. CHAR 2 510 511 Transact ion Type. CHAR 2 512 531 Contract Number. CHAR 20 532 533 Routing. CHAR 2 534 568 Carrier / Rout ing Descript ion. CHAR 35 569 572 SCAC. CHAR 4



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 573 574 Transportat ion Method/Type Cd.CHAR 2 575 578 Shipment Method Of Payment. CHAR 4 579 598 Shipment Payment Method Descr.CHAR 20 599 602 Terms Code. CHAR 4 603 604 Terms Type Code. CHAR 2 605 606 Terms Basis Date Code. CHAR 2 607 612 Terms Discount Percent. DECIMAL 6 (###.##) 613 619 Terms Discount Due Date DATE 6 (Future Use). 619 621 Terms Discount Days Due. INTEGER 3 (###) 622 627 Terms Net Due Date. DATE 6 (Future Use). 628 630 Terms Net Days. INTEGER 3 (###) 631 640 Terms Discount Amount DECIMAL 10 (#######.##) (Future Use). 641 660 Terms Descript ion CHAR 20 661 661 Allow ance / Charge Indicator CHAR 1 (Future Use). 662 671 Special Services Code. CHAR 10 (Future Use). 672 673 Allow ance/Charge Handling MethCHAR 2 (Future Use). 674 689 Allow ance or Charge Number. CHAR 16 (Future Use). 690 695 Allow ance or Charge Rate. DECIMAL 6 (###.##) (Future Use). 696 705 Allow ance or Charge Total Amt.DECIMAL 10 (#######.##) (Future Use). 706 785 Allow ance or Charge Descript ion.CHAR 80 (Future Use). 786 788 Special Charge / Allow ance Code.CHAR 3 (Future Use). 789 795 PO Total Quantity. INTEGER 7 (#######) 796 799 PO # Of Lines. INTEGER 4 (####) 800 807 PO Weight. DECIMAL 8 (#####.##) 808 815 PO Volume. DECIMAL 8 (#####.##) 816 825 PO Total Amount. DECIMAL 10 (#######.##) 826 827 PO Weight Unit Basis. CHAR 2 (Future Use). 828 829 PO Volume Unit Basis. CHAR 2 (Future Use). 830 833 Division ID. CHAR 4 834 838 Department ID. CHAR 5 839 839 Branch ID. CHAR 8 847 847 Confirmation PO Flag. CHAR 1 848 862 Confirmation To. CHAR 15 863 872 Job Number. CHAR 10 873 897 Misc. Info. 1. CHAR 25 898 922 Misc. Info. 2. CHAR 25 923 947 Misc. Info. 3. CHAR 25 948 962 Deliver To. CHAR 15 963 974 Requested By. CHAR 12



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 975 994 Buyer Name. CHAR 20 995 998 Work Center. CHAR 4 999 999 Back Order Flag. CHAR 1 1000 1000 Taxable Flag. CHAR 1 1001 1001 PO Revised Flag. CHAR 1 1002 1009 PO Revision Date. DATE 6 1009 1010 PO Revision Code. CHAR 2 1011 1035 Vendor Note 1. CHAR 25 1036 1059 Vendor Note 2. CHAR 25 1060 1083 Vendor Note 3. CHAR 25 1084 1107 Vendor Note 4. CHAR 25 1108 1132 Vendor Note 5. CHAR 25 1133 1162 Memo 1. CHAR 30 (Future Use). 1163 1193 Memo 2. CHAR 30 (Future Use). 1194 1203 Memo 3. CHAR 10 (Future Use). 1204 1213 Memo 4. DECIMAL 10 (#######.##). (Future Use). 1214 1219 Memo 5. DATE 6 (Future Use). 1220 1249 Header Memo 1. CHAR 30 (Future Use). 1250 1279 Header Memo 2. CHAR 30 (Future Use). 1280 1309 Header Memo 3. CHAR 30 (Future Use). 1310 1339 Header Memo 4. CHAR 30 (Future Use). 1340 1369 Header Memo 5. CHAR 30 (Future Use). 1370 1399 Header Memo 6. CHAR 30 (Future Use). 1400 1429 Header Memo 7. CHAR 30 (Future Use). 1430 1459 Header Memo 8. CHAR 30 (Future Use). 1460 1489 Header Memo 9. CHAR 30 (Future Use). 1490 1519 Header Memo 10. CHAR 30 (Future Use). 1520 1549 Header Memo 11. CHAR 30 (Future Use). 1550 1579 Header Memo 12. CHAR 30 (Future Use). 1580 1609 Header Memo 13. CHAR 30 (Future Use). 1610 1639 Header Memo 14. CHAR 30 (Future Use). 1640 1669 Header Memo 15. CHAR 30 (Future Use). 1670 1672 Record Indicator. CHAR 3 (ITM) 1673 1699 Trading Partner ID. CHAR 27 1700 1709 PO Number. CHAR 10 1710 1713 PO Line Number. INTEGER 4 (####) 1714 1716 Vendor PO Line Sequence #. INTEGER 3 (###) 1717 1734 Vendor Part ID - PO. CHAR 18 1735 1752 Vendor Part ID - Vendor. CHAR 18



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 1753 1777 UPC Code. CHAR 25 1778 1802 Item ID. CHAR 25 1803 1832 Item Descript ion 1. CHAR 30 1833 1862 Item Descript ion 2. CHAR 30 1863 1887 Item Cross-Reference. CHAR 25 1888 1894 Quantity Ordered. INTEGER 7 (#######) 1895 1896 Unit Of Measure. CHAR 2 1897 1906 Unit Price. DECIMAL 10 (#######.##) 1907 1916 Unit Price (Pricing U.O.M.) DECIMAL 10 (#######.##) 1917 1918 Item Basis Of Unit Price. CHAR 2 (Future Use). 1919 1920 Pricing Unit Of Measure. CHAR 2 1921 1930 Extended Cost. DECIMAL 10 (#######.##) 1931 1940 Retail Price DECIMAL 10 (#######.##) (Future Use). 1941 1950 Freight Amount. DECIMAL 10 (#######.##) (Future Use). 1951 1956 Requested Date. DATE 6 1957 1962 Promised Date. DATE 6 1963 1968 Cancel By Date. DATE 6 1969 1974 PO Date. DATE 6 1975 1980 Not Before Date. DATE 6 1981 1987 PO Unit Weight. DECIMAL 7 (####.##) 1988 1994 PO Unit Volume. DECIMAL 7 (####.##) 1995 2001 PO Extended Weight. DECIMAL 7 (####.##) 2002 2008 PO Extended Volume. DECIMAL 7 (####.##) 2009 2012 Division ID. CHAR 4 2013 2017 Department ID. CHAR 5 2018 2025 Branch ID. CHAR 8 2026 2035 Job Number. CHAR 10 2036 2045 Dest inat ion CHAR 10 2046 2057 Requisit ion By. CHAR 12 2058 2067 Requested By. CHAR 10 2068 2069 Buyer ID. CHAR 2 2070 2073 Work Center. CHAR 4 2074 2074 Taxable Flag. CHAR 1 2075 2075 PO Line Revised Flag. CHAR 1 2076 2090 PO Detail Memo 1. CHAR 15 2091 2105 PO Detail Memo 2. CHAR 15 2106 2111 Commodity Code. CHAR 6 2112 2131 Contract Number. CHAR 20 2132 2135 Item Revision Level. CHAR 4 2136 2145 Customer Order Number. CHAR 10 2146 2149 Customer Order Line Number. INTEGER 4 (####)



Start End Posit ion Posit ion Field Descript ion Field Type Field Size 2150 2153 Cust. Order Sub Line Number. CHAR 4 2154 2183 Memo 1. CHAR 30 (Future Use). 2184 2213 Memo 2. CHAR 30 (Future Use). 2214 2223 Memo 3. CHAR 10 (Future Use). 2224 2233 Memo 4. DECIMAL 10 (#######.##). (Future Use). 2234 2239 Memo 5. DATE 6 (Future Use). 2240 2269 Detail Memo 1. CHAR 30 (Future Use). 2270 2299 Detail Memo 2. CHAR 30 (Future Use). 2300 2329 Detail Memo 3. CHAR 30 (Future Use). 2330 2359 Detail Memo 4. CHAR 30 (Future Use). 2360 2389 Detail Memo 5. CHAR 30 (Future Use). 2390 2419 Detail Memo 6. CHAR 30 (Future Use). 2420 2449 Detail Memo 7. CHAR 30 (Future Use. 2450 2479 Detail Memo 8. CHAR 30 (Future Use). 2480 2509 Detail Memo 9. CHAR 30 (Future Use). 2510 2539 Detail Memo 10. CHAR 30 (Future Use). 2540 2569 Detail Memo 11. CHAR 30 (Future Use). 2570 2599 Detail Memo 12. CHAR 30 (Future Use). 2600 2629 Detail Memo 13. CHAR 30 (Future Use). 2630 2659 Detail Memo 14. CHAR 30 (Future Use). 2660 2689 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 bt look_edipoh char 2 10 trandate_edipoh char 6 11 datew ant_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 30 17 department_edipoh char 30 18 remarks_edipoh char 20 19 bslook_edipoh char 2 20 vsname_edipoh char 27 21 vsaddr1_edipoh char 27 22 vsaddr2_edipoh char 27 23 vsaddr3_edipoh char 27



# Field Name Field Type Field Size 24 vscity_edipoh char 18 25 vsstate_edipoh char 4 26 vscntry_edipoh char 10 27 vszip_edipoh char 10 28 vsattn_edipoh char 27 29 vsphone_edipoh char 15 30 vshipto_edipoh char 10 31 transcd_edipoh char 2 32 transtype_edipoh char 2 33 contract_edipoh char 20 34 rout ing_edipoh char 2 35 carrier_edipoh char 35 36 scac_edipoh char 4 37 trmethod_edipoh char 2 38 frtpay_edipoh char 4 39 fpdesc_edipoh char 20 40 poterms_edipoh char 4 41 termtype_edipoh char 2 42 termbase_edipoh char 2 43 trm_pcnt_edipoh decimal 10 44 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 10 49 trm_desc_edipoh char 20 50 allow ind_edipoh char 1 51 spsrvcd_edipoh char 10 52 allow meth_edipoh char 2 53 allow num_edipoh char 16 54 allow rate_edipoh decimal 10 55 allow tot_edipoh decimal 10 56 allow desc_edipoh char 80 57 allow cd_edipoh char 3 58 po_qty_edipoh decimal 10 59 po_lines_edipoh integer 4 60 poextw t_edipoh decimal 10 61 poextvl_edipoh decimal 10 62 pototal_edipoh decimal 10 63 pow tbase_edipoh char 2 64 povlbase_edipoh char 2 65 division_edipoh char 4 66 dept_edipoh char 5 67 branch_edipoh char 8 68 conf irming_edipoh char 1 69 conf irmto_edipoh char 15 70 job_edipoh char 10 71 miscinfo1_edipoh char 25 72 miscinfo2_edipoh char 25 73 miscinfo3_edipoh char 25 74 deliverto_edipoh char 15 75 req_by_edipoh char 12



# Field Name Field Type Field Size 76 buyer_edipoh char 20 77 w orkcntr_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 25 84 vendnote2_edipoh char 25 85 vendnote3_edipoh char 25 86 vendnote4_edipoh char 25 87 vendnote5_edipoh char 25 88 memo1_edipoh char 30 89 memo2_edipoh char 30 90 memo3_edipoh char 10 91 memo4_edipoh decimal 10 92 memo5_edipoh char 6 93 hmemo1_edipoh char 30 94 hmemo2_edipoh char 30 95 hmemo3_edipoh char 30 96 hmemo4_edipoh char 30 97 hmemo5_edipoh char 30 98 hmemo6_edipoh char 30 99 hmemo7_edipoh char 30 100 hmemo8_edipoh char 30 101 hmemo9_edipoh char 30 102 hmemo10_edipoh char 30 103 hmemo11_edipoh char 30 104 hmemo12_edipoh char 30 105 hmemo13_edipoh char 30 106 hmemo14_edipoh char 30 107 hmemo15_edipoh char 30 Indexes: index edipoh_idx1 on edipoh(partnrid_edipoh)index edipoh_idx2 on edipoh(poid_edipoh)



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 25 10 desc1_edipod char 30 11 desc2_edipod char 30 12 xref_edipod char 25 13 po_qty_edipod decimal 10 14 po_um_edipod char 2 15 po_cost_edipod decimal 10 16 po_cost2_edipod decimal 10 17 pocstbase_edipod char 2 18 cost_um_edipod char 2 19 extcost_edipod decimal 10 20 ret lprc_edipod decimal 10 21 frt_edipod decimal 10 22 datew ant_edipod char 6 23 dateprom_edipod char 6 24 canceldt_edipod char 6 25 podate_edipod char 6 26 notbefdt_edipod char 6 27 pounitw t_edipod decimal 10 28 pounitvl_edipod decimal 10 29 poextw t_edipod decimal 10 30 poextvl_edipod decimal 10 31 division_edipod char 4 32 dept_edipod char 5 33 branch_edipod char 8 34 job_edipod char 10 35 dest intn_edipod char 10 36 req_by_edipod char 12 37 request_by_edipod char 10 38 buyer_edipod char 2 39 w orkcntr_edipod char 4 40 taxable_edipod char 1 41 linerevsd_edipod char 1 42 podmemo1_edipod char 15 43 podmemo2_edipod char 15 44 commodity_edipod char 6 45 contract_edipod char 20 46 itemrevlv_edipod char 4 47 slsordnum_edipod char 10 48 slsordlin_edipod integer 4 49 slsordsub_edipod char 4



# Field Name Field Type Field Size 50 memo1_edipod char 30 51 memo2_edipod char 30 52 memo3_edipod char 10 53 memo4_edipod decimal 10 54 memo5_edipod char 6 55 dmemo1_edipod char 30 56 dmemo2_edipod char 30 57 dmemo3_edipod char 30 58 dmemo4_edipod char 30 59 dmemo5_edipod char 30 60 dmemo6_edipod char 30 61 dmemo7_edipod char 30 62 dmemo8_edipod char 30 63 dmemo9_edipod char 30 64 dmemo10_edipod char 30 65 dmemo11_edipod char 30 66 dmemo12_edipod char 30 67 dmemo13_edipod char 30 68 dmemo14_edipod char 30 69 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 (Conf lict). Opt ion Value: EDIPOG



EDIMNTU- EDI ORDER MAINTENANCE FILE UPDATE. A. Program Summary. The program w ill select any orders and/or order lines w hich have been deleted w hich w ere EDI orders, generate records in the EDI Order Maintenance Header and Detail tables for the transact ions and remove the applicable records from the EDI Open Order Header and Detail tables. The program has the capability of being run interact ively or as an MISCRON job. B. Program Detail. The operator w ill be prompted if they w ant to proceed w ith the program. The f irst pass of the program w ill determine Open Order Header records that have been deleted. The system w ill 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 w ill access the Order Maintenance Header record (ormnta) for the transact ion to determine the deleted record (based on the transact ion having a status code of ' D' in the maint_code_ordera f ield). The system w ill then generate a record in the EDI Order Maintenance Header table (ormntc) w ith the data in the EDI Open Order Header record (orderc). The serial number assigned to the deletion record (maint_code_ordera) w ill be updated to the EDI Order Maintenance Header table as w ell. The system w ill generate records in the EDI Order Maintenance Detail table (ormntd2) w ith the data from all the records for the order in the EDI Open Order Detail table (orddet2) along w ith the serial number assigned to the delet ion (maint_ser_ordera). If for any reason a corresponding record is not found in the Order Maintenance table (ormnta), the system w ill assign a serial number of ' 9999999999' to the EDI Order Maintenance Header record (ormntc) and the EDI Order Maintenance Detail records (ormntd2) in order to f lag these records. The corresponding records in the EDI Order Header Table (orderc) and EDI Order Detail Table (orddet2) w ill be deleted after the maintenance records are generated. The second pass of the program w ill determine order detail lines that have been deleted. The system w ill 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 w ill access the Order Maintenance Detail record (ormntd) for the transact ion w hich has a status code of ' D' in the maint_code_orddet f ield. The system w ill generate a record in the EDI Order Maintenance Detail table (ormntd2) w ith the data in the EDI Open Order Detail record (orddet2). The serial number assigned to the delet ion record (maint_code_orddet) w ill be updated to the EDI Order Maintenance Detail table as w ell. If for any reason a corresponding record is not found in the Order Maintenance Detail table (ormntd), the system w ill assign a serial number of ' 9999999999' to the EDI Order Maintenance Detail record (ormntd2) in order to f lag these records. The corresponding records in the EDI Order Detail Table (orddet2) w ill be deleted after the maintenance records are generated.



C. Screen Layout.



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. rout ing_orderc 2 CHAR ROUTING CODE. scac_orderc 4 CHAR SCAC CODE. asnf lag_orderc 2 CHAR ASN GENERATION FLAG. asndate_orderc 4 DATE ASN GENERATION DATE. asnt ime_orderc 8 CHAR ASN GENERATION TIME. asnuser_orderc 8 CHAR ASN GENERATION USER. asnbatch_orderc 4 INT ASN GENERATION BATCH NUMBER. invf lag_orderc 2 CHAR INVOICE GENERATION FLAG. invdate_orderc 4 DATE INVOICE GENERATION DATE. invt ime_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).



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_t ime_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.



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.



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 Definit ion. Program Name: EDIMNTU Parameter 1: CRON Program Path: EDIPROGS Military Time: (Set to t ime desired). Daily Job: (Set to days desired). Selected Days: (Set to dates desired).



EDIBILU- EDI BILLING FILE UPDATE. A. Program Summary. The program w ill generate records in the EDI Open Invoice and Invoice History tables and remove records from the EDI Open Order tables for EDI transact ions, which have been invoiced. This program should be setup to run from BILL as a subrout ine. B. Program Detail. The program is designed to run from the BILL program after the billing update is completed (bill3* ). This w ill be the last program run in the billing cycle. The program w ill f irst determine if the transact ion being processed is for an EDI customer based on a record exist ing in the EDI order header table (orderc) for the invoice being processed. The process described below w ill occur for EDI customer transact ions. For each of these transactions, the system w ill 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 transact ion header record. The system w ill 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 transact ion detail record. Once the records are generated, the program w ill determine if the order is st ill open in the Open Order table (orderb). If it is not, the EDI order record in the EDI Open Order table (orderc) for the transact ion w ill be removed and all records for the transact ion in the EDI Open Order Detail f ile (orddet2) w ill be removed. If the order is st ill open, the system w ill verify that each line number in the EDI Order Detail table (orddet2) is st ill open in the Order Detail table (orddet). For all lines w hich have been removed, the system w ill remove the lines in the EDI Order Detail table (orddet2). The advanced shipment not ice f ields in the EDI Order Header Table (orderc) w ill be cleared for shipments w ith backorders remaining on f ile. - The ASN Generat ion Flag w ill be set to ' N' (asnf lag_orderc). - The ASN Generat ion Date w ill be set to ' 01/01/1980' (asndate_orderc). - The ASN Generat ion Time w ill be set to < NULL> (asnt ime_orderc). - The ASN Generat ion User w ill be set to < NULL> (asnuser_orderc). - The ASN Generat ion Batch # w ill be set to < NULL> (asnbatch_orderc). The invoice generat ion f ields in the EDI Order Header Table (orderc) w ill be cleared for shipments w ith backorders remaining on f ile.

- The Invoice Generat ion Flag w ill be set to ' N' (invf lag_orderc). - The Invoice Generat ion Date w ill be set to ' 01/01/1980' (invdate_orderc). - The Invoice Generat ion Time w ill be set to < NULL> (invt ime_orderc). - The Invoice Generat ion User w ill be set to < NULL> (invuser_orderc). - The Invoice Generat ion Batch # w ill be set to < NULL> (invbatch_orderc).



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. rout ing_invoicec 2 CHAR ROUTING CODE. scac_invoicec 4 CHAR SCAC CODE. asnf lag_invoicec 2 CHAR ASN GENERATION FLAG. asndate_invoicec 4 DATE ASN GENERATION DATE. asnt ime_invoicec 8 CHAR ASN GENERATION TIME. asnuser_invoicec 8 CHAR ASN GENERATION USER. asnbatch_invoicec 4 INT ASN GENERATION BATCH NUMBER. invf lag_invoicec 2 CHAR INVOICE GENERATION FLAG. invdate_invoicec 4 DATE INVOICE GENERATION DATE. invt ime_invoicec 8 CHAR INVOICE GENERATION TIME. invuser_invoicec 8 CHAR INVOICE GENERATION USER. invbtach_invoicec 10 CHAR INVOICE GENERATION BATCH NUMBER.



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.



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.



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.



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. rout ing_invoicec 2 CHAR ROUTING CODE. scac_invoicec 4 CHAR SCAC CODE. asnf lag_invoicec 2 CHAR ASN GENERATION FLAG. asndate_invoicec 4 DATE ASN GENERATION DATE. asnt ime_invoicec 8 CHAR ASN GENERATION TIME. asnuser_invoicec 8 CHAR ASN GENERATION USER. asnbatch_invoicec 4 INT ASN GENERATION BATCH NUMBER. invf lag_invoicec 2 CHAR INVOICE GENERATION FLAG. invdate_invoicec 4 DATE INVOICE GENERATION DATE. invt ime_invoicec 8 CHAR INVOICE GENERATION TIME. invuser_invoicec 8 CHAR INVOICE GENERATION USER. invbatch_invoicec 10 CHAR INVOICE GENERATION BATCH NUMBER.



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.



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.



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 - Mult i-Process Program Parameter Maintenance. Program Name: EDIBILU Calling Program Name: BILL Sending Field 1: invnum_invoiceb



EDIPRG- EDI FILES PURGE. A. Program Summary. This program w ill 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 opt ion is provided to clear the EDI open invoice tables only or all the tables. The program has the capability of running interact ively or as a scheduled job through MISCRON. B. Program Detail. When accessing the program, the operator w ill be prompted to indicate w hether they w ant to purge the open invoice tables only. The operator w ill then be prompted to verify that they w ant to proceed w ith the purge. The program w ill f irst examine the open invoice header and detail tables. If a record does not exist in the standard Open Invoice Header table (invoiceb) w ith the same invoice number as the EDI Open Invoice Header table (invoicec), the system w ill 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 f iles only, the program w ill then examine the invoice history tables and the order maintenance f iles. If a record does not exist in the standard Invoice History Header table (invb) w ith the same invoice number as the EDI Invoice History Header table (invc), the system w ill 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) w ith the same serial number as the EDI Order Maintenance Header table (ormntc), the system w ill 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) w ith the same serial number as the EDI Order Maintenance Detail table (ormntd2), the system w ill delete the records for the serial number in the EDI Order Maintenance Detail table (ormntd2).



C. Screen Layout.

D. MISCRON - Cron Job Maintenance - Setup. Program Name: EDIPRG Parameter 1: CRON Program Path: EDIPROGS Military Time: (Set to t ime desired). Daily Job: (Set to days desired). Selected Days: (Set to dates desired).



EDITPMCM- EDI TRADING PARTNER MANUAL CUSTOMER MAINTENANCE PROGRAM. A. Program Summary. This program w ill 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 def ine the trading partners and customers that w ill be generat ing outbound EDI documents for manually entered transact ions not originally received through an EDI purchase order. B. Program Detail. A new table has been added to the system to allow the def init ion of these customers. See sect ion D for the f ile format for the EDI Trading Partner Manual Customer Table. See sect ion C1 for the maintenance screen display format. The follow ing describes the logic for each menu opt ion. B1. Add Menu Options Logic. The program w ill prompt for the trading partner id / mailbox number and w ill validate that the trading partner is a valid trading partner and display the trading partner name below the trading partner id. The drop down w indow feature w ill allow the operator to select the trading partner based on the trading partner id or the trading partner name; see sect ion C2 for the drop dow n w indow screen display format. The program w ill then prompt for the entry of a customer id and w ill validate that the customer is a valid customer and display the customer name to the right of the customer id. The drop dow n w indow feature w ill allow the operator to select the customer based on the customer id, customer name, customer cross-reference or phone number; see sect ion C3 for the drop dow n w indow screen display format. The program w ill prompt for the 30 character memo 1 f ield. The program w ill prompt for the 30 character memo 2 f ield. The program w ill prompt for the 10 character memo 3 f ield. The program w ill prompt for the memo 4 f ield, w hich allow s decimal numeric values. An entry of < NULL> w ill not be permit ted. The program w ill prompt for the memo 5 date f ield. An entry of < NULL> w ill not be permit ted. B2. Update Menu Options Logic. The program w ill allow select ion based on the trading partner id, customer id and memo f ields w ithin the trading partner manual customer table. The system w ill provide the opt ions for Update, Next record, Previous record, Help and Exit . When ut ilizing the update opt ion, the system w ill prompt for each memo f ield sequentially and allow the operator to override them.



B3. Query Menu Options Logic. The program w ill allow select ion based on the trading partner id, customer id and memo f ields w ithin the trading partner manual customer table. The system w ill provide the opt ions for Next record, Previous record, Help and Exit. B4. Remove Menu Options Logic. The program w ill allow select ion based on the trading partner id, customer id and memo f ields w ithin the trading partner manual customer table. The system w ill provide the opt ions for Remove, Next record, Previous record, Help and Exit . B5. View Menu Options Logic. The program w ill allow select ion based on the trading partner id, customer id and memo f ields w ithin the trading partner manual customer table. The program w ill allow you to sort by the trading partner id or the customer id w ith a different report format for each sort opt ion and w ill allow the report to be output to screen, printer, or hold f ile. See sect ion C4 for the view opt ion sort select ion screen format. See sect ion E for the view report formats. B1-6. Generate Menu Options Logic. The program w ill allow you to generate mult iple records in the table for a trading partner based on the criteria entered. The program w ill prompt for the trading partner id / mailbox number and w ill validate that the trading partner is a valid trading partner and display the trading partner name below the trading partner id. The drop down w indow feature w ill allow the operator to select the trading partner based on the trading partner id or the trading partner name; see sect ion C2 for the drop dow n w indow screen display format. Once the trading partner is displayed, the program w ill prompt for the entry of the customer criteria (customer id, customer name, customer cross-reference and customer phone number) to ut ilize to select records to generate; see sect ion C5 for the screen display format. Once the operator enters the criteria, the system w ill determine if any records meet the criteria in the customer master table. If no records meet the criteria, the system w ill display the message " No records found" and return to the customer criteria. If any records meet the criteria, the system w ill display the number of records w hich w ill be generated (based on the records exist ing in the Customer Master Table but not in the Trading Partner Manual Customer Table) and ask the operator if they w ant to proceed. Note that the prompt w ill require select ion criteria to be entered. The system w ill then prompt for the 5 memo f ields and then prompt the operator " Generate Records (Y/N) ?" . If the operator enters " Y" , the system w ill generate records for all the customers selected w ith ident ical t rading partner id and memo f ields. If the operator enters " N" , the system w ill return to the Trading Partner ID prompt.




C2. Trading Partner ID Option Screen Choose from the drop down window



C3. Customer ID Option choose from the drop down window.

C4. View Report Sort Options Screen.



C5. Generate Option - Customer Selection Criteria Entry Screen.



File and Field Layouts D1. EDITPMC – EDI TRADING PARTNER MANUAL CUSTOMER MASTER TABLE. FIELD NAME DESCRIPTION TYPE SIZE cust id_editpmc Customer ID CHAR 10 partnrid_editpmc Trading Partner ID CHAR 27 memo1_editpmc Memo 1 CHAR 30 memo2_editpmc Memo 2 CHAR 30 memo3_editpmc Memo 3 CHAR 10 memo4_editpmc Memo 4 DECIMAL 10 memo5_editpmc Memo 5 DATE 4 mis1_editpmc MIS 1 – Future Use CHAR 10 mis2_editpmc MIS 2 – Future Use CHAR 2 mis3_editpmc MIS 3 – Future Use CHAR 2 mis4_editpmc MIS 4 – Future Use DECIMAL 10 mis5_editpmc MIS 5 – Future Use DATE 4 Indexes: Unique index on custid_editpmc. Index on partnrid_editp.



EDIMCG- EDI MANUAL CUSTOMER TRANSACTION GENERATION. A. Program Summary. This program w ill allow the system to generate records in the EDI Order Header and Detail tables for manually entered transact ions for customers w hich are def ined as EDI trading partner manual transact ion customers. In this manner, when the EDI outbound documents are generated, the records w ill already exist in the current EDI transact ion tables. This program should be setup to run from BILL as a subrout ine. B. Program Detail. The program is designed to run from the ORDER program after the transact ion is accepted (ACF order1* ). The system w ill select the open order record from the Order Header " A" Table w hich matches the order number passed (where ordnum_ordera = ordnum_orderb). The system w ill then determine if a record exists in the EDI Trading Partner Manual Customer Table for the sold to customer of the transact ion (w here cust id_editpmc = soldto_ordera). If a record does not exist, indicat ing that this is not an EDI manual transact ion customer, the system w ill exit the subrout ine and return to the Order Entry program. If the trading partner record does exist, the system w ill access the EDI Trading Partner Master record (Table name: editp; condit ion: w here partnrid_editp = partnrid_editpmc). If a record is not found, the system w ill exit the subrout ine. If a record is found, the system w ill determine the transact ion types to allow , based on the transact ion type assignment method of the trading partner (Field name: t ranmeth_editp). If the transact ion type assignment method is " 0" and the transaction type is not a regular order (OR), the system w ill exit the subrout ine. If the transact ion type assignment method is " 1" and the transaction type is not a regular order (OR) or a return merchandise (RM), the system w ill exit the subrout ine. If the transact ion type is valid for the trading partner, the system w ill determine if an EDI Order Header record exists for the transact ion (w here ordnum_orderc = ordnum_ordera). If a record does not exist, the system w ill generate the record, based on the f ield mapping defined in sect ion C1. If a record already exists and the EDI Header Memo 40 f ield (Field name: memoh40_orderc) is set to " MANUAL" , indicat ing that this transact ion is a previously generated manual transact ion, the system w ill delete the exist ing record and add the record back in, based on the current values in the applicable f ields. If the transact ion type assignment method for the trading partner (Field name: t ranmeth_editp) is " 1" , the system w ill also set the transact ion code (Field name: t ranscd_orderc) to the transact ion type of the transact ion. For each order detail record, the system w ill determine if a corresponding record exists in the EDI Order Detail Table for the transact ion (w here ordnum_orddet2 = ordnum_orddet and lineno_orddet2 = lineno_orddet and subno_orddet2 = subno_orddet; note that the sub number f ield may be NULL).



If a record does not exist , the system w ill generate the record, based on the field mapping def ined in sect ion C2. If a record already exists and the EDI Detail Memo 40 f ield (Field name: memod40_orddet2) is set to " MANUAL" , indicat ing that this transact ion is a previously generated manual transact ion, the system w ill delete the exist ing record and add the record back in, based on the current value in the applicable f ields. To calculate the retail price on new records, the system w ill do the follow ing logic: • Get EDI Trading Partner record (w here partnrid_editp = partnrid_editpmc). • If the retail price customer id (Field: retailid_editp) for the trading partner is NULL, the retail

price w ill be set to zero. • If the retail price customer id for the trading partner is not in the Customer Table (where

id_customer = retailid_editp), the retail price w ill be set to zero. • If the retail price customer id for the trading partner is valid, the system w ill call the standard

pricing calculat ion rout ine (get_sellprice) passing the follow ing f ields to the rout ine: Retail Price ID (retailid_editp), Item ID (itemid_orddet), Transact ion Date (transdate_orderb). If the return value from the subrout ine is NULL, the retail price w ill be set to zero. If the return value is not NULL, the retail price w ill be set to the result of the follow ing calculat ion: round(5, < return value> ).

To determine the quantit ies and unit of measures to use w hen updating the records, the system w ill do the follow ing logic: • Get ACF opt ion "ediuomv" to determine the EDI Unit of Measure Validat ion Method to be used. • If the value of the opt ion is NULL or not equal to " 2" , do the follow ing:

• Set the quantity ordered to the quantity on the order (Field names: qtyord_orddet2 = qtyord_orddet).

• Set the alternate quantity ordered to zero (Field name: altqtyord_orddet2 = 0). • Set the unit of measure to the order unit of measure (Field names: uom_orddet2 =

uom_orddet). • Set the alternate unit of measure to the order unit of measure (Field names: altuom_orddet2

= uom_orddet). • If the value of the opt ion is set to " 2" , do the follow ing:

• If the alternate quantity ordered (Field name: altqtyord_orddet) = 0:

• Set the quantity ordered to the quantity on the order (Field names: qtyord_orddet2 = qtyord_orddet).

• Set the alternate quantity ordered to zero (Field name: altqtyord_orddet2 = 0). • Access the EDI Unit of Measure Table (Table name: ediuom) based on the trading

partner id, item id and unit of measure code (w here partnrid_ediuom = partnrid_orddet2 and itemid_ediuom = itemid_orddet and uom_ediuom = uom_orddet). • If a record is found, set the unit of measure f ields (Field names: uom_orddet2,

altuom_orddet2) to the customer unit of measure (Field name: custuom_ediuom) def ined for the trading partner, item id and unit of measure. If multiple records are found, select the record w ith the lowest customer unit of measure code (Field name: custuom_ediuom).



• If a record is not found, set the unit of measure f ields (Field names: uom_orddet2,

altuom_orddet2) to the unit of measure on the order (Field name: uom_orddet).

• If the alternate quantity ordered (Field name: altqtyord_orddet) is not 0:

• Set the quantity ordered to the quantity on the order t imes the alternate conversion factor plus the alternate quantity ordered (Field names: qtyord_orddet2 = ((qtyord_orddet * altconv_orddet) + altqtyord_orddet). This is the quantity ordered converted to the alternate unit of measure.

• Set the alternate quantity ordered to the quantity on the order t imes the alternate conversion factor plus the alternate quantity ordered (Field names: altqtyord_orddet2 = ((qtyord_orddet * altconv_orddet) + altqtyord_orddet). This is the quantity ordered converted to the alternate unit of measure.

• Access the EDI Unit of Measure Table (Table name: ediuom) based on the trading partner id, item id and the alternate unit of measure code (w here partnrid_ediuom = partnrid_orddet2 and itemid_ediuom = itemid_orddet and uom_ediuom = altuom_orddet). • If a record is found, set the unit of measure f ields (Field names: uom_orddet2,

altuom_orddet2) to the customer unit of measure (Field name: custuom_ediuom) def ined for the trading partner, item id and alternate unit of measure. If mult iple records are found, select the record w ith the low est customer unit of measure code (Field name: custuom_ediuom).

• If a record is not found, set the unit of measure f ields (Field names: uom_orddet2, altuom_orddet2) to the alternate unit of measure on the order (Field name: altuom_orddet).

Once all the records have been processed, the system w ill return to the standard Order Entry program. Note that the EDI Order Header record w ill only be generated for those transact ions w hich were manually entered. Note that the EDI Order Detail record w ill be generated for those transact ions w here were manually entered and also for any detail lines manually added to those transact ions which were generated through the EDI P.O. Upload program (EDIPOLD). Note that the f ields w ill be set in the EDI Header tables based on the values in the f ields the each t ime the order is accepted w hen the order is added or updated to the system. The f ields w ill be set in the EDI Detail tables based on the values in the f ields entered on the order detail line the each t ime the order is accepted after the detail line has been added to the order and the records are generated. Note that the mapping, def ined in sect ion C, maps our standard fields to the EDI Order Tables. This may not be consistent w ith the information normally provided by the trading partner. For example, the item id f ield sent by the trading partner can be your item id, the customer' s part number, the UPC code, etc. The item id f ield generated through the manual transact ion generat ion w ill alw ays be your item id. Other f ields w hich are normally sent in by the trading partner (for example, media event code) w ill not be valued w hen the transaction is manually generated.



C. EDI Order Table Mapping. C1. ORDERC - EDI ORDER HEADER FILE – MAPPING. FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. invnum_orderc 10 CHAR INVOICE NUMBER. ordnum_orderb. ordnum_orderc 10 CHAR ORDER NUMBER. ordnum_orderb. batch_orderc 2 SMINT EDI BATCH NUMBER. 0. partnrid_orderc 27 CHAR TRADING PARTNER ID / MAILBOX #. partnrid_editpmc. billto_orderc 35 CHAR BILL TO ID. < NULL> . soldto_orderc 35 CHAR SOLD TO ID. soldto_ordera. shipto_orderc 35 CHAR SHIP TO ID. shipto_ordera. bslook_orderc 35 CHAR SHIP TO ID INDICATOR. < NULL> . trandate_orderc 4 DATE TRANSACTION DATE. t ransdate_orderb. reqdate_orderc 4 DATE REQUESTED DATE. reqdate_orderb. shipdate_orderc 4 DATE SHIP DATE. shipdate_orderb. canceldte_orderc 4 DATE CANCEL DATE. cancldate_orderb. podate_orderc 4 DATE PURCHASE ORDER DATE. podate_orderb. cust_po_orderc 22 CHAR CUSTOMER P/O NUMBER. cust_po_orderb. pobatch_orderc 10 CHAR CUSTOMER PURCHASE ORDR BATCH. < NULL> . refno_orderc 30 CHAR REFERENCE NUMBER. < NULL> . dept_orderc 30 CHAR DEPARTMENT NUMBER. < NULL> . remarks_orderc 80 CHAR REMARKS. remarks_orderb. media_orderc 2 CHAR MEDIA/EVENT CODE. < NULL> . shipname_orderc 35 CHAR SHIP TO NAME. shipname_ordera. If shipto_ordera = " SAME" : soldname_ordera. shipaddr1_orderc 35 CHAR SHIP TO ADDRESS 1. shipadr1_ordera. If shipto_ordera = " SAME" : soldadr1_ordera.



FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. shipaddr2_orderc 35 CHAR SHIP TO ADDRESS 2. shipadr2_ordera. If shipto_ordera = " SAME" : soldadr2_ordera. shipaddr3_orderc 35 CHAR SHIP TO ADDRESS 3. shipadr3_ordera. If shipto_ordera = " SAME" : soldadr3_ordera. shipcity_orderc 19 CHAR SHIP TO CITY. shipcity_ordera. If shipto_ordera = " SAME" : soldcity_ordera. shipstate_orderc 4 CHAR SHIP TO STATE. shipstate_ordera. If shipto_ordera = " SAME" : soldstate_ordera. shipcntry_orderc 10 CHAR SHIP TO COUNTRY. shipcntry_ordera. If shipto_ordera = " SAME" : soldcntry_ordera. shipzip_orderc 9 CHAR SHIP TO ZIP CODE. shipzip_ordera (First 9 characters). If shipto_ordera = " SAME" : soldzip_ordera (9 characters). shipattn_orderc 27 CHAR SHIP TO ATTENTION. shipattn_ordera. If shipto_ordera = " SAME" : soldattn_ordera. markfor_orderc 45 CHAR MARK FOR. markfor_orderb. terms_cd_orderc 4 CHAR TERMS CODE. terms_cd_orderb. transcd_orderc 2 CHAR TRANSACTION CODE. If t ranmeth_editp < > " 2" :

< NULL> . If t ranmeth_editp = " 2" :

t ranstype_orderb. transtype_orderc 2 CHAR TRANSACTION TYPE. < NULL> . contract_orderc 12 CHAR CONTRACT NUMBER. < NULL> . rout ing_orderc 2 CHAR ROUTING CODE. < NULL> . scac_orderc 4 CHAR SCAC CODE. < NULL> .



FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. asnf lag_orderc 2 CHAR ASN GENERATION FLAG. " N" . asndate_orderc 4 DATE ASN GENERATION DATE. " 01/01/1980" . asnt ime_orderc 8 CHAR ASN GENERATION TIME. < NULL> . asnuser_orderc 8 CHAR ASN GENERATION USER. < NULL> . asnbatch_orderc 4 INT ASN GENERATION BATCH NUMBER. 0. invf lag_orderc 2 CHAR INVOICE GENERATION FLAG. " N" . invdate_orderc 4 DATE INVOICE GENERATION DATE. " 01/01/1980" . invt ime_orderc 8 CHAR INVOICE GENERATION TIME. < NULL> . invuser_orderc 8 CHAR INVOICE GENERATION USER. < NULL> . invbatch_orderc 10 CHAR INVOICE GENERATION BATCH #. 0. memo1_orderc 30 CHAR MEMO 1 (ALPHA). < NULL> . memo2_orderc 30 CHAR MEMO 2 (ALPHA). < NULL> . memo3_orderc 10 CHAR MEMO 3 (ALPHA). < NULL> . memo4_orderc 10 DEC MEMO 4 (NUMERIC). 0. memo5_orderc 4 DATE MEMO 5 (DATE). " 01/01/1980" memoh1_orderc 30 CHAR HEADER MEMO 1. < NULL> . memoh2_orderc 30 CHAR HEADER MEMO 2. < NULL> . memoh3_orderc 30 CHAR HEADER MEMO 3. < NULL> . memoh4_orderc 30 CHAR HEADER MEMO 4. < NULL> . memoh5_orderc 30 CHAR HEADER MEMO 5. < NULL> . memoh6_orderc 30 CHAR HEADER MEMO 6. < NULL> . memoh7_orderc 30 CHAR HEADER MEMO 7. < NULL> . memoh8_orderc 30 CHAR HEADER MEMO 8. < NULL> . memoh9_orderc 30 CHAR HEADER MEMO 9. < NULL> .



FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. memoh10_orderc 30 CHAR HEADER MEMO 10. < NULL> . memoh11_orderc 30 CHAR HEADER MEMO 11. < NULL> . memoh12_orderc 30 CHAR HEADER MEMO 12. < NULL> . memoh13_orderc 30 CHAR HEADER MEMO 13. < NULL> . memoh14_orderc 30 CHAR HEADER MEMO 14. < NULL> . memoh15_orderc 30 CHAR HEADER MEMO 15. < NULL> . memoh16_orderc 30 CHAR HEADER MEMO 16. < NULL> . memoh17_orderc 30 CHAR HEADER MEMO 17. < NULL> . memoh18_orderc 30 CHAR HEADER MEMO 18. < NULL> . memoh19_orderc 30 CHAR HEADER MEMO 19. < NULL> . memoh20_orderc 30 CHAR HEADER MEMO 20 - SHIP VIA CODE. shipvia_orderb. memoh21_orderc 30 CHAR HEADER MEMO 21. < NULL> . memoh22_orderc 30 CHAR HEADER MEMO 22. < NULL> . memoh23_orderc 30 CHAR HEADER MEMO 23. < NULL> . memoh24_orderc 30 CHAR HEADER MEMO 24. < NULL> . memoh25_orderc 30 CHAR HEADER MEMO 25. < NULL> . memoh26_orderc 30 CHAR HEADER MEMO 26. < NULL> . memoh27_orderc 30 CHAR HEADER MEMO 27. < NULL> . memoh28_orderc 30 CHAR HEADER MEMO 28. < NULL> . memoh29_orderc 30 CHAR HEADER MEMO 29. < NULL> . memoh30_orderc 30 CHAR HEADER MEMO 30. < NULL> . memoh31_orderc 30 CHAR HEADER MEMO 31. < NULL> . memoh32_orderc 30 CHAR HEADER MEMO 32. < NULL> . memoh33_orderc 30 CHAR HEADER MEMO 33. < NULL> .



FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. memoh34_orderc 30 CHAR HEADER MEMO 34. < NULL> . memoh35_orderc 30 CHAR HEADER MEMO 35. < NULL> . memoh36_orderc 30 CHAR HEADER MEMO 36. < NULL> . memoh37_orderc 30 CHAR HEADER MEMO 37. < NULL> . memoh38_orderc 30 CHAR HEADER MEMO 38. < NULL> . memoh39_orderc 30 CHAR HEADER MEMO 39. < NULL> . memoh40_orderc 30 CHAR HEADER MEMO 40. " MANUAL" . Indexes: Index on ordnum_orderc. Index on partnrid_orderc, cust_po_orderc. Index on batch_orderc, ordnum_orderc.



C2. ORDDET2 - EDI ORDER DETAIL FILE MAPPING. FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. ordnum_orddet2 10 CHAR ORDER NUMBER. ordnum_orddet. invnum_orddet2 10 CHAR INVOICE NUMBER. ordnum_orderb. lineno_orddet2 4 INT LINE NUMBER. lineno_orddet. subno_orddet2 4 CHAR SUB NUMBER. subno_orddet. batch_orddet2 2 SMINT EDI BATCH NUMBER. 0. partnrid_orddet2 27 CHAR TRADING PARTNER ID / MAILBOX #. partnrid_editpmc. ponumber_orddet2 22 CHAR CUSTOMER P/O NUMBER. cust_po_orderb. polineno_orddet2 4 CHAR CUSTOMER P/O SEQUENCE NUMBER. < NULL> . custprt1_orddet2 18 CHAR CUSTOMER PART ID. custpart id_orddet.

(First 18 characters). custprt2_orddet2 18 CHAR CUSTOMER PART ID 2. < NULL> . upc_orddet2 25 CHAR UPC CODE. xref_orddet. sellitem_orddet2 25 CHAR ITEM ID. itemid_orddet. desc_orddet2 18 CHAR ITEM DESCRIPTION. desc1_orddet (First 18 characters). qtyord_orddet2 10 DEC QUANTITY ORDERED. < Calculated Quantity Ordered> (* * )

qtyord_orddet. OR qtyord_orddet * altconv_orddet) + altqtyord_orddet.

altqtyord_orddet2 10 DEC ALTERNATE QUANTITY ORDERED. < Alt Calculated Qty Ordered> (* * )

0 OR

(qtyord_orddet * altconv_orddet) + altqtyord_orddet.

uom_orddet2 2 CHAR UNIT OF MEASURE. < Calculated Unit of Measure> (* * )

uom_orddet OR altuom_orddet OR custuom_ediuom.



FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. altuom_orddet2 2 CHAR ALTERNATE UNIT OF MEASURE. < Calculated Alt . Unit of Meas.> (* * )

uom_orddet OR altuom_orddet OR custuom_ediuom.

orgprice_orddet2 10 DEC ORIGINAL SELLING PRICE. sellprice_orddet. altorgprc_orddet2 10 DEC ALTERNATE ORIG. SELLING PRICE. 0 altsellpr_orddet2 10 DEC ALTERNATE SELLING PRICE. 0 retailprc_orddet2 10 DEC RETAIL PRICE < Calculated Retail Sell Price> (* ). f reight_orddet2 10 DEC FREIGHT AMOUNT. 0. spcsrv1_orddet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 1. < NULL> . spcsrv2_orddet2 8 CHAR SPECIAL INSTRUCTIONS - LINE 2. < NULL> . delins1_orddet2 60 CHAR DELIVERY NOTES - LINE 1. < NULL> . delins2_orddet2 60 CHAR DELIVERY NOTES - LINE 2. < NULL> . memo1_orddet2 30 CHAR MEMO 1 (ALPHA). < NULL> . memo2_orddet2 30 CHAR MEMO 2 (ALPHA). < NULL> . memo3_orddet2 10 CHAR MEMO 3 (ALPHA). < NULL> . memo4_orddet2 10 DEC MEMO 4 (NUMERIC). 0. memo5_orddet2 4 DATE MEMO 5 (DATE). " 01/01/1980" . memod1_orddet2 30 CHAR DETAIL MEMO 1. < NULL> . memod2_orddet2 30 CHAR DETAIL MEMO 2. < NULL> . memod3_orddet2 30 CHAR DETAIL MEMO 3. < NULL> . memod4_orddet2 30 CHAR DETAIL MEMO 4. < NULL> . memod5_orddet2 30 CHAR DETAIL MEMO 5. < NULL> . memod6_orddet2 30 CHAR DETAIL MEMO 6. < NULL> .



FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. memod7_orddet2 30 CHAR DETAIL MEMO 7. < NULL> . memod8_orddet2 30 CHAR DETAIL MEMO 8. < NULL> . memod9_orddet2 30 CHAR DETAIL MEMO 9. < NULL> . memod10_orddet2 30 CHAR DETAIL MEMO 10. < NULL> . memod11_orddet2 30 CHAR DETAIL MEMO 11. < NULL> . memod12_orddet2 30 CHAR DETAIL MEMO 12. < NULL> . memod13_orddet2 30 CHAR DETAIL MEMO 13. < NULL> . memod14_orddet2 30 CHAR DETAIL MEMO 14. < NULL> . memod15_orddet2 30 CHAR DETAIL MEMO 15. < NULL> . memod16_orddet2 30 CHAR DETAIL MEMO 16. < NULL> . memod17_orddet2 30 CHAR DETAIL MEMO 17. < NULL> . memod18_orddet2 30 CHAR DETAIL MEMO 18. < NULL> . memod19_orddet2 30 CHAR DETAIL MEMO 19. < NULL> . memod20_orddet2 30 CHAR DETAIL MEMO 20 - ITEM MEMO 1. imemo1_orddet. memod21_orddet2 30 CHAR DETAIL MEMO 21 - ITEM MEMO 2. imemo2_orddet. memod22_orddet2 30 CHAR DETAIL MEMO 22 – DETAIL SOLD TO ID.

(See ACF opt ion edinfmt for usage). memod23_orddet2 30 CHAR DETAIL MEMO 23. < NULL> . memod24_orddet2 30 CHAR DETAIL MEMO 24. < NULL> . memod25_orddet2 30 CHAR DETAIL MEMO 25. < NULL> . memod26_orddet2 30 CHAR DETAIL MEMO 26. < NULL> . memod27_orddet2 30 CHAR DETAIL MEMO 27. < NULL> . memod28_orddet2 30 CHAR DETAIL MEMO 28. < NULL> . memod29_orddet2 30 CHAR DETAIL MEMO 29. < NULL> . memod30_orddet2 30 CHAR DETAIL MEMO 30. < NULL> .



FIELD NAME SIZE TYPE DESCRIPTION / SOURCE FIELD. memod31_orddet2 30 CHAR DETAIL MEMO 31. < NULL> . memod32_orddet2 30 CHAR DETAIL MEMO 32. < NULL> . memod33_orddet2 30 CHAR DETAIL MEMO 33. < NULL> . memod34_orddet2 30 CHAR DETAIL MEMO 34. < NULL> . memod35_orddet2 30 CHAR DETAIL MEMO 35. < NULL> . memod36_orddet2 30 CHAR DETAIL MEMO 36. < NULL> . memod37_orddet2 30 CHAR DETAIL MEMO 37. < NULL> . memod38_orddet2 30 CHAR DETAIL MEMO 38. < NULL> . memod39_orddet2 30 CHAR DETAIL MEMO 39. < NULL> . memod40_orddet2 30 CHAR DETAIL MEMO 40. " MANUAL" . Indexes: Index on ordnum_orddet2, lineno_orddet2, subno_orddet2. Index on partnrid_orddet2, ponumber_orddet2, polineno_orddet2. Notes: (* ) Retail Price Calculat ion:

- Get EDI Trading Partner record (w here partnrid_editp = partnrid_editpmc). - If retail price customer id (Field: retailid_editp) is NULL, retail price is zero. - If retail price customer id is not in the Customer Table (w here id_customer = retailid_editp),

retail price is zero. - Call the standard pricing calculat ion rout ine (get_sellprice) passing the follow ing f ields to the

rout ine: retailid_editp, itemid_orddet, t ransdate_orderb). - If the return value is NULL, the retail price is zero. - If the return value is not NULL, the retail price is the result of the follow ing calculat ion:

round(5, < return value> ). (* * ) Quantity & Unit of Measure Calculat ions – see the details in sect ion B.



D. Implementat ion Requirements. D1. RUN Funct ion – Mult i-Process Parameter Maintenance. Program Name: edimcg Calling Program Name: order Sending Field 1: ordnum_orderb D2. ACF – Applicat ion Control File Maintenance. Option Code: order1* Option Descript ion: EDI Manual Order Generation Subrout ine. Option Value: edimcg

Table of Contents - Jason Industrial · The third party EDI communication, translation and mapping software package must receive EDI purchase order transactions (850), translate and

Documents