Receiving and Sending Electronic Data Interchange Sales Order Documents

This chapter discusses how to:

Click to jump to parent topicReceiving Requests for Quotes (840/REQOTE)

This section provides an overview of inbound requests for quotes, lists prerequisites, and discusses how to receive requests for quotes.

Click to jump to top of pageClick to jump to parent topicUnderstanding Inbound Requests for Quotes

When a customer sends you requests for quotations (840/REQOTE), the translator software maps the data to a flat file, and the Inbound Conversion program copies them to the Electronic Data Interchange (EDI) inbound interface tables. After the data is in the EDI inbound interface tables, you need to copy it to the sales order management application tables so that the JD Edwards EnterpriseOne Sales Order Management system can process the purchase orders.

To copy the data, run the Inbound Edit/Update program from the Request for Quote (RFQ) Sales menu (G47211). The Inbound Edit/Update program retrieves the data from the EDI inbound interface tables and copies it to the Sales Order Management application tables.

Note. When you run the Inbound Edit/Update program, the Sold To and Ship To address data in the EDI inbound interface tables must be valid address book numbers. If the trading partner's ID differs from their address book number in the system, use the translator software's cross-reference feature to convert the ID number to the address book number.

When the Inbound Edit/Update program copies the data into the sales order management application tables, the JD Edwards EnterpriseOne Sales Order Management system:

The process for receiving inbound requests for quotation is similar to the process for receiving purchase orders, except that you do not have to commit inventory.

EDI Inbound Interface Tables

When you run Inbound Edit/Update, the program uses these EDI inbound interface tables:

Mapping Guidelines

Mapping is the process of converting information from one table structure to another.

In the F47091 table, the following fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F47092 table, these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F47093 table (if used), these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F4706 table (if used), the following fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F4714 table, these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F4715 table (if used), these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

Application Table Update

When you run Inbound Edit/Update for request for quotation documents, the program copies the data from the EDI inbound interface tables and updates these application tables in the JD Edwards EnterpriseOne Sales Order Management system:

See Also

Setting Up Customer Billing Instructions

Click to jump to top of pageClick to jump to parent topicPrerequisites

Before you complete the tasks in this section:

Click to jump to top of pageClick to jump to parent topicReceiving Requests for Quotes

Select Request for Quote (RFQ) Sales (G47211), Inbound Flat File Conversion to convert data from the flat files and copy it to EDI interface tables.

The Inbound Edit/Update program creates quote orders within the Sales Order Management application tables. If errors are detected, the system produces an error report in the Work Center. The Inbound Edit/Update program updates EDI documents that are successfully processed in the EDI inbound interface tables to prevent duplicates. The program updates EDI documents by placing Y in the Processed column (EDSP) in all of the EDI inbound interface tables.

Click to jump to parent topicReceiving Customer Orders (850/ORDERS)

This section provides an overview of inbound customer orders, lsits prerequisites, and discusses how to receive customer orders.

Click to jump to top of pageClick to jump to parent topicUnderstanding Inbound Customer Orders

When a customer sends you purchase orders (850/ORDERS), the translator software maps the data to a flat file and the Inbound Flat File Conversion program copies it to the EDI inbound interface tables. Once this data is in the EDI inbound interface tables, you need to copy the data to the sales order management application tables so that the JD Edwards EnterpriseOne Sales Order Management system can process the purchase orders.

To copy the data, run the Inbound Edit/Update program from the Customer Order menu (G47212). The Inbound Edit/Update program retrieves the data from the EDI inbound interface tables and copies it to the Sales Order Management application tables.

Note. When you run the Inbound Edit/Update program, the sold to and ship to address data in the inbound EDI interface files must be valid address book numbers to process correctly and be copied to the sales order management application files. If the trading partner's ID differs from their address book number in the system, use the translator software's cross-reference feature to convert the ID number to the address book number.

