Business Units

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Identify Business Unit Object Relationships

Business Unit Object Relationships

To ensure data integrity, Business Unit assignments must meet certain requirements. The following table shows a list of Business Unit object relationships.

Referred: Objects that contain the object type. You can create or assign object types from these objects.

Referring: When the object type contains the objects, you can create or assign referring objects from the object type.

Object TypeReferred by ObjectsReferring to Objects
PositionPositions (subordinates)Participant, Title, Plan, Position Group, Positions (manager)
Position GroupPositionNone
PlanPosition TitleRule
RulePlanFormula, Variable, Territory, Fixed Value, Quota, Rate Table, Lookup Table
FormulaRule, Formula, Rate Table, Lookup TableFormula, Variable, Fixed Value, Quota, Rate Table, Lookup Table
VariableRule, Formula, Rate Table, Fixed Value, Lookup Table, TerritoryRate Table, Fixed Value, Territory
TerritoryRuleCategory, Classifier
Fixed ValueRule, Formula, Lookup Table, Rate Table, Fixed Value Variable 
QuotaRule, Formula, Lookup Table, Rate Table 
Rate TableRule, Formula, Lookup Table, Rate Table VariableFormula, Lookup Table, Quota Variable, Fixed Value
Lookup TableRule, Formula, Lookup Table, Rate TableCategory, Classifier, Category Tree, Formula, Lookup Table, Fixed Value
Category HierarchyCategory, Lookup TableNone
CategoryTerritory, Lookup TableClassifier (indirectly through the relationship), Category Hierarchy
ClassifierTerritory, Lookup Table, CategoryNone

Items Controllable by Business Units

The following table lists Business Unit security constraints by type of object.

Workspace/ItemControllable by Business Units
ParticipantsCan be assigned to one or more Business Units
TitlesCan be assigned to one or more Business Units
PositionsCan be assigned to a single Business Unit
Position groupsCan be assigned to a single Business Unit.

Not directly assignable to a Business Unit.

Relationships are controlled indirectly by the position’s Business Unit assignment.
Roll TypesNot directly assignable to a Business Unit.
Compensation ElementsCan be assigned to one or more Business Units

Can be assigned to one or more Business Units

Subcategories can be assigned to only those Business Units to which the parent category is assigned (or a subset thereof).
ClassifiersCan be assigned to one or more Business Units
Orders, TransactionsCan be assigned to a single Business Unit

Results Data

(Credits, Measurements, etc.)

Assigned to the Business Unit to which the position is assigned.

If you change a position’s Business Unit assignment, when you next run the calculation the results data follows the position. If you need to re-run the calculation, you must do so for all periods in which the Business Unit assignment change is effective.


Can be assigned Read and/or Full access to any combination of Business Units.

Users can set a default Business Unit.
RolesNot directly assignable to a Business Unit.
Global ValuesNot directly assignable to a Business Unit.

Business Unit General Rules

The following list contains general rules about assigning or changing Business Units for objects that are in hierarchies (categories, relationships):

A set of Business Units for an object must contain the set of Business Units for its referring objects. You cannot remove a Business Unit if it violates this condition.

For example, if you have a category associated with BU1 and BU2, its category hierarchy must also have BU1 and BU2. You cannot remove the Business Unit from the hierarchy. If you later remove BU1 from the category, you can then remove it from the hierarchy.

Create the object type with the Business Unit that has the referred object.

For example, you cannot assign a Product Sales Specialist to the BU_Europe Business Unit unless his or her manager is also assigned to at least the BU_Europe Business Unit as well.

You cannot change a category’s Business Unit assignment in a way that separates it from the categories or classifiers beneath it.

For example, if the Bike Products subcategory is assigned to the Europe and Australia Business Units, and all items beneath that subcategory are also assigned to the Europe and Australia Business Units, you cannot change Bike Products to be assigned only to the North America Business Unit.

If you assign a Business Unit to a category during the creation of a category hierarchy, the Business Unit of the category persists in its subcategories as they are created.

Changes to Business Units cascade only a single level for most objects but includes the category hierarchy. For example, if you change the Business Unit for a subcategory, the change cascades to the parent category and the category hierarchy.

