Hierarchy
⤷ IS-U-EDM (Application Component) Energy Data Management
⤷ EE_DATEX (Package) Data Exchange at Point of Delivery Level
Basic Data
Data Element | E_DEXSCHEDTYPE |
Short Description | Schedule Data Exchange Process |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | E_DEXSCHEDTYPE | |
Data Type | NUMC | Character string with only digits |
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 | Schedule |
Medium | 15 | Schedule Proc. |
Long | 20 | Schedule Process |
Heading | 9 | Schedule |
Documentation
Definition
You can define whether the execution of a data exchange process can be scheduled.
When you schedule data exchange processes, you have the following options:
- No scheduling
The application determines when the process is executed. The due date for process execution for each point of delivery cannot be determined and monitored in advance. Process execution and data communication occur simultaneously and are both logged.
- Schedule asynchronous data sending
The application determines when the process is executed. Outbound messages are send sent at the due date independently of the process execution. The due date of execution for each point of delivery cannot be determined in advance.
- Schedule process execution
Process execution can be detached from the application and is scheduled in advance for each point of delivery. Scheduled export data processes are executed for the relevant points of delivery at the due date. In the case of import data processes, the system monitors the completeness of process execution for all the relevant points of delivery.
Dependencies
The category in the definition of the basic process defines whether the implementation lets you schedule the execution of a given data exchange process can be scheduled.
Example
- The sending of profiles from distributors to suppliers is an export data exchange process whose due dates can be scheduled for each point of delivery.
- The receipt of profiles from an automated meter reading system (AMR) is an import data exchange process whose due dates can be scheduled for each point of delivery. This ensures that the completeness of the data exchange can be verified at any time.
- Changes to master data is an IDE event that is not scheduled. The changes to the data are directly communicated to other market players.
- The sending of a customer switch notification is triggered by the application. However, depending on the communication partner the data can be exchange at a fixed date (such as the 15th of the month).
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 464 |