Skip to Main Content

E-Business Suite

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Utilizing Priority Rule Set in Account Rules for Mapping

Tauseef RasulMay 4 2022

This is for Accounting Hub Setups for Oracle Financials. We are using mapping sets to be used in Account Rules. Our condition requirement is if there is no result coming from mapping sets used in priority 1 then only proceed to priority 2 evalution. We are not able to find a way to achieve this using user defined formula or accounting rule within accounting rule as well. Also we cannot use default approach in mapping sets due to requirement explained below (Rule "When * is used in one of the input sources, subsequent input value must also be *" cannot be applied):
Target Segment Priority Rule / Mapping Set
Department segment in Cloud 1 - Department - Based on legacy Account, legacy Dept and legacy Location
Department segment in Cloud 2 - Department - Based on legacy Account
Department segment in Cloud 3 - Department - Based on legacy Department & legacy Location
Department segment in Cloud 4 - Department - Based on legacy Location
Department segment in Cloud 5 - Department - Default
In priority rule 1, we want to evaluate account, dept and location from legacy (stored in mapping set as an example) to see if new cloud department can be derived. If not then move to rule 2 which is derive based on legacy account. If still not derived then move to rule 3 which is derive based on legacy department and legacy location and so on.
Essentially our condition requirement is if there is not result coming from mapping sets using in priority 1 then only proceed to priority 2 and so on. As you can see due to the way priorities are we cannot use default legacy value approach in mapping sets as its does not follow the rule "When * is used in one of the input sources, subsequent input value must also be *".
Is there any other functionality available that can help achieve this?

Comments

Processing

Post Details

Added on May 4 2022
1 comment
156 views