OBIA comes with a set of domain values, dependent on the bi app that will be implemented. These domain values are distinct sets of values/codes that act as conformed warehouse code sets. In the sense, that multiple sources can map their codes to warehouse specific codes (source independence); thus, giving the ability to utilize multiple sources with one code set. The OOTB domain value sets are used to create and calculate prepackaged metrics which are used in OOTB reports. Now there are cases where the source data can not be easily mapped to a domain value or the list of available domain values does not fit your model and you wish to extend the list of available domain values to map to. In prior OBIA implementations, this was done via files. Starting with OBIA 18.104.22.168+ which uses ODI this is now controlled and done within CM (Configuration Manager) and/or FSM (Functional Setup Manager). However, some domain value sets do not allow you to extend or add new domain codes. This leaves you with just the OOTB list of values which you may or may not like. The solution I propose will allow you to add values to these none extensible domain value sets.
NOTE: This is not supported by Oracle. Use at your own risk. Basically there might be OOTB measures that are using these DW code/value pairs in pre-built metrics. With changes to these non-extensible domain values, one can potentially break these pre-built metrics and OOTB reports. Any changes will need the RPD metrics and OOTB reports to be analyzed and modified accordingly.
The RCU schema XXX_BIACOMP houses these domains and their members (or value lists). The workaround to make a non-extensible domain extensible, so that it’s value list can be changed and used in Functional Setup Manager, is the following:
- Launch Configuration Manager in browser: http://<host>:9704/biacm
- Log in as bi apps admin user: (ie. biadmin)
- Navigate to Domains Administration -> Manage Warehouse Domains
- Search for your Offering and Domain in question
- Note the Code for the Warehouse Domain that needs to be extensible.
- Now log into the XXX_BIACOMP schema, using the XXX_BIACOMP user.
- Run the following DML to enable the domain. Use the Code noted from step 5:
SET EXTENSIBILITY_TYPE_CODE = ‘E’
WHERE DOMAIN_CODE = ‘<WAREHOUSE DOMAIN CODE>‘;
8. Log back into Configuration Manager, and navigate to Domains Administration -> Manage Warehouse Domains.
9. Search for the warehouse domain to modify. Select the warehouse domain within the Warehouse Domains pane.
10. In the lower pane, Warehouse Members, click the (+) icon to create the new domain member code(s). This icon will now be enabled. Note: At this time, there are no easy ways to delete/remove members from domains, without hacking into the database. So it is not advised.
11. Now, these new members are available for mapping to source codes using either one of the following two ways
a. Navigate to Domains Administration -> Manage Domain Mappings and Hierarchies. Search for the domain(s) that were changed. You will observe existing OOTB source domain codes mapped to corresponding warehouse codes and also any new source codes, which have not been mapped. You can finish mapping source to warehouse domains here.
b. Change/modify source to warehouse domain mappings in Functional Setup Manager via implementation projects .