COPA Delta

[Former Member]

Hi,

I am using delta enabled COPA datasource to extract copa data into BW. In our delta que(RSA7), COPA datasource is not accumulating any new or changed delta records. After a full load, I have successfully initialised delta and I can see the COPA datasource in RSA7. Can someone tell me what are the steps for a successfull delta method.

Thanks,

Rao.

[Former Member]

If a DataSource implements a delta process that uses several characteristic values, the record mode must be a part of the extract structure and the name of the corresponding field must be entered in the DataSource as a cancellation field (ROOSOURCE-INVFIELD).

[Former Member]

Simulate Initialization of Delta Process using KEB5 transaction and read <u>following SAP provided information thoroughly before you start doing this:</u>

You can use this function to simulate the initialization of the delta procedure for a DataSource and to set the time stamp of the DataSource to a desired value. You can then plan an InfoPackages for delta updates.

Note: Only use this function in the cases described below. Inappropriate use can cause irreparable inconsistencies in your data in the SAP BW.

The simulation occurs as follows: the system sets the DataSource status to "Update successful" and gives it the time stamp you entered. A data package is also logged with the interval 0 to that time stamp. This data package sends 0 records to the SAP BW.

It makes sense to simulate the initialization of the delta procedure under the following circumstances:

You want to perform an initial test in the SAP BW using just a reduced amount of transaction data so that you can view reports with data from your CO-PA DataCube, for example, without having to replicate several million data records in the SAP BW.

In this case, set the DataSource time stamp in the Date and Time field to a date a few weeks ago.

Apart from executing this function, you also need to make the following settings in the SAP BW to simulate the initialization of the delta procedure.

a) In transaction RSADMIN in the SAP BW, enter your name in the field User for whom the debugging mode is active.

Consequently, the indicator Update data in the source system immediately in the tab page Update parameters in the InfoPackage Scheduler is then unlocked for entries.

b) Create an initialization InfoPackage and deactivate the indicator Update data in the source system immediately for this InfoPackage. In this way, you stop the system from immediately processing the request IDoc in the source system.

c) Start the initialization InfoPackage.

d) In the monitor, set the overall status for this InfoPackage to "OK" (green light).

You want to continue a delta replication from a different DataSource. This is sometimes necessary (for example, after an upgrade from R/3-Release 3.x to 4.5) if you wish to use the new option for updating multiple valuations (transfer prices). You then need a DataSource containing the valuation category (VALUTYP) as well as the currency type (CURTYPE).

In this case, simply copy the time stamp from the old DataSource by entering the name of that DataSource in the field from a different DataSource. Then continue the delta replication from the new DataSource.

Note: The initialization of the delta procedure must also be simulated in the SAP BW for the new DataSource. To do this, follow the points a) thru. d) described above.

Hope this is helps; please assign points if it does...thanks

A.Ramasubban

[Former Member]

Good example

[Former Member]

Hi Nandakumar,

We use cost_based Datasource in this particular operating concern. I am assuming this is delta enabled datasource. All I did was selected the required fields from segment and item level tables and replicated into BW. I did not do anything regarding to delta functionality because I am assuming this delta functinality is taken care by OLTP suystem. I don't know, are there some settings that I have to set in OLTP system before I initialize? I appreciate your help. Thanks

Rao.

[Former Member]

Hi Rao,

Please review the link below.

https://www.sdn.sap.com/sdn/developerareas/bi.sdn?contenttype=url&content=/irj/servlet/prt/portal/pr... to set up connection co-pa - extraction

Hope it helps,

Sree

[Former Member]

Hi Rao,

I feel your datasource uses TimeStamp Management Delta process.

Enable the time stamp using KEB5 transaction

hope this will hlep you

Regards,

A.Nandakumar

[Former Member]

I have a question too. Suppose a COPA load is happening to BW system on a daily schedule. The delta fails on a day. Since it is COPA load, we need to rectify the error soon and continue with the rest of the loads. One method was suggested by one team memebr is to force the load to red, delete the request from the target, try a re-load of the delta. If successful, load the delta again for a zero number of records. Is this the correct method? My doubt is if the COPA loads are based on a time stamp, the failed delta also has a time stamp set, isnt? So where I can check for the time stamp? transaction code or table etc.. ? How I make sure of the correct load, that I ddnt miss any data between the last(failed) load and the later load? Can I do something on the timestamp entries? ?How can I analyse the problem with the load?

An earlier reply would be appreciated.

Thank you.

Treeza

[Former Member]

COPA-extraction does not use the delta queue. COPA-delta is based on a timestamp, which is updated after each delta extraction. The COPA-DataSource reads the COPA-tables directly.

[Former Member]

Can you tell elaborate about the timestamp you followed for delta method, and which COPA datasource you are using Cost Based or Account Based..

Regards,

A.Nandakumar

[Former Member]

RSA7 does not necessarily show records for all the datasources. For details refer to OSS Notes 380078

Hope this helps