Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
MM-CBP (Application Component) Consumption-Based Planning (See Also PP-MRP)⤷
WSRP (Package) Retail: Store Replenishment
Basic Data
| Data Element | WSRP_PLHZ |
| Short Description | Replenishment Lead Time |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PERAN | |
| Data Type | DEC | Counter or amount field with comma and sign |
| 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 | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
Total amount of time taken to replenish a material.
Use
The planned issues and receipts are taken into consideration for the duration of the replenishment lead time. In the case of an ATP check (ATP = Available to promise), the replenishment lead time is determined from the material master data.
If there is no logistics data for a material (for example, for replenishment for customers), the time period you enter is used as the replenishment lead time.
The following conditions apply for the time period:
- The time period begins with the Planning Date and is always given in days. Only the working days within this period as defined by the factory calendar for the store are taken into consideration.
- The current day on which you carry out the planning is considered as being completely in the past and is therefore not counted in this time period.
- It is assumed that the goods arrive on the morning of the last day of this time period. The last day is therefore only included when determining the planned issues and receipts (using ATP), however, not when forecasting sales. A forecast is therefore only possible for a time period of at least two days.
Example
You start replenishment planning on the Tuesday evening of the current week. The goods receipt for this planning is on the Friday of the current week.
This therefore makes a time period of four days, however, only two of these are counted in the calculation:
- Tuesday
- As planning takes place in the evening, the consumption for this day has already been subtracted from the stock and is therefore not counted as forecast sales.
- The planned issues and receipts for this day have also already been added to the stock and are therefore not considered separately.
- Wednesday
- The forecast sales and the planned issues and receipts are entered into the calculation.
- Thursday
- Same as Wednesday.
- Friday
- Goods receipt takes place in the morning. The forecast sales and the planned issues and receipts for this day are therefore not included in the calculation.
Notes
All documents connected with a purchase order are considered as planned receipts. These include purchase requisitions, purchase orders, shipping notifications, rough goods receipts and replenishment deliveries for stock transport orders (delivery type "NL").
Deliveries that do not have any reference to a document, such as deliveries without reference (delivery type "LO") and stock transport deliveries (delivery type"UL"), are only considered as issues, however, not as receipts.
Dependencies
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in | 110 |
