Delta Initialization

[henry_jones]

How do you determine when/if you need to "freeze" R/3 when you are initializing the delta for new content (Example: We are going to use A/P Business Content. Do I need to bring down the R/3 side, so that no transactions are run while we are loading the data for the first time? Why/ Why not?

[Former Member]

Hi,

The need to prevent transactions in OLTP system depend on the type of deltamechanism used by the specific data source. Some deltamechanism such additive sources like 0CO_OM_CCA do not need downtime because the additive architecture allow transactions during initialization. Others like LIS* need a "sleeping" system. The need for sleeping system is in general determined by the complexity of data scenarios (UPDATES, DELETES, INSERTS).In controlling You only find INSERT operations which simplyfies the deltaarchitecture considerably where as Sales And Dist. You can delete, update and insert data in many different ways, which means it is very complex to handle changes in source data during init load.

[Former Member]

Also, there is safety delta of about 2 hours which means any changes done prior to 2 hours will only be written to delta queue.

There is no standard way of knowing whether to take the system down for init, but if you are curious you can do the test in test system: while init is going on, try to change or post additional documents for A/P, you will not face any issues.

[Former Member]

What is your BW version?

For A/P, there is no need to bring down or lock-users just for doing init.

[henry_jones]

I'm using version 3.1... but how do I determine if I need to bring it down for other installs or versions...

...Thanks