When the Inbound Edit/Update program copies the data into the sales order management application tables, the JD Edwards EnterpriseOne Sales Order Management system:

You can customize the system and the processing options of the Inbound Edit/Update program according to the way you and the trading partner do business. For example, if the trading partner prefers to use their own item numbers, you can set up item cross-references in the JD Edwards EnterpriseOne Inventory Management system. The JD Edwards EnterpriseOne Sales Order Management system converts the trading partner item numbers into the equivalent item numbers when you run the Inbound Edit/Update program.

If you want to override the address book information for the sold to or ship to address (for example, a direct ship situation), you can use the F4706 table. Within this table, the Address Type field (ANTY) indicates whether you are overriding the sold to, ship to, or parent address information. The Inbound Edit/Update program copies this override information to the F4006 table within the JD Edwards EnterpriseOne Sales Order Management system.

You can also run Inbound Edit/Update for customer orders to process orders for kits if you have defined the kit in the F4101 table with a stocking type of K. You must also define the relationships between the kit item and its components in the F3002 table.

When you run the Inbound Edit/Update program, every detail line on the customer order must be correct for the JD Edwards EnterpriseOne Sales Order Management system to process the order. If errors occur on any part of the customer order, the JD Edwards EnterpriseOne Sales Order Management system does not process the order. The Inbound Edit/Update program continues to process the next order in the batch.

As the JD Edwards EnterpriseOne Sales Order Management system creates the sales orders, it automatically marks the corresponding records in the inbound EDI interface tables as processed by placing Y in the EDI Successfully Processed field (EDSP). Any record that has been processed cannot be reprocessed.

Shipment, Destination, Quantity Orders

Shipment Destination Quantity (SDQ) is an optional segment that might be received on an inbound purchase order (850). The purpose is to be able to provide a consolidated order due to the fact that a shipment might be repetitious. The SDQ segment provides a detailed breakdown by store and quantity.

If the trading partner wants items on a single order to be shipped to various destinations, you can map information for multiple ship-to locations to the SDQ table.

Note. The bill-to and ship-to locations must be the same.

This example illustrates the SDQ segment within an EDI ANSI formatted purchase order:

GS*PO*3034881418*3033771916*970903*1338 ST*850*170001 BEG*00*PO*5439**970827 DTM*002*970827 PO1*1000*1150*EA*798**BP*210 PID*F****Mountain Bike, Red SDQ*EA*ZZ*4242*500*4243*100*4244*250*4245*300 CTT*1 SE*15*170001 GE*1*17

EDI Inbound Interface Tables

When you run Inbound Edit/Update, the program uses these EDI inbound interface tables:

Mapping Guidelines

Mapping is the process of converting information from one table structure to another.

In the F47011 table, the following fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F47012 table, these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F47013 table (if used), these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F4706 table (if used), the following fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F4714 table (if used), these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

In the F4715 table (if used), these fields must contain data before you can effectively use the Inbound Edit/Update program for customer orders:

Updating Application Tables

When you run Inbound Edit/Update for customer orders, the program copies the data from the EDI interface tables and updates these tables in Sales Order Management:

See Also

Entering Kit Information

Click to jump to top of pageClick to jump to parent topicPrerequisites

Before you complete the tasks in this section, verify that you have mapped the minimum required fields. Also verify that you have properly set up the Sold To field for the customer in Customer Billing Instructions, as follows:

Click to jump to top of pageClick to jump to parent topicReceiving Customer Orders

Select Customer Order (G47212), Inbound Edit/Update.

The Inbound Edit/Update program creates sales orders within the Sales Order Management application tables. An audit trail report is produced indicating whether errors were detected or the documents were successfully processed. If errors are detected, detailed error messages are written to the Employee Work Center. The Inbound Edit/Update program updates EDI documents that were successfully processed by placing Y in the EDI Successfully-Processed column (EDSP) in all of the EDI inbound interface tables. Any record that has been processed cannot be reprocessed.

