Ansicht
Dokumentation
EHENV_SCEN - Environment Management Scenario
Vendor Master (General Section) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Definition
You use this authorization object to control the access to environment management scenarios in Environment, Health, and Safety depending on the scenario location.
Defined fields
The following table contains the fields for the authorization object and their possible values:
| Field | Possible Values | Description |
|---|---|---|
| ACTVT | - | Activity |
| 03 | Display | |
| 06 | Delete | |
| 23 | Maintain | |
| 76 | Enter | |
| 94 | Override | |
| LOCTYPE | - | Location type (depends on the corresponding Customizing activity: Specify Location Types). The following values are delivered by default. |
| Business Unit | Business Unit | |
| Company | Company | |
| Equipment | Equipment | |
| Production Unit | Production Unit | |
| Site | Site | |
| Storage Location | Storage Location | |
| Work Center | Work Center | |
| LOCSTATUS | - | Location Status |
| 01 | New | |
| 02 | Active | |
| 03 | Inactive | |
| 04 | Historic | |
| LOCAUTHGRP | - | Location authorization group. Depends on the corresponding Customizing activity:Specify Authorization Groups. |
| Unrestricted Access | Standard delivery value | |
| LOCPLANT | - | Plant ID; depends on the corresponding table for plants T001W: Plants/Branches. |
| LOCCOST | - | Cost center; depends on the corresponding table for cost centers CSKS: Cost Center Master Record. |
| LOCCOMP | - | Company code; depends on the corresponding table for company codes T001. |
| LOCBUSAREA | - | Business area; depends on the corresponding table for business areas TGSB. |
| LOCCOUNTRY | - | Country code. Depends on the corresponding table for countries T005: Countries. |
| LOCREGION | - | Region; depends on the corresponding table for regions T005S. |
The field ACTVT controls the activities of the user.
- Activity 06 (Delete), enables the configured user to delete environmental data and compliance scenario activities (data collections, calculations, samplings, and so on).
- Note that, when you want to delete activities and compliance scenarios, the system first checks whether there is recorded environmental data in the compliance scenario activities, and then performs the authorization check. This means that the system allows users who are not configured with activity 06 (Delete) to delete empty compliance scenario activities and empty compliance scenarios.
- Activity 76 (Enter) controls the access of the environmental technician to pending data collections.
- This activity must be enabled for users with the role environmental technician. Otherwise, they cannot enter environmental data into the system and hence process pending data collections.
- Activity 94 (Override) enables the configured user to take action on environmental data (add, replace, invalidate, or approve it). The user is not authorized to manage compliance scenarios.
- The non-mandatory fields LOCTYPE, LOCSTATUS, LOCAUTHGRP, LOCPLANT, LOCCOST, LOCCOMP, LOCBUSAREA, LOCCOUNTRY, and LOCREGION are used to specify the compliance scenario depending on the additional details of its location. For each role that uses the EHENV_SCEN authorization object you can define the following in the authorization data:
- If the user is authorized to manage compliance scenarios that are assigned to locations with specific details only, specify the concrete values in the corresponding fields of the authorization object.
- If the user is authorized to manage compliance scenarios that are assigned to locations with any details, specify an asterisk (*) in the corresponding fields of the authorization object.
- If the user is authorized to manage compliance scenarios that are assigned to locations without any details, specify an empty string ('') in the corresponding fields of the authorization object.
- Note that you are not allowed to specify an empty string for the non-mandatory field LOCAUTHGRP. Therefore, if the user is authorized to manage compliance scenarios that are assigned to locations without set LOCAUTHGRP, specify a new authorization object separately and ommit any entries in that field.
ABAP Short Reference ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 9826 Date: 20240523 Time: 044825 sap01-206 ( 89 ms )
