Flex Code Groups Cannot be Migrated with the Configuration Migration Tool
(Doc ID 2385099.1)
Last updated on MARCH 29, 2019
Applies to:Oracle Health Insurance Claims Adjudication - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Flex code groups are an important tool to create sub sets of flex codes. These subsets are important to validate data in dynamic logic. However these groups cannot be migrated from one environment to another. Manual maintenance in each and every environment is error prone and time consuming. The implementation guide does not list this object as being "migratable", but it would be a great enhancement to the system if it was.
The current process is:
1) Create a flex code definition and flex codes.
2) Create a flex code group based on that flex code definition and add a subset of the available flex codes to that group.
3) The group cannot be migrated from one environment to another with the configuration migration tool.
The desired result for an object that is configurable, and even has a predefined method in dynamic logic, is for that object to be available as configuration migration object as well.
Use case: A flex code definition was created with all the country codes. For certain products service is only allowed in specific countries or regions. Since a region can contain a large list of countries, a flex code group is used to represent a region. The content of that region can now only be maintained manually in each and every environment!
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document