If you change the Business Unit assignment of an item, changes are not propagated to its referred items.

If you change the Business Unit assignment for a position, Commissions updates the position’s associated results data during the next calculation run. Results data that is manual, imported, or historical continues to have the old Business Unit assignment.

To change the Business Unit assignment of multiple objects, select them in the summary view and change the Business Unit in the detail view.

Touchless Deployment

Touchless Deployment is a self-service capability that fully empowers customers to develop and deploy custom code in the EXT Schema.

Without Touchless Deployment, your developers could create custom code and other database changes to the extended (EXT) schema in a development environment, but would have to submit a service ticket to publish the changes to a production environment. Touchless Deploymentallows youto deploy database changes into the EXT schema in the production and non-production environments, enabling them to continuously test and deploy database schema changes in their tenant. This option makes database refactoring much simpler, and there is no need to create service tickets when you need to push custom code to your production instance.

· Users can easily develop and deploy tables, sequences, procedures, views, and more.

· The deployment starts immediately, as long as no pipelines are running.

· All deployment details and errors are accessible to enable troubleshooting in case the deployment fails.

Touchless Deployment service for EXT schema is based on an open-source tool called Liquibase.Liquibase is an open-source tool that can be used for database refactoring.

Liquibase lists all the changes made to the database in a sequential manner. The changes are recorded in a changelog in the order in which they need to be deployed. Liquibase then uses the changelog to inspect and execute the updates that are not yet applied to the database. Customers need to upload the changelog and SPM will use Liquibase to execute the changes.

Enabling Touchless Deployment

To enable the Touchless Deployment feature, create a service request. Support will enable the Touchless Deployment REST Service on your tenant and notify you.

The Touchless Deployment permission is added to a role in the Security workspace. The Commissions user who deploys the database changes would then be granted access to the role. Generally this would be a system role used only for touchless deployment; in the example below, we are using a user called U_TouchlessDeployment and a role called R_TouchlessDeployment.

To configure permissions for Touchless Deployment:

1. In Manage Setup → Security → Roles, create a new role called R_TouchlessDeployment.

2. Open the Permissions tab.

3. Select Administration.

4. Under Touchless Deployment, check the box under the Update column and save the role.

When enablingTouchless Deployment in your environment, keep in mind the following points:

  • Touchless Deployment is available only for the EXT Schema and not for TCMP Schema. TCMP Schema related changes require a support ticket.
  • Ensure your syntax matches to the standard Oracle and HANA SQL scripts in your artifact.
  • Ensure you rollback the right deployed status ID.
  • Currently, Touchless Deployment is not Applicable for HDI Containers used in your SDI Project.
  • Refer to the Liquibase Documentation to understand the Syntax

Product Glossary