Click to jump to parent topicReceiving Customer Order Changes (860/ORDCHG)

This section provides an overview of customer order changes and discusses how to receive customer order changes.

Click to jump to top of pageClick to jump to parent topicUnderstanding Inbound Customer Order Changes

When a customer sends you purchase order changes (860/ORDCHG), the translator software maps the data to a flat file, and the Flat File Conversion program copies it to the EDI inbound interface tables. After this data is in the EDI inbound interface tables, you need to run the Inbound Edit/Update program for Customer Order Changes to compare the received changes to the original data on the open sales order. The Inbound Edit/Update program retrieves the data from the EDI inbound interface tables and compares it to the applicable sales orders.

When the Inbound Edit/Update program compares the data in the EDI inbound interface tables with the data in the sales order management application tables, the system:

After the Inbound Edit/Update program identifies the changed orders, you can use the Sales Order Entry program (P4210) to update the changed orders.

Using the EDI Inbound Interface Tables

When you run Inbound Edit/Update for customer order changes, the program uses these EDI inbound interface tables:

If you set the processing option to compare the data in the inbound EDI purchase order tables, the program also uses these EDI inbound interface tables:

Using Mapping Guidelines

Mapping is the process of converting information from one table structure to another.

In the F47131 table, the following fields must contain data before you can effectively use the Inbound Edit/Update program for customer order changes:

Map either the Order Number or the Customer Order Number to the header record. The program uses the EDI document number on the header to process detail records.

In the F47132 table, these fields must contain data before you can effectively use the Inbound Edit/Update program for customer order changes:

Click to jump to top of pageClick to jump to parent topicReceiving Customer Order Changes

Select Customer Order Change (G47213), Inbound Edit/Update.

The Inbound Edit/Update program updates EDI documents that are successfully processed in the EDI inbound interface tables to prevent duplicates. The program updates EDI documents by placing Y in the Processed column (EDSP) in all of the EDI inbound interface tables.

Click to jump to parent topicReceiving Advice into Sales (861/RECADV)

This section provides an overview of inbound receiving advices and discusses how to receive advice into sales.

Click to jump to top of pageClick to jump to parent topicUnderstanding Inbound Receiving Advices

Receiving advice (861/RECADV) is a document that represents customer confirmation to the supplier. This document indicates that the customer has received all or part of the order. The receiving advice document also includes the customer's acceptance or rejection of the items and describes the condition of the items upon their receipt.

In a nonconsignment warehouse environment, the customer sends the receiving advice after the customer records the receipt of goods (what was accepted and rejected). The supplier then updates the customer sales order with the information that the supplier received from the customer and issues an invoice to the customer.

When a supplier receives receiving advice into sales documents from a customer, the translator software maps the data into a flat file, and the Inbound Conversion program copies it to the EDI inbound interface tables. After this data appears in the EDI inbound interface tables, the supplier needs to copy the data to tables in the JD Edwards EnterpriseOne Sales Order Management system so that the JD Edwards EnterpriseOne Sales Order Management system can process the receiving advice documents.

To copy the data, run the Inbound Edit/Update program from the Customer Order menu (G47212). The Inbound Edit/Update program retrieves the data from the EDI inbound interface tables and copies it to the Sales Order Management application tables.

When the Inbound Edit/Update program copies the data into the tables in the JD Edwards EnterpriseOne Sales Order Management system, the JD Edwards EnterpriseOne Sales Order Management system:

Depending upon the business environment, the transaction can be inbound to sales or inbound to purchasing. This transaction can also be sent out of purchasing.

Using the EDI Inbound Interface Tables

When you run Inbound Edit/Update for receiving advice into sales, the program uses these EDI inbound interface tables:

Using Mapping Guidelines

Mapping is the process of converting information from one table structure to another.

In the F47071 table, the following fields must contain data before you can use the Inbound Edit/Update program for receiving advice into sales effectively:

In the F47072 table, these fields must contain data before you can use the Inbound Edit/Update program for receiving advice into sales effectively:

