Explaining and Executing the Transformation from Classic (LO-VC) Models into Advanced (AVC) Models

Watch the following video, which explains the three existing transfer scenarios.

The following figure explains possible migration and transformation scenarios of LO-VC to AVC.

The following video explains the data needed to be transformed and the data, which stay as they exist in the system.

You group models that are to be transformed at the same time in work areas.

The LO-VC model is checked in advance (for any necessary adjustments).

The AVC model is created by copying LO-VC master data (then the adjustment that might be necessary).

You use a congruency check to compare the results of the LO-VC model and the AVC model.

Releasing the AVC model releases the corresponding master data and automatically configures it with the AVC model in the future.

The transfer of the material variants involves an exchange of the configuration profiles from LO-VC to AVC.

LO-VC models are transformed at a fixed explosion date. (In other words, only one change status for engineering change management).

In general, multilevel models are also transferred to AVC across all levels. Multiple models can also be transformed together (interesting in the case of large overlaps in global object dependencies).

Each LO-VC master data record can only be transformed to AVC once.

It will not be copied during transformation:

• Material masters
• Classes (Also Class Nodes)
• Characteristics
• BOMs including object dependencies
• Task list including object dependencies
• Variant tables (classic variant tables must be copied manually)

Function and pfunction cannot be used in AVC object dependencies or in classic object dependencies in BOM and routing.

Transaction VCH_L2A_WORKSPACES starts. Here, you create a transition workspace. You assign a name, a description, and a key date for exploding the master data. Optionally, a target change state can be specified (for AVC objects).

After saving, the system automatically takes you to the detail view of the transition workspace. LO-VC models can be added using the Add Model button. Save.

Choose the Start Transition button to start master data determination. (Multilevel explosion of models and determination of transforming configuration profiles and high-level dependencies). This defines the transition workspace.

The next steps are performed in the Transition Workbench (button). You start the Transition Workbench. In addition to the button, you can also access it using transaction: VCH_L2A_WORKBENCH.

The Transition Workbench is divided into three areas:

• Object hierarchy (= model hierarchy similar to PMEVC, but only transformation-relevant data)
• Transition Objects
• Message Area

Double-clicking on the header object explodes the model and lists the transition objects.

The Transition Objects area supports the actual model transformation. First, you select the objects to be transferred to the AVC model.

In the message area, you receive result messages for the executed actions. There are three different message categories:

• Source Compatibility Check Messages (LO-VC)
• Messages for Compatibility Check of Target (AVC)
• Messages for renaming, copying, and assigning AVC objects

To check the LO-VC models (that is, check AVC compliance), start the second step by selecting the relevant lines in the Transition Objects area and choosing Check LO-VC Object. The result is displayed in the message area.

Messages can contain the following points:

Obsolete setting in LO-VC configuration profile (warning).

Interface designs in the configuration profile that can no longer be used (warning).

Irrelevant settings regarding restrictable characteristics (warning).

Syntax element such as function and pfunction that is no longer supported.(error message).

By selecting all and choosing the Copy button, you create the AVC model.

The AVC configuration profile is created but not released and still without object dependencies.

The AVC object dependency is created but not released and not yet assigned.

This dependency can now be changed to improve the result of the check of the AVC data in the next step.

The system tries to work with the suffix, _AVC, for all new master data. The name can be changed manually in column AVC: Object Name in advance.

The next steps are (using the corresponding button):

• Check AVC objects.

• Assign Global Dependencies to the New AVC Model.

All newly created AVC master data is Released (status) using the button of the same name.

You can start the comparison using the Start Comparison button from both transactions, VCH_L2A_WORKBENCH and VCH_L2A_WORKSPACES. The comparison is always made with reference to an original document such as a sales order or material variant.

The last step is the transfer of the material variants. You convert the material variants with a classic configuration profile to material variants with an AVC configuration profile. You can do this using transaction: VCHMOVMVAR. You can only transfer a single material variant or all material variants of a configurable product.

If you choose Execute, a simulation with the corresponding AVC model is executed in the background for all selected LO-VC material variants. The system displays a list of the material variants with the following information:

• The global material variant
• The plant-specific material variants
• The configurable material
• The source profile, that is, LO-VC Configuration Profile
• The target profile, that is, AVC Configuration Profile
• The comparison status

The transfer has not yet been executed. If you select the required lines and choose the Convert Material Variants button, the switch to the AVC configuration profile is performed and documented by the changed status.