6 Responses to “10 Important Things to Improve ODI Integrations with Hyperion Planning Part 2 (Procedure Loop)”

  1. Thanks, I have recently been looking for facts about this subject for ages and yours is the best I have located so far.

    • Hi Johnetta how are you? Thank you very much for your comments sorry for the delay to answer you, we are in a middle of a huge project that is taking our life always. We’ll try to put more good posts sooner.

  2. […] Then you may loop this scenario for any number of applications as you may see in our post about it here. […]

  3. […] it continues its tasks. To accomplish that, we would need to create an ODI procedure and use the command on source/target technique to select ODI_JOB_B and its children that are currently running. It would look like […]

  4. […] export the correct object. So here we will use two of our favorite techniques to make it dynamic: Command on Source/Target and ODI metadata repository SQL. This is how it works: we will create an ODI procedure that will […]

  5. […] with one of the best features that ODI has (if you read our blog, you know that we just love it): command on source/target. Let’s create a procedure and add our SQL statement in the command on source […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: