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.

STEP 1:

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

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

Access the Tcode SE38 for the creation of the Z File within your SAP system in the customer namespace. Enter the Program name and select Create button. In our case we have changed the program name from

ZMST_FILL_MSEG_FROM_MKPF à ZMST_FILL_MSEG_FROM_MKPF_V3.

Place the name exactly the same as mentioned in the SAP Note.

Fill out the program attributes as shown below and make it the Executable program

Enter the package name which would be in the customer namespace

Now assigning this newly created program object to the same change request that had already been created using the Developer account

Within the ABAP editor of the just created program, Select the below mentioned path from the Menu bar.

Utilities->More Utilities->Upload/Download->Upload

From this option you can directly import the file from your system directory.

Import the file that has been downloaded from the SAP Note 1516684 attachments. After importing Activate the file.

Now on the initial screen of the SAP ABAP editor choose execute button to run the file.

This would be the initial Selection screen of the file just imported.

Before running the program, create the TMP index in MSEG DB Table.

Access Tcode SE11 for changing the MSEG table. Enter table name and select change

System will prompt an information message stating to make the changes only if they are urgent. Select ok

Select Indexes… button from the Application toolbar besides the Technical Settings button

All the Indices of the MSEG table would have been shown. From the create button mentioned below, choose Create index option for the TMP index to be created for MSEG table.

Enter the Index Name i.e. TMP.

System will prompt a Warning message stating that we did not place it within the customer namespace

Select ok. System will again prompt the same message about the namespace. Ignore it and press Enter.

Select Maintain in Logon Language button from the options provided on the popup message.

Enter the Short description for the index. This is not given in the SAP note 1516884. It can be any but be descriptive. Select Table Fields button copying the fields from the MSEG table to be included within the TMP index.

Select the fields from their check boxes mentioned in the SAP note 1516884 and press Copy button. Fields with their short descriptions would copy to the index creation frame

The fields have been copied.

Save the index and assign it to the same change request which we have already created so that all the objects be transported correctly and simultaneously.

Activate the index.

You need not worry about the warnings. Select No to ignore the warnings.

Object has been successfully activated as it can be seen from the status bar below.

You can now view the TMP index from the list of MSEG indices. TMP has been highlighted in the snapshot below.

Moving on to the more indices to be create over the same SAP DB table MSEG, follow the same procedure to create the BUD, M1 and M2 indices for MSEG table which would help in executing the program in an efficient manner in terms of the records access.

Important: We also have to modify the Standard M SAP Index for MSEG

Again follow the same procedure to add BUDAT_MKPF field within the M index. Save and activate the index. System will give an information message stating the error messages and prompting to view the log information.

View the log information. From here the error message is that “INDX MSEG~M was not activated”.

The SAP system will itself provide the solution to activate the index and that would be the conversion of the Index which can be performed from the tcode SE14

Follow the procedure to convert the Index.

From the MSEG list of indices BUD, M1 and M2 would be in Active state while M index would be in InActive state. For it to be activated as well, we would now convert the index through SE14.

Access tcode SE14. MSEG table would be pre entered in the input field. Press Enter and you will be given the below mentioned snapshot. SelectActivate and adjust database with Save data option and select Yes to execute the selected option

Redesigning of the MB51 Standard SAP report 3\3

It would take time to activate the database because it will recreate all the indices at system end. View and ignore the problems if it states the DB space problem.

Moving on to the SAP Note 1516684, we are now fully ready to execute the report. We have changed the MSEG table, added the fields in MSEG from MKPF successfully, created the Indices; Modified the MSEG Standard Index M by adding a field from MKPF activated the Indices, created the table. Now we are all set to go to run the report. Follow the instructions from the SAP Note 1516684.

Most importantly, carefully read the instructions to run the report from the SAP Note. The report would run in background mode and also we have to mention the Blocks of the data from the MSEG table and actual runs per block to cover the whole data from the MSEG table.

In order to identify the block size of the MSEG table i.e. the total number of entries that exists in the MSEG table, we used the transaction SE11 to identify how many blocks can be made to cover the entire data from MSEG. Access SE11 and Enter MSEG as the Table name, select display table, the below screen would be displayed and here you can identify the number of entries by selecting the Number of Entries pushbutton. Before this do blank Width of output list and Maximum No. of Hits option as highlighted in the snapshot below.

In our case the total existed entries are 16,569,028 within the MSEG table. If we divide this number to a single block of 10,000,000 than the runs per block would be 17 to cover the entire data from MSEG for conversion.

Select the path mention below from the Menu bar;

Program->Execute in Background

The System will ask for the print parameters. Give your print parameters.

Another popup asking for the starting mode to select. Select Immediate mode and press Save icon

From the job overview session, you can have the status of your report run in background mode.

This report would take enough time to convert all your documents within the MSEG table. You Can always monitor the progress via Job overview in SAP.

After the successful run of the report again run the report with ‘Show documents to be converted’ mode with ‘Update MSEG’ checked and block size and Number of runs per block size remained in their default values. This time you would not run it in background as it would not take much time to execute.

The result of the second mode would be that ‘All documents were converted’ as mentioned below.

Again run the report with the third Mode selected.

You can view the status of current report via SM50

Again the successful run message would be ‘All documents were converted’, which would mean that we are exactly going in the right direction.

This mode is of much importance as it will place a conversion complete check within the table that we have created earlier with the name MMIM_CONTROL_LOG, which would confirm that the conversion of MSEG has been successfully completed without any impediments.

Monitor the Status through SM37.

The second mode has been run successfully, now we are all set to go for the Regeneration of MB51 according to the new code and new data from MSEG.

Again schedule the background task for the last mode to Regenerate MB51.

We got an error as mentioned below. You won’t get it if you have already placed exactly the same name of the Z file in your SAP editor. We got it because we change the name of the file and this is causing an error.

For this to run without any obstacles, we changed the following code in ZMST_FILL_MSEG_FROM_MKPF_V3. Open the editor to change the code in change mode.

Search for the ‘reading’ keyword or the exact error ‘Error during reading source code’ within the source code of the file. You will easily see above the error they mentioned to read the file with the name hardcoded. Change it accordingly if you already change the name of the file during creation. If you do not change the file name, than you do not need to perform the step.

We change it to ZMST_FILL_MSEG_FROM_MKPF_V3

After the change, now again execute the report. And you will see the successful message stating that ‘Report RM07DOCS_GENERATED updated’ which would mean that the standard MB51 coding has now been updated to the new changes and new logic would be executed which would fetch the data from MSEG.

Now You can transport the created request.

SAP Note

SAP Note which previously known as OSS note is a Patch released by SAP to fix bug or Error in the Standard SAP program. SAP will provide the corrections through SAP Note for customers to implement the changes, which will resolve the program errors

Transaction Code

We can implement the SAP note with the help of SNOTE

How we can apply the SAP note

We have to download the SAP note before apply any note and we can download this note with SNOTE.

Execute the note on successful downloading and it would auto be implemented

Once the note successfully downloaded, now select the note and click on execute button to implement SAP note

Select yes, confirming that you have understood the side effects of the note.

click on continue

Ignore the Information Message.

when you click on OK button then window will be prompt for transport request. here you can create a new request.

After that, list of changes that are being made will be displayed in above screen. Click on continue button to proceed to apply the changes.

Click on continue button to proceed further

SAP Note implemented successfully.

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.

STEP 1:

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

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

Access the Tcode SE38 for the creation of the Z File within your SAP system in the customer namespace. Enter the Program name and select Create button. In our case we have changed the program name from

ZMST_FILL_MSEG_FROM_MKPF à ZMST_FILL_MSEG_FROM_MKPF_V3.

Place the name exactly the same as mentioned in the SAP Note.

Fill out the program attributes as shown below and make it the Executable program

Enter the package name which would be in the customer namespace

Now assigning this newly created program object to the same change request that had already been created using the Developer account

Within the ABAP editor of the just created program, Select the below mentioned path from the Menu bar.

Utilities->More Utilities->Upload/Download->Upload

From this option you can directly import the file from your system directory.

Import the file that has been downloaded from the SAP Note 1516684 attachments. After importing Activate the file.

Now on the initial screen of the SAP ABAP editor choose execute button to run the file.

This would be the initial Selection screen of the file just imported.

Before running the program, create the TMP index in MSEG DB Table.

Access Tcode SE11 for changing the MSEG table. Enter table name and select change

System will prompt an information message stating to make the changes only if they are urgent. Select ok

Select Indexes… button from the Application toolbar besides the Technical Settings button

All the Indices of the MSEG table would have been shown. From the create button mentioned below, choose Create index option for the TMP index to be created for MSEG table.

Enter the Index Name i.e. TMP.

System will prompt a Warning message stating that we did not place it within the customer namespace

Select ok. System will again prompt the same message about the namespace. Ignore it and press Enter.

Select Maintain in Logon Language button from the options provided on the popup message.

Enter the Short description for the index. This is not given in the SAP note 1516884. It can be any but be descriptive. Select Table Fields button copying the fields from the MSEG table to be included within the TMP index.

Select the fields from their check boxes mentioned in the SAP note 1516884 and press Copy button. Fields with their short descriptions would copy to the index creation frame

The fields have been copied.

Save the index and assign it to the same change request which we have already created so that all the objects be transported correctly and simultaneously.

Activate the index.

You need not worry about the warnings. Select No to ignore the warnings.

Object has been successfully activated as it can be seen from the status bar below.

You can now view the TMP index from the list of MSEG indices. TMP has been highlighted in the snapshot below.

Moving on to the more indices to be create over the same SAP DB table MSEG, follow the same procedure to create the BUD, M1 and M2 indices for MSEG table which would help in executing the program in an efficient manner in terms of the records access.

Important: We also have to modify the Standard M SAP Index for MSEG

