Skip to Content

/wp-content/uploads/2013/02/29_182215.png

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

/wp-content/uploads/2013/02/30_182216.png

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.

/wp-content/uploads/2013/02/31_182561.png

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

/wp-content/uploads/2013/02/32_182291.png

Enter the package name which would be in the customer namespace

/wp-content/uploads/2013/02/33_182292.png

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

/wp-content/uploads/2013/02/34_182293.png

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

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

/wp-content/uploads/2013/02/35_182562.png


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.

/wp-content/uploads/2013/02/36_182294.png

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

/wp-content/uploads/2013/02/37_182295.png

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

/wp-content/uploads/2013/02/38_182296.png

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

/wp-content/uploads/2013/02/39_182300.png

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

/wp-content/uploads/2013/02/40_182563.png

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

/wp-content/uploads/2013/02/41_182301.png

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

/wp-content/uploads/2013/02/42_182302.png

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.

/wp-content/uploads/2013/02/43_182303.png

Enter the Index Name i.e. TMP.

/wp-content/uploads/2013/02/44_182564.png

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

/wp-content/uploads/2013/02/45_182565.png

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

/wp-content/uploads/2013/02/46_182566.png

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

/wp-content/uploads/2013/02/47_182304.png

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.

/wp-content/uploads/2013/02/48_182305.png

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

/wp-content/uploads/2013/02/49_182306.png

The fields have been copied.

/wp-content/uploads/2013/02/50_182309.png

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.

/wp-content/uploads/2013/02/51_182567.png

Activate the index.

/wp-content/uploads/2013/02/52_182568.png

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

/wp-content/uploads/2013/02/53_182569.png

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

/wp-content/uploads/2013/02/54_182570.png

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

/wp-content/uploads/2013/02/55_182571.png

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

/wp-content/uploads/2013/02/56_182572.png

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.

/wp-content/uploads/2013/02/57_182573.png

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

/wp-content/uploads/2013/02/58_182574.png

Follow the procedure to convert the Index.

/wp-content/uploads/2013/02/59_182310.png

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.

/wp-content/uploads/2013/02/60_182311.png

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

/wp-content/uploads/2013/02/61_182312.png

Redesigning of the MB51 Standard SAP report 3\3

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Jürgen L

    It looks like the access to many screen shots is broken. Can you update?

    The link to the 3rd part does as well not work.

    further you should add a link back to part 1 (as well in part 3 back to part 1 and 2), this makes it easier for the community to get all pieces together.

    Further I recommend to add  these tags to make it visible as well from MM space overview page as related content:

    mm, materials_management

    (0) 
    1. M. Abdul Jamil Post author

      hi Peter,

      Hopefully, You are doing well

      Dear, the SAP installed on window in my company and Users were facing issue regarding slow speed of MB51. so, I made this document and upload on this forum and Now I edit this blog and as per suggestion of Jurgen I also make a part of mm, Materials_management.

      Regards,

      (0) 
      1. Former Member

        Well, in a SAP on Windows blog I expect windows related information.
        The information you posted is application and database related and has no operating system specific information.

        Think about, what is happening to this blog if every problem, enhancement to any Netweaver component will also posted here only because the application server is running on a Windows operating system!

        regards

        Peter

        (0) 

Leave a Reply