Turn off auto update data target from ODS object after init load?

[Former Member]

BW Forum,

We began loading ODS object 0CCA_O09 (CCA line items) to feed 0CCA_C11 recently. The ODS object properties were set to automatically activate the ODS data and then automatically update the data targets (0CCA_C11). We later decided against automatically updating data targets, instead choosing to load infosource 0CO_OM_CCA_9 to 0CCA_C11, 0CCA_O09 and 0COOM_C02 concurrently. We left the automatic activation of the ODS data on.

However, after I migrated the change to disable automatically updating data targets, 0CCA_O09 still continues to send a delta or an init to the CCA_C11 cube when we load data. The auto update of data targets was turned off, yet the delta continues. I deleted the initialization from the data mart, and the next time it sent a new initialization. Consulting note 712916 talks about this being normal (new init sent if init not found).

How can I turn off the automatic update of data targets once they were turned on? I thought transporting the ODS setting change would take care of this, but the auto data update continues.

We're using BW 3.3 SP 15 on Oracle 9.2.0.3.

Thanks for your time and consideration!

Doug Maltby

Anyone else

Message was edited by: Douglas Maltby

[Former Member]

Did you check to see if the transport was successful in changing the ODS setting?

[Former Member]

Yes, I verified the transport was successful in turning off the setting in the ODS object. The "Update data targets from ODS object automatically" checkbox is unchecked (empty).

[Former Member]

Another silly question: are you loading the ods via an existing process chain (the follow up load to cube step is in this PC)? If not, the last thing you might want to try is to create a new infopackage to load this ODS. Call SAP if this does not work!

[Former Member]

At this point, Joe, there are absolutely no silly questions.

Yes, the ODS is loaded via the existing process chain. Since the other CO cubes (0CCA_C11 and 0COOM_C02) are loaded concurrently from the same infopackage that loads 0CCA_O09, there is no need to follow up a load from the ODS to the cube in the process chain. However, I understand that there MUST be a type "Update ODS Object Data (Further Update)" process behind process "Activate ODS Object Data". All it has in the variant is the ODS object. It is not intended to send a delta load to the CCA_C11 infocube.

Also, I took your suggestion and have inserted a brand new (not copied) delta infopackage to load the ODS object. I can't find any subsequent processing buried in the original infopackage, but a new one certainly eliminates that possibility. I can't load it immediately since it's in production and we're in the middle of a heavy BPS planning cycle, but have inserted & activated the new package in the production process chain.

Thanks for the idea, Joe.

Doug