This document explains some of the EDI messages commonly used in Logistic Execution or shipping process. We have tried to explain functionality of each EDI messages in brief which will help users to quickly refer and take decision on which EDI message is suitable for transmitting data from SAP to other involved parties or vice a versa. It is assumed that the target audience is aware of standard sales business processes mapped in SAP ECC.
We will cover below EDI messages –
Sr. No | EDI Message | Description |
1. | EDI – 204 | Motor Carrier Load Tender |
2. | EDI - 990 | Response to a Load Tender |
3. | EDI – 997 | Functional Acknowledgment (FA) |
4. | EDI - 214 | Transportation Carrier Shipment Status Message |
5. | EDI – 304 | Shipping Instructions |
6. | EDI – 856 | Ship Notice/Manifest |
7. | EDI – 940 | Warehouse Shipping Order |
8. | EDI – 945 | Warehouse Shipping Advice |
EDI – 204: Motor Carrier Load Tender
This transaction set can be used to allow shippers or other interested parties to offer a shipment to a full load (truckload) motor carrier. This message is used to transmit information related to detailed schedule of the shipment, Equipment Requirement like size of the required Truck, Ship to Party details like name, location and contact details. Material / goods with weight and volume information along with Unit of Measure and shipping instructions. It is not to be used to provide a motor carrier with data relative to a less-than-Truckload bill of lading, pickup notification, or manifest.
The carriers will send EDI-990 as a response to Load Tender transaction indicating acceptance or declination of the load.
EDI – 990: Response to a Load Tender
Shippers send EDI-204 Load Tender transaction to Carriers normally for full truck load and in response to Load Tender transaction, carrier responds with EDI-990 transaction indicating whether the load is accepted or rejected. This transaction can also carry additional information related to acceptance or rejection of the offered load, freight acceptance along with conditions if any.
As an acknowledgement of the 990 transaction, EDI-997 functional acknowledgement will be sent by carrier or consignee.
EDI – 997: Functional Acknowledgment (FA)
This transaction is used to just acknowledge the receipt of the EDI transaction by receiver. This transaction means that the receiver has received the transaction and it is processed by EDI translator. This does not mean acceptance or rejection of the business function intended in the transaction. It may indicate if there are any issues observed in EDI standards for that transaction.
EDI – 214: Transportation Carrier Shipment Status Message
EDI – 214 transactions are used by carrier agencies to provide shippers / consignee the status of their shipment. This transaction can include information related to Ship from to SHIP To location details, address, co-ordinates, date and time stamp of pick up and estimated delivery, Shipment information like packing, weight and quantity and most important information reason for status and exception information.
The receipt of shipment status transaction can be informed using EDI – 997 functional acknowledgements.
EDI – 304: Shipping Instructions
This transaction serves different purpose when used for Ocean carrier or forwarding agents or brokers.
In case of an ocean carrier, this transaction is used to provide information required to create Ocean BOL (Bill of Lading document), Sea waybill and other shipping documents. However, when it is used to transmit data to freight forwarder or custom broker, it provides information on shipping and financial details.
EDI – 856: Ship Notice/Manifest
This transaction is used to send Advance Shipment notification (ASN) between the trading partners. This transaction contains information about Order data, materials or goods, their weight, and volume, packaging information, and carrier and tracking information along with ship to location details.
The EDI 856 transaction is commonly used in response to EDI 850, EDI 830, or EDI 862 transactions.
EDI – 940: Warehouse Shipping Order
This warehouse shipping order transaction is used to instruct remote warehouses to ship orders. It is commonly used by manufacturer or wholesaler, to instruct a warehouse to make a shipment to a buyer. The 940 may also be used to confirm a shipment, modify a shipment or cancel a previous shipping order. The 940 transaction normally instructs the warehouse on what to ship, how much and when. The transaction may include specific information relating to Manufacturer, item quantity, shipment method, shipping party details and billing related data. The 940 Warehouse Shipping Order data can be generated from Sales Order or Purchase Order information.
An acknowledgement transaction EDI-997 will be submitted by warehouse in response to EDI-940.
EDI – 945: Warehouse Shipping Advice
This transaction will be used by warehouse to confirm seller that the shipment has been made. The transaction includes data such as Ship From and Ship To location along with Date stamp, shipment method, service level and items and quantity shipped. The 945 transaction provides the information needed for the seller to reconcile the quantity shipped against the order quantity, create an invoice and generate an 856 Advance Ship Notice (ASN) transaction.
Mapping EDI messages with SAP IDOCs
IDocs and EDI transactions are only data structures, so we can literally map anything to anything. The most important thing is to understand the underlying business process before you can select the appropriate EDI and corresponding IDOC. The key is business process.
In case of inbound processing the user needs to understand which business document / transaction to be triggered from incoming EDI message and that will drive selection of IDOC to perform the desired transaction. The determination of IDOC also needs additional information on process code, function module which can be obtained with the help of technical team.
However, in case of outbound processing the SAP document / transaction drives IDOC selection to transmit application data to outside systems. All the application data is transmitted but its functional consultant’s role to perform mapping of this data with the appropriate fields of EDI message fields.
Most generally used mapping of EDI transactions with SAP IDOCs –
Sr. No | EDI Transaction | Description | IDOC Basic Type | Message Type | Direction |
1. | EDI – 204 | Motor Carrier Load Tender | SHPMNT04 | IFTMIN / SHPMNT | I / O |
2. | EDI - 990 | Response to a Load Tender | DELVRY03 | I | |
3. | EDI – 997 | Functional Acknowledgment (FA) | SYSTAT01 | STATUS | I |
4. | EDI - 214 | Transportation Carrier Shipment Status Message | TRXSTA01 | TRXSTA | I |
5. | EDI – 304 | Shipping Instructions | SHPMNT04 | IFTMIN / SHPMNT | I / O |
6. | EDI – 856 | Ship Notice/Manifest | SHPMNT05 / DELVRY03 | SHPADV / SHPCON | I / O |
7. | EDI – 940 | Warehouse Shipping Order | DELVRY03 | SHPORD / DESADV | I / O |
8. | EDI – 945 | Warehouse Shipping Advice | DELVRY03 | SHPCON / WHSCON | I / O |
References:
- scn.sap.com
- help.sap.com
- SAP Managed Tags:
2 Comments
