Clarification Regarding the Use of APIs in Oracle Advanced Benefits (OAB)
Last updated on AUGUST 08, 2017
Applies to:Oracle Advanced Benefits - Version 12.1 HRMS RUP9 and later
Information in this document applies to any platform.
Customer would like to use the “ben_elig_dpnt_api.process_dependent_w” API to update covered dependents after they have been defaulted to a plan in a different plan type to check the “Covered” dependent checkbox.
Given that we are using an Oracle API, would this be supported? If not, what would not be supported – the records touched by the API, or OAB as a whole?
Customer would like to understand better what and why the use of published API’s in OAB is or is not supported.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms