Delta Records

[Former Member]

Hello Gurus

I would really appreciate if anyone could tell me how to deal with the <b>delta extraction</b> failure.

1. 0 from 0 records extracted with QM status red. Added records 0 and Transferred 0?

2. 0 from 10,000 records extracted with Qm status red. Transferred records 0 and Added 0? with no data in PSA.

3. 10,000 from 10,000 records extracted with QM status red. Transferred records 0 and Added 0? with data in PSA.

4. 0 from 10,000 records extracted with QM status GREEN. Transferred records 0 an added 0?

Note: We faced a problem for the question 2. when clicked on the infopackage we got the msg stating tat last delta is failed ,,,,repeat the delta..so when we shceduled , action is getting cancelled.

Thanks and Regards

Annie

[Former Member · Accepted solution]

Hi Annie,

With Delta extraction if a load fails and the request with Red status is updated in the Data Target, then the subsequest Delta is not possible.

What you can try is, Go to the Data Targets which is getting updated and delete all the request with Red Status in the Data Target and then try reloading.It will work.

Hope it helps.

Regards

Parth.

[Former Member · Accepted solution]

Hi partho

In my scenario 0 from 10,000 records extracted with QM status red. In data target no Transferred=0 Added=0 and no data available in PSA.

when i open the infopackage i am getting the prompt somethin like

last delta failed

repeat delta...

when i clicked on the schedule action is getting cancelled

If i delete the request from the data target and PSA the 10,000 records will be vanished..(Am i right?) and will not be available in R/3 RSA7. if i repeat the delta also those records will not arrive into BW. I am confused with this kind of delta failure..hope its clear.

Thanks and Regards

Annie

[majeed_mohammedabdul · Accepted solution]

Hi Annie,

Unless the delta load goes through successfully (or is forced to Green), the system does not move on to the next delta. So if your failed delta was Red in the QM status, the system should bring over the same records on the next try.

Regards

Majeed

[Former Member · Accepted solution]

Hi,

One of the consulting note says that : (in your case)

<i>set the request to GREEN in the monitor using a QM action.

The system then requests a delta again since the last delta request has not yet occurred for the extractor.

Afterwards, you must reset the old request that you previously set to GREEN to RED since it was incorrect and it would otherwise be requested as a data target by an ODS.</i>

To do above step , you have to check one thing in R/3 system:

<i>Check the DELTARNR field in the roosprmsc table. The value(request) that is displayed should be as the one request before to the last request(failed one) in the monitor in the BW system (the previous request of failed request).</i>

with rgds,

Anil Kumar Sharma .P

Message was edited by: Anil Kumar Sharma

[Former Member · Accepted solution]

Hi Anil

Thanks that's really a good explanation. so as you mentioned

<i>Afterwards, you must reset the old request that you previously set to GREEN to RED since it was incorrect and <b>it would otherwise be requested as a data target by an ODS</b>.</i>. can you please elaborate on this point as i am not clear.

On to my understand to above explanation first i should convert the red to green and repeat the delta.

Then before resetting that green to red again i need to check in R/3 table roosprmsc field DELTARNR should contain the request no of failed request. If the failed on exists i should turn to red other wise?

After turning to red should i delete the request?

Thanks

Annie

[Former Member · Accepted solution]

Hi,

<i>Afterwards, you must reset the old request that you previously set to GREEN to RED since it was incorrect and it would otherwise be requested as a data target by an ODS..</i>

It is required not to get double records. if the old request that you previously set to GREEN has uploaded few records to cube , you may be get a chance to have double records. This happens if the data target is Cube . For ODS it does not happen .Because second time entered records will overwrite the previous one.

I hope, you can ignore this above italic coted statement. in your case, no record is updated to DT by the earlier failed request.

<i>If the failed on exists i should turn to red other wise?</i>

Yes.

After turning to red should i delete the request?

Yes.But not required to uload the data. It is required for further taskes (Activation in case of ODS,Compression...)

With rgds,

Anil Kumar Sharma .P

[Former Member · Accepted solution]

Hi Anil

Thanks for the Explanation. I assigned full points for you.

Thanks

Annie