Management Systems Consulting, Inc.

Excellence in Computing

Honesty ~ Integrity ~ Loyalty ~ Respect

Glossary of Computer Terms (5C)

Internet Slang

Int'l Trade Terms

Web Suffix Table

HIPAA Glossary

****************************

USA Founding Documents

United We Stand!

Never Forget!

Support our Troops!

Remember our Veterans!

****************************

Company Profile

Privacy

Contact Us!

***********************

Visit IQ-Home for your housing design needs:

***********************

Updated:05/16/2008

JDE EDI-850

Generalized JD Edwards EDI 850 Mapping Processing

1.0 Purpose of Procedure

The EDI Mapping Procedure converts information from one file structure to another.

2.0 Scope

To be supplied.

3.0 Process Owner

Director of Electronic Commerce / Technology

4.0 Input

N/A

5.0 Procedure

Client Company EDI Transaction Processes consist of the Customer Order (850 Inbound), Invoice (810 Outbound), Advance Shipping Notice (856 Outbound), Purchase Order Change (860 Inbound), Text Message (864 Inbound), Shipping Status (214 Inbound), Planning Schedule (830 Inbound), Product Activity (852 Inbound), Acknowledgment (Outbound 855), and Organizational Relationships (816 Inbound).

Each of the individual processes is described in the following pages, and flow process charts (and de-compositions) of each of the processes are located at the end of this document.

6.0 Customer Order (850 Inbound)

6.1 Process Summary

Customer Sales Orders are created from Purchase Orders issued by the Customer. The Purchase Order contains specific information such as the firm placing the order, the items and quantities ordered, ship-to instructions, and requested delivery date(s).

Using the cross-reference information set-up in J.D. Edwards, the System 47 files will be used to convert the EDI Purchase Order into a J.D. Edwards Sales Order. The Order Activity rules will be used to perform the full cycle of ORDER FULFILLMENT

6.2 Process

6.2.1 The sending party (trading partner) transmits Purchase Order transactions to the Client Company Network Mailbox. Depending on Client Company trading partner, documents can be traded either directly (point-to-point) or over a third-party Network (Value Added Network).

6.2.2 A communication session is initiated by dialing in to the Network to receive Customer Order transactions from trading partners.

6.2.3 The EDI translator software processes incoming data and maps it to the J.D. Edwards inbound EDI files. (System 47).

6.2.3.1 The J.D. Edwards inbound EDI files (System 47) include:

· F47011 - Sales Order Header

· F47012 - Sales Order Detail

· F47013 - SDQ

· F4706 - Order Address Information

· F554104 - Customer Item Tag File for POs

· F4714 - Order Text Lines (Header)

· F4715 - Order Text lines (Detail)

6.2.4 Program P4104 performs the following actions:

6.2.4.1 Retrieves the Customer Item Number

6.2.4.2 Retrieves the Client Company business Unit, EDI Document type from F01092 (Supplemental Database)

6.2.4.3 Determine payment terms from preference profile (If not available, use default from customer master file)

6.2.4.4 Manipulates dates (Requested Ship Date)

6.2.4.5 Creates multiple Sales Orders from SDQ transmissions

6.2.4.6 Retrieves freight code, SZFRTH, from preference profiles

6.2.4.7 Determine exception Shipment lead times from F01092 (Supplemental Database) Calculate Ship Date

6.2.4.8 Determine exception transit times from F01092 (Supplemental Database)

6.2.4.9 Determine Ship-to/Bill-to/Store # Address Book Numbers

6.2.5 The batch edit/update program (P47011) performs the internal edits, then creates or updates transactions in the J.D. Edwards Sales Order System. In addition the program determines whether or not an item is in the correct order multiple (standard pack). If an item is not in the correct standard pack, the order will go on “Standard Pack” hold.

6.2.6 For orders with errors, the following steps are performed:

6.2.6.1 If the edits are not satisfied, an exception report is produced (R47011A).

6.2.6.2 Inquires are made into transactions that are in error and manual corrections are made (Status Inquiry/ Revisions G47212). The edit is re- executed. If there are no errors, the system creates transactions, which update J.D. Edwards production files.

6.2.7 For orders without errors, Pricing Edit generates a price exception report. The ‘Processed Y/N’ field (SYEDSP) will be populated with the value = ‘E’ if exception occurs.

6.2.8 J.D. Edwards Sales Orders are created and the Sales Order Header and Detail production files are updated. An EDI Sales Order Audit report is also printed. On the orders:

6.2.8.1 Document type, “SZ”, is assigned

