Authorization Objects

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_470/helpdata/en/ea/e9b0054c7211d189520000e829fbbd/content.htm

Created on November 15, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 4
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Table of content
1 Authorization Objects
1.1 Authorization Checks: Example
1.2 General Authorization Object for Processing BOMs
1.3 Authorization Object for BOM Plant
1.4 Authorization to Process BOM Without Change Number
1.5 Authorization Object for Mass Changes
1.6 Authorization Object for Variable Lists

PUBLIC Page 2 of 4
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1 Authorization Objects
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:

General Authorization Object for Processing BOMs

Authorization Object for BOM Plant
Authorization to Process BOM Without Change Number
Authorization Object for Mass Changes
Authorization Object for Variable Lists

Checking Authorization Objects

The following table shows which functions check which authorization objects.

Function Authorization object

Create BOM, C_STUE_BER (bill of material)

change BOM 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, C_STUE_BER (bill of material)

BOM group, and plant allocation C_STUE_WRK (plant)

BOM explosion, C_STUE_BER (bill of material)

where-used list,
BOM comparison

Display change documents S_SCD0

(change documents)

Variable lists for C_VARLIST

BOM explosions (objects for variable lists)

The documentation assumes that the user has unrestricted authorization for all functions.

Authorization Checks: Example

1.1 Authorization Checks: Example

The authorization object BOM plant (plant allocation) is defined for two users. Both have the value 01 (create and allocate) entered in the Activity field.
However, they have different values for the Plant .
User A
has the values 0001, 0002, and 0003.
User B
has the value 0001.
If these two users want to extend the area of validity of a BOM in plant 0001 to include plants 0002 and 0003, the difference takes effect. User A is allowed to
make this allocation. User B is not authorized to create BOMs in plants 0002 and 0003, so User B cannot make the allocation.

Additional authorization checks are carried out for engineering change management, document management, and other related application areas.
For more detailed information, see the documentation on the individual application concerned.

1.2 General Authorization Object for Processing BOMs

This authorization object allows you to restrict access to BOM maintenance functions. When you try to start a BOM function, the program checks this
authorization object. If a change is made to the authorization object while you are processing a BOM, another check is made automatically.
Fields in Authorization Object C_STUE_BER

Fields Possible values Description

ACTVT 01 Create
(activity) 02 Change
03 Display
06 Delete
24 Create archive file
41 Delete from database

STLTY M Material BOM

(BOM category) E Equipment BOM
D Document structure
K Order BOM

PUBLIC Page 3 of 4
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 S Standard BOM
T Functional location BOM

STLAN These field values are defined in Customizing.

(BOM usage)

BEGRU 0000-ZZZZ Used to further restrict authorizations for BOM

(authorization group) maintenance (BOM header)

1.3 Authorization Object for BOM Plant

This authorization object allows you to protect the allocation of a BOM to a plant.
Fields in Authorization Object C_STUE_WRK

Fields Possible values Description

ACTVT 01 Create
(activity) 02 Change
03 Display

CSWRK Enter the plant where the activity can be performed.

(BOM plant)

STLAN These field values are defined in Customizing.

(BOM usage)

1.4 Authorization to Process BOM Without Change Number

Authorization object C_STUE_NOH lets you maintain a BOM that has a history requirement without a change number.
The authorization object contains field NOHIS (authorization to change BOMs without a change number). To assign this authorization, enter X.

Only assign authorization object C_STUE_NOH in exceptional situations, because this authorization means that changes to BOMs will no longer
be fully documented.

1.5 Authorization Object for Mass Changes

Authorization object C_STUE_MAS determines whether you can make mass changes to bills of material. This authorization object is checked when you call
the mass change function.
The authorization object contains field ACTVT (activity). You enter the value 16 (execute) in this field.

1.6 Authorization Object for Variable Lists

This authorization object lets you restrict maintenance of the following objects in variable lists:
List name
Profile
Maximum block
Display block
For BOM reporting functions, you can define company-specific variable lists for on-screen display and printouts.
Fields in Authorization Object C_VARLIST

Fields Possible values Description

ACTVT 01 Create
(activity) 02 Change
03 Display
16 Execute (use of profile in reporting lists)
Transfer list name
21

BEGRU 0000-ZZZZ Used to further restrict maintenance authorizations

(authorization group)

PUBLIC Page 4 of 4
© 2014 SAP SE or an SAP affiliate company. All rights reserved.