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 | MDRD_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 | MDRD_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 receiving MRP areas should be determined explicitly to find alternative historical data (AHD), and also controls the way in which the receiving MRP areas are determined.
The delivery relationship states which recipients are supplied with a certain material by an MRP area. It only makes sense to maintain a profile in a scenario in which the forecast in the MRP area is created on the basis of receiving MRP areas, and it is necessary to limit the supplied MRP areas (Post Distribution Forecasting = PDF). PDF scenarios that do not determine the delivery relationship explicitly are, however, also possible if the delivery relationship is given implicitly. Examples of a delivery relationship that is given implicitly are:
- The requirement quantities from stock transport orders are already aggregated at issuing MRP area level when they are updated to SAP BW (implicit delivery relationship).
- The requirement quantities from stock transport orders are updated in SAP BW at receiving MRP area level, but they are accessed using the issuing MRP area (implicit delivery relationship).
Always choose this kind of scenario if you do not expect any changes in the delivery relationship that are significant for creating the alternative historical data. The forecast on the basis of material consumption does not enable subsequent correction if the delivery relationship changes either.
The determination of the delivery relationship is a runtime-intensive process. To avoid problems with runtime, note the following:
- The explicit determination of delivery relationships should be avoided completely if possible (see PDF scenarios without explicit determination of the delivery relationship).
- If explicit determination is required, it should be carried out at MRP area or material group level whenever possible. Determination at material level should only be chosen if absolutely necessary.
- The method for determination and the scope of the checks should be kept as small as possible if determination at material level has been set.
- If there is a simple delivery relationship but it cannot be mapped simply using the methods and checks provided, the delivery relationship should be determined using a customer-specific logic (rule-based or customer-specific table). To do this, use the BAdI method EX_BADI_MDRD_001.
- Another way of avoiding high volumes of data and improving program runtime is to use references. The delivery relationship is determined and saved for a small number of MRP areas/materials. Other MRP areas/materials then reference this data. Referencing is possible using the method EX_BADI_MDRD_005.
- Delivery relationships should only be redetermined if required (that is, if there are significant changes to the existing delivery relationship) and should not be redetermined for a large amount of data at the same time. Otherwise, the delivery relationships saved after one determination should be used for the forecast.
You define the profile for determining the delivery relationship in Customizing.
History
| Last changed by/on | SAP | 20050428 |
| SAP Release Created in | 600 |
