MuleSoft Accelerator for SAP icon

MuleSoft Accelerator for SAP

(6 reviews)

Use case 3b - Quote-to-cash - B2B EDI

Enable the order fulfillment message flows between buyers and supplier using EDI message formats as a form of communication between applications. Easily integrate Slack with purchase orders for prompt action by the operation and service teams.

Contents

See also

Overview

Across every industry from manufacturing to healthcare and retail, the streamlined B2B integration of your ERP systems (especially SAP) with those of your trading partners (buyers) is critical to your organization’s success.

MuleSoft Accelerator for SAP allows you to reduce errors and manual intervention, and avoid the hassle of sending paper invoices by utilizing EDI messaging. The solution leverages Anypoint Partner Manager to automate the full lifecycle of a typical order-to-cash workflow by integrating EDI transaction exchanges with you and your buyers and automatically creating an order back in SAP S/4HANA.

Use case description

The purpose of this use case is to enable the purchase order and post-purchase order transaction flows between businesses, with one business serving as the buyer and the other as the supplier. This is to support the inclusion of EDI message formats as a form of communication between applications.

Glossary

TermDefinition
APMMulesoft’s Anypoint Partner Manager (APM).
B2BBusiness-to-business (B2B), also called B-to-B, is a form of transaction between businesses.
CIMThe Cloud Information Model (CIM) defines a set of standard data structures that can be used as canonical representations of common entities for integrating systems.
EDIElectronic Data Interchange (EDI)

High-level architecture

ANSI ASC X12:

sap-b2b-edi-architecture-x12.png

UN/EDIFACT:

sap-b2b-edi-architecture-edifact.png

Sequence diagrams

ANSI ASC X12:

sap-b2b-edi-sequence-diagram-x12.png

UN/EDIFACT:

sap-b2b-edi-sequence-diagram-edifact.png

Use case considerations

bulb.png In order to use the pre-built EDI templates, suppliers would need to purchase the Anypoint Partner Manager add-on along with the EDI connectors (X12, EDIFACT). Buyers may use any EDI software of their choice.
  • ANSI ASC X12 and UN/EDIFACT are the EDI document standards considered for this use case.
  • The following X12 EDI formats are supported in this use case:
    • EDI 850 : Purchase Order
    • EDI 855 : Purchase Order Acknowledgement
    • EDI 856 : Advanced Shipping Notice
    • EDI 810 : Invoice
    • EDI 820 : Payment Order/Remittance Advice
  • The following EDIFACT EDI formats are supported in this use case:
    • EDI ORDERS : Purchase Order
    • EDI ORDRSP : Purchase Order Acknowledgement
    • EDI DESADV : Advanced Shipping Notice
    • EDI INVOIC : Invoice
    • EDI REMADV : Payment Order/Remittance Advice

Technical considerations

  • An SFTP server is set up to simulate a Buyer system.
  • Buyer’s ERP would drop/pickup EDI files from the SFTP server.
  • SAP S/4HANA is the Supplier system.
  • The customer and the products used in EDI transactions are pre-synced between the Buyer and SAP S/4HANA.
  • Use CIM as the canonical model where applicable.

End-to-end scenarios - X12

  • Purchase Order Transaction Flow:
    • 850 Purchase Order from Buyer to SAP S/4 HANA.
    • 855 Purchase Order Acknowledgment from SAP S/4 HANA to the Buyer.
  • Post Purchase Order Transaction Flow:
    • 856 Advanced Shipping Notice from SAP S/4 HANA to the Buyer.
    • 810 Invoice from SAP S/4 HANA to the Buyer.
    • 820 Payment Order/Remittance Advice from Buyer to SAP S/4 HANA.

End-to-end scenarios - EDIFACT

  • Purchase Order Transaction Flow:
    • ORDERS Purchase Order from Buyer to SAP S/4 HANA.
    • ORDRSP Purchase Order Acknowledgment from SAP S/4 HANA to the Buyer.
  • Post Purchase Order Transaction Flow:
    • DESADV Advanced Shipping Notice from SAP S/4 HANA to the Buyer.
    • INVOIC Invoice from SAP S/4 HANA to the Buyer.
    • REMADV Payment Order/Remittance Advice from Buyer to SAP S/4 HANA.

Systems involved

  • B2B
  • EDI
  • EDIFACT
  • Slack
  • SAP S/4HANA

Goals

