Could I block business processing at storage location level?
for example:
plant code: 1200,
storage location: 4500;4600;4700
all these storage location are assigned to the plant code, and all of them have dealt with business data.
now, the customer tell me they do not want 4700 to deal with the furthur business data, what's more, they do not want to do so by delete the 4700.
someone tell me that SAP can use userexit to control the business issue. but I can not find the program name include the special userexit.
Maybe someone can help me again? thanks!!
_________________
I believe I can fly, I believe I can touch the sky.
Hi,
Have you tried to look at the 'Authorization check for the Storage Location' under Authorization Management?
Cheers,
HT
_________________
Moderator:
Hi,
Have you tried to look at the 'Authorization check for the Storage Location' under Authorization Management?
Cheers,
HT
Hello! Ha Tran,
You know, the 'authorization check' is not aglie for this case, you must give all the allowable structure data into the user profiles. But anyway, thanks for your attention and your suggestion. We had used the authorization check for the case.
best regards
Dickson
_________________
I believe I can fly, I believe I can touch the sky.
Hi,
Of course, the setting of 'Authorization Check at the Storage Location' can be used as one of several alternative options. In this case, use Transaction MM06 to set a deletion flag for material at storage location level. This shall be done for all materials that have this storage location that can be found by checking the table MARD with SE16. As well the message M7 127 from warning to error message (transaction OMCQ) must be changed.
Cheers,
HT
_________________
Moderator:
Hi,
Of course, the setting of 'Authorization Check at the Storage Location' can be used as one of several alternative options. In this case, use Transaction MM06 to set a deletion flag for material at storage location level. This shall be done for all materials that have this storage location that can be found by checking the table MARD with SE16. As well the message M7 127 from warning to error message (transaction OMCQ) must be changed.
Cheers,
HT
****************************************************
I think your solution is right for this case ! I will suggest my customer to do so. thanks for your help again!
Regards
Dickson
_________________
I believe I can fly, I believe I can touch the sky.