on 2024 Nov 24 4:52 PM
Hello SAP Team,
I am reaching out to bring to your attention about an weird error which we encountered for standard migration object (Batch at material level).
System details: "Migrate Your Data – Fiori App S4H2022 FPS02." Staging tables approach.
Below steps to reproduce the issue:
1) We created a new project and added standard Migration object "Batch master at material level" from the initial screen of the S/4HANA Migration Cockpit. Later, with the help of this standard we created another copy of migration object by providing a different object description through LTMOM and generated the object.
2) We downloaded the template and filled the data of the standard object and completed all the steps in the Migration cockpit and batches got created successfully. [No issues]
3) In the second iteration, this time we have chosen the copied version of migration object from the same project, filled sample data and attempted to upload. The file was successfully uploaded, data successfully transferred into the staging tables.
In the next step, "Prepare" we are getting error "Batch level is on Material level" choose the right migration object.
Note: This error we haven't encountered when we used the standard template. This issue is occurring only for the copied migration objects that to specific to this Batch Migration object.
We have checked the system configuration and it is pointed to material level.
Message no: CNV_DMC_SIN 280
However, I wanted to seek your expertise and insights on how we can address and resolve this error effectively.
Your guidance on the recommended steps, potential causes, or any workarounds would be immensely valuable in ensuring a smooth migration of this data. I appreciate your prompt attention to this matter.
Thank you for your assistance, and I look forward to your guidance.
Regards,
Vishwa
Request clarification before answering.
Hello, Vishwa! Hope you're doing well!
The root cause of this error is very likely related to the fact that the MO (Migration Object) was copied using LTMOM. There doesn't seem to be any misconfiguration in place from what you described, as you mentioned that the standard MO is working fine and the system's batch level is set to material level.
As explained by the SAP Note 2481235, copied MOs using LTMOM become user-defined MOs, decoupling from their original standard template. Even though the standard MO is used as reference for the copy, the decoupling can have a series of consequences, such as unexpected errors that don't occur with their fully standard counterparts.
To confirm if that's the root cause of the error, you could try uploading the exact same sample data to the fully standard MO and check if the errors are thrown too!
If no errors are thrown, the copied MO is the root cause of this error message! You'd need to either proceed with the usage of the standard MO, or, if necessary for some reason, create a new Migration Project with the fully standard MO.
I hope that helps! Good luck with your data migration activities!
Best regards,
Caio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
4 | |
3 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.