Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VA (Package) Application development R/3 Sales
Basic Data
| Data Element | PLAGD |
| Short Description | Validity period for delivery schedule split |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PRGUE | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | Validity |
| Medium | 15 | Validity period |
| Long | 20 | Validity period |
| Heading | 3 | Val |
Documentation
Definition
Specifies the period of time in weeks or months that the delivery schedule split is valid.
When generating a planning delivery schedule, the system uses the number of weeks or months that you enter here to determine the split validity end date, beginning from the base date. It takes the last day of this period as the validity end date. Note that the week or month of the base date is always counted as the first week or month.
When you enter 0, the system takes the week or month previous to the base date as the validity end date.
If no date type (week or month) has been specified for the split validity period, the system takes as the validity end date the last day of the period made up of the daily, weekly, and monthly schedule lines in the forecast delivery schedule.
Use
The system uses the delivery schedule split validity period to determine which schedule lines are to be included in (or excluded from) the planning delivery schedule:
- The system does not take into account schedule lines in the forecast delivery schedule whose dates lie completely after the validity end date.
- Daily schedule lines whose dates lie within the validity period are copied unchanged to the planning delivery schedule.
- Weekly and monthly schedule lines in the forecast delivery schedule whose dates lie within the validity period are split according to the split rule and copied to the planning delivery schedule.
A schedule line may contain dates that lie both within and without the validity period. In this case, the system splits the schedule lines, but includes in the planning delivery schedule only those generated schedule lines that lie on or before the validity end date. Generated schedule lines that lie after the validity end date are not taken into account.
A schedule line with no split rule is copied unchanged to the planning delivery schedule if at least one of its dates lies within the validity period.
When you select the adopt schedule lines indicator, the system adopts unchanged into the new planning delivery schedule those schedule lines in the previous planning delivery schedule whose dates lie completely after the validity period end date.
Example
The base date is 04/02/1998. This is a Thursday, week 14.1998.
If you set the delivery schedule validity period to 32 weeks, the system determines the last day of week 45.1998, or 11/08/1998, as the validity end date.
If you set the validity period to 7 months, the system determines the last day of month 10.1998, or 10/31/98, as the validity end date.
Caution
The splitting rule range specifies how long the delivery schedule splitting rule is valid.
The delivery schedule split validity period specifies the overall validity of the delivery schedule split.
Although both influence schedule line splits, the split validity period overrides the splitting rule range in every case.
For related information and an example illustrating how the split range and split validity period work together, see the delivery schedule splitting range.
History
| Last changed by/on | SAP | 19970812 |
| SAP Release Created in |
