Solution : https://service.sap.com/sap/support/notes/208477 (SAP Service marketplace login required)
Summary :
When posting order confirmations with backflushing or automatic goods receipt in SAP, the goods movements may not be fully updated immediately, but rather create only request records due to system's technical settings. The expected behavior, as per the customization in process control (Transaction OPKC), should allow immediate postings in the update program. However, transactions such as CO13 and CORS from Release 4.6, and BAPI transactions like BAPI_PRODORDCONF_CREATE_HDR, don’t necessarily adhere to these settings due to technical constraints. The solution involves adjusting process control settings in Customizing to specify update timing (immediately in dialog, update program, or background job). Additionally, in the event of lock situations or errors, goods movement updates may delay, not generating an error record but a request record, manageable via Transaction CO1P. Regular job scheduling for updating these records is advised.
Key words :
pm/pp/pp-pi/ps orders, automatic goods receipt backflushing actual costs, bapi_prodordconf_cancel bapi_prodordconf_create_hdr bapi_prodordconf_create_te bapi_prodordconf_create_tt, future change record reason, selectively update individual markings, update process runs independently, lock situation => request record, automatic goods receipt, automatic goods receipts, successful => error record
Related Notes :
1609187 | FAQ: PP-PDC interface |
1586230 | FAQ: Confirmation using BAPI in production order |
744403 | Confirmation BAPI's do not produce any results |
515656 | CO12: No message for incorrect goods movements |
442966 | Goods movements for reprocessing not visible in COGI! |
327137 | Problems with dependent goods movements as of Release 4.5 |
313985 | Cancel confirmation with goods mvts as of Rel. 4.6 |
312584 | PDC: Confirmations with goods movements |