Skip to Content
Author's profile photo Former Member

Example for Version Management

Versioning allows you to manage, document and keep track of changes made to a product.


Product modules are used to accelerate the modeling process.

In addition to the general documentation available on the Help Portal ( -> SAP for Utilities as part of CRM 7.0 EHP3 -> Application Help -> Product Modeling for Utilities), we want to offer you an example of the possible versions of a product module in the system.

In our example, you create a product module with version 0001, and the attribute Consumption Total. This version has the status In Progress:


If you set the status to Active for Testing, you can’t change the product module any more, until the version has been released, set obsolete or the old version has been retrieved:



If you set the status to Obsolete, you can no longer change the product module:


You can only create a new version of the product module:


If the version is reversed, the status of the product is changed back to In Process again, so that you can change the product module again:


You can add a product module to products. In this example, you have assigned the product module IUTA_ELEC_MODULE with version 0001 to a single-household rate contract (IUTA_ELEC_SINGLE) and a family-household rate contract (IUTA_ELEC_FAMILY):


When you release version 0001 of the product module, you can no longer change it. You can only create a new version:


You create version 0002 of product module IUTA_ELEC_MODULE:


You add attribute Rate Category , update the assigned products and release version 0002:


When choosing the History menu entry, you can display the version 0001 for PM IUTA_ELEC_MODULE. In this case, the attribute Rate Category added to version 0002 disappears:


Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.