Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
Showing results for 
Search instead for 
Did you mean: 
If you have got this error so, you are in the right place.

We came across this problem after migration from EHP7 FOR SAP ERP 6.0 to S4HANA ON PREMISE  2020 while running t-code MIGO as shown below picture.


So, in this blog, I am going to show how to solve this error with detailed steps.

The error occurs while running t-code MIGO and transferring MSEG data to view NSDM_V_MSEG. Because the field mentioned below in MSEG has been enhanced to include CI_COBL. But this field in view NSDM_V_MSEG doesn't exist.

So we are going to fix it by creating an EXTEND VIEW in Eclipse because we are having a problem with CDS view.

Above picture the data definition is mentioned for the view NSDM_V_MSEG that we'll use in next steps.

Open Eclipse and follow the steps below.

1. Click on Open ABAP Development Object and search for data definition NSDM_DDL_MSEG.

This is the view that we are going to extend.

2. Right click on System Library and select Other ABAP Repository Object.

Then select Data Definition and continue with Next.

Provide Data Definition with name and description and continue.

Select Extend View and Finish.

So, the template has been created and now we can add the field which is enhanced in MSEG.

After activating you can check the field in t-code SE11.

The problem is solved. And now you can run MIGO without getting the error.

Conclusion: if we have inconsistency with the tables like MSEG, MARC, MKPF, xBEW, and etc, and with their views, we have to extend view of that enhanced field that makes inconsistency.

Referenced SAP notes: 2242679, 2865970.
Labels in this area