Again follow the same procedure to add BUDAT_MKPF field within the M index. Save and activate the index. System will give an information message stating the error messages and prompting to view the log information.

View the log information. From here the error message is that “INDX MSEG~M was not activated”.

The SAP system will itself provide the solution to activate the index and that would be the conversion of the Index which can be performed from the tcode SE14

Follow the procedure to convert the Index.

From the MSEG list of indices BUD, M1 and M2 would be in Active state while M index would be in InActive state. For it to be activated as well, we would now convert the index through SE14.

Access tcode SE14. MSEG table would be pre entered in the input field. Press Enter and you will be given the below mentioned snapshot. SelectActivate and adjust database with Save data option and select Yes to execute the selected option

Redesigning of the MB51 Standard SAP report 3\3

It would take time to activate the database because it will recreate all the indices at system end. View and ignore the problems if it states the DB space problem.

Moving on to the SAP Note 1516684, we are now fully ready to execute the report. We have changed the MSEG table, added the fields in MSEG from MKPF successfully, created the Indices; Modified the MSEG Standard Index M by adding a field from MKPF activated the Indices, created the table. Now we are all set to go to run the report. Follow the instructions from the SAP Note 1516684.

Most importantly, carefully read the instructions to run the report from the SAP Note. The report would run in background mode and also we have to mention the Blocks of the data from the MSEG table and actual runs per block to cover the whole data from the MSEG table.

In order to identify the block size of the MSEG table i.e. the total number of entries that exists in the MSEG table, we used the transaction SE11 to identify how many blocks can be made to cover the entire data from MSEG. Access SE11 and Enter MSEG as the Table name, select display table, the below screen would be displayed and here you can identify the number of entries by selecting the Number of Entries pushbutton. Before this do blank Width of output list and Maximum No. of Hits option as highlighted in the snapshot below.

In our case the total existed entries are 16,569,028 within the MSEG table. If we divide this number to a single block of 10,000,000 than the runs per block would be 17 to cover the entire data from MSEG for conversion.

Select the path mention below from the Menu bar;

Program->Execute in Background

The System will ask for the print parameters. Give your print parameters.

Another popup asking for the starting mode to select. Select Immediate mode and press Save icon

From the job overview session, you can have the status of your report run in background mode.

This report would take enough time to convert all your documents within the MSEG table. You Can always monitor the progress via Job overview in SAP.

After the successful run of the report again run the report with ‘Show documents to be converted’ mode with ‘Update MSEG’ checked and block size and Number of runs per block size remained in their default values. This time you would not run it in background as it would not take much time to execute.

The result of the second mode would be that ‘All documents were converted’ as mentioned below.

Again run the report with the third Mode selected.

You can view the status of current report via SM50

Again the successful run message would be ‘All documents were converted’, which would mean that we are exactly going in the right direction.

This mode is of much importance as it will place a conversion complete check within the table that we have created earlier with the name MMIM_CONTROL_LOG, which would confirm that the conversion of MSEG has been successfully completed without any impediments.

Monitor the Status through SM37.

The second mode has been run successfully, now we are all set to go for the Regeneration of MB51 according to the new code and new data from MSEG.

Again schedule the background task for the last mode to Regenerate MB51.

We got an error as mentioned below. You won’t get it if you have already placed exactly the same name of the Z file in your SAP editor. We got it because we change the name of the file and this is causing an error.

For this to run without any obstacles, we changed the following code in ZMST_FILL_MSEG_FROM_MKPF_V3. Open the editor to change the code in change mode.

Search for the ‘reading’ keyword or the exact error ‘Error during reading source code’ within the source code of the file. You will easily see above the error they mentioned to read the file with the name hardcoded. Change it accordingly if you already change the name of the file during creation. If you do not change the file name, than you do not need to perform the step.

We change it to ZMST_FILL_MSEG_FROM_MKPF_V3

After the change, now again execute the report. And you will see the successful message stating that ‘Report RM07DOCS_GENERATED updated’ which would mean that the standard MB51 coding has now been updated to the new changes and new logic would be executed which would fetch the data from MSEG.

Now You can transport the created request.

SAP Note

SAP Note which previously known as OSS note is a Patch released by SAP to fix bug or Error in the Standard SAP program. SAP will provide the corrections through SAP Note for customers to implement the changes, which will resolve the program errors

Transaction Code

We can implement the SAP note with the help of SNOTE

How we can apply the SAP note

We have to download the SAP note before apply any note and we can download this note with SNOTE.

Execute the note on successful downloading and it would auto be implemented

Once the note successfully downloaded, now select the note and click on execute button to implement SAP note

Select yes, confirming that you have understood the side effects of the note.

click on continue

Ignore the Information Message.

when you click on OK button then window will be prompt for transport request. here you can create a new request.

After that, list of changes that are being made will be displayed in above screen. Click on continue button to proceed to apply the changes.

Click on continue button to proceed further

SAP Note implemented successfully.