Symptom
The system allows the selection of a WBS element belonging to a different plant in purchase requisitions. Documents are posted successfully with an incorrect plant-WBS combination.
This may lead to misleading data and incorrect reflection in financial and project reports, impacting monitoring and reconciliation.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a purchase requisition in a specific plant.
- Enter a WBS element belonging to a different plant.
- Post the document successfully.
Cause
- The system works differently when comparing the field 'plant' with other fields in the system - for example as the accounts behind operation BSX are created as statistical cost element in CO, the items have to be posted within CO as well.
- The CO-account assignment check has to ensure that data like Business Area and Profit Center always match to the account assignment. Otherwise, an inconsistency would be created between CO and FI respect CO and PCA.
- However, the plant is not such an organizational unit which have to refer to the WBS-master data. It is possible to enter a WBS from plant XXXX to an item for plant YYYY, this is allowed. No inconsistency occurs.
- The plant will never be taken from the account assignment for interface postings, only for CO-internal postings where the plant is not set already.
Resolution
- This behavior is the standard system design; there is no check on the plant, meaning it can differ in the WBS element and/or profit center in a purchasing document.
- Implement a custom check for purchase requisitions to validate the plant-WBS combination using BADI Check of Purchase Requisition Item (MM_PUR_S4_PR_CHECK).
Keywords
wbs element, plant mismatch, purchase requisition, sap s/4hana cloud, incorrect data, financial reports, project reports, monitoring, reconciliation, mm_pur_s4_pr_check, custom check, standard design, co-account assignment, profit center, business area, interface postings, organizational unit , KBA , MM-PUR-REQ-SSP-2CL , Fiori UI for Self Service Procurement (Public Cloud) , Problem
SAP Knowledge Base Article - Public