Hi Reddy,
read carefully oss note: 422173
Information: BW/CO-PA upload data inconsistency correction
Symptom
Due to an error in the OLTP or BW during the delta upload, a data inconsistencyoccurs between OLTP and BW. This may occur if the extraction terminates when reading the data in the Profitability Analysis or if a problem occurs when the two systems were communicating.
This problem can only occur for DataSources with the old logic (time stamp management in the Profitability Analysis).
As of Plug-In Release PI2004.1 (Release 4.0 and higher), there is a new additional logic (generic delta) for the delta process. Old DataSources can be converted the new logic here. New DataSources automatically usethenew logic. With the new logic, the time stamp management appears in the Service API and no longer in the Profitability Analysis.
This note only refers to DataSources with the old logic.
Both program ZUNDOUPD and transaction KEB5 must ONLY be used for DataSources with the old logic.
Other terms
KEB0, RD144, KEB2, KEB5, data inconsistency, inconsistency, inconsistent correction
Reason and Prerequisites
Another initialization of the delta process is no longer possible or is not required due to the dataset or the archiving that already occurred.
Solution
The Profitability Analysis manages the information for the delta processitself. Therefore, the replication status of the DataSource must be checked in the OLTP and adjusted with the requests in BW. You must then update the DataSource to the correct status in the OLTP and delete all requests in BW that were loaded using the 'Repeat' update mode.
First check the detailed information for the DataSource in transactionKEB2. There you will find all delta requests from BW that were requested since the last initialization with the number of records read and sent and the time stamp of the DataSource. You have to adjust this information with the monitor in the BW System for the corresponding InfoPackage.
If you have identifiedthelast request that was processed correctly both in the OLTP and in BW, you have two possible options to eliminate the problem.
1. Set the time stamp of the DataSource in transaction KEB5 to thevalue of the last (in both systems) successful delta updates. The time stamp is available in the last "Timestamp" column under "Data packets" in transaction KEB2. When you start transaction KEB5 for the affected result area and DataSource using the 'Direct input' option and the time stamp determined in transaction KEB2, the DataSource is initialized without a data read with the entered time of the last successful delta update. If you then delete the incorrect updated requests in BW, you can continue with the delta process. The disadvantage of this method is that the log information in transaction KEB2 is lost for all updates prior to the start of Transaction KEB5.
2. To receive the log information in transaction KEB2, you can also downloadthe ZUNDOUPD program from SAPSERV3. This is available as ZUNDOUPD.TXT in the 'general/R3server/abap/note.0422173' directory. The program has the following options:
Display CO-PA request log:
Displays the data also available in Transaction KEB2. The detail log is only possible in old plug-in versions (before Plug-In 1999).
Rollback most recent request:
In each case, roll back a delta update from the log in transaction KEB2. There are three different activities:
Reset status of InfoSource:
If an error occurred with the selection in the OLTP system, the DataSourcehas the 'Update failed' or 'Delta update is running' status. In this case, you must use this option to reset the status in the update run to be able to load data again.
Delete request log:
With this option, the value of the time stampforthe delta process is reset to the value of the previous delta update in the update run. It is always set back to one delta.
Decrease delta counter:
The counter for delta updates is reduced by one in the update run.
Before you start the program in the update run, check whether an extractionprocess is still running in the OLTP. Resetting the status of the DataSource is only necessary if the status in transaction KEB2 is not 'Update successful'. You must not adjust the counter for delta updates, even if you delete requests using the 'Delete request' option.
Finally, you need to set the statusof the requests in the monitor function of the BW System to 'green' as otherwise you will not be able to load new InfoPackages.
ATTENTION: With incorrect entries, irreparable inconsistencies can occurin the extractor in the management of delta information. In particular, setting the time stamp to times that are very close to thecurrent time can cause problems. All inconsistencies can be removed by reinitializing again (with or without a delta transfer).
/manfred
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.