There are many non-standard EDI transactions that can be implemented during a Trading Partner sell-side onboarding process. There are 7 transactions we want to dig a bit deeper into. Understanding the importance of each transaction is imperative to a successful implementation. These transactions are characterized as non-standard or not commonly integrated with an Enterprise Resource Planning (ERP) system. The complexity of the integration varies based on ERP limitations and may require custom file integrations.
____________________________________________________________________________________
Criteria for Completion
____________________________________________________________________________________
Assess your Enterprise Resource Planning (ERP) limitations and capabilities.
Identify any EDI transactions that may require a custom integrated file. Some transactions may require significant customizations which may impact project timelines and costs.
____________________________________________________________________________________
Non-standard EDI transactions
____________________________________________________________________________________
Inventory Inquiry/Advice (846)
The 846 transaction is used by buyers and sellers to update inventory levels.
This transaction communicates stock quantities, locations, and availability dates to Trading Partners.
Price/Sales Catalog (832)
The 832 transaction delivers detailed product and pricing information.
This transaction includes item attributes, descriptions, packaging, and pricing to keep Trading Partners informed.
Order Status Report (870)
The 870 communicates the status of your order.
This transaction is sent by the seller to the buyer, providing updates on pending orders, line items, or the entire order.
This transaction can also be set up, configured and/or sent via a scheduled event within Transaction Manager.
The 870 is a response to the inbound Order Status Inquiry (869).
Motor Carrier Load Tender (204)
The 204 is used in transportation and logistics to offer shipments to carriers.
This transaction replaces phone and fax communications which standardizes shipment requests.
Response to Load Tender (990)
The 990 is sent by carriers to shippers in response to the 204.
This transaction indicates an acceptance or rejection of a shipment while facilitating logistic communications.
Motor Carrier Freight Details and Invoice (210)
The 210 is sent by carriers to shippers, consignees, or billing services.
This transaction provides shipment and billing details which automates the invoicing process.
Transportation Carrier Shipment Status Message (214)
The 214 is sent by carriers to provide real-time shipment status updates.
This transaction includes location, condition, estimated delivery times, and enhances the supply chain's visibility.
____________________________________________________________________________________
Warning Callout
____________________________________________________________________________________
Custom integrations for these EDI transactions could require additional testing to ensure data accuracy and process reliability.
____________________________________________________________________________________
Additional Information
____________________________________________________________________________________
Grouping EDI transactions by function (inventory, pricing, order status, logistics) helps clarify integration requirements and responsibilities.
Maintain clear documentation for each custom integration to streamline troubleshooting and future updates.