6.2.8.2 Customer Item Number is converted to a J.D. Edwards Item Number.

6.2.8.3 Default Branch/Plant is allocated for the detail line.

6.3 The following EDI business requirements are assumed to have been met:

6.3.1 Sales Order type code “SZ” must be set up with its corresponding Order Activity Rule.

6.3.2 Customer Item Cross Reference table

6.3.3 Ship-from Branch/Plant

6.3.4 Standard Pack is defined in the Item Master and Item Branch/Plant with Unit of Measure conversion.

6.3.5 Customer ship-to store address

6.3.6 Customer Billing Instructions including the EDI Transaction Set.

6.4 The following EDI TECHNICAL REQUIREMENTS are assumed to have been met:

6.4.1 Customer Profile has been set up within the EDI Translator.

6.4.2 Customer Communication Script has been set up.

6.4.3 Customer Technical Requirements have been met in the EDI Mapper.

1.1 De-composition of Customer Order Process Flow

CUSTOMER

ORDERS

The sending party (trading partner) transmits Purchase Order transactions to the Client Company Network Mailbox. Depending on Client Company trading partner, documents can be traded either directly (point-to-point) or over a third-party Network (Value Added Network).

EDI MAILBOX

A communication session is initiated by dialing in to the Network to receive Customer Order transactions from trading partners.

TRANSLATOR

The EDI translator software processes incoming data and maps it to the J.D. Edwards inbound EDI files. (System 47).

JDE Database

System 47 Files

The J.D. Edwards inbound EDI files (System 47) include:

F47011 - Sales Order Header

F47012 - Sales Order Detail

F47013 - SDQ

F4706 - Order Address Information

F4714 - Order Text Lines (Header)

F4715 - Order Text lines (Detail)

EDI Purchase Order

Pre-Processing

P47011A

Version: EDI0001

Based on File: F47011

Associated Programs:

P55AB#

· Retrieves the Address Book Number

P554104

· Retrieves the Customer Item Number

· Retrieves the Client Company business Unit, EDI Document type from F01092 (Supplemental Database)

· Determine payment terms from preference profile (If not available, use default from customer master file)

· Manipulates dates (Requested Ship Date)

· Creates multiple Sales Orders from SDQ transmissions

· Retrieves freight code, SZFRTH, from preference profiles

· Determine exception Shipment lead times from F01092 (Supplemental Database) Calculate Ship Date

· Determine exception transit times from F01092 (Supplemental Database)

· Determine Ship-to/Bill-to/Store # Address Book Numbers

Text Box: Order Creation / Edit
P47011

The batch edit/update program (P47011) performs the internal edits, then creates or updates transactions in the J.D. Edwards Sales Order System.

In addition the program determines whether or not an item is in the correct order multiple (standard pack). If an item is not in the correct standard pack, the order will go on “Standard Pack” hold.

Text Box: Post-Processing
P47011A

Pricing Edit - Generates price exception report. The ‘Processed Y/N’ field (SYEDSP) will be populated with the value = ‘E’ if exception occurs.

Can: JDE Database
(Sales Order Created)

ORDERS WITH NO ERRORS

J.D. Edwards Sales Orders are created and the Sales Order Header and Detail production files are updated. An EDI Sales Order Audit report is also printed. On the orders:

· Document type, “SZ”, is assigned

· Customer Item Number is converted to a J.D. Edwards Item Number.

· Default Branch/Plant is allocated for the detail line.

The following EDI business requirements are assumed to have been met:

· Sales Order type code “SZ” must be set up with its corresponding Order Activity Rule.

· Customer Item Cross Reference table

· Ship-from Branch/Plant

· Standard Pack is defined in the Item Master and Item Branch/Plant with Unit of Measure conversion.

· Customer ship-to store address

· Customer Billing Instructions including the EDI Transaction Set.

The following EDI technical requirements are assumed to have been met:

· Customer Profile has been set up within the EDI Translator.

· Customer Communication Script has been set up.

· Customer Technical Requirements have been met in the EDI Mapper.

Flowchart: Document: Audit
Report
(R47012A)

This report summarizes the orders that were created in the Sales order system.

Flowchart: Document: Exception
Report
(R47011A)

ORDERS WITH ERRORS

If the edits are not satisfied, an exception report is produced (R47011A).

Text Box: EDI Order Revision

Inquires are made into transactions that are in error and manual corrections are made (Status Inquiry/ Revisions G47212). The edit is re- executed. If there are no errors, the system creates transactions, which update J.D. Edwards production files.