SAP ABAP IMG Activity GRPC_MAINVERSION (Maintain Event Version)
Hierarchy
☛
GRCFND_A (Software Component) GRC Foundation ABAP
⤷
GRC-SPC (Application Component) Process Controls
⤷
GRPC_CUSTOMIZING (Package) Customizing

⤷

⤷

IMG Activity
ID | GRPC_MAINVERSION | Maintain Event Version |
Transaction Code | S_GR4_71000049 | (empty) |
Created on | 20081203 | |
Customizing Attributes | GRPC_MAINVERSION | Maintain Event Version |
Customizing Activity | GRPC_MAINVERSION | Maintain Event Version |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | GRPC_MAINVERSION |
Use
In this Customizing activity, you define the event version. The version refers to metadata describing the event. This metadata is used by the GRPC_EVENT_RECEIVE Web Service.
Only events with a version can be accepted and further processed by the Event Monitoring functionality.
Requirements
The Version uses the Event Type and Partner, so you have to prepare them first.
In Process Control, the Event Type is the rule name. Therefore, the event is identified with the corresponding rule by the Event Type.
Standard settings
The event is identified by the version number. For each version, define the corresponding Event Type and Partner.
For each version, you must define how the Format Check Type is executed. Choose one of the following options:
- No check – The detail structure is not checked at all.
- BAdI – The detail structure is checked via the BAdI (an ABAP program).
- Item detail table – The detail structure is checked based on the item table. For this check, it is assumed that the event detail is structured as name-value pars. For each pair name, the cardinality and data type are required.
Based on the data type, there are also some additional parameters needed. Cardinality provides for all possible combinations. You can define cardinality as: 0...1, 0...N, 1...1, 1...N. However, there is no explicit way to define N.
The data types are listed below: - Any - This allows any value
- String - Any text, its length can be limited. The max length is established in LENGTH.
- Character - Text with fixed length. The length is established in LENGTH.
- Date - The date according to the XML standard. The format is YYYY-MM-DD.
- Time - The time according to the XML standard. The format is HH:MM:SS.
- Integer - An integer, including the +/- sign.
- NUMC - A numeric character with a fixed length. The length is established in LENGTH.
- Pattern - The pattern according to the SAP pattern defined for CP (ABAP statement Covers Pattern). This pattern is stored in PATTERN.
Activities
- Enter the version number in the Frmt Version field. Define the Format Check Type according to the option detailed above. Provide a description in the Text field.
- Select a line and then select the Event Types and Partners folder. Provide Event Type and Partner information (use F4 help, if needed).
- If the Item detail table structure check is selected for the Format Check Type, select the Field details folder. Provide the required entries according to the description above. For example, you must provide the Field Name and Cardinality.
Example
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
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 | GRPC_MAINVERSION | 0 | GR11000001 | Process Controls |
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 |
VC_GRPC_VERSION | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20081217 |
SAP Release Created in | 300 |