Regulating user authorizations for Goods Receipting transactions

Regulating user authorizations for Goods Receipting transactions

In our SAP R/3 4.6C implementation, we have added functionality via a BAPI to Goods Receipting (transaction MIGO) that allows users to update certain fields (e.g. inventory no.) in the relevant asset master records.

    Requires Free Membership to View

    Login

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.


However, to do this we have had to add certain authorizations (e.g. A_S_ANLKL etc.) to the Goods Receipting role. This in itself is not an issue but when a user has other asset-related roles the additive effect of autorizations presents a security problem.

In attempting to overcome this we have created a new authorization object ZA_S_ANLKL that is effectively a copy of A_S_ANLKL. This authorization object has been assigned to transaction AS02 via SE93. This allows me to add an extra check for activity=02 but it does not allow me to put the relevant classes and company codes in a role. Is there a better approach?
I would use a customer exit in the ABAP behind MIGO to check for the specified values in your custom authorization object. Additionally, you should determine if there is a similar exit to comment out the A_S_ANLKL check that is undesired.

This was first published in April 2003

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top