AdapterSDI component which allows connectivity to external sources.
PipelinePipeline is a compensation computation process initiated from the Pipeline workspace in the Job Queue view or from the command-line utility. The pipeline produces compensation and pay results for payees assigned to variable compensation plans. See Commissions online help for more details.
Commissions WorkspaceDesignated area in Commissions where related compensation objects are grouped together so that a user can perform related tasks from the same place.
AdjustmentA change to the amount of a transaction, credit, or deposit.
Administration DataCommissions data set up during implementation to identify and group data. Includes users, groups, business units, calendars, message log, roles, periods, and data types (credit types, earning codes, earning groups, event types, and reason codes). Administration data is tracked by audit history only, and is not versioned.
Aggregate credit incentive ruleA general incentive rule used to calculate incentives by comparing a specified measurement value, usually an aggregation of credited transactions, to a rate or rate table to calculate total incentive output earned by a participant.
Allocate stageCalculation stage in which credits and primary measurements are calculated and allocated to participants. The input to the stage is classified transactions from the Classify stage; the output is credits and primary measurements that are allocated to position assignments.
Applied balanceThe status of a balance is set to "applied" in the Post stage of the calculation, after the balance is posted. Balances marked "applied" are not processed during calculation runs.
Assign PermissionPermission that allows a user to assign compensation elements to variables in a plan.
Associated duplicateAn order credit that is the same as another credit for all attributes except period. Transaction credits do not have associated duplicates.
Attainment levelLevel of sales performance for an individual compared to a quota. Often used to determine the applicable rate from a rate table for an incentive.
Attainment periodThe period type for which attainment is measured for an incentive rule calculation. For example, an incentive rule might determine an attainment level using quarter-to-date performance.
Audit historyList of all of the changes that have been made to an object over time.
Audit logA set of additions, modifications, and deletions to a objects in the database.
BalanceRepresents the net effect of a payment change calculated for a finalized period. Once a period is finalized, new payments cannot be calculated for that period. For finalized periods, any payment difference is stored as a positive or negative balance.
Base unit typeSpecifies the predefined unit type. Commissions includes the following base unit types: percent, integer, quantity, and currency.
BatchA group of similar objects produced, processed, or gathered together and treated as a single unit. For example, a batch can be a data set that is processed during a calculation run. You specify the batch name when importing data into staging tables.
BonusGenerally, a kind of incentive award that is awarded when a specified performance goal is met, such as attainment of a quota.
Bonus ruleA type of incentive rule used to calculate incentive awards. A bonus rule is typically a formula-driven incentive rule that uses a formula rather than a measurement to determine rule output. For example, you can create a formula for an incentive rule that awards a one-time payout of a 10K bonus after the payee’s quarterly quota is attained.
BooleanA unit type that restricts the range of allowed values to 0 or 1 (true or false).
Business nodeAn internal object that is a unique combination of a position, a payee, and a plan. Business nodes do not correspond to a table in the database.
Business unitA data security feature that can be used to provide another layer of data access security by segregating compensation data for different parts of the corporate structure.
CalendarAn object that defines the frequency by which compensation payments can be made, and generally matches the corporate fiscal calendar.
CategoryA component of the category hierarchy used to filter sales transactions into meaningful bundles for any commissioned business event. Categories and classifiers provide a flexible and generic way to incorporate knowledge of any specific business entities into the compensation process.
Category hierarchyThe tree structure that organized categories, subcategories, and classifiers. A category hierarchy typically includes a classifier type and a root category with associated classification rule, one or more optional subcategories, and one or more classifiers with associated definitions.
Classification dataCategories and classifiers. Tracked by both audit history and effective time.
Classification ruleA user-defined expression that defines what kind of classifiers in the category hierarchy are to be matched against which fields on the transaction. You create classification rules when you create the category hierarchies.
ClassifierAn object that has a unique identifier and a set of fields defined by the associated classifier type. For example, in the Product category, each classifier represents a unique product with a unique identification number. Classifiers are used by classification rules to match fields on a transaction, and by compensation rules to filter input to the rule.
Classifier assignmentThe relationship created by assigning a classifier to a category for a specified period of time. A classifier can exist in multiple category hierarchies, but it can be assigned only once in each hierarchy.
Classifier typeA label that defines the type of classifer being organized in a category hierarchy. Predefined classifier types include customer, postal code, and product. New classifier types can also be defined by the administrator.
Classify stageCalculation stage that classifies valid transactions. Input to the stage is valid transactions, output is classified valid transactions and associated classification records. Consists of one step, Classify.

Generally, a type of incentive award based on credited transactions or other measurement value and usually proportional to the value of the measurement.

A commission is also the term for an object created by a per-credit commission rules. You can view Commission objects in the Commissions workspace.

Commissions Stage Tables 
Commit sizeThe number of records to commit to the database at one time. This depends on the size of your rollback segments.
Compensate and Pay sequenceSequence of calculation stages that includes the Classify, Allocate, Reward, and Pay stages.
Compensation elementReusable objects that you can build into compensation rules or other calculations to return a value or set of values. Includes fixed values, formulas, lookup tables, rate tables, territories, and variables. Compensation elements are tracked by both audit history and effective time.
Compensation plan

Set of compensation rules used by the calculation to calculate compensation and payments.

A compensation plan generally consists of at least one of each type of compensation plan rule: credit, measurement, incentive, and deposit.

Compensation ruleCombination of input, condition criteria, and an output result. You use compensation plan rules to specify how Commissions calculates credits, measurements, incentives, and deposit amounts for participants who are assigned to the plan.
Create default dataA calculation process that runs automatically to initialize measurements and incentives during a calculation run.
CreditAllocation to a participant of the value of a sales transaction, a part of an order, or an entire order.
Credit dateSpecifies when a credit rule for a participant can be processed by the calculation. If a transaction’s compensation date is outside of the participant’s credit dates, the credit is not created during the calculation run.
Credit ruleCompensation plan rule used by the calculation to calculate and allocate credits to participants.
Credit typeLabel that defines the source of data from which a credit was created. Credit types are used in credit rules so that credits of different types can be calculated separately.
CSV fileA plain text file with comma separated values. In SAP Commissions, you can export data from a workspace summary view into a CSV plain text file. You can export any record that is listed in the summary view
Current versionThe version displayed for effective dated objects based on the Default Calendar date and or period.
Data typeThe user-defined types of data (credit types, earning groups, earning codes, event types, reason codes, and fixed value types).
DB ExplorerIs a component, which allows access to HANA database objects.
Default currencyThe default currency set in SAP Commissions for payment processing.
Deferred resetA calculation reset stage in which Commissions does not physically delete results data from the database. Instead, the results data is marked as invalid, and can be removed at a later time.
DepositAmount of compensation calculated for a participant for the period in which the calculation was run. A deposit is usually associated with a specific earning group.
Deposit ruleOne of the basic rule types processed by the calculation that make up a variable compensation plan. Deposit rules are processed during the Reward stage to calculate how much of each kind of incentive compensation a participant has earned in a specified period, and when the compensation can be paid.
Direct creditCredit allocated to a participant based directly on a sales transaction, as opposed to allocation based on another credit.
Duplicate creditNamed credit that is derived from the same source transaction or order as an existing credit. When you create a credit rule, you specify whether duplicate credits are allowed.
Earning codeLabel used in deposit rules to differentiate kinds of deposits. For example, you can use earning codes to differentiate types of bonuses within the Bonus earning group. Earning codes are not used during calculation processing; they are passed to external systems, such as payroll systems.
Earning groupA label used to group similar types of deposits into a single payment. Payments of the same earning group will aggregate or offset each other.
EarningAmount of money calculated by the calculation as potential payment, less any amounts previously deposited and paid (or created as a balance) during the specified period.
Effective dateThe start and end dates for a version of an object. Tracks which version of an object and related objects are active. Objects tracked by effective dates are reference data, including participants, positions, titles, relationships, plans, rules, formulas, variables, rate tables, territories, lookup tables, and fixed values.
End datingInvolves changing the effective end date of the last version of an object to a specific date. This should be done when an object is no longer active, but has associated calculation results and cannot be deleted.
Event typeA label on the transaction that describes the type of business event representated by the transaction. For example, you can specify invoice, billing, and shipping as the event type that triggers the processing of a sales transaction.

SAP Commissions exports payments by saving them to an output file for use in an external payroll system. Export occurs in both the Pay stage and Post stage.

You can also import and export compensation rules and rule elements from the workspaces.

EXT SchemaA temporary schema in the HANA database that facilitates data validation, transformation, aggregation, and cleaning for large volumes of data. Customers are allowed to create custom tables and stored procedures in the EXT Schema, but not the TCMP Schema.
Extended attributeAttributes provided for objects when additional attributes are required in addition to the generic attributes. Extended attributes can be renamed, and are displayed on the object.
External credit allocationThe process by which a transaction includes data that specifies to which position, participant, or title it should be allocated. This process is external to the Allocate stage, which normally performs the allocation of credits to position assignments.
FilterTo compare data to user-specified criteria to reject any data that does not meet the filter criteria.
Finalized periodPeriod that is closed to new calculation and posting of payments. A change to a finalized period is reported as a balance.
Finalize stage

Calculation stage in which payments for a period are closed. You can finalize a period for just a position group, in which case no more payments can be generated for that group but payments can still be generated for other participants.

The Finalize stage also converts negative incremental deposits to posted negative balances, unless Commissions is configured not to make negative payments.

Fixed valueA numerical quantity used to represent an amount. Used to store static numeric values for use in different rules. You can specify fixed values to apply only to a specified period. You can use fixed values for a number of purposes, including quotas, target bonus amounts, commission rates, or Boolean (true/false) information.
Fixed value type

