How to restrict users for changing goods issuing storage location in process order?

[Former Member]

Dear All,

I am working on process order. When my users, create/change process order
by transaction COR1/COR2, herein they check material availability and if any material shortage is there then they go into tab component overview and changes the storage location because in other storage location stock may be there, and then issue the stock and complete the production.

I want that if they are changing the storage location and save the transaction then system should check the authorization that whether this user is authorized for the storage location or not? and throw an error if he is not authorized for selected SLoc in 'component overview' tab.

I do not want to grey out the SLoc field because it will restrict authorized users also. So I want to use any technical option hence please suggest it.

If anybody done such restriction in process order then please share the solution.

Thanks,

Naresh

[Former Member · Accepted solution]

Dear Naresh,

Please check the authorization object M_MSEG_LGO for storage location check. Please created a role with the authorization object ( Restricting storage locations) and assign it to the user.

Please also check the SAP note 523511 and SAP knowledge based article 1668678.

[Former Member · Accepted solution]

Dear Naresh,

                                    You can restrict this as said by Mr. Sathis, but you need to maintain another setting in MM....> IM ......> Auth control for the movement type. If you activate there for 261 ,this object M_MSEG_LGO is called and check in the User profile. If the User is having the sloc in the object:M_MSEG_LGO then transaction is allowed.

Regards,

Subrahmanyam B

[Former Member]

Thanks to All

[rohan_somji]

Hi Naresh,

                  Have you tried screen variant & freezed the field for limited users.

Thanks & Regards,

Rohan Somji

[Caetano]

Hi Naresh

Is this issue solved? Can you please close this thread selecting the correct answer or share the solution?

BR

Caetano

[Former Member]

Hi Naresh,

   for your solution follow following steps Which I have implemented for a client for same issue. For this you need help of BASIS Consultant.

M_MSEG_LGO

Definition

Using this authorization object you can limit the maintenance of goods movements via the storage location of a plant.

Defined fields

The authorization object contains four fields:

• Activity: defines whether the user

• may enter goods movements (Activity=1)

• may change goods movements (Activity=2)

• may display goods movements (Activity=3)

• Movement type: defines the movement types with which the user may maintain goods movements.

• Storage location: defines which storage locations in which plant a user may maintain.

• Plant: defines which plants the user may maintain.

  In the various authorizations for this object, you define which movement types and with which activity for which storage locations in which plants the user may maintain goods movements. 

Example

User A may enter, change and display goods movements with all movement types in all plants and in all storage locations. Authorization:

• Activity '01-03' or '*'

• Movement type '*'

• Storage location '*'

• Plant '*'

  User B may only display goods movements with all movement types in storage location 0001 in plant 0002. Authorization: 

• Activity '03'

• Movement type '*'

• Storage location ,'0001'

• Plant '0002'

  User C may only enter, change and display goods movements using movement types 501 and 502 in storage location 0001 in plant 0002. User C may therefore only post and reverse goods receipts without purchase order into the warehouse. Authorization: 

• Activity '01-03' oder '*'
• Movement type '501-502'
• Storage location ,'0001'
• Plant '0001'

Hope you will resolve your problem with the help of this.

Regards

Shyam

[JeevanSagar]

M_MSEG_LGO authorization is only for posting goods movements, not for the component overview field in production/process order. Also that authorization prevents the user from posting to/from that storage location altogether for particular movement type, not just for a material.

Like Senthil mentioned, if you restrict the storage location at COR1/COR2 level they can change the storage location in COR6/MB1A/MIGO/MB11.

If you still want to restrict you can use the user exit PPCO0023 or BAdI WORKORDER_UPDATE. You'd have to create a custom authorization object and assign that object to authorized users.

[Former Member]

Dear Jeevan,

                Can't we use the M_MSEG_LGO route ?? IF it can/can't be used, how good/better controls are there in the above proposed soln by you ? Please light on it.

Regards,

Subrahmanyam B

[JeevanSagar]

Hi,

M_MSEG_LGO is only for posting goods movements to/from that storage location (to control in tcodes MB1A/CO11/CO11N/MIGO/MB11). Not for changing the issue storage location in the component overview of production/process order.

[Anupam1143]

Hi

M_MSEG_LGO can only be used when you activate authorisation management  for SLOC in SPRO under MM>Goods Issue/Trasnfer posting>Authorisataion management>Authorisation check for Slocs.

Regards

Anupam Sharma

[Former Member]

Hi Naresh,

Wondering if the authorizations settings could actually restrict the user to just change the SLoc entry in the Order/Component overview! Even if they could, they may not fulfill the process requirements.

• Kindly recall that, the user who enters the confirmation or goods movement can still change the SLoc entry.
• You may be able to restrict goods movements from selected SLoc - per the authorization settings for the respective user.

Alternatively, you can set up Transaction variants which prevent changes to SLoc entry in the order as well as confirmation/goods movements; and assign this transaction to the normal users.

• And only select few users would have access to normal transactions, which would allow them to change the SLoc entries.

Regards,

Senthil

[Navid_Ansari]

HI Mr.Subrahmanyam B thanks for your advice it worked for me to imply restrictions on Storage Location via authorisation Control check in MM->IM->Authorisation. Thanks a lot for the same.