When exactly source system recognizes the last delta is succesfull/failed.

Question

When exactly does the source system recognizes the last delta is successful/failed?
Case -1: In logistic applications..
             What if I changed quality status to red for a successfully completed delta, and then requested new delta?
Case -2 : In Financial applications..
              When exactly BWOM2_TIMEST fields updated. I mean BW acknowledges to the delta load immediately saying it is successful or fail, or at the time when we request the next delta?
              What if I changed quality status to red for a successfully completed delta, and then requested new delta? It executes repeat or returns 0 records.

Answer 1

Hi,
Here's the explanation:
Scenario 1 -Logistics Delta
Sinc logistics delta comes from Delta Queue (RSA7) and IP takes daa from Delta queue so betwen RSA7 and BW, IDocs are transferred which sends messages for successful completon of extraction. As soon as extraction is over and a particular IDoc is sent to BW the BW marks the delta s successful. This happenes exactly when job is Source system completes Now if you make a successful delta as red then the IP identifies that last delta was not successful and requestes a repeat of last delta which again goes to RSA7 and picks the last delta and also the new deltawhich has come in RSA7. Note: RSA7 stores both new delta records and one last successful delta records(for delta repeat)
Scenario 2 - FI Delta
Sinc FI deltas are based on timestamp mechanism there are 2 possibilities:
a) The extraction fails while picking records from R/3 table (G/L, Ap and AR tables). In this case the timestamp isnot registered in BWOM2_TIMEST table and arepeat will work fine.
b) The load fails during procssing in BW (e.g update rules processing) and the job has completed in R/3 and has set the timestamp in table BWOM_TIMEST. In this case we will have to reetthe tmestamp and run the delta again.