SAP ABAP Data Element ASYSANA (Exception active for 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 | ASYSANA |
Short Description | Exception active for 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 | Act.p.Anal |
Medium | 15 | Active f.per.A. |
Long | 29 | Active for periodic analysis |
Heading | 1 | P |
Documentation
Definition
Causes the system to create a periodic analysis for the exception.
Use
In a periodic analysis, the system checks the data that is selected as the area to analyze for exceptional situations at freely-definable intervals (hourly, weekly, daily, monthly).
If the exceptional situation occurs, the system automatically notifies the user via mail or fax, or workflow.
There are two types of periodic analysis:
- Event-driven
The search for exceptional situations is only triggered when the data has changed because an event (for example, sales order, purchase order, stock movement) has taken place. The system only checks those characteristics actually affected by this change.
- System-driven
The system checks all data selected as the area to analyze for exceptional situations.
History
Last changed by/on | SAP | 19950401 |
SAP Release Created in | 470 |