About Dataset

M3 DMP uses Datasets imported from M3 BE. A Dataset in M3 BE is a combination of: Keys, Accumulators and Transaction types.

The following list displays some accumulators used in M3 for creating Datasets for M3 DMP.

Field Description
UCDEMA Demand
UCIVQT Invoiced quantity
UCORQT Ordered quantity
UCSAAM Sales amount
UCUCOS Cost price

 

The Transaction Types that are attached to a Dataset are as follows:

  • 30 - Delivered/Not Invoiced
  • 31 – Order received quantity
  • 32 – Invoiced quantity
  • 33 – Sales budget
  • 34 – Demand/Calculated sales forecast
  • 39 – Calculated base forecast.

A record in a Dataset is always registered as a combination of an accumulator and a transaction type. The following table lists the types of Accumulator and Transaction Type combinations:

Accumulator - Transaction Type combination Names
UCORQT, 31 Order received statistics
UCIVQT, 32 Sales statistics
UCUCOS, 32 Cost price
UCSAAM, 32 Sales amount
UCIVQT, 33 Sales budget
UCUCOS, 33 Cost price
UCSAAM, 33 Sales amount
UCDEMA, 34 Demand
MFCFOR,34 Calculated sales forecast
MFCFOR,39 Calculated base forecast
MFMFOR,34 Manual sales forecast
MFMADJ,34 Manual adjustments

 

A Dataset is an aggregated extract of information in the sales statistics files (OSASTD/OSBSTD).Using a subset of the sales statistics files,views displaying the information are created to make a good forecast. Based on the number of key fields involved, the view enables you to drill down into the data.

Example

Keys in a Dataset are defined as Customer and Item, in weekly buckets. The invoiced quantities are defined as the accumulators. For each combination of customers and items, the sums of invoiced quantities get recorded in the sales statistics files per time bucket.

An Application Program Interface (API) program generates the Datasets and the building of the file is completely transparent to the user. You create a Dataset by activating the Dataset. The system does the rest. The system creates a file to host the Datasets input.

If you deactivate a Dataset, the related file and its content are deleted. You can still recreate its content in either Sales Statistics.Re-create (OSS995) or Order Received Statistics.Re-create (OSS990). Once a Dataset is active (status 20), it accumulates data. But a Dataset never accumulates data from the past.

Example

If you activate a Dataset with a starting date of 060510, it will never contain orders older than this date. If you do want to incorporate the past orders, you have to recreate the order/sales statistics with OSS995/OSS990.

If you have a Multi-Unit Coordination (MUC) setup, several records will be updated in the sales statistics file (OSBSTD)-one record for the division in which the order was invoiced and another for the consolidation division.

Datasets are created in M3 BE, which are then imported into M3 DMP. There are 3 ways in which a Dataset is setup for forecasting in M3 DMP, they are as follows:

  1. Setup Dataset for Manual Forecasting in M3 DMP

    For Manual Forecasting, the following accumulators and transaction types must be attached to the Dataset:

    • Accumulator – UCIVQT
    • Transaction type – 33

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

    Note that Manual forecast = A sales budget in M3

  2. Setup Dataset for Calculated Forecasts in M3 DMP

    For Total Forecasting, the following accumulators and transaction types must be attached to a Dataset:

    • Accumulator – UCDEMA
    • Transaction type – 34 and 39

    When activating the Dataset, all sales forecasting related accumulators, for example: MFCFOR – Calculated forecast, are automatically attached to a Dataset.

  3. Setup Dataset for Sales Budgeting in M3 DMP

    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.