Hierarchy

⤷

⤷

IMG Activity
ID | CF_OLPSCC_V_TC81 | Define authorization group |
Transaction Code | S_ALR_87003822 | IMG Activity: CF_OLPSCC_V_TC81 |
Created on | 19981222 | |
Customizing Attributes | CF_OLPSCC_V_TC81 | Define authorization group |
Customizing Activity | CF_OLPSCC_V_TC81 | Define authorization group |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CF_OLPSCC_V_TC81 |
You define the authorization groups for the digital signatures in this work step.
You can use the authorization groups to help you restrict the authorizations for approving ECR/ECOs as follows:
- You define different authorization groups for users who work in different task areas.
- In the user master record, allocate each user with the correct authorization for the authorization group that corresponds to his/her task area (authorization object: C_SIGN_BGR).
- Define single signatures that have to be entered by users in a specific user group and are used in the signature strategies for the change types of an ECR/ECO.
The authorization groups are not taken into account if, in the ECR/ECO, a single signature suffices to approve which system status is set and a signature strategy is not required.
Example
Release of the change order and also release of the object changes (for example, BOM changes) must be approved in your company. You must make the followoing settings for this:
- Define the authorization groups FECM (Release change master record) and FECO (Release object).
- The boss of production and his/her replacement receive an authorization for the group FECM, the engineering/design boss and his/her replacement for the group FECM.
- Define a single signature for the approval of the object change Allocate this to the authorization group FECO.
Requirements
Standard settings
Recommendation
Activities
- Decide which user groups or task areas you have to be able to distinguish between in your company.
- Define an authorization group for each user group.
Further notes
Authorization groups take effect in all areas where a digital signature is used. Before you change the authorization groups available, or use them for your own requirements, please check that any the changes you make do not cause problems in other areas.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | CF_OLPSCC_V_TC81 | 0 | ABA0000132 | Engineering Change Management |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V_TC81 | V - View | SM30 | LO-ECH | Define authorization group |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |