Converting Non-Versioned Product Structures
This document explains how to convert non-versioned product structures to versioned product structures.
Since versions in product structures became available, customers with legacy product structures also started using versions. Product structure versions are defined with a version number in addition to the company, facility, product number, and structure type.
Aside from having both non-versioned product structures coexist with version structures, users can potentially convert non-versioned to versioned product structures. This process of conversion to versions will inspect the existing product structure, evaluate the effective dates of the child tables such as the material and operation tables (MPDMAT and MPDOPE), and generate product structures with non-overlapping dates.
Before you start
The versions of product structures can be created if the corresponding facility has the 'Version management' parameter set to 1 or 2 in 'Facility. Open' (CRS008).
Outcome
A non-versioned product structure is created for the desired product structure.
Follow these steps
- Use the API transaction 'StartVersioning' in PDS001MI to start versioning for a product structure.
- Specify the details for the product and structure type to be converted to versions.
- Optionally, specify a 'From date', a 'To date', or both. This information can be provided to bracket the overall effectivity of the versions.
The source product structure is copied into a target structure type to save the original record. The input data is then considered, the dates of material and operation data for the given product structure are evaluated, and a sequence of versions is generated.
Since versions cannot have overlapping dates, multiple passes of date logic are performed using both the ‘From date’ and the ‘To date’ of the material and operation tables to identify the versions required.
The relevant child tables are populated with new dates with respect to the effective dates of the new versions created. These tables include rate compensators or alternate materials, as applicable for each version. If any step fails, the whole process is aborted and reverted to the original state.
This conversion is performed only if the facility (CRS008) uses versions (VRNU > 0). Product structures being versioned cannot refer to an ECO managed product. Other validations include checks of the product existence in the facility, if the product structure is not already versioned, and other compatibility checks in 'Settings. Product Structures' (CRS787) before the conversion process is initiated.
For example, if the source product structure has three material lines with the following effective dates:
FACI = A01, PRNO = ABCDE, STRT = 001
Bill of Material (MPDMAT)| Item | From date | To date |
|---|---|---|
| Material 1 | 0 | 99999999 |
| Material 2 | 2019-11-30 | 2020-12-31 |
| Material 3 | 2020-03-01 | 2020-12-31 |
After the conversion, there will be four versions:
| Version | From date | To date |
|---|---|---|
| 1 | 0 | 2019-11-29 |
| 2 | 2019-11-30 | 2020-02-29 |
| 3 | 2020-03-01 | 2020-12-31 |
| 4 | 2021-01-01 | 99999999 |
The material tables for the above versions will be as follows:
Bill of material for version 1| Item | From date | To date |
|---|---|---|
| Material 1 | 0 | 2019-11-29 |
| Item | From date | To date |
|---|---|---|
| Material 1 | 2019-11-30 | 2020-02-29 |
| Material 2 | 2019-11-30 | 2020-02-29 |
| Item | From date | To date |
|---|---|---|
| Material 1 | 2020-03-01 | 2020-12-31 |
| Material 2 | 2020-03-01 | 2020-12-31 |
| Material 3 | 2020-03-01 | 2020-12-31 |
| Item | From date | To date |
|---|---|---|
| Material 1 | 2020-12-31 | 99999999 |