Show TOC

Process documentationProduct Configurator

 

The Product Configurator is a tool that is available to you in Account Management (FS-AM) and in Master Contract Management (FS-MCM). You can define and control the description options of a contract using a product that serves as a template. The Product Configurator provides the following functions:

  • Create product categories

  • Define attributes for product categories

  • Create any number of products for each product category

  • Group products together in product groups.

  • Create versions of products

  • Set attributes for products

    You define permitted features, fixed values, default values, permitted value ranges and field modifications. The total attributes define the scope of functions of the contracts created for the product.

  • Product managers can simply and quickly design new products and introduce them on the market.

    You do not require programming knowledge.

The following overview shows the relationship between the product category, product, and contract:

Products are based on product categories that are depicted as attribute hierarchies in the system. The main task of the product category is to define a number of attributes that are available to all products in this product category. Examples of product categories: Account and Card. The individual attributes are used to store information for each product. They are defined for each product category and can be given values within a product.

A product is the specific characteristic value of a product category, and the basis for contracts. Each contract that is agreed on between a bank and a customer is based on a product. In the product, you specify which fields you want a contract to have and the extent to which the processing staff are permitted to change the individual field contents during contract processing.

The system generates a new product version each time an important change is made to a product. Each product version has a status and a validity.

A contract is based on a specific product from which it inherits all its characteristics and attributes. The degree of autonomy permitted in contract processing is determined by the settings in the product.

Process

Structure of the Attribute Hierarchy

The attribute hierarchy contains all attributes for contracts. They are depicted in a tree structure.

The attribute hierarchy displays the hierarchical assignments of the attributes and is client-specific. You can use the hierarchy nodes Used Attributes and Unused Attributes to decide which attributes are to be available in the individual product categories. You can reassign the individual attributes to other positions within the attribute tree.

If you create or change attributes, the changes are made in all clients (cross-client). Newly created attributes are assigned under the Used Attributes hierarchy node in the client that is to be processed. However, these new attributes are not used initially in other clients. They are assigned under the Unused Attributes hierarchy node.

Attributes determine the functions of a product: The more attributes you assign to a product, the more options you have for defining a contract in terms of characteristics and features. The settings for the individual attributes specify the scope of functions, structure of the product, and contracts based on this product.

The attribute hierarchy can consist of the following attribute categories, which are highlighted in different colors. Choose Color Key to see the corresponding color assignments.

  • grouping attribute

    Grouping attributes are only used to group other attributes, and are not forwarded to contracts. They can also be used for the required attribute logic.

  • Feature attribute

    Feature attributes are used to determine whether certain functions are permanently available in a contract, for example, the standing order function. You can lock features temporarily in a contract by setting feature locks.

  • Field attribute

    Field attributes give fields in the contract, such as Currency, a fixed value or a default value. You can also store a permitted value range or a field modification.

  • Matrix

    Matrix attributes have a padlock in the product that controls the changeability of the table fields and a traffic light that visualizes the attribute status. You can label a matrix attribute in the attribute hierarchy as required attribute.

    When you are processing products, a matrix of traffic lights and padlocks appears on the detail screen. You can change individual traffic lights and padlocks, entire lines or columns, or the entire matrix. Each traffic light/padlock combination has the same effect on a contract as the traffic light/padlock combination of a feature attribute, whereby the combination of traffic light red, padlock open is also possible.

  • List

    A list attribute functions like a matrix attribute defined in one column. List attributes have a padlock in the product that controls the changeability in the contract and a traffic light that visualizes the attribute status.

Note Note

In Account Management, you can also use some field attributes for attribute derivation if they have been flagged with "Derivation Attribute Category" in the product category. For more information about attribute derivation, see the Attribute Derivation function description.

End of the note.

Every field in the dialog, direct input and BAPI must refer to a corresponding attribute in the attribute hierarchy of each product category. To make it easier to find the relevant attribute, the attribute hierarchy is structured according to the tab pages and group boxes in dialog processing. Each of these fields has corresponding fields in the direct input and BAPI channels.

Variations are required in special areas only, for example if a hierarchy is to be displayed as a graphic in dialog processing and edited using drag and drop. In this case, the corresponding attributes have fields in the direct input and BAPI channels. These fields do not exist in the dialog since entries are made in the background by the graphic tool.

Every descriptive characteristic of a contract is an attribute. You can only enter data for a contract in fields that have at least one corresponding attribute in the attribute hierarchy of the product category apart from the not used attributes. The settings in the product and the product version affect the field modification.

Products

In a validity period, there is only ever one product version that is both active and valid (there can be several active product versions). When changes are made to active products, the system creates a new product version when saving to avoid data inconsistencies. You can save changes to inactive products in the same version or in a new version.

The product attributes have traffic lights and padlocks with which you can control the corresponding fields in the contract.

* The combination of red traffic light / open padlock is only possible for attributes of the matrix attribute category. At contract level you can activate (green traffic light) a matrix element with a red traffic light by clicking on it provided the padlock is open in the product.