The optional, user-defined attribute that can be assigned to a fixed value.

Fixed value types are used to organize fixed values into similar groupings, such as quotas and commission rates.

Flat FileFlat file allows you to specify data attributes, such as columns and data types table by table, and stores the data in plain text format.
Flow GraphA graphical user interface to develop data integration mapping and transformations.
FormulaNamed, reusable object used to store an expression, such as a mathematical calculation. Used most often in conditions and action statements within a compensation plan rule, but also used in rate tables and lookup tables.
Full modeDefault mode for the calculation. Designates calculation of compensation for all positions and transactions in a specified period.
FunctionPredefined, reusable operation used in a compensation rule. Functions are selected in the legal moves list in the Rule Editor or Formula Editor.
Generic attribute

A label used in the initial name of a custom attribute. A set number of generic attributes are provided for strings, integers, dates, and Booleans.

The Administrator can customize these attributes. If a generic attribute is not active, it does not display in the workspace.

HANA DatabaseSAP HANA database, which is used by Commissions for data storage and processing.
HeldFlag set on a credit or deposit that prohibits the object from being processed until a specified release date.
Hire dateDate a participant begins employment at a company or enters into a company’s variable compensation system.

To load data from an external system into a staging area of the repository. You can run validation checks on the data in the staging area before transferring the data to the production tables and running the calculation.

You can also import and export compensation rules and rule elements from the workspaces.

IncentiveThe compensation amount in commissions or bonuses that is calculated by incentive rules during the incentive step of the calculation.
Incentive ruleCompensation plan used to calculate the incentive compensation (bonuses and commissions) for each participant assigned to the plan by comparing measurements or credits to quotas and rates. Incentive rules are processed during the Reward stage of the calculation.
Incremental depositDeposit of earnings based on new or modified transactions and credits.
Incremental ModeCalculation processing mode that designates processing of only those transactions and credit that are new or changed (flagged as runnable) since the last calculation run.
Incremental order credit

An order credit that is the difference between the current, candidate order credit and the sum of previous order credits.

The credit generated from an order credit rule that specifies the creation of incremental credits when duplicate credits occur.

Indirect creditSee rolled credit.
Inline object

An object created during the creation or modification of another object.

For example, you can create new titles from the Positions workspace, rules from the Plans workspace, and formulas from the rules workspace.

IntegerThe base unit type or one of the pre-defined unit types that stores whole number values (positive, negative, or zero values).

Lowest level of a tree structure hierarchy. In relation to category hierarchies, the leaf-level is the classifier. In relation to periods, the leaf level is the smallest period unit in a fiscal year, usually a month or two weeks.

Legal movesList of the literals, functions, data fields, and references that are valid for a compensation rule. You select from the legal moves list when creating the input, conditions, and output of compensation plan rules and formulas in the rule editor.
LiteralLegal move that specifies a static type of data. Literals include date, string, Boolean, duplicate behavior, and unit type.
LocaleSet of parameters that defines a user’s language, country, and any special preferences defined for the user interface. A typical locale identifier consists of a language identifier and a region identifier. Locale sets the display format for date and time as well as currency.
Log fileA plain text file that contains messages generated during calculation runs.
Lookup tableA multi-dimensional table that is a compensation element. Lookup tables are created by the user to store a set of values for use in rules and formulas.
Major period typeThe larger calendar unit that is demarcated in the calendar bar of effective version dialogs. The major period type is displayed as a long tic mark, the minor period type as a short tic mark. You can set the major and minor period types in the Calendar workspace.
Manual credit, deposit, order, or transactionCredit, deposit, order, or transaction that is created rather than calculated or imported into SAP Commissions.
Measurement periodSpecifies the type of period for which the participant should be paid in an incentive rule. For example, if the incentive rule’s measurement period is month, revenue commission rates are applied to the measurements for each month
Measurement ruleCompensation plan rule run by the calculation to calculate measurements for position assignments for a specified period. See primary measurement rule and secondary measurement rule.
Measurement contribution valueThe amount a credit contributes to a measurement. If the measurement is a calculated value, the contribution value is different from the credit value. For example, for a measurement that is 125% of a credit that has a value of 100, the contribution value is 125.
Message logThe log file to which errors and other processing information are written when you run the calculation.
Minor period typeThe smaller calendar unit that is demarcated in the calendar bar of effective version dialogs. You can set the major and minor period types in the Calendar workspace.
ModificationA change to information on an existing record. Often done on organization data, such as changes to the address of a participant. A modification does not create a new record whereas an adjustment does.
ModuleUsed at the command line for import calculation operations to specify the type of data to import.
Negative paymentThe output from a Pay stage that produces a payment liability, or a payment amount with a negative numeric value.
ObjectA data item that the user can view or manipulate. Each kind of object has an associated workspace.
ODATAProtocol for building and consuming REST APIs.
OffsetUsed to refer to a period that is relative to the period being run.
On-demand position processing

