Change Set

Change Set is a feature which increases traceability of changes (in Setup or via scripting) and ensures that appropriate recording of changes occurs in the relevant change management procedures. A change set encompasses a group of changes that are performed in a single set. Each change in SAP CPQ is logged in Audit Trail as a part of a change set.

Change sets can only be created in development and testing SAP CPQ environments. If you want a change set to be displayed in Setup in sandbox and production environments, you need to deploy it from the lower environment once the changes have been tested and applied there.

Change sets can be active and inactive. Of all the active change sets, only one can be in use at a time. You can select the change set you wish to use in the Change Set dropdown in Setup. Once you select a change set, all changes that you apply to SAP CPQ from that moment on will be logged in Audit Trail under that change set. The inactive change sets do not appear in the dropdown, but you can find them in Setup > Audit Trail > Change Set (where all change sets created by administrators are listed) and activate them again. Changes cannot be logged under an inactive change set.

Using change sets to improve tracking of changes is optional. If you do not need to assign any changes to a change set, simply leave the DEFAULT (CPQ-1) change set selected in the Change Set dropdown in Setup. That way, all changes you perform will be logged with the CPQ-1 change set ID in the Audit Trail.

The default change set will be selected every time you log into SAP CPQ regardless of whether a different change set was previously selected or not. If you make some changes under a custom change set, exit setup and then enter it again without logging out, the custom change set you have previously used will be the selected one.

Creating a Change Set

There are two ways to create change sets. You can access the Change Set dropdown in the Setup. The names and IDs of active change sets in your environment are displayed here.

  1. Click cpq_1908.1_change_set_add_new.jpg next to the Change Set dropdown in Setup.
    A popup window displays.
  2. Enter the name of a new change set in the indicated field.
  3. (Optional) Enter the description of a new change set in the indicated field.
  4. Click Save.
    Once you create this change set, it will automatically be activated.

Alternatively, you can:

  1. Go to Setup > Audit Trail > Change Set.
    The grid containing all available change sets (except the default one) displays. It has the following columns: Edit, Active, Name, Description, Change Set ID, Date and User.
  2. Click New Change Set.
    A popup window displays.
  3. Enter the name of a new change set in the indicated field.
  4. (Optional) Enter the description of a new change set in the indicated field.
  5. Click Save.
  6. (Optional) To edit column visibility, click .
    The new change set is now listed in the Change Set grid. Once created, the change set can be edited.


Currently, change sets cannot be deleted, but they can be deactivated with the Active toggle switch.

Change Set and API

If a change is performed via API, and you wish to assign it to a change set, enter the change set ID in the header for each API call. You can only use IDs of active change sets. The key entered in the header should be ChangeSetId, and its value should be the value of that change set ID (for example, CPQ-10).

This is the list of affected APIs:

  • AUXTableAdministrator
  • CompanyAdministration
  • ImportMaterialsFromERP
  • SimpleProductAdministration
  • UpsertPricebook
  • UpsertPricebookWithDistributionChain
  • UserAdministration
  • CustomerAdministration

Deploying a Change Set

It is possible to deploy active change sets from development and testing to sandbox and production environments. In this initial phase of improved SAP CPQ transport mechanism, there are two ways to deploy change sets to target environments. You can either do it manually or via a deployment package.

Manual Deployment

Once you click the Deploy button in Setup > Audit Trail > Change Set, a popup window displays. You are prompted to select a target environment and a change set or change sets that should be deployed to it.

  • Target environments – a list of connected environments (Deploy/Send Changes > Deployment Setup > Connected Environment). If there are no connected environments, you need to establish a connection between environments first.
  • Change set grid – a grid with all active change sets. You can select change sets you wish to deploy here.

When a change set is deployed from one of development or testing environments, it will appear in the target environment’s list of active change sets. No changes previously performed in the source environment will be applied to that environment automatically or logged in the target environment’s Audit Trail.

Example: An administrator selects the CPQ Test change set in the source environment, performs some changes manually and sends that change set's definition to the target environment by clicking the Deploy button in the Change Set page. Then an administrator selects that change set on the target environment and applies the same changes manually there.

Deployment Package

To deploy a change set via a deployment package, navigate to the Deployment Packages tab in Setup > General > Deploy/Send Changes > Deployment Setup in the source environment and click Create Package. There, you can select the change set and deploy the package to the target environment.

If the change set with that ID already exists in the target environment, it is preselected in Setup and all changes that were deployed in the package are applied in the target environment and logged as a part of that change set. If the change set does not exist in the target environment, it is created, preselected and all changes associated with it are applied in the target environment and logged in that environment's Audit Trail.

If an administrator performs one change in the source environment as a part of the Change Set A and another change as a part of the Change Set B, there are no restrictions which prevent both changes to be sent as a part of the Change Set B if they are deployed in the same package when Change Set B was selected in Setup.

You are here: SAP Sales Cloud CPQ Online HelpAdmin Page HelpAudit TrailChange Set