How to move SAP Commissions plan data from one environment to another

[Lara]

It's a common challenge: you've spent months developing an application in your dev environment or sandbox, you've put in weeks of testing and documenting, and now you're faced with the challenge of getting all of your code into Production. In this article, we'll cover the steps to do this in your SAP Commissions implementation.

In SAP Commissions, the objects that can be moved using this method are:

• Fixed Values


• Territories


• Quotas


• Formulas


• Rate Tables


• Lookup Tables


• Variables


• Rules


• Plans

This is a two-step method that involves downloading the objects to an .XML file, then importing the .XML file using the Pipeline. In the instructions below, I'll export all the Fixed Values in my environment.

Step 1: Downloading the .XML file

• Open the Workspace containing the objects you wish to export. We'll be using Fixed Values.


• Click the Export to XML icon

 

 

 

 

• In the Export to XML dialog box:
  
  
  
  • Select Export Selected or Export All
  
  
  • Select which versions to export.
  
  
  • Select Export Related Data. Optionally, you can export related Lookup Tables, Lookup Table Cells, and related Quota cells.
  
  
  
  

 

 

 

 

 

 

 

 

 

 

 

• Select Export

The file will appear in your default Downloads folder.

 

Step 2: Importing the XML file using the Pipeline

• Log in to the destination tenant using an account with permission to run a Pipeline. Open SAP Commissions.


• From the Run menu, select Pipeline


• Click the Run a Pipeline icon on the Toolbar

 

 

 

• Select Import Plan Data and select Next

• Click Choose File and navigate to the file location


• Select Update Existing Objects and click Next


• Leaving all other settings at the default, continue clicking Next until you reach the Summary page. Click Start.

This will import the objects to the new destination.

Recommendations and Best Practices

Here are a few things that will ensure your objects are transferred seamlessly.

• Use a separate XML file for each different type of object. For example, export Plans separately from the Rules they contain


• Use Update Existing Objects when importing the plan data.


• In order to ensure that all dependencies are met, import your objects in this order:
  
  
  
  • Fixed Values
  
  
  • Territories
  
  
  • Quotas
  
  
  • Formulas
  
  
  • Rate Tables
  
  
  • Lookup Tables
  
  
  • Variables
  
  
  • Rules
  
  
  • Plans