Dillema in selecting Delta Specific Field

[Former Member]

Hi Gurus,

I have stuck in a situation and would heavily appreciate your help.

I have created a Generic datasource ZAFRU which extracting data from AFRU table.

I used Last Changed On (LAEDA) as delta specific field but later i found it is not working because more than 50% of records dont have last changed on date (LAEDA) in it.

So, later i used Posting Date (BUDAT) as delta specific field but still facing a problem. Like, suppose there is a service order which is posted three months ago but changed 5 days ago so delta will not capture the changed record as posting date (BUDAT) is not changed but only Last Changed On date (LAEDA) is changed.

In this way i am not able to use either fields as delta specific fields.

Also, can't use timestamp for delta specific field as it is not present in AFRU table and Document number also as it is blank for all the records.

Please suggest what should i use in delta specific field so that i should not miss any record in BI.

Thanks,

Saurabh

[Former Member · Accepted solution]

Hi saurabh,

Use ERSDA LAEDA,BUDAT fields in AFRUand make pseudo delta (say past three days , past seven days)on them. This should not miss any record.

Speak with functional people when and how LAEDA,BUDAT are populated IN AFRU to track the changes in confirmation entries accordingly you can use the fields.

Thanks

Vamsi

[Former Member · Accepted solution]

Vamsi Talluri,

Thanks a lot for your quick and precise reply.

Just one thing, will you provide me the brief explanation of Pseudo Delta and exactly which fields i should include in the pseudo delta ?

also i have kept DSO as intermediate to load data ultimately to cube so repeated records shoul not cause any problem.

your help would be greately appreciated.

[Former Member · Accepted solution]

Hi Saurabh,

First enable selections for ERSDA,LAEDA,BUDAT for the datasource on this table. Create three infopackages and write below routines on ERSDA,LAEDA and use these to the DSO. Even they are repeated it won't be a problem.

Once you write below code for an infopackage on say field ERSDA so what all the confirmations created from today to past 7 days will be coming into DSO.

Similarly for LAEDA and BUDAT.... also we create another two infopackages and load similarly every time to DSO which makes that no record to be missed.

data: l_idx like sy-tabix,

l_sdate type SCAL-DATE,

l_edate type SCAL-DATE.

read table l_t_range with key

fieldname = 'ERSDA'.

l_edate = sy-datum.

l_sdate = l_edate - '7'.

l_t_range-low = l_sdate.

l_t_range-high = l_edate.

l_t_range-sign = 'I'.

l_t_range-option = 'BT'.

l_idx = sy-tabix.

*....

modify l_t_range index l_idx.

p_subrc = 0.

Regards

vamsi

Edited by: vamsi talluri on Jul 13, 2011 7:43 PM

[Former Member · Accepted solution]

Thanks a lot Vamsi Talluri.

this has solved my problem and i have successfully loaded data with three infopackages.

have assigned points to your valuable efforts and response.

[former_member804850 · Accepted solution]

Dear Mr. Saurabh and Mr. Tamsi,

If use that pseudo code, whether I must change Extraction Mode to Full or still let it be Delta?

Thanks and BR,

Clement A. S.

[Former Member]

hi,

You will need to create a new Z field to enable delta capabilities for the custom DS.

Go through the following links

this may help you

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c062a3a8-f44c-2c10-ccb8-9b88fbdcb...

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf...

regards,

Arvind.