Understanding Variant Tables, Functions, and PMEVC

Objectives

After completing this lesson, you will be able to:
  • understand BAdIs, variant tables and functions.
  • explain the benefits of the product modeling environment PMEVC

Variant Tables

Variant tables are used to store combinations of characteristic values. For example, you can only have a gray car interior if the exterior paint color is blue.

Variant tables can simplify dependencies. You reference the table in the dependency and the system used the table to check assigned values or infer values.

Note

If the interdependencies change between characteristic values, the table content also changes. There's no need to change the individual dependencies.

You can link a variant table to a database table.

You can use variant tables with all dependencies types.

  • In selection conditions, preconditions, constraints, and the conditional part of procedures, variant tables can be used to check the values entered during configuration.
  • In procedures and constraints, you can also use tables to infer values.
  • In constraints, you can use tables to restrict the allowed values for a characteristic (restrictable characteristics)

The next figure gives you an example and variant tables in syntax.

A table labeled TAB2_## displays a matrix with mast height and fork length characteristics. The image includes instructions for using these characteristics in a procedure for determining values in a configuration profile.

How to Work with Variant Tables

The following simulation gives you an example of a Variant Table.

ExerciseStart Exercise

Variant Functions

The following figure gives you an introduction to Variant Functions in LO-VC.

No variant functions are available under advanced processing mode AVC. Instead, you work with BAdIs. These are/were created with releases realized in 2019.

New BAdIs in AVC

This figure shows a screenshot of an SAP interface. It shows enhancement spot details and BAdI definitions. The right side lists BAdI functions and notes that multiple implementations are allowed.

VCH_HL_MD_DOMAIN_MODIFY

Overrule the values predefined in the characteristic master data.

Execution:

  • Only AVC high-level configuration

  • First activation of a configurable instance

Scope:

  • Add new domain values and intervals

    Delete predefined domain values

  • Change certain attributes of predefined values

Use Case Examples:

  • Build up empty domains from tables including language-specific description for string characteristics.

  • Add temporary values for special promotions.

  • Change value description for certain customers.

  • Change static defaults, for example, for certain customer materials.

  • Restrict domains on level of configuration model.

VCH_HL_PRE_VALIDATE_ASSIGN

Modify value assignments before processing the dependencies.

Execution:

  • Every round trip before dependency processing

  • Considered in high-level dependency processing

  • Control assignment on all instances

Scope:

  • Add new assignments.

  • Delete value assignments.

Use Case Examples:

  • Call external web service, RFCs, other APIs.

  • Call external engine, for example, BRF+.

  • Pass values from one instance to another instance without specifying every characteristic.

  • Read other class types like 001, 019, 017 and z-tables.

  • Read master data table (only data stored on database) for value assignment.

  • Check user inputs before dependency processing.

  • Replaces many variant functions of LO-VC.

VCH_HL_POST_VALIDATE_ASSIGN

Modify value assignments after processing the dependencies.

Execution:

  • Every round trip after dependency processing

  • NOT Considered in high-level dependency processing

  • Control assignment on all instances

Scope:

  • Add new assignments (all instances).

  • Delete value assignments (all instances).

Use Case Examples:

  • Switch author to external assignments (avoid changes by user)

  • $SUM_PART; $COUNT_PART (if not needed in validation)

  • Calculation of weights, surfaces, electrical, and mechanical parameters

  • Ability to review fully configured object looking for specific information and set a value

  • Replaces many variant functions of LO-VC

VCH_HL_ON_SAVE

Modify value assignments while leaving configuration

Execution:

  • While leaving configuration

  • NOT Considered in high-level dependency processing

  • Control assignment on all instances

Scope:

  • Lock configuration.

  • Add new assignments.

  • Delete value assignments.

Use Case Examples:

  • Special checks on valuation consistency.

  • Set values for other processes to use (customer tables).

  • Delete values of helper characteristics (not to be stored to CBASE).

Traces

The processing of object dependencies is not documented in the standard system. However, documentation can be activated using the trace.

A trace exists under LO-VC.

The text in the image outlines the trace function used to monitor internal processing steps for dependencies. It lists objects for tracing, additional filter criteria, and options to define detail levels.

A trace also exists under AVC, as shown in the following figure for detailed information.

This screenshot shows the configuration of Forklift T-FC99 with a Bill of Material. The configuration status is released, and trace details are displayed.

The next figure also explains the trace functionalities under AVC.

Screenshots show a user interface for filtering and inspecting components and characteristics, with various elements highlighted in red. Instructions for selecting components and characteristics to filter or inspect are displayed alongside lists of assigned constraints and dependencies.

The last figure shows a system reaction for an inconsistent configuration.

A software interface shows a configuration model for a forklift, listing characteristics and dependencies, with an overlay displaying additional configuration details. The interface includes a sidebar for basic component configuration and a panel for dependency codes.

How to Trace in AVC

The following simulation shows you how to trace under AVC.

ExerciseStart Exercise

How to Work with Inconsistency in AVC

The next simulation shows you possible inconsistencies in AVC.

ExerciseStart Exercise

Product Modeling Environment

The product modeling environment (PMEVC) represents a different transaction. It contains a large proportion of the modeling activities that were previously spread over many transactions. These previous transactions remain valid. In addition, the product modeling environment includes new functionality and legacy functionality in a more elegant way. You can always switch between the PMEVC and the previous transactions.

PMEVC Navigation Area

The following video gives you an overview on Product Modeling Environment tool.

The following video explains in detail the navigation area or Product Modeling Environment tool.

PMEVC Maintenance

Now let's have a look at the PMEVC maintenance.

The following figure shows you the possibilities you have.

Steps for interactive configuration in a product modeling environment include creating a configuration profile, assigning a variant class, managing dependencies, and maintaining change management. Additional tasks involve working with variant tables, functions, and creating a knowledge base object.
A list of tasks related to creating and maintaining a knowledge base and simulations, with a screenshot showing a configuration scenario for assigning reference characteristics in a sales order. Functions include drag and drop, assigning variant conditions, and integrated simulation.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn