Regarding Pseudo delta or delta enabling in generic datasource

[Former Member]

Hello,

I am on a support project and have been asked to analyse an infopackage which bring data for header only. Datasource is based on FM which has few fields including one date - created on field only.

Base table is VBAK which has ( ERDAT and AEDAT ),

how can I enable delta now ? I don't think it's possible on ecc side now as FM is already there.

Can I do something at BW side ? Please help and also can I see any improvement in IP runtimes after enabling Psuedo delta or I need to split IPs based on range as DS is full only.

thanks and regards,

Aman.

[FCI · Accepted solution]

You either handle the delta :

• on the ECC side by activating it at the dataSource level and by adjusting the code of the MF.
• on the BW side by playing with the selections on the creation and modification dates at the infoPackage level (supposing they are available as selection).

[Former Member · Accepted solution]

Thanks Frederic.

It's been proposed that data source won't be touched at ECC side ( It has only created on date and no changed on date include ) and so I think it won't be possible to implement pseudo delta at BW side because of no 'changed on' date ?

Also, another query : if we split the IPs into different smaller IPs based on range , will it reduce the runtime to some % ? We are looking to implement delta along with reducing IPs runtime.

thanks and warm regards,

Aman

[FCI · Accepted solution]

Yes, with no changed date, no possible delta.

The impact of splitting the IP depends on the ABAP you code on the ECC and BW side. It normally can't hurt (if you don't split tool much). Will it bring some benefits ? Yes if you parallelize the execution of the IP (taken into account the available ressources on the ecc and the BW side).

[Former Member · Accepted solution]

Thanks Frederic,

As of now we are planning to split IPs into 4 IPs based on Sales order number range and see how it goes without coding on BW or extra coding on ECC DS.

For delta, now I have to propose addition of "changed on" field in data source as no other option is there left.

Again thanks for all the points and clarity.

regards,

Aman

[former_member534639]

Hi,

I would bear in mind that "created on" is not necessary a timestamp (looks like only dd-mm-yyyy), and hence is not a very good criteria for selection. if you have na timestamp, then its ok though.. a logic such as

if last_tmstp < current_time + x ...

x would be the safety interval. Generic DataSources and similar are not my expertise, hence I just wanted to add this point above..

Cheers!

[Former Member]

Any updates..please..