Hierarchy
⤷ IS-A (Application Component) Industry Solution Automotive
⤷ DIMP_MOVE_FROM_CORE_PACK (Package) Common DIMP objects, which were formerly in core
Basic Data
Data Element | CALLSPAN |
Short Description | Call object for a specific period n (such as n days) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC10 | |
Data Type | NUMC | Character string with only digits |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
With this parameter you control for which time period the system generates call objects for waiting calls.
Note
It is important that the call interval in the scheduling parameter of the maintenance plan is larger or at least the same size as the time period entered here!
For the calculation of the until date (date until which the call object can be generated) is always the system date of the report run. The given time period is added to the system date of the report run. For all waiting maintenance calls, whose call date lies in this period, the system generates the maintenance call object.
Example
Call object for time period n: 14
Unit of the time period: days
Report run on: 01.01.XX
The system generates until 15.01.XX for the waiting call object.
If you are working with a call horizon of 100% and you regularly run the deadline monitoring, you can use this parameter to control for how many days you need your call object to be generated for. This means if n-days = 14, then the system generated the call object 14 days before the planned date.
History
Last changed by/on | SAP | 20050301 |
SAP Release Created in | 46C |