Name: Creating a Classification Rule in SAP SuccessFactors Incentive Management
Uploaded: 2025-6-27
Duration: 242 s
Description: In this video, you’ll learn what a Classification Rule is and how it relates to Classification Data. You will also learn how to create a new Classification Rule.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>In this video, you’ll learn what a Classification Rule is and how it relates to Classification Data. You will also learn how to create a new Classification Rule.</div></div>

Creating a Classification Rule in SAP SuccessFactors Incentive Management

Hello and welcome. In this video, I'll explain what the classification rule is and demonstrate how to create one in SAP SuccessFactors Incentive Management. If you remember, classification refers to the way transaction data is classified and organized into different buckets. Classification data is organized in a tree structure that consists of categories, subcategories and classifiers. For example, let's say that BikesInMotion wants to use classification data to determine if a transaction is a sale of a mountain bike. Here we can see that in the classification hierarchy this product ID is a mountain bike. We want to make sure every transaction with this product ID is associated with this classifier record. The classification rule is a boolean expression used to match a transaction to a classifier. It's the mechanism in which we use a unique identifier to match a classifier record to a transaction. In the example here, the identifier is the product ID, but we could also use the customer ID, postal code, or any other identifier depending on the type of data. This rule is invoked during the Classify stage of the calculation process. The output is classified transactions. Classification rules match a transaction to a single classifier in a category hierarchy. If you have several category hierarchies with the same classifier type, such as products, the same transaction can be classified under each category hierarchy, but not twice under the same one. It is important to define the classification rule to avoid transactions not getting classified. If the classification rule is left blank, the system won't classify transaction data. It's also important to ensure that the field on the transaction is populated when records are loaded into your system. Let's take a look at what constitutes a valid expression for a classification rule. While classification rules can be very simple or very complex, they should always evaluate to a field on the classifier on one side and a field on the transaction on the other. For example, this classification rule is looking for a match between a transaction and the product hierarchy using the product ID as the match field. Let's see how this classification rule is created. Starting from the home screen under manage plans, I'll choose Plan Data, then select Classification. I'll select the Classifiers tab, Then I'll select Product Tree. Now I'll choose the three dots on the toolbar, then select Edit to edit the hierarchy. The classification rule will go in the expression field. To create the rule, I'll open the window editor. In the first placeholder, I'll enter transaction and select transaction.productID from the dropdown. This references the product ID field on the transaction record. In the second placeholder, I'll enter an equal sign and select it from the drop-down. This tells the system to look for an exact match. And in the third placeholder, I'll enter product and select product.product ID. This tells the system to retrieve the Product ID field on the product record. To close the window editor, I'll choose the checkmark. Finally, I'll save the changes. I've now created a classification rule that tells the system to match a transaction to a classifier when the product ID field on the transaction record matches the product ID field on the classifier. Thanks for watching!