Map the JD Edwards EnterpriseOne sales order detail line number in the EDI receiving advice detail record.

Map the total quantity received to UREC. Other quantities that are informational only should be mapped to URET, UDMG, UREJ, UIQ1, UIQ2, and UIQ3. The informational quantities display on the Damaged/Rejected Goods Report along with their corresponding reason code, but they are not used in processing.

Updating Application Tables

When you run Inbound Edit/Update for receiving advice into sales, the program copies the data from the EDI interface tables and updates these application tables in the JD Edwards EnterpriseOne Sales Order Management system:

Click to jump to top of pageClick to jump to parent topicReceiving Advice Into Sales

Select Receiving Advice Sales (G47216), Inbound Edit/Update.

The Inbound Edit/Update program updates EDI documents that are successfully processed in the EDI inbound interface tables to prevent duplicates. The program updates EDI documents by placing Y in the Processed column (EDSP) in all of the EDI inbound interface tables.

Click to jump to parent topicReceiving Ship and Debit Claim Acknowledgments (845/PRICAT)

This section provides an overview of inbound ship and debit claim acknowledgments, lists prerequisites, and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Inbound Ship and Debit Claim Acknowledgments

Electronics distributors, suppliers, and manufacturers often enter into agreements to address the cost fluctuations associated with electronic components and products. These agreements can result in a distributor receiving credit back from the supplier or manufacturer for products shipped. In the electronics industry, the process for these agreements is referred to as Ship and Debit.

Based on the established agreements, electronics distributors submit claims to electronics suppliers. Some suppliers notify the distributors when claims are received.

Flat File Cross-Reference for Acknowledgments

The system needs to identify the flat file with the claim acknowledgments before it can upload the data. When you run the inbound flat file conversion program, the system retrieves the data from the flat files. You complete these setup steps only once.

Before you can set up the flat file cross-reference, you must set up the folders for the flat files on the appropriate drives of the computer or network.

Some suppliers send acknowledgements when they receive the submitted claims. When you run the Flat File Conversion program (or alternatively, the Ship and Debit Update Report (R47762Z1) for claim acknowledgments, the system copies data from the F4576Z1 table and updates the F4576 table.

You can set up both proof and final versions of the Ship and Debit Update Report program. In proof mode, the system does not update any records. When you run the proof version first, you can check for errors and make any necessary corrections before you run the final version. You can also set the options to update the status of the claims when you run the final version of the program.

The system differentiates EDI transactions and their related components by using these key fields:

Using Mapping Guidelines

Mapping is the process of converting information from one table structure to another. At a minimum, these fields in the interface table must contain data before you can effectively convert the inbound claim acknowledgments:

See Also

Working with Ship and Debit Adjustments

Click to jump to top of pageClick to jump to parent topicPrerequisites

Before you complete the tasks in this section, you must:

Click to jump to top of pageClick to jump to parent topicSetting Up the Flat File Cross-Reference for Acknowledgments

Select Electronic Commerce Interoperability (G47311), Flat File Cross Reference.

Important! When you enter a path and file name for the flat file that identifies where the system uploads the data, any folders in the file name path must already exist. The system does not create any folders. For example, use double back slashes (\\) in the filename. c:\\Claim Acknowledgment\\F47762Z1.txt.

Click to jump to top of pageClick to jump to parent topicReceiving Claim Acknowledgments (845/PRICAT)

Select Electronic Commerce Interoperability (G47311), Inbound Flat File Conversion.

Click to jump to parent topicReceiving Ship and Debit Claim Status (849/ORDRSP)

This section provides an overview of inbound ship and debit claim status, lists prerequisites, and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Inbound Ship and Debit Claim Status

Electronics distributors, suppliers, and manufacturers often enter into agreements to address the cost fluctuations associated with electronic components and products. These agreements can result in a distributor receiving credit back from the supplier or manufacturer for products shipped. In the electronics industry, the process for these agreements is referred to as Ship and Debit.

Based on the established agreements, electronics distributors submit claims to electronics suppliers. After suppliers process the claims, they notify the suppliers on the status of the claim. If a claim has been rejected, the notification includes a reason code.

Flat File Cross-Reference

The system needs to identify the flat file with the claim status information before it can upload the data. From the Electronic Commerce Interoperability menu (G47311), select Inbound Flat File Conversion, and then select the version to receive claim acknowledgments (849/ORDRSO). When you run the inbound flat file conversion programs, the system retrieves the data from the flat files. The program copies the data from the F4576Z1 table) and updates the F4576 table. You complete these setup steps only once.

Before you set up the flat file cross-reference, set up the folders for the flat files on the appropriate drives of the computer or network.

Notifications of Claim Status

After the supplier has processed the claims, they notify you with either an approved or rejected status. Additionally, the claim amount might be a different amount than what you submitted originally. When you run Inbound Flat File Conversion (or alternatively, the correct version of the Ship and Debit Update Report), the system copies from the F4576Z1 table and updates the F4576 table.

You can set up both a proof and a final version of the Ship and Debit Update Report program. In proof mode, the system does not update any records. When you run the proof version first, you can check for errors and make any necessary corrections before you run the final version. You can also set the options to update the status of the claims when you run the final version of the program.

The system differentiates EDI transactions and their related components by using these key fields:

Using Mapping Definitions

Mapping is the process of converting information from one table structure to another. At a minimum, these fields in the interface table must contain data before you can effectively convert the inbound claim status:

Click to jump to top of pageClick to jump to parent topicPrerequisites

Before you complete the tasks in this section:

Click to jump to top of pageClick to jump to parent topicSetting up the Flat File Cross-Reference for Claim Status

Select Electronic Commerce Interoperability (G47311), Flat File Cross Reference.

Important! When you enter a path and file name for the flat file that identifies where the system uploads the data, any folders in the file name path must already exist. The system will not create the folders. Use double back slashes (\\) in the filename. For example, c:\\Claim Status\\F47762Z1.txt.

Click to jump to top of pageClick to jump to parent topicReceiving Notifications of Claim Status (849/ORDRSP)

Select Electronic Commerce Interoperability (G47311), Inbound Flat File Conversion.

Click to jump to parent topicSending Responses to Requests for Quotes (843/QUOTES)

This section provides an overview of responses to requests for quotes (RFQs) and discusses how to send responses to RFQs.

Click to jump to top of pageClick to jump to parent topicUnderstanding Responses to RFQs

This section discusses the Outbound Extraction Program.

Running the Outbound Extraction Program to Send Responses to RFQs

Use the Outbound Extraction program to send a response to a request for quote (843/QUOTES). From the Request for Quote (RFQ), Sales menu (G47211), select Outbound Extraction.

Run this program after the system receives and processes an inbound request for quotation.

You can set processing options to:

The Outbound Extraction program extracts records from the Sales Order Management application tables and creates Responses to Requests for Quotes within the EDI outbound interface tables so that they can be sent to the trading partner.

Using Application Tables

When you run Outbound Extraction for responses to RFQs, the program extracts data from these application tables:

Using EDI Outbound Interface Tables

When you run Outbound Extraction for responses to RFQs, the program creates records in these EDI outbound interface tables. After these records are created, you need to perform the flat file conversion process:

See Also

Entering Quote Orders

Click to jump to top of pageClick to jump to parent topicSending Responses to Requests for Quotes

Select Request for Quote (RFQ) Sales (G47211), Outbound Extraction.

Click to jump to parent topicSending Order Acknowledgments (855/ORDRSP)

This section provides an overview of outbound order acknowledgments and discusses how to send order acknowledgments.

Click to jump to top of pageClick to jump to parent topicUnderstanding Outbound Order Acknowledgments

