Skip to Content
avatar image
Former Member

Implement authorisation on Storage Type level

Good day,

Is this possible?

Auth. blocks on Storage type level, Pysical as well as Dynamic Storage types, for all movements into, out or within the warehouse, to authorised users by selected Storage types. But we do not want to place auth. limits on Creating Transfer orders.

Is this possible in Standard SAP, our auth. people think it is not possible.

Pls advise.

Tnx a million!!

B.Reg.

C. Smolders

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Mar 26, 2008 at 11:32 AM

    Hello Smolders,

    It is SAP standard that authority checks for WM were not designed to check authorization for LGTYP. For example, transaction LT12 only checks the authorisation of the warehouse number. The storage type is treated as a dummy variable in this case. You can see this in the following section of code:

    1.) Transaction LT10 (Stock Transfer):

    AUTHORITY-CHECK OBJECT CON_BER_LGNUM

    ID 'LGNUM' FIELD P_LGNUM

    ID 'LGTYP' DUMMY.

    2.) Transaction LT12 (Confirm TO)

    AUTHORITY-CHECK OBJECT CON_BER_LGNUM

    ID 'LGNUM' FIELD P_LGNUM

    ID 'LGTYP' DUMMY.

    Hope this helps to clarify.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 01, 2008 at 10:27 AM

    Hello Smolders,

    It is not appropriate to communicate SDN Forum questions over email. Thus I would like to answer to your questions here.

    The authorization object being used is L_LGNUM. You'll see the definition of CON_BER_LGNUM in FL000TOP :

    ****

    DATA: CON_BER_LGNUM(10) VALUE 'L_LGNUM',

    ...

    ****

    I've attached the following SAP Library Documentation for you which explains further:

    ******

    When creating transfer orders, a high degree of accuracy is attained by combining the authorization check of the objects L_BWLVS and L_LGNUM. If the system allows a certain WM movement type, you can process all storage types when you create transfer orders as defined in the WM table for movement types and/or the table for alternative storage types.

    If a storage type is changed manually, the system makes an additional authorization check for that storage type. The check sequence is as follows:

    Check for warehouse number authorizations.

    Check for storage type.

    First the system checks whether the storage type entered is used in the storage type search (Customizing, Strategies). If the storage type is defined in the search sequence, the respective storage type is not checked against the user master. If the storage type is not defined in the storage type search table, the system executes a check against the user master.

    ************************************************************************

    The logic behind the authorization check on the storage type is that if a user does not have the authorization for a specific storage type then he gets an error message if he manually tries to enter a storage type for which he has no authorization. However, if he processes the TO creation and the storage type is found due to the storage type search in customizing then the TO will still be created.

    The logic behind the authorization check on the storage type is that if a user does not have the authorization for a specific storage type then he gets an error message if he manually tries to enter a storage type for which he has no authorization. However, if he processes the TO creation and the storage type is found due to the storage type search in customizing then the TO will still be created.

    The idea behind this is that customizing settings are correct and are followed, only manual manipulations are checked.

    During the confirmation of the TO it´s not possible to change the

    Storage type, so the check at this stage is limited intentionally to the warehouse number.

    I hope the above information has been useful.

    Add comment
    10|10000 characters needed characters exceeded