SAP ABAP Data Element AEVENT (Event-driven periodic analysis)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCY (Package) Application development R/3 Early Warning System LIS
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCY (Package) Application development R/3 Early Warning System LIS
Basic Data
Data Element | AEVENT |
Short Description | Event-driven periodic analysis |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Event |
Medium | 17 | Event-driven |
Long | 24 | Event-driven |
Heading | 50 | Event-driven reporting |
Documentation
Definition
Causes the periodic analysis to be event-driven.
Use
The selected dataset is analyzed for exception situations in a time frame that can be self-defined.
If an exception situation occurs, you will be automatically notified by system mail or work flow.
In contrast to the system-driven periodic analysis, searching for exception situations is only triggered when there is a change in the data as a result of an event (for example, sales order, purchase order, stock movement). The system then only analyzes those characteristics where there was an actual change.
Procedure
If you want to execute the periodic analysis by event, select the field.
History
Last changed by/on | SAP | 19950411 |
SAP Release Created in | 470 |