Name: Creating a Classification Rule in SAP SuccessFactors Incentive Management
Uploaded: 2020-3-2
Duration: 266 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 Classification Rule.

Share feedback

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

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><p>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 Classification Rule. </p></div></div></div></div></div></div>

Creating a Classification Rule in SAP SuccessFactors Incentive Management

Hi, My name is Lily.  In this video, I’ll explain a Classification Rule  and demonstrate how to create one in SAP    Commissions.  If you remember, Classification data refers to    how transaction data is classified and organized  into different buckets.  Classification data is organized in a tree structure with different  categories, subcategories, and classifiers.  This ensures sales reps are accurately compensated.    During pipeline processing in the Classify stage,  SAP Commissions uses the Classification rule to classify valid transactions.  The Classification Rule is the expression used to  match the classifier to the transaction record. Classification rules are required to match a transaction to one classifier  in a given category hierarchy.  If you have several category hierarchies with the same classifier type,  the same transaction can be classified under each category hierarchy,  but not twice under the same one. During the Pipeline run, the Classify stage uses classification rules to  determine how to bundle the transactions,  using classifiers.  The output is classified transactions. The Classification Rule is a Boolean,  true or false, expression in which we match a field, such as Product ID, on a classifier record to a field on a transaction.  It’s the mechanism in which we use a unique identifier,  such as a Product ID, to match a Classifier record to a Transaction being processed.  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.  A classification rule must specify a comparison between a field on the  Classifier record and the same field on the transaction record.   Once the system finds a match,  the transaction gets classified.  Through the use of Territories,  credits for these transactions are allocated  to the appropriate person who receives credit for the transaction. Each company identifies the fields they want to use in the Classification Rule.  These are based on the kind of data/ or factors they use to determine how their transactions are filtered and classified.  And how their sales reps are compensated. Some companies use Product types/ID while  other companies use geographic data such as the region where the product was sold. For example:  billing state on the transaction record  and the state field on the classifier record.   Another example can be based on the channel the product was sold through. Based on what makes the most sense to your business,  you select which fields you want to identify in the Classification Rule.  It’s important that the field that you identify in your Classification Rule  is also the field that has data populated on the Transaction record  when transaction records are loaded into the system.  Note, that the system ignores invalid classification rules.  This is an example of a correct expression:   Transaction.Product ID =Product.Product ID. Now, I’ll show you how to create a Classification Rule  that tells the system how to match a Transaction to a  Classifier using the Classification Rule.  I previously created the classification hierarchy.   From Plan Data, I’ll click on Classification.    I’ll select a Category.  I’ll select a Category.  I’ll scroll down and click the pencil icon in the Category Hierarchy Details pane.  Then, I’ll click the Expression box within the Classification Rule box.  In the first placeholder, I’ll type Trans  and select Transaction.Product ID.  This tells the system to look at the transaction record  and look for the product ID field.   In the second placeholder, I’ll type and select the equal sign.  This tells the system to look for an exact match. And in the third placeholder,  I’ll type Prod and select Product.Product ID.  This tells the system to find the product record and look for the ID field.  Now, I’ll save.   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!