Run the Outbound Extraction program (R42565) from the Customer Order menu (G47212) to convey receipt of the order along with pricing and availability information to the customer (855/ORDRSP). You run this program after processing inbound customer orders.

The Outbound Extraction program extracts records from the Sales Order Management application tables and creates Order Acknowledgments within the EDI Outbound Interface tables so they can be sent to the trading partner.

Using Application Tables to Send Order Acknowledgments

When you run Outbound Extraction for order acknowledgments, the program extracts data from these application tables:

Using EDI Outbound Interface Tables to Send Order Acknowledgments

When you run Outbound Extraction for order acknowledgments, the program creates records in these EDI outbound interface tables (after these records are created, you need to perform the flat file conversion process):

Click to jump to top of pageClick to jump to parent topicSending Order Acknowledgments

Select Customer Order (G47212), Outbound Extraction.

Click to jump to parent topicSending Order Change Acknowledgments (865/ORDRSP)

This section provides an overview of outbound order change acknowledgments and discusses how to send order change acknowledgments.

Click to jump to top of pageClick to jump to parent topicUnderstanding Outbound Order Change Acknowledgments

Run the Outbound Extraction program (R47142) for order change acknowledgments (865/ORDRSP) to confirm that an order was changed and to convey pricing and availability information to the customer. Run this program after receiving and processing an inbound customer order change.

When you run Outbound Extraction for order change acknowledgments, the program also updates the status of the sales order detail lines according to either:

The Outbound Extraction program extracts records from the Sales application tables and creates Order Change Acknowledgments within the EDI Outbound Interface tables so that they can be sent to the trading partner.

Using EDI Outbound Interface Tables to Send Order Change Acknowledgments

When you run Outbound Extraction for order change acknowledgments, the program creates records in these EDI outbound interface tables (after these records are created, you need to perform the flat file conversion process):

Using Application Tables to Send Order Change Acknowledgments

When you run Outbound Extraction for order change acknowledgments, the program extracts data from these application tables:

Click to jump to top of pageClick to jump to parent topicSending Order Change Acknowledgments

Select Customer Order Change (G47213), Outbound Extraction.

Click to jump to parent topicSending Shipping Notices (856/DESADV)

This section provides an overview of outbound shipping notices, lists a prerequisite, and discusses how to send shipping notices.

Click to jump to top of pageClick to jump to parent topicUnderstanding Outbound Shipping Notices

A Shipping Notice (856/DESADV) is a document that gives the customer advanced notice that the order they have placed with the supplier has been shipped.

The Outbound Extraction program (R47032) extracts records from the Sales application tables and creates Shipping Notices within the EDI Outbound Interface tables so they can be sent to the trading partner.

Run the Outbound Extraction program for Shipping Notices to generate shipping notices for customers. Outbound shipping notices contain detail information arranged in hierarchical levels. Generate the outbound shipping notice after the online shipment confirmation occurs in the JD Edwards EnterpriseOne Sales Order Management system. During online shipment confirmation, enter related shipping information, such as carrier, container ID, shipper number, and quantity shipped.

The way that you set the processing options and data sequencing for this program is crucial to produce the correct hierarchical levels. You must first specify the hierarchical levels in the F47HL table or in the processing options of the Outbound Extraction program for Shipping Notices. Then, specify the fields on which to sequence and sort during data sequencing of the Outbound Extraction program. This action creates the hierarchical levels. The fields and level breaks that you specify in the data sequencing must correspond to the level breaks specified in the processing options. The shipment ID specified in the processing options should be the highest level specified in the data sequencing.

In the processing options, you can specify the value placed in the Shipment ID field using one of these four fields, depending upon how you set up and record the shipping process:

The Shipping Notice Outbound Extraction program copies the value in the selected field into the Shipment Identifier field (SYSPID) in the EDI outbound interface tables.

Generating Shipping Notices

