Dataset Transaction Type Update

This document explains the different transaction types used in datasets and how they are updated.

Transaction types are used to classify the input to and content of a dataset, which is a user-defined statistical storage site. A dataset's content is controlled by its combination of transaction types, key fields, accumulator fields and date limits.

Outcome

By understanding and adopting this concept, you may improve performance and have a better control information for your business processes. The information stored in datasets can be used for forecasting, budgeting and statistical purposes.

During this process, the following changes are made in M3:

Before you start

There are a number of conditions that must be met in order for the transaction type to be updated.

The specific prerequisites are further described for each transaction type separately.

Multiple Unit Coordination

Re-creation

Order entry and sales statistics can be re-created. You specify the date from which re-creation should be performed and you can choose whether to re-create a single dataset only or all of the statistics (the OSASTD or OSBSTD files) based on open and/or invoiced order lines. You might need to do this when, for example, item groups have been changed.

Note that re-creation of all of the statistics will take time and may affect the system performance. If you have performed archiving since the last re-creation or system start-up, the archived orders are excluded in the re-creation. This may result in different contents in the datasets.

Re-creation must be performed from central (blank) division.

The programs used for re-creation are specified below.

How

Each dataset transaction type consists of two numerals. The first numeral indicates the demand source and the second indicates the source within this demand source.

The following transaction types may be used:

30 = Delivered not invoiced statistics – customer orders

The delivered not invoiced statistics for customer orders is updated when a delivery line is reported in 'CO Delivery. Approve' (OIS155) or when a picking list is reported in 'Picking List. Report' (MWS420). The delivery header and lines are created by 'Update delivery header and line' (OIS900).

Autostart job OSS980 creates a record in the sales statistics file (OSBSTD). During invoicing, transaction type 30 is replaced by transaction type 32. Transaction type 30 can be re-created by using 'Delivered/Not Invoiced Stats. Re-create' (OSS985).

Prerequisites:

31 = Order entry statistics – customer orders

The customer order entry statistics are updated when you enter a customer order. When you exit 'Customer Order. Open Line' (OIS101), autostart job OSS900 creates a record online in the order sales statistics file (OSASTD). The transaction type is adjusted when an order line is changed. If the change date and entry date are the same, the current record is changed in the statistics. If the change date is a date other than the entry date, the line in the database is marked with a "C" (for technical reasons) and a sequence number, and a new record is created in the statistics. Transaction type 31 can be re-created by using 'Order Received Stats. Re-create' (OSS990).

Prerequisites:

32 = Sales statistics – customer orders

The sales statistics for customer orders is updated by 'Invoice - update statistics' (OIS190) during invoicing. The sales statistics file (OSBSTD) is updated. Transaction type 32 can be re-created by using 'Sales Statistics. Re-create' (OSS995).

The update is controlled by two parameters in 'Settings - Customer Order Invoicing' (CRS722/E). The 'Update accounting entry' parameter must be selected in order for sales statistics to be created. The 'Update sales statistics' parameter controls whether sales statistics should be updated immediately during invoicing, either by a batch job or an autojob, or separately. If you want to update the sales statistics at a later stage, you can run 'CO Invoice. Post-Process' (OIS196/E) and select the 'Update sales statistics' parameter. You may also update the sales statistics separately using 'Sales Statistics. Update' (OIS691).

Prerequisites:

33 = Sales budget – customer orders

Sales budgets are created manually in 'Sales Budget. Enter Values' (OSS421). Note that you must always connect a sales budget version to a dataset with transaction type 33. This transaction type cannot be re-created.

34 = Sales forecast – customer orders

Sales forecasts are created in 'Sales Forecast. Generate in Dataset' (OSS440), which is controlled by the forecast method selected.

If you use advanced forecasting (that is, when the Demand accumulator field (UCDEMA) is included in the dataset), a number of forecast fields are added automatically. In standard forecasting, forecast on a field (such as UCIVQT) is based on the data in the same field (UCIVQT). Then when you use UCDEMA, forecasting is instead based on other fields. Forecasting is controlled by the forecast method.

The forecast is saved in the dataset field CFOR.

Transaction type 34 cannot be re-created, but can be re-calculated.

35 = Lost sales - customer orders

Lost sales statistics is updated when an order line is deleted using 'Customer Order. Delete Line' (OIS119). When deleting the line, you are asked whether the sales statistics should be updated on panel (OIS119/D). You may also manually update the lost sales statistics by using 'Customer Order. Enter Lost Sales' (OSS450).

Transaction type 35 cannot be re-created.

39 = Calculated base forecast - customer orders

Calculated base forecasts are created in 'Sales Forecast. Generate in Dataset' (OSS440). The base forecast is calculated from base demand and does not include seasonal factors or period length variations that affect demand.

The base forecast is used as the first step in automatic forecasting and is saved in the dataset field BFOR.

Transaction type 39 cannot be re-created, but can be re-calculated.

70 = Delivered/not invoiced statistics - service orders

This transaction type corresponds to type 30 for service orders.

The delivered not invoiced statistics for service orders are updated when a delivery line is reported in 'Planned Service Order. Print' (SOS620). The delivery header and lines are created by 'Update delivery index' (SOS600).

When a service order line has been delivered, autostart job OSS980 creates a record in the sales statistics file (OSBSTD). During invoicing, transaction type 70 is replaced by type 72.

Transaction type 70 can be re-created by using 'Delivered/Not Invoiced Stats. Re-create' (OSS985).

Prerequisites:

72 = Sales statistics – service orders

This transaction type corresponds to type 32 for service orders. The sales statistics for service orders is updated by 'Invoice - update statistics' (SOS190) during invoicing. The sales statistics file (OSBSTD) is updated. Transaction type 72 can be re-created by using 'Sales Statistics. Re-create' (OSS995).

Prerequisite:

73 = Sales statistics – maintenance orders

This transaction type corresponds to type 32 for maintenance orders. The sales statistics for maintenance orders are updated by 'Invoice - update statistics' (COS190) during invoicing. The sales statistics file (OSBSTD) is updated. You may also update the sales statistics separately by using 'Sales Statistics. Update' (COS691).

Transaction type 73 can be re-created by using 'Sales Statistics. Re-create' (OSS995).

Prerequisite:

The 'Update sales statistics' parameter in 'Maint CO Type. Open' (COS010) must be selected.

81 = Order received statistics – project

This transaction type corresponds to type 31 for project orders. The order received statistics for project orders are updated when a project invoice is created, changed or deleted in 'Project Invoice. Update' (POS480) or 'Project Invoice. Update Lines' (POS481). The invoice status must be less than 70. Autostart job OSS900 creates a record online in the order sales statistics file (OSASTD).

Transaction type 81 can be re-created by using 'Order Received Stats. Re-create' (OSS990).

Prerequisites:

82 = Sales statistics – project

This transaction type corresponds to type 32 for project orders. The sales statistics for project orders are updated by 'Invoice - update statistics' (POS190) during invoicing. The sales statistics file (OSBSTD) is updated. The project invoice must have status 70 or greater.

In 'Settings - Project Invoicing' (CRS792) or 'Project Invoice. Update' (POS480) you can set the level on which sales statistics should be updated, either for the invoice line (the total sum) or for the suffix line (the detail level). The value set in (POS480) will override the value in (CRS792).

Transaction type 82 can be re-created by using 'Sales Statistics. Re-create' (OSS995).

Prerequisite:

The 'Update sales statistics' parameter in 'Project Type. Open' (POS010/E) must be selected. You can choose to update sales statistics for final invoicing and on-account invoicing (alternative 1) or for advance, partial and on-account invoicing (alternative 2).

Related topics