Show TOC

Process documentationProcess Flow of Product Version Change

 

This process is run when you change the product version for a master contract. During a product version change, the system checks the fields and field values of the contract for the new product version. The system changes the fields and field values depending on the settings for the source contract, the target product version, and the transfer procedure, which means that the properties of the contract can be changed. The system makes these changes by comparing the fields and field values with the settings for the corresponding attributes and attribute values of the source contract and the target product version.

The attribute group, and not the attribute category, to which an attribute belongs determines whether the attribute and its corresponding field in the master contract are included in the product version change. You assign attributes to attribute groups in Customizing for the master contract product change. Along with the transfer procedure, the attribute group is one of the central units of all product change Customizing.

The following list shows which attributes and their corresponding fields in the master contract are included in the product version change for an attribute category:

  • Feature attribute

    In system Customizing for the product change, everyfeature attribute is assigned to its own attribute group with the prefix BCFE (contract elementFeatures) and to the BDT applicationDummy. Apart from the feature attribute, this attribute groups contains no other attributes (such as field attributes).

    All feature attributes in the product and the table of features in the master contract are included in the product version change.

  • Matrix attribute

    In system Customizing for the product change, every matrix attribute is assigned to its own attribute group with BDT application. Apart from the matrix attribute, this attribute groups contains no other attributes (such as field attributes).

    All matrix attributes in the product and the table of features in the master contract are included in the product version change.

  • Field attribute

    • In system Customizing for the product change, some of the field attributes are assigned to attribute groups with the BDT application. These attribute groups can contain multiple field attributes.

      These field attributes in the product and their corresponding fields in the master contract participate in the product version change.

      Note Note

      For the field attributes of some contract elements (such as compensation: participant (REIC)), the product version change can change from green to green, red to red, or red to green, but not from green to red. In this case, you cannot deactivate a field attribute already being used in the master contract in the new product version.

      End of the note.

    • In system Customizing for the product change, some of the field attributes are assigned to dummy attribute groups.

      These field attributes in the product and their corresponding fields in the master contract are not included in the product version change.

Process

The process flow of a product version change described below is considerably simplified.

  1. The program for executing product version changes opens a master contract.

  2. The relevant contract elements of the contract check their fields and change these depending on the attributes defined in Customizing for the product change.

    Note Note

    Note that the contract elements keep or discard future, time-dependent changes already made to contract fields depending on the Future Contract Changes: Master Contract Product Change indicator.

    End of the note.

  3. The system makes consistency and plausibility checks for the master contract.

  4. The system saves the master contract in its status that was changed by the product version change in the database.

Note Note

The product version change does not change the attributes that are assigned to a dummy attribute group in Customizing. A dummy attribute group can contain relationship attributes of the master contract participants. To use a new application for existing participants of a master contract, edit every participant individually for the respective master contract on the Contract Relationships tab page after the product version change:

  1. Activate the new application.

  2. Edit the new relationship attributes.

For more information about editing the participants, see Editing Contract Relationships.

End of the note.

More Information

For information about the relevant contract elements and the behavior of the corresponding attributes, see Customizing for Master Contract Management under Start of the navigation path Technical Documentation for Master Contract Management (FS-MCM) Next navigation step Objects in Master Contract Management Next navigation step Contract Next navigation step Contract Specialization Next navigation step Contract Elements End of the navigation path.