You can organize BOM processing in your company to suit the way your company is structured. It is often the case that basic data that is relevant to all applications is created in a central department, then application-specific data is added using the change function.
You can structure authorizations to reflect your organization. The 4 authorization objects for defining access authorizations are assigned to object class Production planning.
The following authorization objects are defined for maintaining BOMs:
Checking Authorization Objects
The following table shows which functions check which authorization objects.
Function |
Authorization object |
Create BOM, change BOM |
C_STUE_BER (bill of material) C_STUE_WRK (plant) C_STUE_NOH (change without history) |
Mass changes |
C_STUE_MAS C_STUE_BER (bill of material) |
Archive BOM |
C_STUE_BER (bill of material) C_STUE_WRK (plant) |
Display BOM, BOM group, and plant allocation |
C_STUE_BER (bill of material) C_STUE_WRK (plant) |
BOM explosion, where-used list, BOM comparison |
C_STUE_BER (bill of material) |
Display change documents |
S_SCD0 (change documents) |
Variable lists for BOM explosions |
C_VARLIST (objects for variable lists) |
The documentation assumes that the user has unrestricted authorization for all functions.
Authorization Checks: Example