on ‎2025 May 28 4:28 PM
Hi,
We are upgrading our MDG system version to S/4 HANA 2023 and we've encountered a problem during the mass processing of Business Partner.
We have understood that the entity BP_ADDUSG has been replaced by BP_ADUSTD in the data model. Currently, both entities are active in our system. In the UI, the new entity BP_ADUSTD is correctly populated and displayed.
However, when we import data using the Excel file in a consolidation/mass process scenario, the system still writes data to the old entity BP_ADDUSG. As a result, after the Change Request is created, we do not see the data in the expected section, and we encounter an error due to the absence of the required data.
Additionally, we receive a warning message indicating that an obsolete method is being called, likely triggered after the data is written to BP_ADDUSG.
Our main question is:
How can we ensure that the data is written to the correct entity, BP_ADUSTD?
Is there a specific mapping or customizing setting that allows us to control this behavior?
Even when values are not explicitly provided in the input file, the system continues to derive and populate the old entity as it did prior to the upgrade. We suspect this behavior may be linked to the mass processing logic or data import framework (Excel/Web Service), which might still reference the old entity.
Any guidance or documentation you can provide to help us correctly redirect the data to BP_ADUSTD would be greatly appreciated.
Thank you
Request clarification before answering.
To solve the issue, please check SAP Note 3372801 "Upgrade or Conversion for Master Data Governance, Central Governance".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.