By Thomas Thuresson
July 26th, 2018
The setup is straightforward, and Oracle has made it easy to add the new target dimensions.
Create New Target Application
A new Target Application type is now available in the Target Application setup.
You can use the Prefix to add multiple versions of the same dimension type, such as adding two Custom dimension types for two different custom dimensions.
The system creates a target dimension for each dimension type and creates a list of the most common dimension properties.
Only the Member Name, Parent and Alias properties are enabled by default, but you can easily enable more properties or add more properties that are not automatically created.
The metadata load functionality uses the standard FDMEE (Data Management) data tables and allows for 23 properties for each target dimension (ACCOUNT, ENTITY, ICP, UD1-UD20).
Once the required target applications (dimensions) are created you follow the standard Data Management setup routines to create new Import Formats, Locations, and Load Rules.
Make sure that the File Type is one of the “All Data Type” options when creating the Import Format for the source file.
Create a new Location that uses the new Import Format and Switch to the newly created location using the POV toolbar to create a new Data Load Rule.
Notice that the Target Plan Type is CUSTOM, not one of the application cubes.
Also, make sure to set the target Dimension Name.
Now all that remains is to add mapping for all the enabled properties.
If your source file contains the correct properties you wish to create all you need to do is add a * to * map for each “Dimension”.
If more advanced mappings are required, the full set of Data Management mapping functionality is available.
Since this new feature is built upon the standard Data Managing (FDMEE) functionality, you execute these metadata loads the same way you would run a data load. The loads could be manually executed or fully automated using EPMAutomate.