Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-CBP (Application Component) Consumption-Based Planning (See Also PP-MRP)⤷
WEFF (Package) Retail: Extended Forecast Functions
Basic Data
| Data Element | WDRD_DRDPRF |
| Short Description | Profile for Determining Delivery Relationship |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WDRD_DRDPRF | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | TWDRD |
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 | DRDProfile |
| Medium | 15 | DRD Profile |
| Long | 28 | Deliv. Relationship Profile |
| Heading | 13 | DRD Profile |
Documentation
Definition
The profile for determining the delivery relationship controls whether explicit determination of receiving plants and/or customers is to be carried out for the determination of alternative historical data (AHD), and how the recipient is to be determined.
The delivery relationship tells you which recipients (plants and/or customers) are to be supplied with a material from a specific plant. It only makes sense to maintain such a profile in a scenario, in which theforecast in the distribution center is created on the basis of store and/or customer requirements and it is necessary to limit the receiving plants and/or customers (Post Distribution Forecasting = PDF). PDF scenarios without explicit determination of the delivery relationship are also possible, however, if the delivery relationship is specified implicitly. Examples of implicit delivery relationships are:
- The requirement quantities from stock transport orders or sales orders are aggregated during the update in SAP BW at the level of the issuing plant (implicit delivery relationship).
- The requirement quantities from stock transport orders or sales orders are updated in SAP BW at the level of the receiving plants or customers, but access takes place over the issuing plant (implicit delivery relationship).
- The POS sales quantities for the stores are aggregated at the level of the supplying plant during update in SAP BW. To do this, information is needed about the delivery relationship.
You should always select such a scenario when no changes in the delivery relationship are expected that are significant to structuring the alternative historical data. The forecast based on material consumption (MVER) also gives you the option of making corrections if the delivery relationship is changed.
Determination of the delivery relationship is a performance- and time-intensive process. To avoid runtime bottlenecks, please observe the following points:
- Explicit determination of the delivery relationship should be omitted completely, if possible (see PDF scenarios without explicit determination of the delivery relationship).
- If explicit determination is necessary, it should be carried out at plant or material group level where possible. Determination should only be selected at material level if absolutely necessary.
- If determination is set at material level, the method of determination and the scope of the checks should be kept as small as possible.
- If a simple delivery relationship exists, but it cannot be represented in a simple way using the methods and checks provided, the delivery relationship should be determined using a customer-defined logic (rules-based or customer-defined tables). A customer exit will be provided for this.
- Another way to reduce data volume and improve program runtime is to use references. This involves determining and saving the delivery relationship for a few plant/material combinations. Other plants/materials refer to this data. Such referencing is possible using a customer exit.
- You should only redetermine the delivery relationship when needed (when there are significant changes to the existing delivery relationship) and not run it for too large a data volume at one time. Otherwise, use the delivery relationship that has been determined once and saved, for the forecast.
The profile for determining the delivery relationship is defined in customizing.
History
| Last changed by/on | SAP | 20050428 |
| SAP Release Created in | 110 |
