Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
Basic Data
| Data Element | STORDAYS |
| Short Description | IS-M/SD: Number of Hold Days |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | STORDAYS | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| 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 | HoldDays |
| Medium | 15 | Hold Days |
| Long | 20 | No.Hold Days |
| Heading | 6 | HlDays |
Documentation
Definition
You can specify a minimum number of hold days to determine the length of each step in a monitoring procedure.
The next step in the monitoring procedure can only be reached after the hold days have elapsed.
By specifying hold days, you prevent the system from immediately running through all the steps that are "due" when the monitoring program is delayed (by an offset period).
If you do not specify hold days, this might mean that a customer is unintentionally sent several reminder letters at the same time.
Example
If an item reaches a step for which one hold day is specified on April 1st, the step for this item cannot be changed again until April 2nd.
If no value is maintained for the hold days, the step can change again on the day on which it is reached.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
