Entering content frameFunction documentation Authorization Checks Locate the document in its SAP Library structure


The authorization concept in Warehouse Management guarantees a smooth and secure organization of warehousing logistics.


Defining Profiles

Profiles contain authorization objects for a limited number of transactions. For example, the profile L_WM_ALL contains all authorization objects for tasks in WM (with the exception of L_ARCH). To define profiles, see Tools ® Authorization management ® Create profiles in the Warehouse Management IMG.

Detailed information on how to define profiles is also found in "Basis / Users and Authorizations" in the System Administration documentation.

Defining User Authorizations

For each user who requires authorization to carry out tasks in WM, a user master record must be maintained. To define user authorizations, see Tools ® Authorization management ® Define authorizations in the Warehouse Management IMG documentation.

Detailed information on how to define user authorizations is also found in "Users and Authorizations" in the System Administration Guide.

User Authorization Groups

When configuring WM in Customizing, individual views (partial tables containing specific information) are assigned to authorization maintenance groups that must be included in your authorization concept. These groups are assigned to users using the authorization object S_TABU_DIS. The following authorization groups are applicable to WM:

WMA - WM: Application table

Application table views can be maintained as necessary by WM users.

WMC - M: Application control

These views should only be maintained by system managers or those authorized to make changes in WM configuration menus.

WMC1 - WM: Application texts

These views contain descriptions of various indicators used by WM and must be maintained by users who wish to operate the system in more than one language.

WMS - WM: Control SAP

The WM control views are generally not changed unless such changes are discussed first with an SAP AG representative.



For authorization checks in WM, the following objects can be assigned selectively for each user:


Transaction code in the Warehouse Management System


Warehouse numbers and storage types


Movement types in WM


Special functions in Warehouse Management

These authorization objects are assigned to the object class LE_L. You can view them by choosing Tools ® ABAP Workbench, Development ® Other tools ® Authorization objects ® Objects.

The objects S_ARCHIVE and S_DATASET pertain to archiving of WM data. Additionally, there are authorization objects for the ALE interface.

Transfer Order Processing

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:

  1. Check for warehouse number authorizations.
  2. 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 object L_SFUNC provides the authorization to call up automatic transfer order processing for material staging using the WM/PP interface and to execute repair programs.

For more detailed information about the WM authorization objects, see the Warehouse Management IMG documentation.

General Usage

Using the object L_TCODE you can limit access to certain Warehouse Management transactions.

All WM transactions begin with the letter "L". If you want to work with hazardous materials, you must also include transactions "VM01 to VM03" in your authorization concept.

Calling up the archiving programs is protected by the authorization group L_ARCH (attributes of the reorganization programs concerned). To activate the authorization, you need to add the value L_ARCH to the authorization object S_PROGRAM (system authorization).




Leaving content frame