Ansicht
Dokumentation
/MAP/EVOCC - MAP: Authorization for Event Occurrence
ABAP Short Reference ABAP Short ReferenceThis documentation is copyright by SAP AG.
Definition
Authorization at the level of the event occurrence. This authorization object is checked when changes are made to an event occurrence or to the dimensions assigned to the event in event processing.
See also:
Authorization object /MAP/EVASS
As an alternative to using the standard functions for the authorization check with objects /MAP/EVOCC and /MAP/EVASS, you can implement customer-specific logic for the authorization check using the BAdI /MAP/E_AUTH. You can decide which type of authorization check to use (authorization object or BAdI) for each event.
Defined fields
The object has the following fields:
- ACTVT: Activity
- The following activities are permitted:
- 01: Creation of event occurrence. The creation of an event occurrence includes all changes to this occurrence up to when it is posted.
- 02: Change of event occurrences (that have already been posted)
- The insertion or deletion of values of an assigned event dimension is a change to the event occurrence. For this reason, the system also checks the authorization at the level of the event occurrence using activity 02. Excluded from this are event occurrences that have not yet been posted. In this case, the system checks the authorization using activity '01'.
- 06: Deletion of event occurrences (that have already been posted)
- /MAP/EVID: Event key
- The permitted values are found in the table /MAP/E_EVENT.
- /MAP/PSTOC: "Past Event Occurrences" indicator
- Changing a past event occurrence at a later date is a critical operation, because it usually requires new model training.
- The following values are possible for the check that follows:
- SPACE: Event occurrence is completely in the future.
- 'S': Start date of event occurrence is in the past, but the end date is not.
- 'B': Event occurrence is completely in past.
- 'I': Start and end date of event occurrence are initial (Date '00.00.0000'). The event occurrence does not take place.
The change to the start or end date of an event occurrence leads to two authorization checks:
- The old start and end date can be changed.
- The new start and end date can be changed.
The system only makes the change when both authorization checks are successful.
PERFORM Short Reference rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 3150 Date: 20240329 Time: 170217 sap01-206 ( 36 ms )