Imagine a rate component that is only eligible if the current taxpayer has two tax types. This rate component would need the following eligibility rules:
Taxpayer has real property taxes, and
Taxpayer has personal property taxes.
These rules require only one eligibility group on the rate component. It would looks as follows:
Group No. |
Group Description |
If Group is True |
If Group is False |
1 |
Has real property AND personal property taxes |
Apply rate component |
Skip rate component |
The following criteria will be required for this group:
Group 1: Has real property AND personal property taxes |
|||||
Seq |
Field to Compare |
Comparison Method |
If True |
If False |
If Insufficient Data |
10 |
Algorithm: check if taxpayer has real property taxes |
= True |
Check next condition |
Group is false |
Group is false |
20 |
Algorithm: check if taxpayer has personal property taxes |
= True |
Group is true |
Group is false |
Group is false |
Both criteria are similar - they call an algorithm that performs a logical comparison. These algorithms are a bit counter intuitive (but understanding them will provide you with another way to implement complex eligibility criteria):
Both criterion works as follows:
Field to Compare. We chose a "field to compare" algorithm that checks if the current account has obligations that belong to a given set of tax types. It returns a value of True if the taxpayer has an active obligation that matches one of the tax types in the algorithm. In our example, the "check if taxpayer has real property taxes" algorithm returns a value of True if the taxpayer has at least one active obligation whose obligation type references the real property tax type. The "check if taxpayer has property taxes" algorithm is almost identical, only the tax type differs. Refer to RECF-SRVTY and RECF-AUTOPAY for examples of this type of algorithm.
Comparison Method. We simply compare the value returned by the algorithm to True and indicate the appropriate response.
Bottom line. The "field to compare" algorithm isn't actually returning a specific field's value. Rather, it's returning a value of True or False. This value is, in turn, compared by the "comparison method" and the group is set to true, false or check next accordingly.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]