Full load IP & Delta load DTP (BI 7.3)

[saravanan_a]

Hi Experts,

Data flow  of my scenario is source to cube (transactional data).

IP --> full load

Corresponding DTP --> delta load

Data source : 0CO_OM_WBS_7 (WBS Elements: Commitment Line Items)

Here DTP load is functioning as full load & not as delta. So data getting accumulated in the cube after each run, thus resulting in data inconsistency.

I would like to know why DTP delta functionality is not working? Or did I miss something here? Please clarify.

[saravanan_a · Accepted solution]

Thanks All for clarification..

Can we use delta IP & full load DTP in any scenario? Is this possible/recommended?

I want to confirm from you guys..

Regards,

Saravanan.

[anshu_lilhori · Accepted solution]

Hi,

Full DTP will combine all the PSA request into one single request every time.

Suppose your PSA is having 5 requests out of that 4 are already loaded and 5th request needs to be updated then if you run DTP in full mode it will combine all the 5 requests into one request and load to the target.

In case of delta DTP it will only take the request which needs to be updated so in the above scenario it will only load the the 5th request.

If your target is dso and all the keyfigures are in overwrite mode then full DTP will not create a problem,but in case of cube it will keep adding the same so it is not recommendable.

I would advice you to give a try on this on your own system for better understanding and you will register that forever.

Hope that helps.

Regards,

AL

[saravanan_a · Accepted solution]

Thanks Anshu.. I will try in system as suggested.

[RamanKorrapati · Accepted solution]

Hi,

When your data source supporting delta(info pack delta) functionality why don't you go with Delta DTP.

Delta info pack --> Delta DTP SAP Standard

Delta info pack-- full dtp, it leads data in consistency, Because Full dtp it loads all the request which are lied at PSA during the DTP full load.

Thanks

[Former Member]

All

I have inhertited a similar process to original post.

The load process chain has been running for many years with steps to Cleardown PSA, then PSA Load Full, then DTP from PSA to Cube as Delta. I don't see any reason why the DTP is a Delta, and am thinking about changing this but just had a couple of questions.

My thought is that using FULL loads for both PSA load and Cube load would be faster, are my thoughts correct - as I am not 100% sure of process internally being use for this Delta DTP from a PSA?

Using a Full DTP will mean there will be no processing internally to check when writing the PSA record that if the PSA record represents a "change".

Also, if there is a Delta DTP from PSA to Cube does this mean there is a PSA Delta Queue setup? If so, using a Full load from PSA to cube will stop having to write records to PSA and also to a PSA Delta Queue surely?

I would have throught when the current Delta DTP is running it is reading a PSA Delta Queue to identify the records to load, then having to do a second read to pick up actual PSA data (or is this maybe picked up in first read?)

I would really appreciate someone giving some understanding on the Delta mechanism internally on the PSA so I can understand if the loads are likely to be more efficient/faster. Of course I will test and measure this actually, but want to ensure my understanding is corect.

Regards

Simon

[RamanKorrapati]

Hi Saravana,

Delta functionality is depend on the data source not psa.

DTP Delta is working fine,but Dtp delta functionality is working on the request basis, if your info pack daily pulling full load then same request will move to target and leads to data consistency.

Seems like your data source not supporting delta functionality.

Go with any one of the Anshu suggestion which suits your business to avoid the data inconsistency.

Thanks

[Former Member]

Hi Raman,

Can't we have full IP  and then delta DTP?

Thanks

Vishal

[Former Member]

Hi,

If we have full ip and then delta dtp it wont work as desired...

Bcos delta work on request basis.. if ur new request is full load then that request is updated to target. dtp doesn't check the records(for old one, new one, changed one) in the new request.

Where as if u implement dso in between the datasource and infocube. For infocube delta dtp takes data from change log table of dso. where we find orecordmode.

Hope u understand..

Regards,

Aravind.

[RamanKorrapati]

hi vishal,

in Below case not possible.

Delta dtp is working on the latest request which was lied in psa, info pack full load, if your data flow is data source--> Cube.

Thanks

[anshu_lilhori]

Hi,

If your datasource doesn't support delta then DTP cant do anything---It will pick all the records present in PSA.

IF you are doing full load daily then two things can be suggested:

1) Delete the content of target and psa daily before loading the data to psa and cube..This way there wont be duplication of records.

2) Introduce DSO between PSA and Cube.As this can facilitate with delta mechanism.

Hope this helps.

Regards,

AL

[saravanan_a]

Hi Anshu,

So we should never use IP as full load & DTP as delta while loading directly from DS to cube?

Delta pointer will work on DSO's and not on PSA's?

Please confirm..

Also can you share some links to understand delta pointers concept? Thanks in advance.

[Former Member]

Hi Saravana,

Using Full/Delta IP depend upon your datasource. If your datasource support delta concept you can use delta IP otherwise not. from PSA to futher target you can use delta DTP.

If you are using Full DTP make sure that before running the IP add step to delete the content of PSA step so that you can have only one request to be loaded in DTP run.

Regards,

Vishal Vaibhaw

[anshu_lilhori]

Hi,

See its simple to understand that if your datasource is not supporting delta loads then you are left with the option of running the IP in full mode only.

Delta DTP and full dtp difference is :Suppose you first time loaded data to PSA---Delta dtp behaves as init with data transfer.

Tomorrow again you loaded the data to PSA(full load) Delta dtp will pick the latest request only whereas in this scenario Full DTP will pick the data from both the requests.

You can experiment the same on your system to draw the conclusion.

I tried finding the supporting document on it but did not find exactly fitting into your requirement.

Hope this helps.

Regards,

AL

[Former Member]

Hi,

As of my understanding ur IP is full load every time. Then DTP to infocube will also be full load. Delta work only on request basis.

Use delete overlapping request or use a DSO.

Regards,

Aravind.

[saravanan_a]

Hi Aravind,

Yes IP is full load every time. Yeah I can make DTP as full load and add to delete overlapping request variant

But I would like to know why DTP delta is not functioning here. I might not be clear in this concept.

Can you pls clarify why DTP cannot be delta and should be full here?

. Delta work only on request basis.

Why Delta will work on request basis? Then what's the difference between full load & delta load dtp?

[Former Member]

Hi,

Delta works on request basis here.

If DTP is delta enabled it only picks the new requests after the previous delta load. If that request is full load or delta load doesn't matter.

If DTP is full then every time it picks all the request from the psa.

Regards,

Aravind.