Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-CBP (Application Component) Consumption-Based Planning (See Also PP-MRP)⤷
WRPL (Package) Retail: Replenishment
Basic Data
| Data Element | WRPLHZ |
| 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
Overall time for replenishing a material.
Use
Expected receipts and issues are taken into consideration for the entire replenishment lead time. The replenishment lead time is defined in the same way as in an ATP check based on the material master data.
If no logistics data exists for a material (for example, replenishment for customers), the time period entered by you is used as the replenishment lead time.
The following conditions are valid for the time period:
- The time period begins on the planning date and is always defined in days. Within this time period only the working days defined by the recipient's factory calendar are taken into consideration. If no factory calendar exists (for example, for customer replenishment), all days are considered.
The date on which you execute planning is considered as being in the past and therefore does not count for this time period.
- The system also assumes that the goods arrive in the morning of the last day. The last day is therefore only included in the calculation of planned receipts and issues (via ATP), and not in the sales forecast. This is why sales can only be forecast for a period of at least 2 days.
Example
You run the replenishment program on Tuesday evening of this week. The goods receipt for this run is posted on the Friday of the same week.
There is a period of four days between planning and goods receipt, but only two days are included in the calculation.
- Tuesday
Since the program is run in the evening, the day's consumption has already been deducted from the stock, and is not calculated as part of forecast sales.
The planned receipts and issues for the day are also already included in the stock figure, and are not included a second time.
- Wednesday
Forecast sales and planned receipts and issues are included in the calculation.
- Thursday
Same as Wednesday.
- Friday
The goods are received in the morning. The forecast sales and the planned receipts and issues for the day are therefore not included in the calculation.
Notes
The system considers all documents as expected receipts if they refer to a purchase order, for example purchase requisitions, purchase orders, delivery notifications, rough goods receipts and replenishment deliveries for stock transport orders (delivery type NL).
Deliveries with no document reference, for example, deliveries without reference (delivery type LO) and stock transport orders (type UL), are only considered as issues and not as receipts.
History
| Last changed by/on | SAP | 19990421 |
| SAP Release Created in |
