Best Practices to Gain Immediate, Actionable Insight into Your Extended Supply Chain

Extended Supply Chain Characteristics

• Multiple geographies – Where do your customers and partners reside?
• Multiple languages and currencies
• Multiple systems – SAP, EDI, Website, portals, …
• Multiple partners – Carriers, freight forwarders, suppliers, manufacturers, distributors
• Varying regulations and compliance requirements – What’s needed to ensure we conduct business legally across the globe?

Various physical events occur, for a product, as it flows through the extended supply chain. Best practices for this process could be listed as follows:

Standard SAP transactions are used to capture transactions across the supply chain. E.g. Purchase Orders, confirmations, ASNs, Invoice receipts, Goods Receipts... Use standard SAP solutions to manage the various parts of the supply chain. E.g. SAP ERP for Procure to Pay, Order to Cash, … SAP Ariba for supplier portal interaction, SAP Event Management for Supply Chain Event Management (the core topic of this blog)

All events pertinent to the supply chain are received from all partners. E.g. Carrier status notifications, vendor Advanced Ship Notices, Manufacturer’s manufactured events. All exception events affecting the supply chain are received from all partners. A reason for the exception needs to be captured.

1. Supply chain events are planned from a timing, location and partner E.g. We expect the delivery to be shipped to Warehouse ABC by Plant 1000 on 2/3/2023 @ 400pm. These plans should be based on actual SAP transaction schedules (E.g. Sales Order schedule line) and the dates are determined based on master data (lead times).
2. The execution of events (when and where they actually occur) are compared with their corresponding plan to determine any discrepancies. These discrepancies can lead to follow-on activities to take corrective action and root cause analysis.‍
3. Monitoring of the Supply Chain plan for events that have not yet occurred, when they should have occurred. This best practice leads to follow-up activities to take corrective action.
4. Events that span multiple processes should be correlated across all of them to ensure complete end-to-end visibility. E.g. Proof of delivery relates to Outbound Delivery, Shipment and Sales Order
5. System messages that communicate the event are also planned and need to be measured.g. The EDI X12 856 is the message that tells us a supplier has shipped the product to us (ASN). We would set up a plan to receive the ASN within 4 hours of the physical shipping of the goods, to ensure that we get the ASN prior to receipt of the goods. I.e. The goods are expected to ship at 2:00 PM and we expect to receive the message at 6:00 PM telling us that the goods have shipped.
6. ‍Manage the Supply Chain by exception – With complete end-to-end visibility into the supply chain, as it’s executing, you are able to proactively identify and react to issues.

Time to Insight – Time from the issue to when we realize that an issue has occurred.‍

Time to Action – Time from the realization that an issue has occurred to when the resolution is actioned.

All data flows from SAP to an analytics tool (SAP HANA Analytics) for aggregation and further “opportunity discovery”. i.e. Where can we find ways to improve the future process, by analyzing the effectiveness of past performance.