Symptom
- Scheduling agreement IDoc processing fails with message "No unique scheduling agreement could be determined" (V4 035)
- IDoc from EMFOR cannot be processed
- System should find only one scheduling agreement, but still IDoc fails with no unique SA found
- System doesn't ignore rejected scheduling agreements and issues error "No unique scheduling agreement could be determined"
Read more...
Environment
- Sales and Distribution (SD)
- Logistics Execution (LE)
- SAP ERP Central Component
- SAP ERP
- SAP enhancement package for SAP ERP
- SAP enhancement package for SAP ERP, version for SAP HANA
- SAP S/4HANA
- SAP S/4HANA Cloud Private Edition
Product
SAP ERP Central Component all versions ; SAP ERP all versions ; SAP S/4HANA Cloud Private Edition all versions ; SAP S/4HANA all versions
Keywords
EMFOR, 51, no unique, rejection reason, scheduling agreements, abgru, userexit_m_code_auswahl, m_vlpma, zaehler, v4035, DELINS, DELFOR, LVED4F0M, VLPKM, matchcode selection, M_CODE_KDMAT , KBA , SD-SLS-OA-SCH , Customer Scheduling Agreement , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.