Transformation in practice
supports a variety of business processes in which the transformation of EDI messages into BOD messages and other message formats plays a significant role. The messages are exchanged between applications that are connected to Infor ION and external trading partners. can be used in combination with , , a communication client, and an ERP system that is connected to ION. These are examples of supported business processes:
Incoming release orders
receives a release order message from an external business partner, for example,
UN/EDIFACT DELFOR. transforms the external release
order message into in-house PlanningSchedule or
ShipmentSchedule BODs. passes the BODs
to .
calculates the new requirements. As the owner of the data, publishes the
PlanningSchedule and ShipmentSchedule BODs with the verb Sync. The PlanningSchedule or ShipmentSchedule BODs are sent to the ERP system that
integrates the new requirements.
Shipment part I – Shipping
During the shipment process, CarrierRoute and Shipment BODs that
have the statuses Staged and Shipped are created by the ERP system. The BODs are published by the ERP system that is the owner
of the data with the verb Sync. receives the CarrierRoute and Shipment
BODs to print labels and waybills and prepare Advance Ship Notices
(ASN). When the shipment is started and receives the status Shipped, provides modified BODs. These CarrierRoute and Shipment BODs
include additional ASN information. uses the verb Process to
pass the BODs to . combines the BODs in an internal document, and transforms the
document into an external ASN message, for example, UN/EDIFACT
DESADV. A communication client receives the message from and sends it to
the external business partner.
Shipment part II – Release Management
During the shipment process, Shipment
BODs that have the status Shipped are created by the ERP system. The BODs are published with
the verb Sync by the ERP system that is the owner
of the data. receives the Shipment
BODs with the status Shipped
and uses the information to update requirements and CUMs.
Invoice to customer
During the shipment process, Invoice
BODs are created and published with the verb Sync by the ERP system that is the owner of the data. The and areas receive the
Invoice BODs. The area uses the invoice data for the ATLAS
and Intrastat procedure. transforms the Invoice
BODs into messages with the required message format of the external
business partner, for example, UN/EDIFACT
INVOIC. A communication client receives the messages from and sends them to
the external business partner.
Incoming self-billing invoice
During the shipment process, a communication client receives
self-billing invoice messages from an external business partner, for example,
UN/EDIFACT INVOIC (SBI). receives the
self-billing invoice messages, transforms the messages into Invoice BODs (SBI), and publishes them. The Invoice BODs (SBI) are sent from ION to the ERP system. The self-billing invoices are processed
for accounting.
Integrating inventory consumption from logistics service provider
During the shipment process, a communication client receives inventory
consumption messages, for example, UN/EDIFACT
INVRPT, from an (external) logistics service provider. The messages
indicate that the shipment is completed. The communication client sends the messages
to .
transforms the messages into InventoryConsumption
BODs and publishes the BODs. The InventoryConsumption BODs are sent from ION to the ERP system. The inventory consumption is processed
and the requirements are reduced according to the booked goods movements. The BODs
are published with the verb Sync by the ERP system
that is the owner of the data to ION. The
area receives the InventoryConsumption BODs and
updates requirements and CUMs.