SAP ABAP IMG Activity GRFNVC_EVENTMETA (Define Event Definition)
Hierarchy
☛ GRCFND_A (Software Component) GRC Foundation ABAP
   ⤷ GRC-AC (Application Component) Access Control
     ⤷ GRAC_UTILITIES (Package) Access Control GRC Various helping infrastructure for ABAP
IMG Activity
ID GRFNVC_EVENTMETA Define Event Definition  
Transaction Code S_GF1_13000077   (empty) 
Created on 20100629    
Customizing Attributes GRFNVC_EVENTMETA   Define Event Definition 
Customizing Activity GRFNVC_EVENTMETA   Define Event Definition 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GRFNVC_EVENTMETA_DOC    

Use

In this Customizing activity, you can define the event definitions, which are then used at the time of receiving events through the integration framework.

The event definitions are used to identity different event sources, and to describe the metadata of the events. Only those events that follow the metadata format can further be processed by the integration framework.

Each event definition has a meaningful name, and is recognized by a combination of event type, partner, and version. It has the following attributes:

  • Processor
    Applications such as AMF, AC, and such others may need information about the incoming events. The processor indicates who should process events of the given event definition. The processor list is predefined and cannot be modified.
  • Check Type
    You can check the incoming events to ensure their validity. For this, a check method is provided with the following possibilities:
    • No Check: In this case, the detail structure is not checked at all.
    • Business Add-In (BAdI): The detail structure is checked using the BAdI (Business Add In program).
    • Item Detail Table: The detail structure is checked in accordance with the item table. For this check, it is assumed that the event detail is structured as name-value pairs. For each pair name, the cardinality and data type are required.
  • Event Fields
    The incoming events data is structured as name-value pairs. It describes the metadata of each name-value pair, including field ID, field type, length, cardinality, aggregation method, pattern, and description.

Requirements

Standard settings

Activities

Creating event types:

  1. Select Event Type from the dialog structure. The Event Type maintenance view appears.
  2. Choose New Entries to create the new event type.
  3. Enter the Event Type and the Event Type Name.
  4. Save trhe entry.
    If you want to change the event type information, select an existing entry and choose Change.

Creating partners:

  1. Select Partner from the dialog structure. The Partner maintenance view appears.
  2. Choose New Entries to create the new partner.
  3. Enter the Partner and the Partner Name.
  4. Enter e-mail address of partners in the E-Mail Address field. The e-mail address is used in the partner notification feature.
  5. Save the entry.
    If you want to change the partner information, select an existing entry and choose Change.

Creating versions:

  1. Select Event Version from the dialog structure. The Event Version maintenance view appears.
  2. Choose New Entries to create the new event version.
  3. Enter the Event Version and Version Text.
  4. Save the entry.
    If you want to change the version information, select an existing entry and choose Change.

Creating event definitions:

  1. Select Event Definition from the dialog structure. The Event Definition maintenance view appears.
  2. Choose New Entries to create the new event definition.
  3. Enter Event Type, Partner, and Version.
  4. Choose Processor and Check Type, and enter the Name.
  5. Save the entry.
  6. Select the created entry, and select from the dialog structure. The Event Fields maintenance view appears.
  7. Choose New Entries to create the fields.
  8. Enter the ID, field type, and cardinality. You must select Aggregation Method if the cardinality is 0..N or 1..N.
  9. Save the entry.
    If you want to change the event definition information, select an existing entry and choose Change.

Example

Business Attributes
ASAP Roadmap ID 201   Make global settings 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
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
GRFNVC_EVENTMETA C - View cluster SM34  
History
Last changed by/on SAP  20100629 
SAP Release Created in 600