EDI business document Order

The business document Order describes the order cycle between trading partners and includes these EDI messages:

Complete these steps to process a simple order cycle:

  1. ORD

    In the Purchase Order (tdpur4100m900) session, create a purchase order that can be sent electronically. Approve the purchase order and prepare an EDI message using the Print Purchase Orders (tdpur4401m000) session.

  2. ORS

    In the Sales Order (tdsls4100m900) session, review the order. Approve the order and generate the acknowledgement EDI message in the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) session.

  3. ORC

    If required, change and re-approve the purchase order in the Purchase Order (tdpur4100m900) session. Again, prepare the EDI message using the Print Purchase Orders (tdpur4401m000) session.

  4. OCA

    Review the changed order in the Sales Order (tdsls4100m900) session, re-approve the order, and print the acknowledgement EDI message in the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) session.

Order (ORD)

The order cycle is initiated when you do either of the following:

  • Specify a purchase order in the Purchase Order (tdpur4100m900) session for a selling company that is set up as a trading partner.
  • Use an order type that has a link to an EDI message and that has the Print Purchase Orders (tdpur4401m000) activity linked. When you print the purchase order, the New EDI Messages Have Been Prepared message appears. The EDI process begins after you create and print the purchase order.

After you prepare a purchase order for EDI in Procurement, the outgoing EDI Order message (ORD) is generated by Electronic Data Interchange. The Messages to be Generated (ecedi7100m000) session verifies whether a message is prepared that must be sent to the purchasing company’s supplier, which is the selling company.

In the Direct Network Communication (ecedi7205m000) session, you can receive and generate EDI messages. If you select the Generate Outgoing Message before Connection check box in the Networks (ecedi0120s000) session, you can generate all outgoing messages prior to reading incoming messages. Running the session creates the ASCII files for the prepared EDI messages. EDI messages generated by LN for external EDI are stored in the appl_from subdirectory. For internal EDI, all generated and received messages are stored in the appl_comm subdirectory, because each company has the same network path.

If you do not use the option to generate outgoing messages before connection in the Networks (ecedi0120s000) session, you can use the Generate EDI Messages (ecedi7201m000) session to create the ASCII files for outgoing messages.

Translation software translates files received from an external trading partner into the file format defined by the BEMIS conversion setups. The translated ASCII files are placed into the appropriate appl_to directory. Internal EDI does not require translation of the files.

Use the Direct Network Communication (ecedi7205m000) session to receive the purchase order. When the customer’s order is received, a sales order is created in Sales. The Remarks in Copied Messages report is generated, which shows the customer order data, the newly created sales order number, sales order lines, and any related remarks.

Order Acknowledgement/Response (ORS)

Sales orders can be reviewed in the Sales Order (tdsls4100m900) session. If necessary, you can make changes to the order. If you print the order acknowledgement in the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) session, the outgoing EDI Order Acknowledgment/Response (ORS) message is prepared.

To send an acknowledgment to the customer, which is the purchasing company, use the Direct Network Communication (ecedi7205m000) session. A report is created that shows which EDI messages are generated. External EDI business partner messages are placed in the appl_from subdirectory under the directory specified for the network. Translation software retrieves the message. Internal EDI business partner messages are stored in the appl_comm subdirectory.

Order Change (ORC)

To change a purchase order that has been sent to the supplier, you can send the supplier an Order Change (ORC) message. Maintain the purchase order in the Purchase Order (tdpur4100m900) session.

To notify the supplier that you want to:

  • Cancel an order line, cancel the order line in Procurement and assign a change type code representing a canceled line.
  • Delete an order line, assign a change type code representing a deleted line. After the Order Change Acknowledgment/Response (OCA) is received from the supplier, you can delete the order line.

Print the changed purchase order lines. Select the lines you want to print in the Print Purchase Orders (tdpur4401m000) session. When the session is run, LN verifies whether the order(s) is prepared for EDI and stored in the Messages to be Generated (ecedi7100m000) session.

If the Generate Outgoing Message before Connection check box is selected in the Networks (ecedi0120s000) session, you can use the Direct Network Communication (ecedi7205m000) session to generate the Order Change (ORC) message. If the Generate Outgoing Message before Connection check box is cleared, you can use the Generate EDI Messages (ecedi7201m000) session to create the ASCII files for outgoing messages. Both sessions generate a report that shows which messages were generated, and both display the reference number, message, and order number.

Use the Direct Network Communication (ecedi7205m000) session to receive the changed purchase order (OCA). When the session receives the customer’s changes to an order, the sales order is updated. A Remarks in Copied Messages report is generated, which shows the order and order lines that were updated, as well as any related remarks.

Note: 

Change type and change reason information is automatically defaulted from the Purchase Order Parameters (tdpur0100m400) or the Sales Order Parameters (tdsls0100s400) session, when:

  • An order line is manually changed or canceled.
  • An order line is added to an existing order.
  • An order line detail is split.
  • Backorder lines are generated. If the sales order line is already completely delivered after a change backorder message comes in from Procurement, a new sales order line is created with a Default Change Type for Add Order Line. If a backorder line is confirmed as a result of partial delivery, the incoming change message of Default Change Type for Change Order Line is processed at the selling company for the open backorder line.

Order Change Acknowledgement/Response (OCA)

You can review updates to the order in the Sales Order (tdsls4100m900) session. To acknowledge the changes, use the Order Acknowledgment/Response (ORS) or the Order Change Acknowledgment/Response (OCA) message. You can define which message must be sent in the EDI Order Change Response field of the Sold-to Business Partner (tccom4110s000) session.

When printing the acknowledgement, select the lines you want to print in the Print Purchase Orders (tdpur4401m000) session. The outgoing EDI Order Acknowledgment/Response (ORS) message, or the Order Change Acknowledgment/Response (OCA) message is prepared.

Use the Direct Network Communication (ecedi7205m000) session to send the acknowledgement to the customer/purchasing company. A report is created that shows which EDI messages are generated. External EDI business partner messages are placed in the appl_from subdirectory under the directory specified for the network. Translation software retrieves the message. Internal EDI business partner messages are stored in the appl_comm subdirectory.

Related topics