Skip to Content
Author's profile photo Former Member

Storage location authorization check with authorization object M_MSEG_LGO

This document explains how storage location can be restricted for a particular user & why it is needed. First let me explain the business scenario.          

Business scenario- Production people while producing finish good they require the raw materials. Production people are giving requisition to stores for the raw materials to produce a particular finish good. Stores person are issuing the raw materials from main stores & when raw materials are moved to production shop floor location then production people can consume the raw material from shop floor location only. Main store location is under the stores department they only can issue the raw material from main store & production people after receiving the raw material from main store to production shop floor location then they can use it.

So from above scenario to achieve this in SAP we require proper storage location authorization check for production & stores user so that store cannot use storage location which is under preview of production & similarly with production . For this if one user for production is there to achieve the requirement we will

                                                                    1> First create an user

                                                                    2> Second we will create a specific role for the user

                                                                    3> Thirdly in the role we will assign the particular storage location authorization for the user

                                                                    4> Fourthly we will assign the role to the particular user

                                                                    5> Fifth point we will functionally set the storage location authorization check

Now the things I have explained above will be shown step-wise with screenshots & how the requirement is achieved.


Maintain movement type & storage location for the role under authorization object M_MSEG_LGO



Assigned Tags

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

      Very nice document... Thanks for sharing.......

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Thanks Santosh

      Author's profile photo Dibyendu Patra
      Dibyendu Patra

      You have missed to give the original authorization object for storage location.

      You have given the screen shot (3rd and 4th) for authorization object M_MSEG_BWA, which is nothing related to this document.

      You have to restrict the storage location via the authorization object M_MSEG_LGO.

      If you press the documentation for the IMG path "Authorization Check for Storage Locations"

      Then you will get the details.

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Dev

      Thanks for rectifying me . As dev mentioned that I missed while giving authorization we need to give authorization for authorization object M_MSEG_LGO see the screen shot below


      Then follow the rest of procedure like assigning the role to user & activate the        authorization check for storage location as shown in the document.

      Author's profile photo Dibyendu Patra
      Dibyendu Patra

      Instead of replying here, you can update your document for the same.

      You will find the edit option right side of your document.

      Go to the edit mode and change the entire changes for your document. Then publish it again.

      Author's profile photo Shkelzen Hasanaj
      Shkelzen Hasanaj

      Hi Sandipan Dutta,

      Thanks for sharing this.

      Have you been able to use this authorization object for reports, i.e. MB52?


      Author's profile photo Pedro Perez
      Pedro Perez

      I have a question, for the same user I want to allow him to use a specific movement type within a given SLoc that should not be allowed in another SLoc. I understan it is possible, right?