Symptom
WBS elements flagged as blocked for purchasing can still receive postings through Service Entry Sheets when the Purchase Order was created with account assignment category "U" and the SES is subsequently posted with category "P".
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a WBS element and set it to blocked for purchasing.
- Create a Purchase Order using account assignment category "U".
- Create and post a Service Entry Sheet for that PO item using account assignment category "P" and select the same blocked WBS element.
Cause
Standard design evaluates the WBS “blocked for purchasing” check during PO account assignment validation at save time. With account assignment category "U", no WBS exists on the PO, so no check occurs. The SES process does not re-run the PO account assignment validations, which allows the bypass.
Resolution
The standard system design allows this bypass behavior, making custom enhancement necessary to achieve complete purchasing block enforcement across all MM document flows. Implement a custom validation on Service Entry Sheets to enforce the WBS purchasing block. Use BAdI MM_PUR_S4_SES_CHECK_HEADER to validate SES account assignments.
BAdi MM_PUR_S4_SES_CHECK_HEADER triggers an error message for Blocked WBS element in Service Entry Sheet creation .
See Also
Keywords
wbs, blocked for purchasing, purchasing block, service entry sheet, ses, account assignment u, account assignment p, mm-pur, project, bypass, validation, badi, MM_PUR_S4_SES_CHECK_HEADER, BD_MMPUR_FINAL_CHECK_PO, I_EntProjElmntBlockFunc_2 , KBA , MM-PUR-SVC-SES-2CL , Service Entry Sheet for Service Procurement (Public Cloud) , Problem
SAP Knowledge Base Article - Public