Calculation mode configured to enhance performance when processing large volumes of positions by processing positions as needed rather than processing the entire set. On-demand position processing has the

following requirements: all transactions are preassigned and all credit rules are written based on preassigned transactions. It is available for full or incremental runs only.

Order creditA credit that is based on data from specified parts of an order or from the entire order. Contrast with transaction credit.
Order-level functionOne of the functions that summarize data applicable to an entire order.
Organization dataIncludes the following objects: participants, titles, positions, position groups, and relationships. Organization data is tracked by both effective time and audit dates.
ParticipantPerson or organization participating in your company’s variable compensation program. Also called payee. A participant can be either an internal employee or an external company, such as a dealer.
Target compensation

Total compensation that a participant can receive for a given period if all quotas and conditions are met. Typically, on-target earnings have two components: base salary and target variable compensation (such as

incentive compensation, stock option, referral bonus, or a target).

Synonyms for on-target earnings include target annual earnings (TAE), total compensation, and target compensation

Payee preassignmentA credit allocation on a transaction that specifies preassignment to a payee, position, or title. Preassigned transactions are processed through the calculation using preassigned credit rules created specifically to process preassigned transactions. These preassigned credit rules evaluate only the subset of positions that are preassigned with any payee/position/title combination while other credit rules evaluate every position loaded per transaction.
PaymentValue of the total deposit to be paid to a participant in the specified period.
Pay stage

Calculation stage in which the following are calculated:

• For non-finalized periods: payments.

• For finalized periods: balance information.

Any past positive or negative payments or balances are added to the current period payment to produce a payment summary. Input to this stage is compensation amounts for participants for the period of the calculation run (from the Reward stage). Output is available to the Post stage, and is also written to an output file (see export).

PercentThe base unit type that stores values in terms of parts per hundred.

Specified duration of time over which incentives are calculated and paid.

Typically, the leaf-level periods are the 12 months, such as January 2022. Each period has an associated period type.

Period typeDesignation that defines the attributes of a kind of period. Common period types include bimonthly, month, quarter, and year.
Per-credit commission rule

A kind of incentive rule used to calculate an incentive by multiplying the value of each credit in a specified measurement by a rate to produce individual commission amounts for each credit. The rate can be based on a fixed value, a constant, the result of a formula, or a rate table.

Results data from per-credit incentive rules is accessed in the Commission workspace.

Contrast with aggregate credits incentive rule.

