ODI Series Part 1

7/23/2019 ODI Series Part 1

http://slidepdf.com/reader/full/odi-series-part-1 1/46

ODI Series Part 1

Now that HAL has really ended its shelf live what to people turn to, well I see a lot of peopleassuming that EPMA must be the answer and end up wishing they have never taken that route If

you load hierar!hies from files or manage them straight from a repository then "#I $"ra!le #ataIntegrator% !ould be the way you want to go, it offers all this fun!tionality and so mu!h more

"#I sits in "ra!le fusion middleware suite of produ!ts and basi!ally it&s an E'tra!t Load and

(ransform $E)L(% tool, it used to be owned by *unopsis until it swallowed by the hungry +aws of

"ra!le It has built in !onne!tivity to all the ma+or databases and now has the added bonus ofEssbase and Planning adaptors whi!h !an be plugged straight into it

"#I in!ludes something known as nowledge Modules that are !omponents, whi!h !ontain theinformation for "#I to perform a spe!ifi! set of tasks against a spe!ifi! te!hnology su!h as

Planning

(here are - different types of Ms and some have already been !reated for use with planning

and essbase

The types of KMs you are likely to encounter are :

• RKM (Reverse Knowledge Modules) are used to perform a customized reverse-engineering ofdata models for a specific technology.

• LKM (Loading Knowledge Modules) are used to etract data from the source data!aseta!les and other systems (files" middleware" mainframe" etc.).

• #KM (#ntegration Knowledge Modules) are used to integrate (load) data to the target ta!les.

Enough or the blurb I am going to try and !over off how you !an use "#I with planning and

essbase though as it is .uite an in)depth topi! I am going to break into down into se!tions thoughstarting today with Installation and part of the !onfiguration

/irst of all you will need to download the "#I installation pa!kage from edelivery, $"ra!le #ataIntegrator, "ra!le #ata Profiling, and "ra!le #ata 0uality for #ata Integrator 12g $121342%

for 5indows Platforms $6#% 7 482M%

The Planning and Essbase ODI adaptors from edelivery Oracle Data Integrator !dapter for "yperion Planning #elease $%&%'%' Installation files

Oracle Data Integrator Kno(ledge Module for Essbase #elease $%&%'%' Installation files

Updated 26/10/08 - I suggest installing ODI Version 10.1.3.4. or a!o"e# t$is %ill $a"e all

t$e latest updated &'s and in(ludes all ne((essar) dri"ers# i* )ou install t$e pat($ )ou %ill

not need t$e Planning/+ss!ase ODI Installation *iles.

Do%nload Version 10.1.3..0 *or all t$e latest &'s



I have set up "#I against a 931 environment before but this time I am going to put it against a

11 environment, the setup shouldn&t be any different though I am hoping adapter files will still

work as I have not seen any for 11 yet

If you are using *0L server as I am for the database repository then you will also need :#;6

drivers, I am going to use the <228 drivers, whi!h !an easily be downloaded from Mi!rosoft

=ou will need :>E 14? $"#I has :>E 14< in!luded% or :# 18? if you are going to use the

5eb servi!es of "#I I intend to demonstrate the web servi!e fun!tionality to run "#I +obs so Ialso download tom!at $version 88 or - is fine% for the web server and A'is< as the web servi!es

!ontainer $It has to be A'is< and version 1< and it is easiest to get the war version%

(he installation of "#I is very simple +ust double !li!k the setupbat inside the @setup@5indows@dire!tory you will be warned if your ma!hine does not pass the pre)re.uisites "n!e in the

produ!t sele!tion !hoose B"ra!le #ata Integrator 121342C, !hoose !omplete whi!h +ust means

the !lient and the server will be installed and sele!t the "#I home and that&s pretty mu!h it

Ne't step is to !opy over the drivers into the odi file stru!ture $@"raHomeD1@ora!ledi@drivers%

If you are using *0L server !opy over s.l+db!+ar

/or essbase !opy over all the +ar files from the drivers dire!tory of B"ra!le #ata Integratornowledge Module for Essbase >elease 9311 Installation filesC

>epeat for Planning, some of the files will already e'ist so +ust keep the latest ones

*o you should have something like this

(o use "#I you will need to !reate two database repositories these are known as the Master

>epository and the 5ork >epository(he Master holds the stru!ture of the different types of te!hnologies, se!urity and version

management of pro+e!ts and models

(he 5ork holds all the information on data models, pro+e!ts and how they are used

If you are using "ra!le grant s!hema user !onne!t and resour!e, for *0L server I +ust made them

dbo



"n!e the databases have been !reated you !an !reate the "#I master repository

Now be!ause I am using s.l server <228 I had to manually enter driver and url string as "#I

only in!ludes preset values for s.l server <222 If you are using "ra!le you !an easily sele!t#river and +ust update the >L

5e now have our Master repository !reated so we !an move on into the topology manager $Idon&t think I will ever get used to that name%

(he topology manager lets you manage all your te!hnologies su!h as essbase and planning, sosay for planning it is where you set up the !onne!tion details to your planning app $or in odi

speak #ata *erver%

5hen you start up the topology manager you have to !onne!t to a Master >epository,unfortunately this is more manual work entering all the :#;6 details again

6li!k the new button when the se!urity repository !onne!tion window opens

=ou need to give a login name, whi!h !an be anything and a username and password, the default

is *PE>FI*">G*N"P*I*



" we are in and the first thing we need to set up is the work repository and you guessed it yet

more entering of the !onne!tion details (here is a tab at the bottom of the topology manager

with BA;C on it that means repositories

Insert a new work repository and enter all the details in the definition and :#;6 tabbed window



5hen you !li!k test you will be asked to pi!k an agent, you !an +ust !hoose Lo!al $No Agent% for now, details on agents shortly =ou will then be asked for a name for the work repository and an

id, the id !an be any numeri! value, I have always left the (ype as development the other option

is E'e!ution

In the topology manager the Hyperion Essbase te!hnology has already been in!luded but the planning needs adding in o to the first tab and !hoose to import topology

Lo!ate the impe'p folder of the planning installation files



All being well Hyperion Planning should then appear in the te!hnologies list

5ell that is it for this session as I said I want to try and break it up into lots of bite sie !hunks

instead of one endless blog

Ne't session will be setting up of the agent and then !onfiguring some of the te!hnologies su!h

as planning



ODI Series Part 2 - ,$e gent

"k, so "#I is installed so we are now going to look at setting up an agent

An agent is a +ava servi!e that a!ts a listener on a designated t!pGip port, the agent allowse'e!ution of sessions su!h as model reverses, pa!kages, s!enarios and interfa!es, you will learn

about more of these later

=ou !an set an agent up to run as a windows servi!es or from a bat!h s!ript, I am going to show

both methods

/irst of all you need to lo!ate and edit the file odiparamsbat that resides in the "#I bin dire!tory

(he se!tion you need to update is after remrem Repository $onnection #nformationrem

pdate the #river and >L to mat!h your "#I repository you should be used to doing this now(he username and password are a!!ount details for the Master repository, you noti!e you have to

enter an en!oded password, and there is a bat!h utility in the bin dire!tory that will en!ode

passwords for you

pdate the "#ID*E6D5">D>EP to mat!h the name of your work repository that you set upin the topology manager

=ou !an leave the "#ID*E> and pass alone if you have not !hanged the se!urity for "#I



(o start the agent you will +ust need to !reate a simple bat!h s!ript

(he port !an be set to anything you like as long as you know it won&t !onfli!t with anything else

Ne't add another s!ript to stop the agent

;efore you !an start the agent a few more additional !onfigurations are re.uired in the topology

manager

/irst you will need to insert an agent and give it a name, enter the host and the port you defined

in the bat!h s!ript

=ou !an&t a!tually test yet as the agent is not running

Ne't I am going to !reate a !onte't, a !onte't is basi!ally a way of grouping different

!omponents together, so you !an have say a development !onte't whi!h will bring together!ertain te!hnologies, databases, appli!ations and agents(here is already a global !onte't available but I like to always set e'tra ones up for fle'ibility,

the !onte't se!tion !an be a!!essed from the se!ond tab



/inally a logi!al agent needs to be !reated whi!h defines the link between the agent and the

!onte't

"n!e this is !ompleted you should be able to start up the agent

:ust to be sure the agent is a!tually working you !an go ba!k and test it from the topologymanager



5ell that&s all well and fine but some people like to have everything running as a windows

servi!e, as long as you have updated the odiparamsbat then it is simple

:ust make sure you !reate the servi!e with the same physi!al agent name and the same port as

you set up in the topology manager

=ou !an !he!k the servi!e is running by opening the agentservi!elog in the bin dire!tory

"ne thing to wat!h out for is that if you "#ID:AFADH"ME is set to a dire!tory with spa!es, if

you are +ust using the default install then you will be fine otherwise you will need to add .uotes

to the +ava !onfig in the odiparamsbat file

set %&#'*'+,+%&#'*'/%M+0!in01ava.eeset %&#'*2'+,+%&#'*'/%M+0!in01avaw.eeset %&#'*$'+,+%&#'*'/%M+0!in01avac.ee

3o

set %&#'*'+,+4%&#'*'/%M+0!in01ava.ee4set %&#'*2'+,+4%&#'*'/%M+0!in01avaw.ee4set %&#'*$'+,+4%&#'*'/%M+0!in01avac.ee4

"n!e the servi!e has been installed remove the .uotes

5ell that !ompletes another session, ne't time I will looking at !onfiguring the topology

manager to point to a planning appli!ation, essbase database, file dire!tory and s.l databasetables before we move on to the designer



ODI Series Part 3 - ,$e (on*iguration (ontinues

Part 3 has arrived and I !an go through the remaining !onfiguration elements inside the topologymanager (he goal is to be able to loadGe'tra!t hierar!hy details from files and !sv files and

database tables into Planning and essbase, to do this we need to set up !onne!tion details toessbase , planning, s.l database and a file store It is going to be s!reen shot heaven today as

sometimes it e'plains mu!h than words !an

/ire up the topology manager and straight into the Physi!al ar!hite!ture tab I will go through

ea!h te!hnology in alphabeti!al order so we start with the file set upIf you going to write to or load from files in "#I you need a define a physi!al lo!ation, for this

e'er!ise the files are going to be in EJ@/ile*tore

If you e'pand /ile you will see that there is already #ata server !reated !alled /ILEDENE>I6,

I am going to ignore that and set up a new one

>ight !li!k and BInsert #ata *erverC

$A physi!al !omponent that stores and returns data is defined as a #ata *erver A data server is

always linked to a single te!hnology%

ive the #ata *erver a name



Added <KG29G2K /or the :#;6 tab you need to have the following driver settings J)

"n!e you hit apply the physi!al s!hema window will appear, this is where you enter details forthe lo!ation of the files and set up the !onte't details

An "#I Physi!al *!hema !orresponds to a pair of s!hemasJ A $#ata% *!hema, in whi!h "ra!le #ata Integrator will look for the sour!e and target data

stru!tures for the interfa!es

A 5ork *!hema in whi!h "ra!le #ata Integrator !an !reate and manipulate temporary work

data stru!tures asso!iated to the sour!es and targets !ontained in the #ata *!hema

=ou need to manually enter the lo!ation into the #ire!tory $*!hema% and the #ire!tory $5ork

*!hema%, most s!reens in "#I are default s!reens so no matter what te!hnology you are using

you will be presented with the same options, so don&t worry if you keep asking the .uestion5hy

I have not found a re.uirement yet to use different values between the data and work s!hema

(here is no su!h fun!tionality as browsing to the file lo!ation so make sure you enter the details!orre!tly



Ne't you need to point it to a !onte't, setting up a !onte't was !overed in the last part Add anew !onte't, you will noti!e that the !onte't that was set up earlier is populated as we made it

default, if you have a number of !onte'ts you !an manually sele!t a different one /inally we

need to provide a s!hema name where information will be stored in the repository

"nto Essbase, I am going to set up a !onne!tion to *ampleG;asi!, it is pretty mu!h the same as before only when you insert the data server you will have to enter the essbase server !onne!tion

details

"ne thing to be aware is not to hit the test button this is only for use with :#;6 !onne!tions sowill fail for produ!ts like essbaseGplanning

/illing in the physi!al s!hema is all manual, so don&t e'pe!t the drop downs to populate with



appli!ations and databases (his is one of the problems with "#I you never really know if you

have got things right until later on be!ause you !an&t test and there is no auto populating

*etting up the planning details is pretty mu!h similar but you must put the >MI port ne't to the

server details, the default port is 11333 I am setting up a !onne!tion to my sample appli!ation$plansamp%



(he ne't te!hnology to set up is a !onne!tion to a database so I !an a!!ess and write to tables, for

me it will be the Mi!rosoft *0L *erver te!hnology but it is very similar for "ra!le set up I have

set up a database !alled Hyp#ata "n!e again it is pretty mu!h the same sort of setup but thistime you enter the :#;6 !onne!tion details and yes you !an even hit the test button



As this time we are using a :#;6 !onne!tion when you set up the physi!al s!hema you !an don&t

have to manually enter information the drop down bo'es are auto populated, the only differen!e

is you have to sele!t the database name and the owner

6reate a name for the logi!al s!hema

"k, the final te!hnology we have to make !hanges to is the B*unopsis EngineC, this is thete!hnology that !an be used when you are transforming data, so for e'ample from a fields from a

flat file and mapping to a planning fields(he te!hnology is already set up and you +ust have to point it the !onte't to it



5ell the !onfiguration is done for what we trying to a!hieve, depending on how you are going to

use "#I will no doubt in!rease the number of te!hnologies you will use, it is a pretty powerfultool and we are +ust tou!hing on the surfa!e that may suffi!e for most users

(hat !on!ludes today&s session, ne't we will move on to the real !entre of the produ!t thedesigner, where we !reate the interfa!es to move the data to and from planningGessbase



ODI Series 4 - +nter t$e Designer

Another blog and yes more "#I, today the designer !omes in to play (he designer is where you perform the main integration work eg loading hierar!hies from flat files or database tables into

planning or transforming data before it is loaded into essbase (he designer stores all thisinformation in the work repository

(he main elements to the designer are models and pro+e!ts a model is a set of datastores

!orresponding to data stru!tures !ontained in a physi!al s!hema In a model you will perform the

reverse engineering for instan!e reverse)engineering the dimensions and properties from a planning appli!ation into a readable !olumn format (he >M $>everse nowledge Model% for

planning should have already been downloaded $see the first part of the "#I series to find out

what you need%

A pro+e!t is a group of ob+e!ts developed using "#I, the !omponents to a pro+e!t areJ)

Pa!kagesJ) A pa!kage is a se.uen!e of steps organied into a flow diagram, so say you wanted to

wait for a file to arrive, load it into a planning dimension, push it to essbase and then send a

su!!essful or failure email then the pa!kage is the pla!e for this

Interfa!eJ) An interfa!e is really a set of rules that define the loading of a #atasour!e from one or

more sour!e #atastores, an e'ample of an interfa!e is load members into planning dimension

Pro!edure J) A pro!edure is a reusable !omponent that groups operations that do not fit into the

interfa!e !ategory, for e'ample sending a bat!h of files through /(P

Fariable J) (his is a value whi!h is stored in "#I, this value !an be set or evaluated to !reate!onditions in pa!kages, it is pretty mu!h what you would e'pe!t a variable to be

*e.uen!e J) A se.uen!e is a variable automati!ally in!remented when used

nowledge Modules 7 I des!ribed these in Part 1 of this series so if you need a refresher +ust

have a .ui!k look ba!k

=ou will get a mu!h !learer understanding of the different !omponents as we start to use them

(he first time you start the designer you will have to set up the !onne!tion to the master

repository and work repository, you should be pretty used to this by now and I promise it is thelast time you will have to do it It is the same as when first set up the (opology manager



(he first ob+e!tive I have set myself to a!hieve in the designer is to load dimension informationfrom a flat file into the sample planning appli!ation, if you have been following then you willhave already set up !onne!tion information to planning and to the flat file dire!tory in the

topology manager

;efore we start make sure you have e'tra!ted the M files $*tart MD% from the impe'p

dire!tory in the downloaded installation files

"ra!le #ata Integrator Adapter for Hyperion Planning >elease 9311 Installation files

MDIM *0L to Hyperion Planning'ml

MD>M Hyperion Planning'ml

"ra!le #ata Integrator nowledge Module for Essbase >elease 9311 Installation files

MDIM *0L to Hyperion Essbase $#A(A%'ml

MDIM *0L to Hyperion Essbase $ME(A#A(A%'ml

MDLM Hyperion Essbase #A(A to *0L'mlMDLM Hyperion Essbase ME(A#A(A to *0L'ml

MD>M Hyperion Essbase'ml

E'tra!t them to "#IDH"ME@ora!ledi@impe'p

(his is +ust so all the knowledge modules are stored in one pla!e and simpler for importing

"n!e you are in the designer, the first thing to do is !reate a new pro+e!t



=ou will noti!e most of the !omponents I des!ribed earlier have been !reated

At the moment all we are going to do is import the re.uired Ms, right !li!k the pro+e!t name

$"#ID#EM"DP>":E6(% and sele!t Import nowledge Modules *ele!t the folder"#IDH"ME@ora!ledi@impe'p and a full list of the Ms available should be displayed

As the first ob+e!tive is +ust to use a flat file and planning we will re.uire the following Ms>M Hyperion Planning $reverse engineer the planning appli!ation%

LM /ile to *0L $load data from a file to a temp area using *0L, the temp area is !ontrolled bythe *unopsis memory manager%

IM *0L to Hyperion Planning $move the data from temp area and load it into the planning

repository using *0L%

=ou may have been wondering what the format of your flat file needs to be and this is where the

>M for planning !omes in, setting up the >M is done in the models area

/irst you need to !reate a models folder, it is nothing more than a folder and lets you maintain



your models 6li!k the Models tab then Insert Model folder $first button% and finally give it a

name

Ne't step is to insert a model, the first model to set up is a data store to hold all the reverse

engineering of the planning app dimensions, when you insert the model you have to name it and

!hoose the te!hnology, in this !ase it will be Hyperion Planning, on sele!tion the logi!al s!hemawill be populated with the s!hema named you applied in the topology manager

Now on to the reverse tab, this is where the !lever M will be used to reverse engineer the

planning dimensions

*ele!t 6ustomied !hoose the !onte't and Logi!al agent $all of these have been set up from the

previous "#I blog%*ele!t >M Hyperion Planning from the M dropdown it will have the pro+e!t name appended

to it



Apply the !hanges and !li!k >everse and let the M does its magi!

How do you know it has !ompleted 5ell a !ouple of ways, +ust wat!h task manager and wait for

the 6P pro!ess to !omplete or offi!ially look in the "perator, now you shout what the hell isthe "perator (he operator is basi!ally a I that displays the status of e'e!utions from "#I and

are !arried out through the use of the Agent

I am not really going to go into any more detail about the "perator until later in the series when

most of the integrations are !omplete, but for now you !an a!!ess it from the start menu or

dire!tly from ea!h "#I appli!ation, in the designer 7 5indows O "pen Module O "perator

*o it looks like our reverse has !ompleted su!!essfully



If you e'pand the model you see ea!h of the available dimensions have been reversed and pla!edin a datastore with the same name as the dimension, there is also an e'tra store for the #A

At present you !annot reverse engineer or load to =earGPeriodGFersionG*!enario that is +ust like

HAL

:ust to point out I have a !ouple of o!!asions where the reverse says it has !ompleted but not all

the dimensions in the datastore have been populated, if this is the !ase +ust run the reverse again

E'panding a datastore su!h as A!!ount and then !olumns, the fields that !an be populated will be

displayed



(his is where is should start to !li!k in your mind what you are trying to a!hieve, from a flat file

you want to populate some of the above fields whi!h will then be loaded into your planning app,whi!h fields you populate is up to you but obviously A!!ount $member%GParent are re.uired if

you don&t populate the other fields then defaults will be used

Most of the fields are self)e'planatory and relate straight to planning, if you have ever used HAL

they will be very familiar If you have never used HAL then the one that stands out the most is

the "peration field

"peration !an have the following values

pdate 7 (his is the default and is used if not populated, it Add, updates, moves the member being loaded

#elete Level2 ) #eletes the member being loaded if it has no !hildren

#elete Ides!endants7#eletes the member being loaded and all of its des!endants

#elete #es!endants7#eletes the des!endants of the member being loaded, but does not delete the

member itself

:ust a slight deviation but I am +ust going to demonstrate what happens when you have not set up

the !onne!tion to the planning app in the topology manager, I +ust renamed the planning app

from plansamp to plansamp1 in the topology manager and ran the reverse again

I have found with "#I that sometimes the error messages are pretty obs!ure, this one is one ofthe better ones B(he appli!ation plansamp1 is invalidC gives you a rough idea, though this is the

first opportunity that you have had to !he!k you set up the !onne!tion !orre!tly

*o now we have reversed our dimensions a !sv hierar!hy load file !an be !reated If you like you

!an +ust !reate a file with headings that relate to all the reversed fields



/or an e'ample say I was going to add the following member as a !hild of a!!ount

(he !sv file would look like this J)

/rom this you should be able to build up a file to mat!h your planning appli!ation pretty easily,

on!e you have !ompleted the file make sure you save it in the file store dire!tory you set up in

the topology manager, in my !ase BEJ@/ile*tore@A!!Load!svC

Now we have to !reate a model and datastore that will pi!k up the file

6hoose /ile as the te!hnology and !hoose the logi!al s!hema you !reated originally in the

topology manager



In the reverse tab sele!t your !onte't

Insert a new #ata*tore and give it a name and if you !li!k browse for file button it should open

up in the !orre!t dire!tory and you !an sele!t the !sv file

In the files tab as we are using a 6*F file then !hoose /ie /ormat as delimited, the file has a

header row so it was set to 1, the field separator was set to other and as a !omma $,%

If you have been following this guide then you may have to go ba!k into the topology manager

as I forgot to set the :#;6 options for the /ile set up, I have !orre!ted the previous blog but this

is what you need to make sure you have set



;a!k to the designer, !li!k the 6olumns tab then the >everse button and all being well the file

stru!ture should be retrieved

"ne thing to wat!h out for if you are using formulas, the physi!al and logi!al length is set to 82

and formulas !an easy surpass that so you will need to in!rease the length and in the reverseddimension !olumn set up whi!h is defaulted to K2

"k we have !reated the sour!e and target elements so now we have to put them together to bring

them together and this is done by !reating an interfa!e, ba!k to the pro+e!ts tab and insert a new

interfa!e



ive it a name and make sure the !onte't is sele!ted, ne't !he!k B*taging Area #ifferent /rom

(argetC and !hoose B*N"P*I*DMEM">=DENINEC

(his allows any transformations between the sour!e and target to be handled by the memory

engine, an e'ample being if you have a !olumn header named (; in the sour!e file and in the planning target it goes to (ime ;alan!e then the memory engine will handle this mapping

"n to the #iagram tab, this is where you drag and drop you sour!e and target datastores, its

!ertainly not the best graphi!ally designed se!tion and I remember thinking it was hideous the

first time I saw it

/irst drag you A!!ount /lat file datastore from the models window into the sour!e window and

then drag the reversed a!!ount dimension datastore into the target window, sele!t yes for the

automati! mapping 5hat this will do is automati!ally map the !olumn headings of your file tothe target planning dimension, if you !reate the file with e'a!tly the same headings as the

dimension properties then you will have less work to do

Anyway you should end up with this lovely looking organised window



:ust stret!h the windows to make it more appealing and understandable

Now we have to map the remaining sour!e and targets, the ones that have been mapped willshow as red in the sour!e, btw the B*C in the sour!eGtarget windows stands for *tring as all the

fields we are using are *tring based In the target window the members that have been

automati!ally mapped will be displayed with an i!on that stands for *our!e so basi!ally meaningthe sour!e is the same as the target

(o map, !li!k on a name in the target window, this should display the mapping window below,

ti!k the BA!tive MappingC bo' and in the implementation window enter the 3 digit name of thesour!e and the !olumn name, so for the (arget of BAliasJ #efaultC the implementation window

will have A66C#efaultDAliasC, finally !li!k the B*taging AreaC button, as we need to use the

sunopsis memory engine to perform the mapping

If you like you don&t have to manually enter the name, you !an !li!k the BLaun!h E'pressionEditorC and sele!t from the window



(he e'pression editor has a whole raft of fun!tions that !an be used but you won&t probably use

them for basi! mappings

(he pro!ess needs to be repeated for the remaining sour!e properties

=ou !an also for!e the value in the target mapping to be a fi'ed value, so say everything wasgoing to be put against a B*our!e Plan (ypeC of 6onsol you wouldn&t need that in your sour!efile and you !an +ust enter the value into the mapping like so J)

If you are going to do this make sure the BA!tive MappingC bo' is ti!ked and e'e!ute on the

staging area is sele!ted

"n!e you have !ompleted all the mappings !li!k on the /low tab and a diagram should be

displayed outlining the pro!ess, if you !li!k on the (arget there are a number of options availablelike setting up error logging and the ability to refresh to essbase after the load has !ompleted



After applying !hanges you !an e'e!ute the interfa!e and the data in the file should be loadedinto planning, you !an !he!k in the "perator to see how the pro!ess went

=ou should also !he!k the log files that were generated, you may see this is the log

<22K)29)<K 13J18J24,129 #E; #wg6mdE'e!ution(hreadQJ Number of !olumns in the sour!e result set does

not mat!h the number of planning target !olumns

I wouldn&t worry about the message, as it is not really an error

In planning your member$s% should have been loaded



*o there we go we have !ompleted the ob+e!tive of loading information from a flat file into a

planning dimension, from here you should be able to do the same for other dimensions

I am going to wrap it up there for today, hopefully it all makes sense and you !an go off and

!reate your own load interfa!es

Ne't time I will look into loading data from a *0L table to planning and look at what !an be

a!hieved with "#I and essbase



ODI Series Part - S to Planning

(he "#I series !ontinues, we are already up to part 8 and still lots to !over In the last part welooked at loading hierar!hies into planning from flat files but there are many o!!asions when the

metadata !an be sour!ed from database warehouses (oday I am going to !over loading metadatadire!tly from db tables into planning

In part 3 I set up a !onne!tion to *0L server and to a database named hypdata, if your warehouse

is "ra!le then it is pretty mu!h the same set up +ust using different :#;6 drivers

/or this e'er!ise I have set up two simple db tables one !ontaining the parentG!hild entity

information and the other !ontaining the member properties

Now there are a few methods of getting them loaded into planning, the first and simplest is to

!reate a view in *0L server or "ra!le to +oin the tables by the !hildGmembers fields

I need to insert a new model in the "#I designer to point the *0L server te!hnology



=ou have the option of manually inserting the datastores to point to the db tablesGviews or you

!an reverse everything from the Model >everse tab

/or some reason it didn&t reverse the Fiew so I +ust !he!ked Fiew, un!he!ked (able and reversed

again, this time it reversed the view

"k ni!e and easy, we +ust need to !reate an interfa!e to load the data from the view into the planning entity dimension

:ust before we do this we will need an e'tra nowledge Module, we will need a LM $Loading

M%, we previously used BLM /ile to *0LC but this time we are loading using *0L

Import M from the Pro+e!t window in the #esigner and !hoose BLM *0L to *0LC



And it should appear in your LM list in the designer

Insert a new interfa!e

Name it set the !onte't and the staging area, whi!h on!e again we going to be using the

B*unopsis memory engineC

In the #iagram drag the Fiew as the sour!e and the planning entity dimension as the target, mapthe fields and you should end up with something like the image above

In the HIE>DMEM;E>* table and HIE>DFIE5 view there is a dimension field, !urrently thereis only Entity information in there but say we started adding e'tra dimension member



information then the above interfa!e would try and load data that is not re.uired for entities

(his !an be easily resolved without having to go ba!k and !hange the view and to be honest!hanging the view wouldn&t be a good idea be!ause we would end up with a view for ea!h

dimension

(his is where filters !ome into play, in the diagram sour!e window drag the dimension field off

the window and this will !reate a filter, then you +ust need to set the filter to value in our !ase it

will be entities

(o !he!k the filter is !orre!t you !an !li!k the B6he!k the e'pression in the #;M*C button that

is on the right hand side of the implementation window =ou !an also !reate filters on the view in

the model tab

=our flow diagram should look like this



I manually added information for the log details in the "ptions window, this time I have also set

the >E/>E*HD#A(A;A*E to =es so after the metadata has been loaded into planning it will push it down to essbase

E'e!uting the interfa!e produ!ed no errors in the log and opening the outline in EA* displayedthe new members so the refresh worked fine

As I said early there were a few methods of loading from two tables one being with the use of a

view, now say you didn&t have a!!ess to the *0L repository to !reate a view or for some reason itwasn&t deemed the right solution then you !an a!hieve the same results by !reating the +oin from

within "#I

(o a!hieve this !reate a new interfa!e and fill in the definition tab in the same way as before, in

the diagram tab drag and drop both datastores HIE>DMEM;E>* R HIE>DP>"PE>(IE* into

the sour!e window

Now in the sour!e window drag 6HIL# from HIE>DMEM;E> onto MEM;E> in

HIE>DP>"PE>(IE*, this will !reate a +oin between the datastores =ou !an then +ust drag the

planning entity dimension into the target and map all the fields

And the final flow diagram should look like



I know this is .uite a simple e'ample but hopefully it does start to show what !an be done with"#I and generate a few ideas how you !an in!orporate it into your own solutions

I am going to leave it there for Planning and ne't time I will move on to using "#I with Essbase,

I will start to look at reverse engineering a database outline and output to different formats



ODI Series Part 6 - Data load to planning

:ust as I thought I would be leaving planning and "#I alone for a while a .uestion has poppedup on the "ra!le forums that is probably easier to answer through a blog

;asi!ally the .uestion is how is it possible to load data into planning that has a member type of

(e't I did skip a blog about loading data into planning through "#I be!ause I felt that it is probably more appropriate to load data dire!tly into essbase using the essbase Ms, no matter

whi!h method you use it all ends up in essbase anyway

*eeing as the .uestion has been asked I will show how data !an be loaded using the planning

M and then move on to the (e't problem

As usual I am going to demonstrate on the planning sample appli!ation so it !an be easily

repli!ated 5hen you load data into planning you first need to set what the data load dimension

will be plus you will need a driver dimension and its members you want to load data for

I am going to set A!!ount as the #ata Load #imension and use *egment as the #river dimension

against member BMP3C

(o do this !hoose Administration O #ata Load Administration from planning web

If you are interested in what happens when you hit save then basi!ally it writes information by

ob+e!t id into the planning app db table H*PD#>IFE>DMEM;E>

*o with a .ui!k bit of *0L

=ou !an output the information you entered into planning web

Anyway on!e you have set these details you !an follow the reverse engineering pro!ess for a



planning appli!ation $if you need a refresher look HE>E%

I !reated a new Model to generate the reverse for

After running the B>everseC you will have e'tra !olumns in the A!!ount #ata*tore than if youhad not set up the data load settings in planning

http://john-goodwin.blogspot.com/2008/09/odi-series-4-enter-designer.html





(he e'tra !olumns areJ) B#ata Load 6ube NameC whi!h defines whi!h essbase !ube you willload the data to, BMP3C 7 this is the *egment member whi!h we set in driver dimension set up

and BPoint)of)viewC whi!h is used to hold the remaining dimension !ombinations for the data

load

I added three a!!ount members Musi!*ales1 7 3 all with the data type of (e't $=ou don&t have

to set the member as te't this is +ust ready for the ne't blog on loading te't data%



Also I made sure that A!!ount was sele!ted in BEvaluation "rderC as otherwise you will not be

able to use the te't fun!tionality in web forms

I !reated a .ui!k form to display data against the new members and for *egment MP3, now I !an

produ!e the flat file

As I pi!ked the data load dimension as A!!ount then the data needed to be by a!!ount, !olumn ;is the B#ata Load 6ube NameC whi!h in this !ase is the !onsol database, the P"F was set to the

remaining dimension members ea!h seperated with a !omma J)6urren!y J) Lo!al

Entity J) N=

Period J) :an*!enario J) A!tual

Fersion J) /=2K

(he final !olumn !ontains the data and is against MP3 as we set that as the driver dimensionmember

"k, ba!k to the "#I developer and set up a new #ata*tore



I !reated this as a !hild of a flat file Model and pointed the >esour!e Name to the 6*F file

/ile /ormat of delimeted, the file has a row heading so that was set to 1, /ield *eperator was set

as a !omma $,% and the (e't #elimeter as .uotation mark $B% be!ause the 6*F file has !ommas in

it to separate the P"F members and e'!el pla!es .uotation marks around the field

(he reverse generated the !olumns from the !sv file



A new interfa!e was !reated, applied the !onte't and set the staging area as the B*unopsis

Memory EngineC

"n the diagram tab, I dragged the #ata*tore for the !sv data load file into the sour!e window and

dragged the planning app #ata*tore for A!!ount on the targetEa!h !olumn in the sour!e was mapped to the target using the staging area for !olumns that havea different name between the sour!e and the target

(he flow diagram should resemble the above



"n!e I had e'e!uted the interfa!e and !he!ked the output log for any errors I ran the form again

to !he!k the data had been populated !orre!tly

*o there we go a .ui!k overview on how to load data into planning using "#I, I !an now move

on ta!kle the problem of loading te't data, stay tunedS



Documents

ODI Series Part 1