The goal of the B2B/EDI use case is to support the:

  • EDI transaction flows related to purchase orders and post-purchase orders between a Buyer and Supplier system.
  • orchestration in Anypoint Partner Manager to receive the Purchase Order from the Buyer in X12 850 or EDIFACT ORDERS format and the creation of Sales Order in SAP S/4HANA.
  • orchestration in Anypoint Partner Manager to receive the Purchase Order Acknowledgement from SAP S/4HANA and convert it to EDI X12 855 or EDIFACT ORDRSP.
  • orchestration in Anypoint Partner Manager to receive the Advanced Shipping Notice from SAP S/4HANA and convert it to EDI X12 856 or EDIFACT DESADV to send it to the Buyer.
  • orchestration in Anypoint Partner Manager to receive the Invoice from SAP S/4HANA and convert it to EDI X12 810 or EDIFACT INVOIC to send it to the Buyer.
  • orchestration in Anypoint Partner Manager to receive the remittance from the Buyer in the EDI X12 820 or EDIFACT REMADV format to send it to the Supplier.

Assumptions and constraints

The following will be used to guide or constrain the solution design at a high level:

  • The Cloud Information Model (CIM) will be used as the canonical model for inbound messages (order creation/remittance notice).
  • For the purpose of this use case, an SFTP server is set up to simulate a Buyer system.



back to top

Before you begin

bulb.png The Accelerators setup guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications.

Workflow X12

This use case enables EDI transactions in X12 formats between Buyer and the Supplier for the Purchase Order Flow.

Goal

To allow a Bi-directional communication between the Buyer and the Supplier for the Purchase Order and Post Purchase Order Transaction Flow.

Steps

  1. An EDI Purchase Order (850) file is placed in the SFTP server (Buyer).
  2. In APM, an Inbound Message Flow for the Buyer is created to:
    • Receive the X12 850 PO from the SFTP server (Buyer)
    • Convert the X12 850 PO to Order CIM
    • Send the order creation request to SAP S/4 HANA
  3. SAP S/4 HANA sends back a Purchase Order Acknowledgement, Advanced Shipping Notice, and Invoice Notice in a SOAP message format to SAP Event Listener.
  4. The SAP Event Listener converts the SOAP message to JSON with required EDI properties.
  5. In APM, an Outbound Message Flow to the Buyer is configured to:
    1. Receive the JSON message from the SAP Event Listener
    2. Convert the JSON message to the appropriate EDI format: X12 855 (PO ACK), X12 856 (Advanced Shipping Notice), or X12 810 (Invoice)
    3. Send the corresponding EDI message to the SFTP server (Buyer)

Successful outcome

  • Creation of Sales Order in SAP S/4 HANA.
  • Creation of X12 855 PO ACK and sent to the SFTP server (Buyer).
  • Creation of X12 856 Advanced Shipping Notice and sent to the SFTP server (Buyer)
  • Creation of X12 810 Invoice and sent to the SFTP server (Buyer)
  • Creation of Invoice payment in SAP S/4 HANA.

Workflow EDIFACT

This use case enables EDI transactions in EDIFACT formats between Buyer and the Supplier for the Purchase Order Flow.

Goal

To allow a Bi-directional communication between the Buyer and the Supplier for the Purchase Order and Post Purchase Order Transaction Flow.

Steps

  1. An EDI Purchase Order (ORDERS) file is placed in the SFTP server (Buyer).
  2. In APM, an Inbound Message Flow for the Buyer is created to:
    • Receive the EDIFACT ORDERS PO from the SFTP server (Buyer)
    • Convert the EDIFACT ORDERS PO to Order CIM
    • Send the order creation request to SAP S/4 HANA
  3. SAP S/4 HANA sends back a Purchase Order Acknowledgement, Advanced Shipping Notice, and Invoice Notice in a SOAP message format to SAP Event Listener.
  4. The SAP Event Listener converts the SOAP message to JSON with required EDI properties.
  5. In APM, an Outbound Message Flow to the Buyer is configured to:
    1. Receive the JSON message from the SAP Event Listener
    2. Convert the JSON message to the appropriate EDI format: EDIFACT ORDRSP (PO ACK), EDIFACT DESADV (Advanced Shipping Notice), or EDIFACT INVOIC (Invoice)
    3. Send the corresponding EDI message to the SFTP server (Buyer)

Successful outcome

  • Creation of Sales Order in SAP S/4 HANA.
  • Creation of EDIFACT ORDRSP PO ACK and sent to the SFTP server (Buyer).
  • Creation of EDIFACT DESADV Advanced Shipping Notice and sent to the SFTP server (Buyer)
  • Creation of EDIFACT INVOIC Invoice and sent to the SFTP server (Buyer)
  • Creation of Invoice payment in SAP S/4 HANA.

Downloadable assets

System APIs

Process APIs

Listeners

Custom components

  • SAP EDI APM Translation Maps | Source



back to top


Reviews