Per-position modeCalculation processing mode that designates calculation of compensation for only the positions that are marked as runnable.
PermissionThe level of access to an object or the ability to perform a specified action. For example, a security role can have read permission for participants, but not have create permission for them.
Permission setGrouping of related data or operations. You can apply permissions to individual objects and processes or to entire permission sets.
CalculationProcess model used to calculate compensation and to import external data into SAP Commissions. The calculation is divided into stages, each stage include one or more conceptual steps.
PlanAlso known as a compensation plan; a collection of rules that specify how to compensate the participants assigned to that plan.
Plan assignmentAssociation of a compensation plan to a position with an assigned participant.
Plan dataObjects used to create compensation plans, including plans, rules, formulas, and variables. Plan data objects are tracked by both audit history and effective time.
PositionDefines a specific, unique job in an organization. Positions are generally filled by people, but can be used to represent a company or another entity.
Position assignmentThe relationship created by assigning a participant to a position for a specified period of time.
Position groupA label assigned to a subset of positions for processing during a calculation run (pay, post, and finalize), for example to process different groups at different times in a period.
Position relationshipAn explicit relationship between two positions used for rolling credits and other data. A common type of relationship is the reporting relationship.
Positions incremental modeSetting for calculation processing that designates calculation for transactions and credits that are flagged runnable, then for positions that are flagged as runnable.
PostedA payment or balance that is permanently stored in the repository and marked as read-only. A posted item has been sent out of the system and therefore cannot be updated. Payments and balances are marked posted during the Post stage.
Post stageCalculation stage in which payments and balances from the Pay stage are permanently stored and marked as read-only. Output is available to the Finalize stage, and is also written to an output file. You can have multiple postings in a period (for different position groups) before the period is finalized.
PostexportThe calculation stage that generates the output file containing payments with a status of Posted.
Primary measurementNamed measurement whose value is the aggregate of the credit amounts specified as input to a measurement rule. Each measurement is associated with a specific period.
Primary measurement ruleCompensation rule used by the calculation to calculate an aggregation of credits. Primary measurement rules are processed during the the Allocate stage.
Processing unitAn optional compensation processing feature that enables you to support calculation processing for subsets of data that are partitioned logically within a single Repository. Processing units are defined by the business units assigned to them.
PurgeTo systematically and permanently remove old and unneeded data. The term purge is stronger than delete. For example, in SAP Commissions you can run the Purge stage to remove a particular batch of data from the staging tables after the data has been validated and transferred from staging to production tables.
QuantityA base unit type that stores numeric values, including partial amounts.
QuotaThe target sales amount for a position for a specified period. In SAP Commissions, you specify a quota by creating a fixed value and assigning it to the appropriate participant or plan.
Rate tableTable used to calculate incentive compensation for a step commission, where a transaction is paid at different rates across rate thresholds or tiers.
Reason codeIdentifier created by a user to identify why an action was taken, for example to identify why a manual credit was created.
Reference dataData about the organization required by SAP Commissions before compensation can be processed. Generally, reference data objects have effective dates. Reference data objects include participant and position data, categories, plan data (plans and rules), and rule elements.
Related objectsData objects that refer to one another by way of assignment or inclusion. For example, a participant and a position are related if the participant is assigned to the position, a position and a plan are related if the position is assigned to the plan, and a lookup table is related to a formula if it is included in the formula.
Relationship hierarchyThe roll relationships between positions.
Release dateIn reference to a deposit or credit that is held, the release date sets the date the item can be passed into the calculation processing.
Relative periodA period which is a specified amount of time in the past or future. The relative period is determined by the offset setting.
Remove dateThe effective end date of a versioned object. The object is removed from active status.
Reporting structureThe structure of reporting relationships between positions. Typically mirrors the company’s organization chart.
Rerun positions modeCalculation processing mode that designates first, the processing of transactions associated with positions flagged as runnable, and second, the positions that are related to the runnable transactions. This list is either the same or larger than the list specified by the user. Applies in Classify, Allocate, and Reward stages.
ResetCalculation process that deletes, sets to zero, or nullifies data so that calculation stages can populate the database with new data. There is a reset process associated with each stage and runs automatically when the stage is run. You can also run each reset process manually from the command line.
REST APIConforms to the design principles of the REST, or representational state transfer architectural style.
Results dataData objects generated by a calculation run.
Reward stageCalculation stage in which secondary measurements, incentives, and deposits are calculated. Processes secondary measurements, incentives, and deposits. Input to this stage is credits and primary measurements that are allocated to participants; output is the compensation amounts for participants for the period in which the calculation was run.
RoleA an object made up of sets of permissions that can be assigned to users. Provides control and flexibility in managing users and their capabilities.
Rollable creditType of credit that can be rolled from one position to another. For example, a sales manager can receive commissions based on a subordinates transaction credits, and these credits can be rolled up the reporting hierarchy. A rollable credit is a rolled credit when it is received by others.
Rolled creditCredit that was allocated based on another credit. Typically, a participant receives a direct credit for a transaction, and the manager receives a rolled credit based on his roll relationship with the participant who was directly responsible for the transaction. Also known as an indirect credit.
Roll relationshipAn association of two positions that is used by the calculation in the process of allocating rolled credits. When you create a roll relationship, you specify a roll type, the source position, and the receiver position. You can also specify dates for which the relationship is in effect.
Roll typeSpecifies the type of roll relationship. Can be thought of as a path between positions along which credits can roll between positions of the relationship hierarchy. You can create as many roll types as you need, and give them any name you like. Credits travel along roll relationships of the same type.
Root categoryTop node of a category hierarchy.
RuleA set of statements that tells the system the sequence of actions to perform when defined conditions are met. Compensation plan rules specify how TrueComp Manager calculates credits, measurements, incentives, and deposit amounts for participants who are assigned to the plan.
RunnableAttribute for data items that designates that the item is available for calculation processing. Typically, items that new or changed are marked as runnable.
Secondary measurementNamed measurement whose value is the aggregate of primary measurements or of calculations based on formulas.
Secondary measurement ruleCompensation plan rule that calculates secondary measurements.
StageProcessing block in the calculation. Each stage can be run independently of other stages, and includes data reset and background operations.
Stage hookA feature that allows you to insert custom steps before or after a calculation stage runs. Stage hooks can be Java classes, script files, or stored procedures.
Staging tablesTemporary data storage area where data from external sources is placed during import. You validate data in the staging area before moving it to the production tables.
Step commissionKind of commission structured such that credit is paid at different rates for different levels, based on a rate table. You can structure step commissions to be calculated on the basis of either individual credits or an aggregate of credits for a measurement
Straight commissionIncentive rule that uses a single rate or formula to calculate a commission.
StringSeries of characters, such as a word.
System preferencesConfiguration preferences that control the user, calculation, worker, communication, and import configuration.
TCMP SchemaThe term used for the standard HANA database tables that contain records for core Commissions data, such as Participants, Transactions, and Plans. Used in contrast to the EXT Schema.
TerritoryCombination of criteria, based on categories and classifiers. Used in credit or primary measurement rules to determine who gets credit for a transaction and in measurement rules to determine how credits are aggregated.
TitleGroup of positions related by job function. Titles are used as a way to group similar positions across the organization.
Touchless DeploymentA self-service capability that empowers customers to develop and deploy custom code in the EXT Schema.
TransactionThe original sales (or other event) data, which includes sub-line data (item, who it was sold to, amount, and so on) on an order. Used as the basic unit of data for compensation processing in TrueComp Manager. Transactions are identified by event type, order ID, compensation date,period, and credit type.
Transaction creditA credit that is based on an individual valid transaction. Contrast with order credit.
Transfer stagePart of the import process in which data is transferred from the staging area to production tables. You can run the transfer process for different selections of validated data.
TrialA status that indicates a payment or balance that is temporarily stored until it is posted.
Unit typeLabel that identifies the type of unit a numerical value represents. For example, percent, integer, quantity, or currency.
Validate stagePart of the import process in which the logical integrity of imported data is verified against format requirements.
VariableA placeholder in rules, formulas, and lookup tables to reference a fixed value, rate table, or territory.
Virtual TableA HANA component, which allows read and write of data from external sources.
Web IDEA web browser interface which allows access to HANA database and SDI components.
WorkerProcess that is invoked by the controller to evaluate compensation rules and update information in the database. A worker is invoked for a particular purpose for a single step of the calculation.
WorkspaceDesignated area where related compensation objects are grouped together so that a compensation administrator can perform related tasks from the same place.
Workspace access rightAccess right that allows user to view and open the workspace listed in the Control tab. User must also have read access to the associated data items.

Other Resources and Links

  • OpenSAP Microlearning is a collection of free, short videos on a number of topics, organized into playlists. Many of these topics do some nicely technical deep dives as well.
  • The SAP Community has a discussion board as well as a blog of technical and business level topics under the SAP Commissions tag.
  • SAP Online Help is the definitive online help for all SAP Products. Here you’ll find documentation on all SAP Commissions topics.


Want to get certified? SAP has a Certified Application Associate path for SAP Commissions. Find it in the SAP Training Shop at

Save progress to your learning plan by logging in or creating an account

Login or Register