Show TOC

Function documentationPMEVC: Check Model Locate this document in the navigation structure

 

In the product modeling environment, you can perform comprehensive checks for your configuration model. The checks include the following areas:

  • Consistency checks

  • Integration checks

  • Performance Checks

  • Knowledge Base Checks

  • Customer-Specific Checks

You can use these checks to improve the quality of your model and to identify errors or weak points centrally.

Features

Consistency Check

  • Characteristics

    The system checks if all the characteristics used in object dependencies are assigned to a class.

  • Sort sequence for procedures

    The system checks if a sort sequence has been specified for procedures. If an object has at least two procedures assigned to it, the system issues a warning if the field for the sorting counter for one of the procedures contains no value. In addition, the system checks that multiple procedures for one object do not have the same sorting counter.

  • Variant tables

    The system checks if the variant tables contain contents.

  • Object dependencies

    The system checks that relationships have the status Released.

  • Constraints

    The system checks that only classes or materials that are contained in the model have been entered in constraints.

Integration Check

The system checks the reference characteristics of the configuration model. It checks whether the assigned tables and table fields are supported in the configuration scenario, and whether multiple reference characteristics exist in a class that link to the same table field.

Performance Checks

  • Checks for variant tables:

    • If the variant table contains more than 10,000 rows and more than 10 columns, you must link the variant table to a database table (see SAP Note 917987). If the variant table has less than 10,000 rows and less than 10 columns, you should not link the variant table.

    • The variant table must not contain empty cells.

    • A variant table (that is not linked to a database table) must not contain more than 99,999 rows (not relevant for IPC).

      You therefore receive a warning if a variant table contains more than 80,000 rows and no link to a database table.

  • Use of actions

    You must not use actions.

  • Use of class-specific overwritten characteristics

    Class-specific overwritten characteristics have a negative impact on performance. As information, the check tool indicates the class in which the overwritten characteristics exist. The user can check whether the overwritten characteristics are necessary or if he or she can replace them.

  • Multiple use of procedures

    You must not use a procedure more than once in the same configuration instance, such as in the configuration profile or in the characteristic, because this can lead to redundant inference of values.

Knowledge Base Checks

In the case of a knowledge base, the check is performed for the run time versions with the latest valid-from date, which can be earlier than or the same as the model date (which was either specified in the entry screen or copied from a change number).

The same checks are performed as when creating, changing, or displaying a runtime version, in other words, the system processes the delta list between IPC (Internet Pricing and Configurator) and the varant configuration (see also SAP Note 837111).

Customer-Specific Checks

If you have defined naming conventions in your company for the different object types of your configuration model, you can use the customer-specific check to ensure that the naming conventions are used consistently. The check is based on prefixes or suffixes for the individual object types, for example, all characteristics are to begin with the prefix CHAR.

You can perform the check for all objects of an object type, or restrict the check to particular groups of an object type.

If you have not specified any groups for a check, this check is applied to all objects (of this object type) without an assigned group, as well as to objects (of this object type) whose group does not have its own predefined check.

You can save the rules that you have defined in the dialog box for the check, as a template.

Activities

  1. In the modeling environment for variant configuration, choose the Check Model pushbutton.

  2. A dialog box appears in which you can select the areas of the check. You can save your entries in a user-specific manner.

  3. If you select the customer-specific checks, a further dialog box appears in which you can specify the rules for checking the naming conventions.

    1. If you want to save your entries as a template, choose Save as Template.

    2. A dialog box appears in which you can save the template with a name.

      In addition, you can save the template in a user-specific manner as a default template, so that the table is filled with the template entries the next time you call it up.

    To call up the templates, choose Load Template and in the resulting dialog box, enter the name of the template or use the input help to select a template.

    To delete the template, choose Delete Template and in the resulting dialog box, enter the name of the template.

  4. The check results are displayed in a separate screen area in the bottom right part of the screen.

  5. If an icon is displayed in the Long Text column, you can double-click the icon to display more information about the message.

  6. If you double-click a message text, the corresponding object is displayed in the detail view.