About Repeat Delta

[Former Member]

Specialists ,

Can any one let me know procedure for Repeat delta & how it works .

Thanks

Gururaj

[Former Member]

Hi Raj,

forcing the req in the monitor to Red tells that the last delta has been failed. R/3 will check the monitor status of the request.

Hope it helps-

MM

[Former Member]

thanks vishnu. i have one more doubt, if forcing the req in the monitor to Red tells that the last delta has been failed, what does forcing the requests in requests tab indicate, doesn't it indicate to r/3 the same or not?? could u pls verify.

Message was edited by: ravi raj

[Former Member]

Hi,

U can put the status to red in the monitor. by going to Status tab in RSMO, click the total status and make it red.

We will do this when we go for the repeat of last delta.

If u take repeat delta then it will fetch both the old delta records as well as the new delta recirds which are in the delta queue.

for more info refer OSS NOte: <b>380078</b>

Hope it helps-

MM

Assign points if it helps..

Message was edited by: vishnuC

Message was edited by: vishnuC

[Former Member]

vishnu,

<i>U can put the status to red in the monitor. by going to Status tab in RSMO, click the total status and make it red.

We will do this when we go for the repeat of last delta.

</i>

what is the difference between forcing it to red in requests tab of infocube and forcing it to red in (RSMO) monitor status tab.

[Former Member]

Hi Gururaj,

about the procedure it's enough to force your first delta request in red (in the monitor) and then to request the delta again in despite of warnings...

Technically speacking, delta repetition is assured by a mechanism that you can observe in RSA7 transaction in R/3: when you look at the 'Total' column in that transaction, this number displays the number of LUWs (Logical Unit of Work) that were written in the delta queue and that have not yet been confirmed (this is a specific technical status field). Now, the most important thing is to understand that this number also includes (apart from the LUWs for the next delta request) the LUWs of the last delta request already uploaded in BW...and this allows you to call a repeating delta request!

In this way a LUW (related to a previous request) disappears from the queue only when it has been transferred to BW

AND

a new delta has been received...

Hope it helps!

Bye,

Roberto

...please don't forget to reward the answers...it's THE way to say thanks here !

[Former Member]

Hi Roberto,

Have one doubt here ,

1.When we request Delta from R/3 to BW , Will it still remain in RSA7 or gets vanished ? irrespective of whether load is succesfull or gone in Red - pls clarify

2.While doing repeat delta , whether new LUV also joins along with old LUVs to BW ?

Thanks

-Gururaj

[Former Member]

Hi dear!

1)Yes (and red or green is not relevant), since the the LUWs must be kept for a possible delta request.

When a new delta has been requested, the source system "understands" that the previous delta was successfully loaded into the BW System, but "old" records still remain available for a (possible) repetition.

A is the first delta. B is the second and C the third ones.

A has been requested in BW. In the meanwhile B arrives. A still remains for repetition. When we confirmed C delta request, B becomes available for a repetition a A is deleted !

2) the repeat delta only takes old records and not even the new ones

Hope now is clearer...

Bye,

ROberto

[Former Member]

Hi Roberto,

I have a doubt now. Do u mean to say that when u request for repeat delta, dont we get the records from the failed delta and also the new records from next delta.??

Please repond.

Thanks,

krish

[Former Member]

roberto,

when u say force the request to red in monitor do u mean force to red in in the tab of requests tab (right click manage of infocube) or is there a way to force it to red in monitor. if in monitor where would tht option be?

Message was edited by: ravi raj