Last updated on JULY 24, 2017
Applies to:Oracle Fusion Absence Management Cloud Service - Version 220.127.116.11.0 and later
Oracle Fusion Absence Management - Version 18.104.22.168.0 and later
Oracle Fusion Benefits Cloud Service - Version 22.214.171.124.0 and later
Oracle Fusion Benefits - Version 126.96.36.199.0 and later
Oracle Fusion Global Payroll Cloud Service - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Many application modules use Fast Formula extensively to implement fairly complex calculation logic. For example Absence Accruals, Compensation Formulas, Payroll, Benefits, ...
Often the formula logic needs to be driven by flags or needs to take into consideration constant variables.
At present such values have to be hard-coded into the fast formula and if they change the formula has to be adjusted and recompiled.
This creates a significant risk if a mistake is made.
The requirement is to store such values outside the formula in a system setting and the formula to read it out at run time.
The only option to do something like this is currently to store it in a Common Lookup, or a User-Defined table.
Both have significant disadvantages: No duplicate meanings in lookups, LDG limitation for UDTs.
Instead it should be possible to store such values in Profile Options.
Provide a Fast Formula Function that reads out a system profile option.
Profile Options are configured via the tasks "Manage Profile Options" and "Manage Administrator Profile Values", and are stored in tables/views FND_PROFILE_OPTIONS_VL and FND_PROFILE_OPTION_VALUES.
The function should take the Profile Option Code and the effective date as parameters as well as a default value in case the function would have returned NULL.
The formula name could be something like GET_PROFILE_OPTION_VALUE .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms