Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Description:
This Document shows step by step Process to load Meta data
and hierarchy from different data sources to Planning.
History:
Version Description Author Publish Date
Change
0.1 Initial Draft Gourav Atalkar 23-Jan-2011
Step: 4) Click on Save it will ask you to create physical schema press ‘OK’.
Step:5) In Technology Tab go to Hyperion Planning expand it and select newly create data
server Right Click and select ‘New Physical schema’.
Step: 8) Click on Save it will ask you to specify the context press ‘OK’.
Step: 9) Go to the Logical Architecture tab Expand Technologies and select Hyperion
Planning Right-click and select ‘New Logical Schema’.
Step: 12) Go to the ODI Designer and create new Project with appropriate name.
Step: 13) Click on ‘Save’. You can check in the project tab
Step: 14) Expand project go to knowledge module right click and import following
knowledge modules.
Step:19) Go to the Reverse Engineer tab select customize check box and enter details as
follows:
Step:21) Newly created Model will be available for Reverse Engineering go to Model tab
select Hyperion planning model and Right Click and select Reverse Engineers. Before
Reverse Engineer the models make sure your agent services are running if not start it with
following command:
C:\oracle\Middleware\Oracle_ODI1\oracledi\agent\bin>agent –NAME=localagent
Step: 23) Go to the Operator Tab check whether the Execution run successfully or not.
If all the checks are green that means your model reversed successfully.
Step: 24) Go to the Designer and open model tab expand Hyperion planning model again.
You can check all the dimensions are visible there from your planning application.
Once you have completed the file make sure you save it in the file store directory you set up
in the topology manager, in my case:
“C:\oracle\Middleware\Oracle_ODI1\oracledi\Demo\Planning\Account_Dim_Load.csv”
Now we have to create a model and datastore that will pick up the file. Insert a new
DataStore and give it a name and if you click browse for file button it should open up in the
correct directory and you can select the csv file.
This allows any transformations between the source and target to be handled by the
memory engine, an example being if you have a column header named DS in the source file
and in the planning target it goes to Data Storage then the memory engine will handle this
mapping.
Go to mapping tab first drag you Account Flat file datastore from the models window into
the source window and then drag the reversed account dimension datastore into the target
window, select yes for the automatic mapping. What this will do is automatically map the
column headings of your file to the target planning dimension, if you create the file with
exactly the same headings as the dimension properties then you will have less work to do.
Once you have completed the entire mappings click on the Flow tab and a diagram should
be displayed outlining the process.
After applying changes you can execute the interface and the data in the file should be
loaded into planning, you can check in the Operator to see how the process went.