Sales Pack Data
If you have pack items (sets of SKUs or multiple units of SKUs sold as one item) then you will need to spread sales of
such items from the pack item level to the individual component SKU level. The interface file SALES_PACK.csv is provided to load component sales values at a summary level of item/location/date. This data is included in sales calculations
for both AI Foundation and Planning applications by adding together the sales of SKUs sold individually on SALES.csv and the sales of items inside packs on SALES_PACK.csv.
As an example, assume you have a SKU# 1090 which is a white T-shirt. This item is sold individually to customers, but it is also included in a pack of three shirts. The 3-pack is sold using a separate SKU# 3451. You must provide the data for this scenario as follows:
-
When SKU 1090 sells to a customer, you will have a transaction for 1 unit on
SALES.csv -
When SKU 3451 sells to a customer, you will have a transaction for 1 unit on
SALES.csv, plus a record for SKU 1090 for 3 units onSALES_PACK.csv(representing the 3 units inside the pack that sold).
When this data is loaded into other applications like MFP, you will see a total of 4 units of sales for SKU 1090, because we will sum together the sales from both interfaces. The pack-level sale of SKU 3451 is not exported to Planning applications because that would result in double-counting at an aggregate level, but it can be used for other purposes such as Retail Insights reports.
When you are providing SALES_PACK.csv you must also provide the pack item/component item relationships
using a dimension file PROD_PACK.csv. Refer to the RAP Interfaces Guide for the full interface specifications
of both of these files.