Business Cases for Using Custom Segments in Rebates
To better understand how custom segment preference works, consider the following example.
If your account has 2 custom segments defined with the following default values:
-
CS1 = val1
-
CS2 = val2
; these custom segment values are set on the preference record.
Then, consider the following 2 transactions are created with different values for custom segments CS1 and CS2:
-
transaction#1:
-
CS1 = val3
-
CS2 = val4
-
-
transaction#2:
-
CS1 = val5
-
CS2 = val4
-
Case 1:
The preference or box is not checked or cleared.
Result:
When rebate transactions are created for the 2 transactions, the custom segment values on the rebate transactions will be taken from the Custom Segment Preferences page or preference record, not from the source transactions.
|
Rebate Transaction |
Class |
Location |
Department |
CS1 |
CS2 |
|---|---|---|---|---|---|
|
RT#1 (from transaction#1) |
C1 |
L1 |
x |
val1 |
val2 |
|
RT#2 (from transaction#2) |
C1 |
L1 |
x |
val1 |
val2 |
Number of groups when accrual is generated = 1
Number of groups when settlement is generated=1
Case 2:
The preference or box is checked.
Result:
When rebate transactions are created for the 2 transactions, the custom segment values on the rebate transactions will be taken from their source transactions.
|
Rebate Transaction |
Class |
Location |
Department |
CS1 |
CS2 |
|---|---|---|---|---|---|
|
RT#1 (from transaction#1) |
C1 |
L1 |
x |
val3 |
val4 |
|
RT#2 (from transaction#2) |
C1 |
L1 |
x |
val5 |
val4 |
Number of groups when accrual is generated = 2
Number of groups when settlement is generated=1