Receipts-Based Forecasting

You can generate a receipts-based forecast after collecting historical receipt transactions from Oracle Fusion Cloud Inventory Management and use this forecast for periodic automated replenishment (PAR).

Note these points about receipts-based forecasting:

  • A healthcare supply chain typically has several inventory locations where PAR is done. At these locations, while inventory isn't tracked, receipt transactions are tracked.

    Therefore, for accurately forecasting demand at these PAR locations, receipts are used as a substitute for usage or consumption information.

  • You can use the predefined forecasting profile named Forecast Receipts for receipts-based forecasting.

    This forecasting profile is optimized for situations where demand needs to be smoothened because receipts are intermittent. All the forecasting methods for intermittent forecasting are enabled for this forecasting profile so that the typically irregular occurrence of receipts can be accounted for. The use of this forecasting profile results in acceptable mean absolute percentage error (MAPE) values.

  • You can use the receipts-based forecast in your replenishment plan through which you're calculating PAR policies.

    You can either configure a demand plan with the Forecast Receipts forecasting profile and then provide this demand plan as a demand schedule to the replenishment plan. Or, you can directly compute the forecast in the replenishment plan using the Forecast Receipts forecasting profile.

  • You can collect receipt-based transactions from Oracle Inventory Management using the guided process for collecting planning data.

    In the Demand data step, in the section for collecting receipts history, you can select the Collect receipts history for organizations and Collect receipts history for subinventories checkboxes.

  • Several measures have been introduced for receipt-based forecasting, and they're contained in the predefined measure group named Receipts-Based Forecasting.

    Some measures are as follows:

    • Adjusted Receipts Forecast: This editable measure contains your override of the value in the Receipts Forecast measure. The override value is presented as a quantity.
    • Adjusted Receipts Forecast Percentage: This editable measure contains your override of the value in the Receipts Forecast measure. The override value is presented as a percentage.
    • Final Receipts Forecast: This calculated measure contains the final receipts-based forecast after accounting for user overrides. Otherwise, the value of the Receipts Forecast measure is returned. The value in the Final Receipts Forecast measure is presented as a quantity.
    • Receipts Forecast MAD: This measure contains the mean absolute deviation (MAD) associated with the receipts-based forecast.
    • Receipts Forecast MAPE: This measure contains the MAPE associated with the receipts-based forecast.
    • Receipts Forecast Bias: This measure contains the statistical bias associated with the receipts-based forecast.

    You must ensure that these measures are in the measure catalog for your demand plan or the replenishment plan that you use for generating the forecast.

  • The Receipts History measure has the Customer, Demand Class, Organization, Product, Sales Representative, and Time dimensions. However, the receipts collected from Oracle Inventory Management aren't associated with customer sites or demand classes. Therefore, for the collected receipts, the customer site and demand class levels are populated with –1 and appear as unassigned in tables and graphs.