When you run the Outbound Extraction program (R47032) for shipping notices, the program processes records from the F49211 table and F4942 table. The program does not write records to the outbound F47037 table during detail processing, but accumulates the quantity, extended amount fields, shipping quantity, extended cost, extended price, and gross weight into Total fields. When the program finds a level break, it writes a record to the outbound F47037 table, which contains the accumulated field totals for that level. When the program finds the highest level break, it writes a record to the F47036 table.

Example: Generating an Outbound Shipping Notice

The purpose of this example is to illustrate the structure of a typical Shipping Notice document.

The first hierarchical level is shipment, the second is order number, and the third is item number. Each of these level breaks occurs in the F47037 table. The value placed next to a level is the value that will be placed in the hierarchical level field (SZHL03) in the F47036 table.

This table is an example of shipment data for which you could send an Advanced Shipping Notice:

Shipment ID

Order Number

Item Number

Quantity

MF123

724 Sales Order (SO)

1001

5

 

 

1002

7

 

850 SO

8787

4

 

 

5454

3

MF789

548 SO

1001

6

 

 

1002

17

 

653 SO

8787

8

 

 

5454

3

In this example hierarchical setup, the highest level break, is shipment. The F47036 table contains the highest level break, or Shipment ID. The EDI Ship Notice/Manifest Header table would contain these two records:

Type

Sequence

EDI Document Number

Shipment ID

H

01

1

MF123

H

01

2

MF789

The outbound F47037 table contains the records listed in this table. This table displays three level breaks for the data. The highest level break is Shipment ID, the next break is Order Number, and the third break is Item Number. The quantity (QTY) column reflects the total amount for that level break. For example, Shipment ID MF123 contains a total of 19 items. Order Number 724 and Shipment ID MF123 contain a total of 12 items. Item Number 1001, Order Number 724, and Shipment MF123 contain a total of five items.

Type

Seq.

EDI Doc #

EDI Line #

Hier. Lvl

Hier. Code

Shipment ID

Order #

Item #

Qty

D

01

1

1

1

S

MF123

724 SO

1001

19

D

01

1

2

2

O

MF123

724 SO

1001

12

D

01

1

3

3

I

MF123

724 SO

1001

5

D

01

1

4

3

I

MF123

724 SO

1002

7

D

01

1

5

2

O

MF123

850 SO

8787

7

D

01

1

6

3

I

MF123

850 SO

8787

4

D

01

1

7

3

I

MF123

850 SO

5454

3

D

01

2

1

1

S

MF789

548 SO

1001

34

D

01

2

2

2

O

MF789

548 SO

1001

23

D

01

2

3

3

I

MF789

548 SO

1001

6

D

01

2

4

3

I

MF789

548 SO

1002

17

D

01

2

5

2

O

MF789

653 SO

8787

11

D

01

2

6

3

I

MF789

653 SO

8787

8

D

01

2

7

3

I

MF789

653 SO

5454

3

The key to creating the various hierarchy levels is the data sequencing. This table is an example of data sequencing used to produce the Advanced Shipping Notice:

Field

Sequence

Shipment ID (Order Number, Container ID, Delivery Note, Invoice, Shipment Number, or Job Number)

1

Order Number

2

Item Number

3

Using Mapping Guidelines

Map the outbound F47036 table to the Beginning Segment of Ship Notice (BSN) Header segment.

You can define the outbound F47037 table to the translator software multiple times, with the Hierarchical Level as the table identifier. Each record in the F47037 table contains information that relates to the last detail record processed when the record was written to the table at the level break. Therefore, you need to define the information that relates to the level that you are processing to the translator software.

For example, if you define a level 1 record with Hierarchy Code S (shipment) to the translator software, you must map fields from the outbound F47037 table that relate to the shipment, such as shipment ID, carrier number, container number, and total quantity shipped. The totals for the fields in this record represent the accumulation of all lower level break fields.

When you define the final level break, such as level break 3 or Hierarchy Code I (Item), you must map fields that are related to the item, such as item number, customer item number, descriptions, quantity shipped, and total price. The totals for the field are for this record only.

