Systems Involved:
ECC and DMC
ECC Process Flow:
1. Users/ Operator are creating production order using CO01 T-code in ECC WPR system
2. Users/ Operator are Releasing production order using CO02 T-code in ECC WPR system.
3. Once the order got released in ECC, it will get triggered to DMC Production system via
IDOC automatically
4. IDOC Message Type LOIPRO and the shop floor configuration to assign the order type with
MES system has been set already.
5. Once the Order has been integrated to DMC Production system, user can see the order in
Integration Message Dashboard with a message type “Order Download” with a status
“Completed”
6. If the Order Download status is Completed, user can proceed further for Manufacturing
Execution
Manufacturing Execution in DMC:
1. User/ Operator need to access “Manage Orders” app in DMC
2. In “Manage Orders” app, user/ operator enter the Order number as below:
3. Once user/ Operator clicks on the order, system will route to another screen where we can
the see the order details like BOM, Operations, SFCs etc.
Click on Release in Background and systems prompts to enter the qty to release. Please
see below screen.
Once user/ operator click on release, SFCs will get created as below:
7518096-025148
4. Once the SFCs have been created in DMC, user / operator needs to perform the execution
using PODs
Goto Launch POD > ASSEMBLE_WC_POD
5. Click on ASSEMBLE_WC_PD and Launch POD
Enter SFC and Work center and Click on Go
Click on Start and the Complete
6. This SFC complete function trigger the Yield confirmation to SAP and this RFC is calling
BAPI i.e. BAPI_PRODORDCONF_GET_TT_PROP and posting the order confirmation.
Once the above OBD has been triggered to EWM, it will process the PGI automatically and
updates back to SAP.
But in this case, OBD has been triggered to EWM, but there is no 261 movement for
consumption postings inside ECC. System created many duplicated deliveries in EWM
where there is no OBD in ECC.
Note: This is the test data which is provided above. Thanks for understanding.