About Datasets

A dataset is a collection of data for demand planning and forecasting. M3 DMP uses datasets imported from M3 BE. In M3 BE, a dataset is a combination of keys, accumulators, and transaction types.

This table shows some accumulators used in M3 to create datasets for M3 DMP:

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

This table shows the transaction types that are attached to a dataset:

Transaction types Description
30 Delivered/Not Invoiced
31 Order received quantity
32 Invoiced quantity
33 Sales budget
34 Demand/Calculated sales forecast
39 Calculated base forecast

For transaction type 34, you can update more accumulators in a dataset:

  • The accumulators that represent 'Ordered quantity' are updated based on order received statistics for customer orders.
  • The accumulators that represent 'Invoiced quantity' are updated based on sales statistics for customer orders.

Automatic updates of these accumulators for transaction type 34 can sometimes eliminate the requirement to define transaction types 31 or 32 for a dataset. This results in smaller dataset sizes and faster updates.

When you use transaction type 34 in a dataset, these additional accumulators are updated:

  • 'Ordered quantity - basic U/M' (UCORQT)
  • 'Ordered quantity - sales price U/M' (UCORQS)
  • 'Ordered quantity - alternate U/M' (UCORQA)
  • 'Ordered quantity - statistical U/M' (UCORQB)
  • 'Invoiced quantity - basic U/M' (UCIVQT)
  • 'Invoiced quantity - statistical U/M' (UCOFQS)
  • 'Invoiced quantity - alternate U/M' (UCIVQA)
  • 'Invoiced quantity - sales price U/M' (UCIVQS)

To update these accumulators, these conditions must be met:

  • Transaction type 34 is added in 'Dataset. Connect Dataset Trans Types'.
  • At least one of the listed accumulators is added in 'Dataset. Connect Accumulator Fields' (OSS402).
  • The accumulator ‘Demand’ (UCDEMA) is added, with an F/C method specified, in 'Dataset. Connect Accumulator Fields' (OSS402).
  • For UCORQT, UCORQS, UCORQA, and UCORQB, the CO type has ‘Update order received statistics’ enabled in 'CO Type. Open' (OIS010).
  • For UCIVQT, UCOFQS, UCIVQA, and UCIVQS, the CO type has ‘Update sales statistics’ enabled in 'CO Type. Open' (OIS010).

'Order Received Stats. Re-create' (OSS990) recreates UCORQT, UCORQS, UCORQA, and UCORQB for transaction type 34. 'Sales Statistics. Re-create' (OSS995) recreates UCIVQT, UCOFQS, UCIVQA, and UCIVQS for transaction type 34.

Note: These accumulators are updated only for customer order transactions. Advanced forecasting must be activated for the dataset.

Accumulator and Transaction type combinations

A record in a dataset is always registered as a combination of an accumulator and a transaction type. This table shows 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 from the sales statistics files (OSASTD and OSBSTD). Using a subset of the sales statistics files, the system creates views that display the information. You can use these views to create a forecast. Based on the number of key fields involved, the view lets you drill down into the data.

Example

Keys in a dataset are Customer and Item in weekly buckets. Invoiced quantities are the accumulators. For each customer and item combination, the sums of invoiced quantities are recorded in the sales statistics files per time bucket.

An Application Program Interface (API) program generates the datasets. File creation is transparent to the user. You create a dataset by activating it. After you activate the dataset, the system creates the file to host the dataset input.

If you deactivate a dataset, the related file and its content are deleted. You can recreate the content in Sales Statistics.Re-create (OSS995) or Order Received Statistics.Re-create (OSS990).

Once a dataset is active (status 20), it accumulates data. A dataset never accumulates data from the past.

Example

If you activate a Dataset with a starting date of 060510, the Dataset does not contain orders that are older than this date. To incorporate past orders, you must recreate the order and sales statistics with OSS995 or OSS990.

If you have a Multi-Unit Coordination (MUC) setup, several records are updated in the sales statistics file (OSBSTD). One record is for the division in which the order was invoiced. Another record is for the consolidation division.

Datasets are created in M3 BE and then imported into M3 DMP. You can set up a Dataset for forecasting in M3 DMP in three ways:

  1. Setup Dataset for Manual Forecasting in M3 DMP

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

    • Accumulator – UCIVQT
    • Transaction type – 33

    You must create and activate at least one Sales budget version for Manual Forecasting.

    Note: A Manual forecast is a sales budget in M3.
  2. Setup Dataset for Calculated Forecasts in M3 DMP

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

    • Accumulator – UCDEMA
    • Transaction type – 34 and 39

    When activating the Dataset, sales forecasting-related accumulators, such as MFCFOR (Calculated forecast), are automatically attached to the Dataset.

  3. Setup Dataset for Sales Budgeting in M3 DMP

    For Sales Budgeting, these accumulators and transaction types must be attached to a Dataset:

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

    You must create and activate at least one Sales budget version for Sales Budgeting.