Collection of Consumption Data for Oracle Replenishment Planning

This topic discusses the collection of consumption inventory transactions or point-of-sale (POS) data from Oracle Fusion Inventory Management for the generation of consumption-based forecasts in Oracle Replenishment Planning.

To generate consumption-based forecasts for your replenishment plan, make these selections on the Collect Planning Data page:

• On the Parameters tab, for the Targeted collection type, under History Data Options on the Demand Planning Data tab, in Organization - Consumption Inventory Transactions to Include, select the types of consumption inventory transactions you want to collect at the organization level. If you select Transfer orders, historical transfer orders at the organization level are collected. If you select All, all historical consumption inventory transactions at the organization level are collected.

• In Subinventory - Consumption Inventory Transactions to Include, select the types of consumption inventory transactions you want to collect at the subinventory level. If you select Transfer orders, both historical transfer orders and historical movement requests at the subinventory level are collected. If you select All, all historical consumption inventory transactions at the subinventory level are collected.

Consumption-based forecasting provides you with these benefits:

• You can improve the effectiveness of your forecast by basing it on demand signals that are closest to your customers.

  Thereby, you can effectively compute your policy parameters and calculate and release your replenishment orders.

• In the retail and healthcare sectors, you can model stores and departments as subinventories. By collecting consumption inventory transactions at the subinventory level, you can generate forecasts at this level.

Historical Transaction Collections for Consumption-Based Forecasting at the Organization Level

When you select All in the Organization - Consumption Inventory Transactions to Include field, all historical transactions are collected at the organization level from Inventory Management for consumption-based forecasting except for those listed in this table:

Transaction Action	Transaction Source	Transaction Type
Issue from stores	Purchase Order	Return to Supplier
Issue from stores	Sales Order	Sales Order Issue
Issue from stores	Transfer Order Return	Transfer Order Return with Scrap

Item Transaction Collections for Consumption-Based Forecasting at the Subinventory Level

When you select All in the Subinventory - Consumption Inventory Transactions to Include field, all item transactions are collected at the subinventory level from Inventory Management for consumption-based forecasting except for those listed in this table:

Transaction Action	Transaction Source	Transaction Type
Direct organization transfer	Transfer Order Return	Transfer Order Return Transfer
Intransit shipment	Transfer Order Return	Transfer Order Return Shipment
Issue from stores	Purchase Order	Return to Supplier
Issue from stores	Transfer Order Return	Transfer Order Return with Scrap
Staging transfer	Transfer Order Return	Transfer Order Return Pick

Difference Between Consumption History and Shipments History

While shipments history includes the history for shipped sales orders, consumption history includes the shipments history as well as the consumption-related history that falls under transaction actions such as Issue from stores.

Measures for Storing Collected or Uploaded Consumption Data

If you're collecting consumption data from Inventory Management, the collected data is stored in the measure that you select in the Shipments History Measures field under History Measures and Attributes on the Demand Planning Data tab.

If you're uploading consumption data from an external source, use the file-based data import (FBDI) template named Supply Chain Planning Measures (ScpMeasuresImportTemplate.xlsm) to import consumption data into the predefined Consumption History measure.

In the import template, enter #ignore under the Customer Level Name and Demand Class Level Name columns if you don't want to specify these levels. Don't enter values in the columns for level member names.