< Back to Top

EDI X12 Order-to-Cash <> SAP S/4HANA Cloud (Overview)

Order-to-cash, also called the O2C cycle, is how your business receives, processes, manages, and completes orders. It begins from the time an order takes place and includes each step of the delivery and payment process. In this case, SAP S/4Hana represents our backend.

This Accelerator contains prebuilt Schemas, Rulesets, Business Processes, and other resources used for development, deployment/execution, and testing. This includes mapping tools specific to several business flows as part of this Accelerator.  Finally, there are also resources necessary to display data in several Cockpit monitoring pages.

Pre-built Integration Flows: Integration flows in CIC are provided to receive X12 850 (Purchase Order) from the Trading partners and create the corresponding Sales Order in SAP S/4Hana. Once the shipment is created the integration flow automatically retrieves details from SAP S/4Hana and creates X12 856 (ASN). 

The integration flow also automatically retrieves material stock details from SAP S/4Hana and creates X12 846 (Inventory Inquiry/Advice) for Trading Partner. The manufacturer (SAP S/4HANA) can instruct the warehouses or warehouses can instruct other warehouses to ship the items ordered, by automatically retrieving sales order with (warehouse flag enabled) details from SAP S/4HANA and create outbound X12 940(Warehouse Shipping Orders) for the warehouse or third-party logistics provider (3PL). 

The warehouse sends out X12 945 (Warehouse Shipping Advice) to SAP S/4HANA to let them know that a shipment has taken place correspondingly outbound delivery is posted in SAP S/4HANA. The Integration flow can also receive X12 875 (Grocery Order) from the Trading partners and create the corresponding Sales Order in SAP S/4HANA with the CIC GROCERY STATUS flag as true. 

Once the Grocery Invoice is created for the Grocery Order in the SAP S/4HANA, Accelerator has the project to retrieve the Grocery Invoice records from the SAP S/4HANA which generates the outbound document like X12 880 (Grocery Products Invoice). When there is stock to be transferred, the manufacturer informs the warehouse/3PL about the items transfer information through X12 943(Warehouse Stock Transfer Shipment Advice) so that they are ready to receive the incoming stock from customer/vendor/any other warehouse. 

Once the stock is received by the warehouse/3PL, they generate X12 944(Warehouse Stock Transfer Receipt Advice) as confirmation for the number of items received to the manufacturer which will update the existing Warehouse Receipt in SAP S/4HANA. 

All the flows will also have the respective X12 997 (Functional Ack) flow and outbound EDI validations included.

Integration Design Specification Template: The document which explains the business rules that are applied while creating the inbound and outbound documents. The template helps in documenting any changes to the template integration as per your requirement. 

Email notification for unknown Trading Partner: If the Inbound/Outbound payloads received where no matching configurations are found, then, an email notification will be generated.

EDI message validations:

  • Duplicate Inbound messages The Accelerator has the logic to handle any duplicate EDI data that is retrieved from the Trading partner. If need be, this can be turned per partner or per doctype.
  • Inbound/Outbound EDI Data validation: Accelerator is enabled to catch any invalid EDI syntaxes in both Inbound and Outbound flow. The execution will be stopped if there are any syntax errors. The settings can be changed to not to stop execution as well.  

Error Handling and Ticket Creation: Accelerator ensures all the processing failures are logged as a ticket and is marked as Issue in the Cockpit.

Out of the box Cockpit visibility: Accelerator is already enabled with the resources necessary to display data in several Cockpit monitoring pages. 

The Message Details view provides the life cycle of an Order until the Invoice is generated.
 

The Accelerator also uses dashboard charts to monitor the various transactions. These include these transactions: 850,856,810,846,940, 945, 875, 880, 860, 943, and 944. 

In each chart, details about the count of messages translated are displayed.

Next Steps

  1. Please review and complete the following prerequisites.
  2. There are other actions you may need to take that are described in initial steps, which include the configuration of Reference Tables and Global Variables.  Steps describing how to add a flow are also provided. See related topics below.

Related Topics

Flows

 

Related articles

Comments

0 comments

Please sign in to leave a comment.