Skip to Content
Author's profile photo MA JAMIL

Redesigning of the MB51 Standard SAP report 1\3

There is lot of threads regarding slow performance of RM07DOCS and MB51/MB5B during data fetching from MSEG and MKPF table. As we know that the MSEG and MKPF is the biggest table of database and have millions of record. I have also received number of complaints regarding slow performance when Users want to fetch the data from MSEG and MKPF tables. I find out the document and think that I have to impalement it step-by-step with screenshot, So that SNC users can implement it smoothly with the help of this document.

You can implement this activity with help of SAP technical Team (BASIS, ABAP).

The below document is the Extension of the MSEG from MKPF fields whilst performing Redesigning of the MB51 Standard SAP report.


For the movement of the MKPF fields to MSEG, refer below the Redesign overview SAP Standard Notes that needs to be implemented in sequential order.


Refer the Action plan below for the detailed Analysis and step by step guide for the movement of fields from MKPF to MSEG and MB51 Redesigning.



It has been said in the Step 1 of SAP Note 1516684 that we need to add the following below mentioned fields within Standard SAP table MSEG along with their Data Elements. We will now guide you through the procedure of adding such fields to MSEG SAP Standard table.

Most Importantly, Do not set the INIT Indicator adjacent to KEY field Checkbox within the DB table.


Access transaction SE11 for SAP ABAP Dictionary to access the SAP Standard and Customized DB Tables.

Enter MSEG in the Database table input field and Press ‘Change’


The System will prompt for the Access Key or SSCR key which would mean that you will have to register this Standard SAP object and on successful registration, an access key would be generated.

Select ‘Maintain in logon language’ option.


You are all set to go to add your fields. But most importantly, as mentioned in the Standard SAP Note that you have to add fields before the Append Structures. Locate the position within the MSEG table where the first append structure had been appended. It would most probably be in the last.

Place the fields in the middle of the last table field and the very first Appended structure. Refer the below snapshot for the exact location. That might be different for others.


Place the fields and their respective DE within the MSEG table on the said location and save it within a change request later transporting it to subsequent systems.


Save the changes.


Activate the SAP Standard table MSEG by pressing the Activation Button on the Application toolbar and select the ok button from the popup asking for the objects to be activated. MSEG table object would be selected by default.


Since it’s a Standard SAP table it would take time to activate and apply the changes. It would be successfully activated with an information message “Active object generated”. The SAP standard table would now contain fields from standard SAP note 1516684.


As the fields have been successfully added in the MSEG table, now create a DB table within the SAP Namespace with the name MMIM_CONTROL_LOG in the package MB along with the Technical attributes. Whole characteristics of DB table have been mentioned in the SAP Note 1516684. Refer the below mentioned snapshot.


Follow the same steps from the ABAP dictionary to create the said table. Access SE11 and enter the name in the DB table field name and press Create. Information message would be displayed, Select Ok.


Since we are creating the table within SAP Namespace, so again we would need to register the object and request for the SAP SSCR Key. Enter the Key within the Access key Input field and press Continue


Since it would be an SAP standard DB table and can only be created in SAP Namespace. An information message would be displayed, Press OK.


Enter the Short Description, Delivery Class and Data Browser/Table View Maint. Options exactly as mentioned in the SAP Note 1516684 . Do not change them according to your needs since we are dealing with SAP Namespace.


Access technical settings of the table. System will prompt for the changes made to be saved and go for the action performed. Save the Changes and Apply Package MB as already mentioned with in the SAP Note 1516684 .


Package MB Entered. Click Save Icon.


Warning message prompting/confirming the SAP Namespace. Press Ok Button.


Assigning the Changes to a Change request later transporting it to the Subsequent Systems.


Access the technical settings and give Data Class and Size Category. Press Save.


Mention MANDT and ACTION fields as the Key fields by checking the Key checkbox followed by the fields


Save and Activate the Table.


View the warning message by pressing YES.


Do not worry about the warning messages.


The Object has been successfully activated.


Now we need to implement the corrections mentioned in the SAP Note 1516684 .


Use SNOTE TCode for the auto implementation of the correction instructions.


Download it in your system and implement it to your SAP system.

for more information, please have a look at below link

Implementation Of SNOTE

Redesigning of the MB51 Standard SAP report 2\3

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Sijin Chandran
      Sijin Chandran

      Very thanks for this really informative contribution 🙂

      I have one doubt the code for passing VGART , BUDAT value from MKPF to VGART_MKPF , BUDAT_MKPF of MSEG will be impleted in note 1516684 I guess ?

      If my guess is incorrect then please tell me how we specify this thing.

      Reason being I need to add other such fields

      Author's profile photo M. Abdul Jamil
      M. Abdul Jamil
      Blog Post Author

      Dear Sijin,

      mistype error now I correct it

      Thanks & Regards,

      Author's profile photo Jürgen L
      Jürgen L

      I was just about to blog it myself -  I finished the conversion yesterday - but then I found your not need to create a second blog for the same, and I will just take the chance to add a little experience here as comment.

      In the meantime there are a few notes more that you might want to consider when implementing this MSEG extension:

      1756236 - MBGR: Redesign der Selektion zur Performance Optimierung   

      1679885 - MB02: Änderungen im Feld XBLNR nicht in MSEG fortgeschrieben

      1685136 - VL01N/VL31N: Field XBLNR_MKPF not filled in MM document item

      I had an issue with an very old Oss note Note 32236 - Incorrect stock qty or stock value in material master

      which needed to be fixed with note 304670 - Renaming consistency analysis tools of the stock

      and had caused some trouble in generating the the new MSEG structure.

      Further we have quite restrictive authorization settings and responsibilities. An application consultant is not allowed to create indices as this can only be done from Basis consultants.  Hence the OSS note 1516684 was a shared activity. If you have as well such an environment, then I recommend to create for each step from note 1516684 an individual transport request.

      The update of 26 million MSEG records needed in total 17 hours 45 minutes on a weekend.

      Author's profile photo Former Member
      Former Member

      Dear jamil

      It is very helpful and detailed document about mb51 because you used snaps to explain it step by step.

      Author's profile photo Sai Krishna
      Sai Krishna

      Dear Jamil,

      Its wonderful.  Thank you very much 🙂

      Author's profile photo Former Member
      Former Member

      Dear Jamil,

      Its wonderful blog.



      Author's profile photo Former Member
      Former Member

      very good! thanks for sharing!