user guide for edi business documents - docs.infor.com document explains the types of edi business...

Infor LN Electronic CommerceUser Guide for EDI BusinessDocuments

Copyright © 2018 Infor

Important Notices

The material contained in this publication (including any supplementary information) constitutes and contains confidentialand proprietary information of Infor.By gaining access to the attached, you acknowledge and agree that the material (including any modification, translationor adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the soleproperty of Infor and that you shall not gain right, title or interest in the material (including any modification, translation oradaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solelyin connection with and the furtherance of your license and use of software made available to your company from Inforpursuant to a separate agreement, the terms of which separate agreement shall govern your use of this material and allsupplemental related materials ("Purpose").In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain suchmaterial in strict confidence and that your use of such material is limited to the Purpose described above. Although Inforhas taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrantthat the information contained in this publication is complete, does not contain typographical or other errors, or will meetyour specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise,for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication(including any supplementary information), whether such errors or omissions result from negligence, accident or anyother cause.Without limitation, U.S. export control laws and other applicable export and import laws govern your use of this materialand you will neither export or re-export, directly or indirectly, this material nor any related materials or supplementalinformation in violation of such laws, or use such materials for any purpose prohibited by such laws.

Trademark Acknowledgements

The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliatesand subsidiaries. All rights reserved. All other company, product, trade or service names referenced may be registeredtrademarks or trademarks of their respective owners.

Publication Information

comediug (U8998)Document code

10.4 (10.4)Release

January 10, 2018Publication date

About this document

.................7Chapter 1 Introduction........................................................................................................

.................7An overview of EDI business documents....................................................................

.................9Chapter 2 Business Document Order................................................................................

.................9EDI business document Order.....................................................................................

...............10Order (ORD).......................................................................................................

...............11Order Acknowledgement/Response (ORS).......................................................

...............11Order Change (ORC).........................................................................................

...............12Order Change Acknowledgement/Response (OCA).........................................

...............13Chapter 3 Business Document Schedule.........................................................................

...............13EDI business document Schedule...............................................................................

...............13Purchase schedules...........................................................................................

...............14Purchase releases.............................................................................................

...............15Preparing EDI messages for push schedules....................................................

...............15Preparing EDI messages for pull forecast schedules........................................

...............15Preparing EDI messages for pull call-off schedules..........................................

...............16Processing EDI messages.................................................................................

...............19Chapter 4 Business Document Delivery...........................................................................

...............19EDI business document Delivery.................................................................................

...............20Advance Shipment Notification (ASN)...............................................................

...............20Reprocessing messages with errors..................................................................

...............21Receipt Discrepancy Notification (RDN)............................................................

...............23Chapter 5 Business Document Freight.............................................................................

...............23EDI business document Freight...................................................................................

...............23Load Information to Carrier (FML).....................................................................

...............24Carrier Status Information (FMS).......................................................................

Table of Contents

...............25Chapter 6 Business Document Invoice.............................................................................

...............25EDI business document Invoice..................................................................................

...............26Invoice (INV)......................................................................................................

...............27Chapter 7 Business Document Error Handling................................................................

...............27EDI business document Error Handling.......................................................................

...............27Sending Error Notification (824/APERAK) to supplier.......................................

...............27Receiving Error Notification (824/APERAK) from customer..............................

...............28Resending canceled and corrected shipment notices in response to receivedError Notifications..............................................................................................

...............29Appendix A Glossary..........................................................................................................

Index

This document explains the types of EDI business documents and the associated EDI messages, assupported by BEMIS.

ObjectiveA business document describes a business process between trading partners. The objective of thisguide is to describe the various types of business documents in the context of EDI and to give a functionalexplanation of the involved EDI messages, which are supported by Baan Electronic Message InterchangeSystem (BEMIS).

Intended audienceThis user guide is intended for the following categories of users: ▪ Users who develop business documents/EDI messages.

▪ Users who want to understand what they can expect from a BEMIS business document andits related EDI messages, as developed by LN.

Document summaryThe first chapter, Introduction, describes the purpose and the general characteristics of the businessdocuments in the context of EDI.

The following chapters describes the EDI messages that relate to the various types of businessdocuments.

This user guide is also provided with a glossary list and an index, which you can find at the end of thisbook.

References ▪ To understand the purpose, contents, and setup of BEMIS, refer to User Guide for BEMIS

U8912 US.

▪ For details on the content and structure of the various business document types, refer toDocument Definitions at Infor EDI .

How to read this documentThis document was assembled from online Help topics. As a result, references to other sections in themanual are presented as shown in the following example:

For details, refer to Introduction. To locate the referred section, please refer to the table of contents oruse the index at the end of the document.

Underlined terms indicate a link to a glossary definition. If you view this document online, you can clickthe underlined term to go to the glossary definition at the end of the document.

Infor LN Electronic Commerce | User Guide for EDI Business Documents | 5

About this document

http://edi.infor.com

Comments?We continually review and improve our documentation. Any remarks/requests for information concerningthis document or topic are appreciated. Please e-mail your comments to [email protected] .

In your e-mail, refer to the document number and title. More specific information will enable us to processfeedback efficiently.

Contacting InforIf you have questions about Infor products, go to the Infor Xtreme Support portal.

If we update this document after the product release, we will post the new version on this website. Werecommend that you check this website periodically for updated documentation.

If you have comments about Infor documentation, contact [email protected] .

6 | Infor LN Electronic Commerce | User Guide for EDI Business Documents

About this document

mailto:[email protected]

mailto:[email protected]

An overview of EDI business documentsElectronic data interchange (EDI) is used to exchange business documents between two systems. Userscan specify business documents of various external EDI standards, such as VDA, UN/ EDIFACT, Odette,and ANSI. With the Baan Electronic Message Interchange System (BEMIS) standard, external standardsare converted to an internal LN standard. Conversion of the internal standard to an external standardand vice versa is performed by an EDI translator.

A business document describes a business process between trading partners.

BEMIS supports the following business documents: ▪ Order (p. 9)

▪ Schedule (p. 13)▪ Delivery (p. 19)▪ Freight (p. 23)▪ Invoice (p. 25)▪ Error Handling (p. 27)


1Chapter 1Introduction


Introduction

EDI business document Order

The business document Order describes the order cycle between trading partners and includes theseEDI messages: ▪ ORD

Order▪ ORS

Order Acknowledgement/Response▪ ORC

Order Change▪ OCA

Order Change Acknowledgement/Response

Complete these steps to process a simple order cycle: 1. ORD

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


2Chapter 2Business Document Order

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

3. ORCIf 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. OCAReview the changed order in the Sales Order (tdsls4100m900) session, re-approve the order,and print the acknowledgement EDI message in the Print Sales OrderAcknowledgements/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 MessagesHave Been Prepared message appears. The EDI process begins after you create and printthe purchase order.

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

In the Direct Network Communication (ecedi7205m000) session, you can receive and generate EDImessages. 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 generatedby LN for external EDI are stored in the appl_from subdirectory. For internal EDI, all generated andreceived messages are stored in the appl_comm subdirectory, because each company has the samenetwork 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 createthe ASCII files for outgoing messages.

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

Use the Direct Network Communication (ecedi7205m000) session to receive the purchase order. Whenthe customer’s order is received, a sales order is created in Sales. The Remarks in Copied Messages


Business Document Order

report is generated, which shows the customer order data, the newly created sales order number, salesorder lines, and any related remarks.

Order Acknowledgement/Response (ORS)Sales orders can be reviewed in the Sales Order (tdsls4100m900) session. If necessary, you can makechanges to the order. If you print the order acknowledgement in the Print Sales OrderAcknowledgements/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 NetworkCommunication (ecedi7205m000) session. A report is created that shows which EDI messages aregenerated. External EDI business partner messages are placed in the appl_from subdirectory underthe directory specified for the network. Translation software retrieves the message. Internal EDI businesspartner 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 OrderChange (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 OrderChange Acknowledgment/Response (OCA) is received from the supplier, you can delete theorder 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 EDIand 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) sessionto generate the Order Change (ORC) message. If the Generate Outgoing Message before Connectioncheck box is cleared, you can use the Generate EDI Messages (ecedi7201m000) session to create theASCII files for outgoing messages. Both sessions generate a report that shows which messages weregenerated, and both display the reference number, message, and order number.

Use the Direct Network Communication (ecedi7205m000) session to receive the changed purchaseorder (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 wereupdated, as well as any related remarks.



Note

Change type and change reason information is automatically defaulted from the Purchase OrderParameters (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 achange backorder message comes in from Procurement, a new sales order line is createdwith a Default Change Type for Add Order Line. If a backorder line is confirmed as a resultof partial delivery, the incoming change message of Default Change Type for Change OrderLine 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 thechanges, use the Order Acknowledgment/Response (ORS) or the Order ChangeAcknowledgment/Response (OCA) message. You can define which message must be sent in the EDIOrder 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 theOrder Change Acknowledgment/Response (OCA) message is prepared.

Use the Direct Network Communication (ecedi7205m000) session to send the acknowledgement to thecustomer/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 directoryspecified for the network. Translation software retrieves the message. Internal EDI business partnermessages are stored in the appl_comm subdirectory.



EDI business document ScheduleThe business document Schedule describes the processing of EDI messages that are used in a supplychain environment, which makes use of purchase schedules to communicate requirements to the sellingcompany.

Purchase schedules represent a timetable of planned requirements, and support long-term purchasingpractices that have frequent deliveries. Purchase schedules are used rather than standard purchaseorders when a more detailed way of specifying delivery dates and times for material requirements isrequired. Purchase schedules are unique for an item and are sent to the purchase business partner ina purchase release.

Purchase schedules

The following types of purchase schedules exist: ▪ Push schedule

A list of time-phased requirements, generated by a central planning system, such as EnterprisePlanning or Project that is sent to the purchase business partner. Push schedules containboth a forecast for the longer term and actual orders for the short term. A push schedule is anonreferenced schedule.

▪ Pull forecast scheduleA list of time-phased planned requirements, generated by Enterprise Planning, that is sent tothe purchase business partner. Pull forecast schedules are only used for forecasting purposes.To order the items, a pull call-off schedule must be generated with the same schedule numberas the pull forecast schedule. Similar to a push schedule, a pull forecast schedule is also anonreferenced schedule.

▪ Pull call-off scheduleA list of time-phased specific requirements of purchased items, triggered from AssemblyControl, or Warehousing (KANBAN, Time-phased order point). A pull call-off schedule is areferenced schedule.


3Chapter 3Business Document Schedule

Purchase releases

The purchase schedule can be sent through the following purchase releases: ▪ Material release

A schedule on which forecast information is provided about shipping times, delivery times,and quantities. In general, a material release can be considered as a planning release. Forpush schedules, the material release can also include the actual order. In this case, the releaseis called a material release with shipping capabilities. A material release can include pushschedules or pull-forecast schedules.

▪ Shipping scheduleA schedule on which detailed information is given about shipping times or delivery times andquantities. A shipping schedule facilitates just-in-time (JIT) management. A shipping schedulecan include push schedules or pull call-off schedules.

▪ Sequence shipping scheduleA supplement to the material release or the shipping schedule with precise information aboutthe production or deliveries of the requirements. This schedule can include the production ordelivery sequence, the order, the place, and the time of unloading after shipment. A sequenceshipping schedule can only include pull call-of schedules.

Consequently, the business document schedule includes these messages: ▪ MRL

Material Release▪ SHP

Shipping Schedule▪ SEQ

Sequence Shipping Schedule


Business Document Schedule

Preparing EDI messages for push schedules

To prepare EDI messages for push schedules in a purchase release: 1. Create a purchase schedule header in the Purchase Schedules (tdpur3110m000) session

and purchase schedule lines in the Purchase Schedule Lines (tdpur3111m000) session.2. Create a purchase release line in the Generate Release Lines (tdpur3222m000) session.3. Approve the purchase release line in the Approve Release Lines (tdpur3222m100) session.4. Print the purchase release in the Print Purchase Releases (tdpur3422m000) session with the

Final Report and the Prepare EDI messages check boxes selected.

Note ▪ If the Release EDI Message Directly check box is selected in the Purchase Contract Line

Logistic Data (tdpur3102m000) session or the Items - Purchase Business Partner(tdipu0110m000) session, LN automatically prepares the EDI messages when a purchaserelease receives the status Scheduled in the Purchase Releases (tdpur3120m000) session.

▪ Use the Direct Network Communication (ecedi7205m000) session to generate the outgoingmessage. A report will list the messages that were generated. The outgoing messages for anexternal EDI business partner are stored in the appl_from directory for retrieval by translationsoftware.

▪ For information about release types, requirement types and corresponding EDI messages,refer to Purchase schedule release types.

Preparing EDI messages for pull forecast schedules

A pull forecast schedule can be generated only from the Generate Order Planning (cprrp1210m000)session in Enterprise Planning and cannot be created manually. Based on the parameters and triggers,the following steps are carried out automatically to prepare EDI messages for pull forecast schedulesin a purchase release: 1. A purchase schedule header is generated in the Purchase Schedules (tdpur3110m000) session

and purchase schedule lines are generated in the Purchase Schedule Lines (tdpur3111m000)session.

2. A purchase release is generated in the Generate Release Lines (tdpur3222m000) session.3. The purchase release is approved in the Approve Release Lines (tdpur3222m100) session.4. The purchase release is printed in the Print Purchase Releases (tdpur3422m000) session.

Preparing EDI messages for pull call-off schedules

A pull call-off schedule can be generated from Assembly Control through the Transfer Assembly PartSupply Messages (tiasc8220m000) session, or from Warehousing through the Generate Orders(KANBAN) (whinh2200m000) or Generate Orders (TPOP) (whinh2201m000) sessions. A pull call-off



schedule cannot be created manually. Based on the parameters and triggers, the following steps arecarried out automatically to prepare EDI messages for pull call-off schedules in a purchase release: 1. A purchase schedule (header) is generated in the Purchase Schedules (tdpur3110m000)

session. If the pull call-off schedule is preceded by a pull forecast schedule, LN searches forthe corresponding pull forecast schedule in the Purchase Schedules (tdpur3110m000) session.Once found, a pull call-off schedule is created with the same schedule number as the pullforecast schedule. In this way, forecasting data and ordering data are separated. If noforecasting data is generated, the pull call-off schedule, as generated in the PurchaseSchedules (tdpur3110m000) session, has no corresponding pull forecast schedule.

2. Schedule lines are generated in the Purchase Schedule Lines (tdpur3111m000) session. Ifthe release type that is linked to the pull call-off schedule is Sequence Shipping Schedule,a schedule line for each call-off is generated in the Purchase Schedule Lines (tdpur3111m000)session, but the sequence details for a particular call off, such as VIN number, and line stationare stored in the Sequence Shipping data (tdpur3517m000) session.

3. A purchase release is generated with the status Scheduled in the Purchase Releases(tdpur3120m000) session. With every generation of a schedule line, a release line detail recordis generated in the Purchase Release Line - Details (tdpur3522m000) session. This recordhas a one-to-one relationship with the schedule line.If the schedule is a sequence shipping schedule, however, the following applies:

▪ Only a purchase release header is created. No purchase release lines and purchaserelease line detail records are created, because items in a sequence shipping scheduleare required for a combination of vehicle number (VIN), line station, and assembly kit. Forthis reason, a link exists between the release header in the Purchase Releases(tdpur3120m000) session and the release lines in the Purchase Release Lines - SequenceShipping Data (tdpur3523m000) session.

▪ Depending on the settings of the Generate Release per Vehicle and Generate Releaseper Item check boxes in the Purchase Releases (tdpur3120m000) session, the releaseis either created by vehicle or by item or business partner.

4. The purchase release is printed in the Print Purchase Releases (tdpur3422m000) session.

Processing EDI messagesYou can use the Direct Network Communication (ecedi7205m000) session to receive the customer’snew release or to update an existing release.

When you receive a new Material Release (MRL), Shipping Schedule (SHP), or Sequence ShippingSchedule (SEQ), a sales release and corresponding schedule(s) are created in Sales. Depending onthe release type, an update to an existing sales release results in a new revision for the sales releaseand the corresponding schedule(s), or in updated sales release/sales schedule(s).

When EDI messages are processed, this data is generated: ▪ A sales release with revision number one in the Sales Releases (tdsls3512m000) session. If

a new EDI message is received for an existing sales release, a sales release revision is createdwith revision number two, and so on.



▪ Sales release lines in the Sales Release Lines (tdsls3508m000) session.

▪ Sales release position details in the Sales Release Line Details (tdsls3515m000) session, forreferenced schedules of the Shipping Schedule type. The Schedule Revisions forReferenced Shipping Schedules check box in the Schedule Terms and Conditions(tctrm1131m000) session determines whether sales schedule revision numbers are used forreferenced shipping schedules. If this check box is cleared and if you receive an update of areferenced shipping schedule, no new sales schedule revision number is created. Instead,the sales schedule is updated. If an update arrives for a sales schedule line, also the salesschedule line is updated. To keep track of the updates, LN files the sales schedule line updatesas revisions in the Sales Release Line Details (tdsls3515m000) session. Consequently a salesrelease position detail refers to a sales schedule line.

▪ A sales schedule with a sales schedule revision number of one in the Sales Schedules(tdsls3111m000) session. If new requirements are received for an existing sales schedule, asales schedule revision is created with revision number two, and so on. The previous salesschedule revision and its requirements are no longer valid after the new sales schedule revisionis approved.

▪ Sales schedule lines in the Sales Schedule Lines (tdsls3107m000) session.

▪ Sequence shipping information in the Shipping Sequence (whinh4520m000) session, andshipping sequence detail revisions in the Sequence Shipping Information (tdsls3517m000)session, provided the schedule is referenced and of the Sequence Shipping Schedule type.

As with all incoming EDI messages, the Remarks in Copied Messages report is generated. The reportdisplays the sales release number and corresponding lines added along with related remarks.



EDI business document Delivery

The business document Delivery describes the shipment and receipt of ordered goods and includesthese EDI messages: ▪ ASN

Advance Shipment Notification▪ RDN

Receipt Discrepancy Notification

To ship and receive ordered goods: 1. After a sales order is released to Warehousing in the Release Sales Orders to Warehousing

(tdsls4246m000) session, prepare the order for shipment to the purchasing company usingthe Generate Outbound Advice (whinh4201m000) and the Release Outbound Advice(whinh4202m000) sessions. Outbound advice includes information for moving goods from awarehouse storage location to a loading dock for shipment.

2. Use the Freeze/Confirm Shipments/Loads (whinh4275m000) session, or the Confirm OutboundASN (whinh4230m100) session to confirm shipments that will prepare Advance ShipmentNotification (ASN) messages.

3. Use the Shipment Notices (whinh3100m000) session to receive the advance shipment noticethat is sent by the selling company.


4Chapter 4Business Document Delivery

4. Use the Warehouse Receipt (whinh3512m000) session to record the quantity of goods receivedfrom the selling company.

5. Confirm the receipt in the Warehouse Receipt (whinh3512m000) session. After you confirma receipt or receipt line, LN sends a Receipt Discrepancy Notice (RDN) message to the sellingcompany if the received quantity differs from the shipment notice line quantity. A discrepancynotice is sent only if advanced shipment notices are used.

Advance Shipment Notification (ASN)

The delivery process is initiated when you do either of the following: ▪ Prepare the warehousing order for shipment to the purchasing company using the Generate

Outbound Advice (whinh4201m000) and the Release Outbound Advice (whinh4202m000)sessions.

▪ Confirm the shipment in the Freeze/Confirm Shipments/Loads (whinh4275m000) session orthe Confirm Outbound ASN (whinh4230m100) session to prepare Advance ShipmentNotification (ASN) EDI messages.

If the Generate ASNs Automatically check box is selected in the Inventory Handling Parameters(whinh0100m000) session, the Freeze/Confirm Shipments/Loads (whinh4275m000) session preparesthe outgoing Advance Shipment Notification (ASN) message. If the Generate ASNs Automaticallycheck box is cleared, you must use the Confirm Outbound ASN (whinh4230m100) session to preparethe outgoing Advance Shipment Notification (ASN) message.

An Advance Shipment Notification (ASN) message can be sent using the Direct Network Communication(ecedi7205m000) session. The generated EDI messages are displayed on a report. External EDI businesspartner messages are placed in the appl_from subdirectory under the directory specified for the network.Translation software will retrieve the message. Internal EDI business partner messages are stored inthe appl_comm subdirectory.

An advance shipment notice (ASN) is an unconfirmed receipt. If the ASN correctly reflects the contentsof the shipment, it can be confirmed, after which the ASN becomes a receipt. The receipt process isfaster if ASNs are received electronically: data entry time is reduced and also the risk of errors. In theWarehouse Receipt (whinh3512m000) session, a selected shipment notice automatically populates thereceipt data with the data from the shipment notice.

Reprocessing messages with errorsValidation errors can appear when incoming messages are processed. These errors prevent the messagefrom being updated in the LN application. The entire message is stored in the Saved Messages to beReceived table and you can view and correct the message using the Saved Messages to be Received(ecedi7150m000) session.

A unique batch number is assigned to each processing occurrence for each network. The SavedMessages to be Received (ecedi7150m000) session records processed incoming messages. Use thissession to display received batch references created when incoming EDI messages are processedsuccessfully or unsuccessfully.


Business Document Delivery

Use the Saved Messages to be Received (ecedi7150m000) session to view and correct data. If youchoose to review the messages interactively, or if errors are encountered when message data is validated,an EDI message will not be processed. The unprocessed message is referred to as Saved Messagesto Be Received. When you select a record, the saved message data details are displayed in the SavedMessage Data to be Received (ecedi7151s000) session.

After the message data is corrected, the message must be approved before it can be reprocessed. Usethe Approve Saved Messages to be Received (ecedi7250m000) session and the Process SavedMessages to be Received (ecedi7252m000) session to complete the steps required for reprocessing amessage.

After the saved message is successfully processed and updated in the LN application with the ProcessSaved Messages to be Received (ecedi7252m000) session, the saved message is automatically deletedfrom saved messages to be received.

If you decide not to process the message, you can delete the message with the Print Saved Messagesto be Received (ecedi7450m000) and/or Delete Saved Messages to be Received (ecedi7251m000)sessions. You can access both sessions from the appropriate menu in the Saved Messages to beReceived (ecedi7150m000) session.

Receipt Discrepancy Notification (RDN)Advance shipment notices can be used to fill receipt data in the Warehouse Receipt (whinh3512m000)session. If a discrepancy exists between the shipment notice quantity and the actual quantity receivedand recorded, the discrepancy is logged. After the receipt is confirmed, a Receipt Discrepancy Notificationmessage (RDN) is prepared for EDI.

The default conversion setup definition of the outgoing receipt discrepancy message includes the receiptdiscrepancy code. The code defines the type of discrepancy as follows: ▪ Quantity received greater than the quantity indicated on the shipment notice (quantity over).

▪ Quantity received less than the quantity indicated on the shipment notice (quantity short).

▪ Shipment notice not received prior to receipt of goods (No ASN).

To indicate that the shipment notice was not received prior to the arrival of the goods, use the ShipmentNotices (whinh3100m000) session to manually specify a shipment notice with zero quantities.

The Direct Network Communication (ecedi7205m000) session will generate the outgoing ReceiptDiscrepancy Notification (RDN) message. A report lists the messages that were generated, and forexternal EDI, the outgoing message (ASCII) files are stored in the appl_from directory for the translationsoftware.

To receive the Receipt Discrepancy Notification (RDN) message, use the Direct Network Communication(ecedi7205m000) session. This session retrieves the RDN message from the appl_to directory, afterthe ASCII file is placed in the directory by translation software. The message indicates that a discrepancywas found between the quantity indicated on the Advance Shipment Notice (ASN) and the quantityactually received.

The EDI Information fields at the shipment header, and the shipment line’s text field are updated withthe information in the discrepancy message.



EDI business document Freight

The business document Freight describes shipment and tracking of loads and shipments; it includesthe following EDI messages: ▪ FML

Load Information to Carrier▪ FMS

Carrier Status Information

Load Information to Carrier (FML)

Load Information to carrier (FML) messages notify business partners of forthcoming subcontractinginstructions. The messages are prepared when you print subcontracting instructions using either of thefollowing sessions: ▪ Actualize Freight Order Clusters (fmfoc3210m000)

In this session, select the Print Subcontracting Instructions check box, and then selectFinal.

▪ Print Subcontracting Instructions (fmfoc3410m000)In this session, select Final.


5Chapter 5Business Document Freight

Note

To generate the EDI messages prepared, use the Generate EDI Messages (ecedi7201m000) session.

Use the Direct Network Communication (ecedi7205m000) session to generate the outgoing message.A report will list the messages that were generated. The outgoing messages for an external EDI tradingpartner are stored in the appl_from directory for retrieval by translation software.

Carrier Status Information (FMS)

Carrier status (FMS) messages are sent by business partners to facilitate tracking of freight order clusters,freight order cluster lines, loads, and shipments. The carrier status information is displayed in the Statusfield of the following sessions: ▪ Load/Shipment Tracking (fmlbd4150m000)

▪ Load (fmlbd4100m100), Tracking tab.▪ Shipment (fmlbd3100m100), Tracking tab.

To access carrier status and other tracking information from other sessions: 1. Click Tracking on the appropriate menu of any of the following sessions:

▪ Freight Order Clusters (fmfoc3100m000)▪ Freight Order Cluster Lines (fmfoc3101m000)▪ Loads (fmlbd4100m000)▪ Shipments (fmlbd3100m000)▪ Shipment Lines (fmlbd3150m000)The Load/Shipment Tracking (fmlbd4150m000) session appears.

2. If required, on the Filter by Status menu, point to Sort By..., and then click the appropriateoption:▪ Freight Order Cluster▪ Freight Order Cluster Line▪ Load▪ Shipment

3. Double-click a line to view tracking details.


Business Document Freight

EDI business document InvoiceThe business document Invoice describes the invoicing and payment of goods and includes the EDImessage Invoice (INV).

The Invoice (INV) message results from the Invoicing procedure in Invoicing. Invoices can be sent to abusiness partner electronically from Invoicing. The Invoice (INV) message can be received in AccountsPayable under Financials.

The invoicing procedure includes several steps. This business document does not discuss all of thesesteps, but only the ones that relate to the generation and processing of the Invoice (INV) message.

Invoice (INV)To generate the Invoice (INV) message: 1. After invoicing data is released to Invoicing, create a billing request in the Billing Requests

(cisli2100m000) session.2. Use the Compose/Print/Post Invoices (cisli2200m000) session to process the billing request,

which includes composing the invoice for the released data and printing the original invoice.You can also use the Print Invoices (cisli2400m000) session to print the invoice. Printing theoriginal invoice prepares the Invoice (INV) for EDI transmission.


6Chapter 6Business Document Invoice

Invoice (INV)After you ship the goods to the customer, which is the purchasing company, and after you transfer theorder to Invoicing and create a billing request, use the Compose/Print/Post Invoices (cisli2200m000) orPrint Invoices (cisli2400m000) sessions to prepare the Invoice (INV) for EDI transmission.

If the Generate Outgoing Message before Connection check box is selected in the Networks(ecedi0120s000) session, use the Direct Network Communication (ecedi7205m000) session to generatethe outgoing message and to provide a report that displays the generated messages. If you do not usethe 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 outgoingmessages.

External EDI messages are placed in the appl_from subdirectory specified for the network and thetranslation software retrieves the messages. Internal EDI messages need not be translated and arestored in the appl_comm subdirectory, which is used for outgoing and incoming messages.

To receive the Invoice (INV) message from a supplier, which is the selling company, use the DirectNetwork Communication (ecedi7205m000) session. A purchase invoice is created and two reports aregenerated. The Remarks in Copied Messages report shows the invoice number(s) generated, alongwith some pertinent remarks. The Incoming EDI Purchase Invoice report lists the invoiced quantityand amounts at the line level, and the tax amounts by tax code ID, if applicable.

If goods are received before the Invoice (INV) message is received, automatic invoice matching occurs.If the invoice message arrives before the order is received, the purchase invoice remains unmatchedand can be manually matched when the goods are received.

The invoice matching can occur either at the invoice header or at the invoice line depending on the datareceived in the incoming purchase invoice message: ▪ Invoice Matching at the Invoice Header

To perform invoice matching at the header, the Automatic Matching check box must beselected in the ACP Parameters (tfacp0100m000) session. If the received message includesa valid customer purchase order number in the invoice header and no invoice order lineinformation, the entire order is matched for all order lines that have goods received. If thetolerance is not met, the entire purchase invoice remains unmatched.

▪ Invoice Matching at the Invoice LineIf the received message includes order line information, each invoice line is matched to thecustomer order lines for which goods were received. The invoice lines for which no goods arereceived remain unmatched.

You can view the received invoice data in the Match/Approve Purchase Invoices (tfacp2107m000)session.


Business Document Invoice

EDI business document Error HandlingThe business document Error Handling describes sending, receiving, and processing Error Notificationmessages.

Sending Error Notification (824/APERAK) to supplierThe EDI Messages Supported by Business Partner (ecedi0511m000) session includes the AutomaticallyPrepare Error Notification check box. If both trading partners select this check box, and an error existsin the received Shipment Notice (856), an outgoing Error Notification (824) message will be prepared.

To manually prepare the Error Notification message, you must run the Print Received Message Errors(ecedi7451m000) session with the Prepare Error Notification check box selected. The error notificationcan be prepared for any erroneous message received, but is of particular use for shipment notices witherrors that are received in supply chain environments.

Use the Direct Network Communication (ecedi7205m000) session to generate the outgoing message.A report will be created that lists the generated messages.

Receiving Error Notification (824/APERAK) from customerAfter you receive an Error Notification (824/APERAK) from your customer (ship-to business partner),and the message (ASCII) files are placed in the appropriate appl_to directory by thetranslation/communication software, use the Direct Network Communication (ecedi7205m000) sessionto receive the Error Notification message.

An incoming Error Notification is associated with a shipment for which an invalid shipment notice wasoriginally sent, and reports application errors that occurred when your business partner tried to processthe previously sent shipment notice.

When the Error Notification is received, the following occurs: ▪ The status of the shipment for which the Error Notification was received, is set to Disapproved.

▪ The Remarks in Copied Message report is generated, showing the shipment notice numberagainst which the Error Notification message was received, and any related remarks.


7Chapter 7Business Document Error Handling

▪ Optionally, the EDI Information field on the shipment header may be updated with the contentsof the Error Notification message.

▪ The shipment notice referenced in the received Error Notification message, is automaticallyprepared for EDI transmission (856/DESADV out).

As with all prepared outgoing messages, you can verify whether the outgoing message was preparedfor EDI using the Messages to be Generated (ecedi7100m000) session. If you do not want the messageto be generated the next time the Direct Network Communication (ecedi7205m000) session is run, youcan delete the message from this session.

Resending canceled and corrected shipment notices in response toreceived Error NotificationsIf you wish to send a canceled shipment notice to your customer, and if the network is set up to generatemessages upon Direct Network Communication, run the Direct Network Communication (ecedi7205m000)session. Otherwise, run the Generate EDI Messages (ecedi7201m000) session to manually generatethe outgoing message. When the outgoing canceled shipment notice is generated, the shipment’s EDIstatus is Modify, indicating that the shipment should be modified to correct the erroneous data, andresent to your business partner.

Note

These shipment notices are supported: ▪ A canceled shipment notice

A canceled shipment notice is intended to cancel a previously sent erroneous shipment notice.In the Conversion of Shipment Status Codes (out) (ecedi4180m000) session, you can specifyoriginal or canceled message codes, which are included in the message.

▪ An original shipment noticeIf the shipment’s EDI status is Confirmed, the shipment notice is considered to be an originalmessage. If the shipment’s EDI status is Disapproved, the shipment notice is considered tobe a canceled message.

If the shipment’s EDI status is Modify, you can correct the reported errors by correcting the shipment’sdate/time, quantity or weight and any other EDI data included on the original shipment notice, after whichyou can resend the corrected shipment notice to your business partner. To resend the corrected shipmentnotice, use the Confirm Outbound ASN (whinh4230m100) session to prepare the corrected shipmentnotice (856/DESADV) for transmission; preparing the outgoing shipment notice sets the shipment’s EDIstatus to Confirmed. If the network is set up to generate messages upon Direct Network Communication,run the Direct Network Communication (ecedi7205m000) session. Otherwise, run the Generate EDIMessages (ecedi7201m000) session to manually generate the outgoing message.

For external EDI, the outgoing message (ASCII) files are placed in the appl_from directory, under thenetwork’s directory, from which the translation/communication software will retrieve them.


Business Document Error Handling

advance shipment noticeA notification that a shipment has been sent. Advanced shipment notices are sent and received bymeans of EDI. You can receive advance shipment notices from your supplier informing you that goodsare to arrive at your warehouse, and/or you can send advance shipment notices to your customers thatthe goods they ordered are about to be delivered.

Synonym: shipment notice

Abbreviation: ASN

ANSIThis acronym stands for American National Standards Institute. ANSI is the central body responsiblefor the identification of a single consistent set of voluntary standards called American National Standards.ANSI is also the US representative to nontreaty standards organizations.

appropriate menuCommands are distributed across the Views, References, and Actions menus, or displayed as buttons.In previous LN and Web UI releases, these commands are located in the Specific menu.

ASNSee: advance shipment notice (p. 29)

billing requestSelects the order types and orders to be invoiced. If you process a billing request, LN selects the invoicingdata and generates the invoices for the order types and orders selected through the billing request.

call-offTo call up goods from a business partner based on a purchase schedule. Call-off involves sending amessage (EDI) to notify a business partner that the scheduled items must be delivered. The messagecontains the item quantity and the date and time they must be delivered.


AAppendix A Glossary

change reasonA means used to identify the reason for a change to a sales or purchase order, for example, a contractlimitation, feasibility issue, or transportation limitation. A change reason is identified by a code.

change typeA user-defined code that can be used to identify types of changes made to orders, such as a pricechange or quantity increase.

EDIFACTThis acronym stands for Electronic Data Interchange for Administration, Commerce, and Transport. Aworldwide organization developing standards for electronic data interchange.

There are other similar organizations (for example, Odette), each using its own subset of standardEDIFACT messages.

When you define messages, you can use the naming convention that coincides with the standard namingconventions to which you are accustomed.

EDI standardA protocol defined at national and international levels to define the process, procedures, and format ofelectronically transmitted data (messages) between two business partners.

electronic data interchange (EDI)The computer-to-computer transmission of a standard business document in a standard format. InternalEDI refers to the transmission of data between companies on the same internal company network (alsoreferred to as multisite or multicompany). External EDI refers to the transmission of data between yourcompany and external business partners.

nonreferenced scheduleA schedule that contains lines without a reference number. Because no specific requirement exists forthe schedule line, nonreferenced schedule lines can first be clustered and then ordered, shipped, andreceived together.


Glossary

purchase releaseA purchase release is used to send out, under one release number, those schedules that share thefollowing common characteristics:

▪ Buy-from business partner▪ Ship-from business partner▪ Ship-to address

▪ Release type (material release/ shipping schedule/ sequence shipping schedule)

▪ Shipment based schedule/ receipt based schedule▪ Communication method▪ Warehouse

purchase scheduleA timetable of planned supply of materials. Purchase schedules support long-term purchasing withfrequent deliveries and are usually backed by a purchase contract. All requirements for the same item,buy-from business partner, ship-from business partner, purchase office, and warehouse are stored inone schedule.

referenced scheduleA schedule that contains lines with reference numbers. When goods are shipped, received, and invoiced,the reference numbers are used to communicate with suppliers and other LN packages.

release typeA classification used to specify the type of the release based on which schedule requirements aregrouped and EDI messages can be generated. These messages are indicated by the used schedule.

requirement typeThree requirement types exist that represent a requirement in time, used for scheduling.

The available requirement types are: ▪ Immediate

▪ Firm▪ Planned

For non-referenced schedules, requirement types are linked to segments.

For pull forecast schedules, the requirement type is always Planned or Immediate. For pull call-offschedules, the requirement type is always Firm.


Glossary

sales releaseIdentifies, by one release number, those sales schedules that share the following common characteristics:

▪ Sold-to business partner.▪ Ship-to business partner.▪ Ship-to address.

▪ Release type (material release/ shipping schedule/ sequence shipping schedule/ pick-upsheet).

▪ Shipment based schedule/ receipt based schedule.▪ Schedule quantity qualifier.▪ Forecast horizon start and end.▪ Sales release origin.▪ Customer release.▪ (Customer order).

sales scheduleA timetable of planned supply of materials. Sales schedules support long-term sales with frequentdeliveries. All requirements for the same item, sold-to business partner, ship-to business partner, anddelivery parameter are stored in the same sales schedule.

sales schedule revision numberA number that uniquely identifies the revision of the sales schedule. The sales schedule revision numberindicates the sales schedule updates that are sent by your business partner.

sequence shipping scheduleA shipping schedule with precise information about the production or deliveries of the requirements.This schedule can include the production or delivery sequence, and the order, the place, and the timeof unloading after shipment.

shipment noticeSee: advance shipment notice (p. 29)

subcontracting instructionsSubcontracting instructions constitute the subcontracting order for a carrier. The subcontractinginstructions list the goods for which the carrier is to carry out the transportation.

VDAAcronym for Verband der Automobilindustrie; A standard for automotive electronic interchange ofbusiness transactions in Germany. This particular standard uses a fixed length field/record format.


Glossary

advance shipment notice, 29ANSI, 29appropriate menu, 29ASN, 29billing request, 29call-off, 29change reason, 30change type, 30Delivery

EDI business document, 19EDI business document

delivery, 19error handling, 27freight, 23invoice, 25order, 9overview, 7schedule, 13

EDIFACT, 30EDI messages

ASN, 20, 27FML, 23FMS, 24INV, 26MRL, 14ORA, 12ORC, 11ORD, 10ORS, 11process, 16RDN, 21receive error notification, 27reprocess, 20resend shipment notices, 28send error notification, 27SEQ, 14SHP, 14

EDI standard, 30

electronic data interchange (EDI), 30Error handling

EDI business document, 27Freight

EDI business document, 23Invoice

EDI business document, 25nonreferenced schedule, 30Order

EDI business document, 9Overview

EDI business document, 7purchase release, 31purchase schedule, 31referenced schedule, 31release type, 31requirement type, 31sales release, 32sales schedule, 32sales schedule revision number, 32Schedule

EDI business document, 13sequence shipping schedule, 32shipment notice, 29subcontracting instructions, 32VDA, 32

Index