Defining Datasets and Sales Budget Versions

Outcome

Datasets needed in M3 DMP are created and activated in M3 BE.

Datasets are imported to M3 DMP to form the basis for collaborative demand planning.

When a Dataset is activated in M3 BE, a file is created to host the Datasets input. The Dataset file contains a subset of the information in the order statistics and sales statistics files (OSASTD/OSBSTD). When these files are updated with a new record, the active Dataset is automatically updated as well if the new record matches the selected keys, accumulators and transaction types in the Dataset.

A Sales Budget Version is a part of the Dataset file but does not contain any information extracted from M3 BE. Any Sales Budget values are stored only in the Dataset file until transferred to item forecasts. Activating a Sales Budget Version does not affect M3 BE in any way.

Before Starting

If running a Multi Unit Coordination (MUC) environment in M3 BE, the user must be allowed to create data in blank division if sales statistics shall cover several divisions.

If the MUC environment is used without UCDIVI as a key field, the demands will duplicate because of the consolidation division that is set in MFS010. To avoid the duplication of demand:

• Use a consolidated division. The demand will be collected for all divisions attached to the consolidated division.
• Use DIVI as a selection for the dataset in OSS403 and OSS404. Exclude the consolidated division.

To enable import of Datasets and Sales Budget Versions to perform collaborative demand planning in M3 DMP, the required Datasets and Sales Budget Versions must be created and activated in M3 BE. M3 DMP creates and manipulates forecast values in the imported Sales Budget Versions.

Activity Description

1. Create and activate Datasets

   Datasets to be imported to M3 DMP are created and activated in this activity. The Datasets used in M3 DMP can include the following transaction types:

   • 30 – Delivered/Not Invoiced Statistics
   • 31 – Order received quantity
   • 33 – Sales Budget
   • 32 – Invoiced quantity
   • 34 – Demand/Calculated sales forecast
   • 35 – Lost Sales
   • 39 – Calculated base forecast

   The Datasets must be defined with transaction type 33 (Sales Budget) to include the Sales Budget Versions created in the next activity. A Dataset must be active to create connected Sales Budget Versions and to be imported to M3 DMP. For we do not need Transaction Type 33. See About Datasets.

2. Create and activate Sales Budget Versions

   In this activity Sales Budget Versions for a defined and active Dataset are created and activated. The process of collaborative demand planning in M3 DMP creates and manipulates forecast values in the imported Sales Budget Versions.

   For Sales Budgeting the following accumulators and transaction types must be attached to a Dataset:

   • Accumulator – UCIVQT
   • Accumulator – UCUCOS
   • Accumulator - UCSAAM
   • Transaction type – 33

   At least one Sales budget version needs to be created and activated for Sales Budgeting.

   The procedure Create Sales Budget Version in the M3 Companion explains how to create and activate an empty Sales Budget Version in program Sales Budget. Open (OSS420). To enter budget values before importing the Sales Budget Version to M3 DMP, refer to procedure Enter Budget Values in the M3 Companion. Note that you only need to create and activate an empty Sales Budget Version in Sales Budget. Open (OSS420) before importing it to M3 DMP.

   Note: See these topics in M3 BE Companion: Datasets, Create Sales Budget Version, Enter Budget Values.