Example: Message Flow for Kanban This section provides examples of the message flow if a customer uses an SAP back-end system for kanban processing with SAP Supply Network Collaboration (SAP SNC). The figures show the messages and message flow for the following back-end variants:
Kanban without materials requirement planning (MRP) as of SAP R/3 4.6C
Kanban with MRP as of SAP ECC 6.0 with industry extension DIMP
SAP delivers standard XSLT mapping for the integration with these back-end variants.
Recommendation
The figures are intended to provide a general overview. SAP recommends using the integration scenarios, which are part of the XI content for SAP SNC. This allows you to generate message flows and routings automatically.
Message Flow: Kanban without MRP

The process runs as follows:
Create kanban request (customer’s ERP system, SAP R/3 4.6C or higher, with or without DIMP)
The customer creates a kanban request in the ERP system. The ERP system transfers the ORDERS.ORDERS03 IDoc to the customer’s SAP NetWeaver System, which converts the IDoc into an XML message of type
ReplenishmentOrderNotification (RON)
and transfers it to SAP SNC.
Note
You have implemented note 844679 for this purpose.
Display kanban call (SAP SNC)
Publish advanced shipping notification (supplier’s ERP system)
When the material is ready for delivery, the supplier can publish an advanced shipping notification in his or her ERP system. The ERP system transfers an XML message of type
DespatchedDeliveryNotification
(DDN) to the customer’s SAP NetWeaver system, which forwards the message to SAP SNC.
Note
Note that the IDocs, XML messages, and mappings depend on which ERP system and releases are being used. Mappings are sometimes required for the message flow between the supplier’s system and SAP SNC, depending on the supplier’s system. Since the mappings are dependent on the supplier’s system, they cannot be predefined in the SAP SNC standard delivery. You must create the mappings as part of a project solution.
Receive advanced shipping notification, or create shipping notification in the Web UI (SAP SNC)
If suppliers do not use an ERP system to send advanced shipping notifications, they can create them in the Web UI. The SAP SNC system transfers an XML message of type
DespatchedDeliveryNotification (DDN)
to the SAP NetWeaver system, which converts the message into the IDoc DESADV.DELVRY03 and transfers it to the customer’s ERP system.
If you use an ERP system without the DIMP industry extension, you use the mapping
DespatchedDeliveryNotification_DesadvDelvry03_01. If you use an ERP system
with DIMP, you use the mapping
DespatchedDeliveryNotification_DesadvDelvry03_02
.
Receive advanced shipping notification (customer’s ERP system)
Receive advanced shipping notification and post goods receipt (customer’s ERP system)
When the customer posts the goods receipt, the customer’s ERP system sends the STPPOD.DELVRY03 IDoc to the SAP NetWeaver system. The SAP NetWeaver system converts the IDoc into an XML message of type
ReceivedDeliveryNotification
(RDN), and transfers it to SAP SNC.
Display goods receipt information (SAP SNC)
Message Flow: Kanban with MRP

This process is basically the same as
Kanban without MRP
with the following exceptions:
Customers can also create a forecast/planning delivery schedule in their ERP system before the kanban request. The ERP system sends the DELINS.DELFOR01 IDoc to the customer’s SAP NetWeaver System, which converts the IDoc into an XML message of type
DeliveryScheduleNotification
(DSN) and transfers it to the SAP SNC system.
Note
You have implemented note 847001 for this purpose.
The customer’s ERP system creates the IDoc PAB_ORDERS.SEQJIT03 for the kanban request, which the SAP NetWeaver System converts into an XML message of type
ReplenishmentOrderNotification
(RON) and transfers to the SAP SNC system.