Show TOC

Function documentationFixed Demands and Fixed Receipts

 

Distribution requirements planning (DRP) considers fixed demands and fixed receipts as well as forecasted demands and stocks to be able to plan replenishment within a bill of distribution (BOD).

Fixed demands are not a part of the regular forecast. Fixed demands are purchase documents that you have created on the basis of specific knowledge, such as marketing promotions. In these documents you can specify which product is required in which quantity and at which location.

Fixed receipts are certain product quantities that come into your BOD but not as a direct response to purchase orders or scheduling agreement releases.

Note Note

If you create a fixed demand and a fixed receipt that occurs in the future, you can simulate removing goods and later stocking them for quality inspection purposes.

End of the note.

Prerequisites

You have created reason codes for fixed demands and fixed receipts in Customizing for Advanced Planning and Optimization under Start of the navigation path Supply Chain Planning Next navigation step Service Parts Planning (SPP) Next navigation step Distribution Requirements Planning (DRP) Next navigation step Define Reason Code for Fixed Demands End of the navigation path. For more information, see the relevant Customizing documentation.

Features

Creating and Changing Fixed Demands and Receipts

For creating fixed demands and fixed receipts you proceed in the same manner, meaning that you create a fixed demand with a positive value for each. You only differentiate a fixed receipt from a fixed demand by setting the Negative Ind. indicator.

To create a fixed demand or fixed receipt you specify the relevant product or location product, choose the Insert pushbutton, and define the fixed demand or fixed receipt as follows:

  • You specify the time from and until when the fixed demand or fixed receipt is valid.

  • You specify one of the reason codes that you defined in Customizing.

    Note Note

    In Customizing for Deployment, you can define that Deployment does not consider fixed demands or fixed receipts with a certain reason code at the parent location. For more information, see Customizing for Advanced Planning and Optimization, under Start of the navigation path Supply Chain Planning Next navigation step Service Parts Planning (SPP) Next navigation step Deployment Next navigation step Define Fixed Demands that Push Deployment Does Not Consider at Parent Loc. End of the navigation path.

    End of the note.

  • You specify whether the quantity of the fixed demand or fixed receipt is reduced by ramping.

    If you set the Ramping indicator and the start date of the fixed demand or fixed receipt is in the past, the system reduces the quantity of the fixed demand or fixed receipt by ramping, meaning in several steps. In this case, the system reduces the quantity of the fixed demand or fixed receipt according to the following formula:

For more information about planning horizons, see DRP Horizons.

  • You can prioritize certain fixed demands. Deployment then treats these fixed demands as prioritized fixed demands during demand fulfillment according to priority tiers. You can also assign a priority value to the fixed demands. If deployment cannot cover all prioritized fixed demands, it proceeds according to the priority values defined here during demand fulfillment, for example by covering all fixed demands with priority value one first. If deployment cannot cover all prioritized fixed demands with a certain priority value, it sorts the fixed demands with this priority value and fulfils the prioritized fixed demand with the earliest start date first.

  • You can exclude certain fixed demands and fixed receipts from push or pull deployment. You can specify this for each fixed demand or fixed receipt in the Deployment Type field.

    • If you choose the PUSH OR PULL entry, the system considers the fixed demand or fixed receipt as part of both push and pull deployment.

    • If you choose the PUSH ONLY entry, the system only considers the fixed demand or fixed receipt as part of push deployment, and not as part of pull deployment. This exclusion is only valid up to the time that you have specified in the Depl. Type Date and Depl. Type Time fields.

    • If you choose the PULL ONLY entry, the system only considers the fixed demand or fixed receipt as part of pull deployment, and not as part of push deployment. This exclusion is only valid up to the time that you have specified in the Depl. Type Date and Depl. Type Time fields.

      Note Note

      For the system to exclude a fixed demand or fixed receipt during deployment, the date in the Depl. Type Date and Depl. Type Time fields must lie after the start date of the fixed demand. If you have not made any entry in the Depl. Type Date and Depl. Type Time fields, the exclusion you defined in the Deployment Type field is valid for the entire validity period of the fixed demand or fixed receipt.

      End of the note.

Displaying Fixed Demands and Fixed Receipts

You can see fixed demands and fixed receipts in the DRP matrix. The system displays fixed demands and fixed receipts in the column of their start date. If the start date has already passed, the system displays them in the Overdue column. If the end date has passed, the system no longer displays the fixed demand or fixed receipt.

In the DRP matrix the system differentiates between the following types of fixed demands:

  • Prioritized Fixed Demand (Non-Overriding)

    Non-Overriding means that the fixed demand does not overwrite the forecast values.

    Example Example

    The forecast value for location product X for June 6th, 2005 is 20. One of your fixed demands for location product X for June 6th, 2005 is 50.

    In the non-overriding mode DRP plans the demand for June 6th, 2005 as 70 pieces.

    In the overriding mode, DRP would plan a demand of 50 pieces because in this case the fixed demand overwrites the forecast result. The system also overrides further forecasted demands of the remaining 30 pieces in the following periods.

    End of the example.

    Example Example

    The following table illustrates the way the fixed demand (overriding) influences the forecasted demands of the following periods.

    Date

    Forecast

    Fixed Demand (Overriding)

    Gross Demand

    Final Forecast

    05. June

    20

    20

    20

    06. June

    20

    50

    50

    07. June

    20

    08. June

    20

    10

    10

    09. June

    20

    20

    20

    On June 6th, DRP plans with a gross demand of 50, as the fixed demand is in the overriding mode, and the fixed demand of 50 pieces overwrites the forecast of 20. The difference between 50 and 20 is 30, which means that there are still 30 forecasted pieces that are to be overwritten by the fixed demand of 50. For this reason, on June 7th, the forecast of 20 is completely consumed by the fixed demand of 50 (from June 6th). On June 8th, 10 of the 20 forecasted pieces are consumed.

    End of the example.

  • Non-Prioritized Fixed Demand (Non-Overriding)

  • Non-Prioritized Fixed Demand (Overriding)

Activities

You can create and change fixed demands and fixed receipts from the SAP Easy Access screen under Start of the navigation path Advanced Planning and Optimization Next navigation step Service Parts Planning (SPP) Next navigation step Distribution Requirements Planning (DRP) Next navigation step Fixed Demands and Fixed Receipts End of the navigation path.

You can display fixed demands and fixed receipts from the SAP Easy Access screen under Start of the navigation path Advanced Planning and Optimization Next navigation step Service Parts Planning (SPP) Next navigation step Distribution Requirements Planning (DRP) Next navigation step DRP Matrix End of the navigation path .