cancel
Showing results for 
Search instead for 
Did you mean: 

need help on using T-code KEB5

Former Member
0 Kudos

In this transacation,

I found that the delta method for COPA data sources can be changed from generic delta to time stamp mgmt in Profitability Analysis.

<b>But it displays warning</b>

This function is only available for DataSources with time stamp mgmt

in Profitability Analysis.

It changes the internal control information on the DataSource.

<b>Improper use can create data inconsistencies that cannot be resolved</b>.

First read the appropriate notes about using this function that are

found in the Extractor IMG.

I read the notes , but couldnt quite understand much,

plz give your inputs if anybody had used this t-code before.

plz look what i am trying to achieve, look at my previous thread

<b>

How to edit copa data source or change delta method.Need t-code/procedure</b>

/community [original link is broken]

0 replies -((

thanks in advance

<b>points will be assigned for inputs</b>

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Ravi,

Generic Extraction is used to extract data from COPA tables. And delta method used to extract delta records (records created after initilization) is timestamp.

What is this timestamp?

Assume that, you have posted 10 records one after the other to the COPA tables. And we do initilization to move all these 10 records to BW system. Later another 5 records are added to COPA tables. How do you think the system identifies these new 5 records (delta records).?

It identifies based on a timestamp field (eg : Document created on ,a 16 digit decimal field).

Assume that, in our previous initilzation, say "document created on" field for the last (or the latest) record is 14/11/2006, 18.00 hrs. and timestamp is set to the 14/11/2006, 18.00hrs. then when you do delta update, the system treats all the records with "document created on" field is greater than 14/11/2006, 18.00 hrs as delta records. This is how new 5 records are extracted to bw system and timestamp is again set to the new value besed in field in the records.(say 14/11/2006, 20.00hrs)

Assume that, you have two records with "document created on" field as 14/11/2006, 17.55hrs and 14/11/2006, 17.57hrs. and they were updated to the COPA table after 14/11/2006,20.00hrs (at this time last delta load is done) due to some reason. How can you bring these two records? For this, purpose we can reset the timestamp at KEB5. In this eg, we can reset as 14/11/2006, 17.50 hrs) and do the delta again. So, the system picks all the records which are posted after 14/11/2006,17.50hrs again. But remember that, doing this, you sending some of the records again (duplicate records). So, make sure that you sending ODS object. otherwise you end up with inconsistant data due to duplicate records.

Hope this helps!!

Vj

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

What is the exact scenario you are working on. This transaction usually has 2 uses and that too for datasources with timestamp management.

1. For testing: If you only want a reduced amount of transaction data in your test BW server, you can set the init process to be successful till a near date and then start pulling in delta.

2. Suppose you want to shift to another delta enabled datasource from the current delta enabled DS you are using. In this case the timestamp of the first is entered for the switch.

If you can explain in detail what you are looking for, could suggest usage.

Rgds

Neeraj