Using Application Tables

When you run the Outbound Extraction program (R47032) for shipping notices, the program extracts data from these application tables:

Using EDI Outbound Interface Tables

When you run the Outbound Extraction program (R47032) for shipping notices, the program creates records in these EDI outbound interface tables (after these records are created, you need to perform the flat file conversion process):

See Also

Processing Shipments According to UCC 128

Click to jump to top of pageClick to jump to parent topicPrerequisite

You need to review and understand the UCC 128 setup and the processing that occurs within the JD Edwards EnterpriseOne Sales Order Management system.

Click to jump to top of pageClick to jump to parent topicSending Shipping Notices

Select Shipping Notice (G47215), Outbound Extraction.

Click to jump to parent topicSending Invoices (810/INVOIC)

This section provides an overview of outbound invoice transmissions and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Outbound Invoice Transmissions

You run the Outbound Extraction program (R42565) from the Sales Invoice menu to generate EDI invoices (810/INVOIC) for customers.

When you run the Outbound Extraction program, note that:

The Outbound Extraction program extracts records from the sales application tables and creates Invoices within the EDI Outbound Interface tables so that they can be sent to the trading partner.

Using Application Tables When Sending Invoices

When you run Outbound Extraction for invoices, the program extracts data from these application tables:

Using EDI Outbound Interface Tables When Sending Invoices

When you run Outbound Extraction for invoices, the program creates records in these EDI outbound interface tables (after these records are created, you need to perform the flat file conversion process):

Click to jump to top of pageClick to jump to parent topicSending Invoices

Select Sales Invoice (G47217), Outbound Extraction.

Click to jump to top of pageClick to jump to parent topicRunning the EDI Invoice Extraction Conversion Program (R47042C)

Select Sales Invoice (G47217), Outbound Flat File Creation.

The R47042C EDI Invoice Flat File Creation enables you to generate the flat file from the database records that exist in these outbound EDI invoice tables:

For Demand Scheduling, the system also uses information from these tables:

Click to jump to top of pageClick to jump to parent topicPurging Outbound EDI Invoice Documents

Select Sales Invoice (G47217), Purge/Archive.

You run the EDI Invoice Outbound Purge (R47049) to purge all EDI invoice transactions. The system marks them as sent by the EDI Invoice Update as Sent program (R47047). The system purges information from these tables:

For Demand Scheduling, the system also purges information from these tables:

Click to jump to parent topicSending Ship and Debit Claims (844/ORDCHG)

This section includes an overview of ship and debit claims, lists a prerequisite, and discusses how to send ship and debit claims.

Click to jump to top of pageClick to jump to parent topicUnderstanding Ship and Debit Claims

Electronics distributors, suppliers, and manufacturers often enter into agreements to address the cost fluctuations associated with electronic components and products. These agreements can result in a distributor receiving credit back from the supplier or manufacturer for products shipped. In the electronics industry, the process for these agreements is referred to as Ship and Debit. Based on the established agreements, electronics distributors submit claims to electronics suppliers.

Run the Ship and Debit Claim Output program (R47761Z1) to submit a claim to a supplier with whom you have an agreement. When you run this program, the system extracts data from the F4576 table and creates records in the F4576Z1 table.

You can set up both proof and final versions of this program. In proof mode, the system does not update any records. When you run the proof version first, you can check for errors and make any necessary corrections before you run the final version. You can also set the options to update the status of the claims when you run the final version of the program.

Click to jump to top of pageClick to jump to parent topicPrerequisite

Before you send ship and debit claims, set up a version of the Ship and Debit Claim Output program (R47761Z1) for each supplier with whom you have an agreement. Identify the path and location for the flat file on the File tab.

Click to jump to top of pageClick to jump to parent topicSending Ship and Debit Claims

Select Ship and Debit Processing (G4511), Ship and Debit Claim Output.