Skip to Content
author's profile photo Former Member
Former Member

Multiple Delta Infopackages after transport - ODS to cube

Hi All,

We have recently run into an issue when transporting our Delta infopackages that update our cubes from an ODS. Here is our current scenario:

Billing ODS --> UPDATES --> Billing Weekly Cube

We created a new Billing Daily cube, so our new scenario is:

Billing ODS --> UPDATES --> Billing Weekly Cube, Billing Daily Cube

Problem is, the system generated Delta infopackage that updates from ODS to cube only had the Billing Weekly cube selected as its data target. So in order for the infopackage to update our new daily cube, we changed it in our DEV system to update into all data targets. When we transported to QA, we end up with two system generated infopackages, one with the old settings (which only updates the Billing Weekly cube) and one with the new setting (update all data targets). We cannot delete the old infopackage because we only have the one infopackage in DEV.

This process to update from ODS to cube is also part of a process chain. Currently the process chain only updates the Billing Weekly cube, where we want it to update Billing Daily as well. So the chain appears to use the old infopackage, instead of the new one.

If anyone can offer assistance, it would be greatly appreciated.

Thanks

Charla

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 18, 2007 at 07:48 PM

    Modify the process chain and include the new info package that loads the new cube.

    Ravi Thothadri

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      In a previous posting, I've learned that you can just maintain the infopackage in any system to update all data targets with data from the ODS, therefore this is what we will do.

      Charla... please gimme points :P.

      John

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.