You can use the Update Tracker
tool to track all changes made in the main memory to database tables of SAP Claims Management. You can do this as soon as the claim has been saved in claims processing.
If you are transferring data from a legacy system, we recommend that you deactivate the Update Tracker
tool (see Prerequisites section).
The Update Tracker
tool is active in the standard system. If you want to deactivate it, you must set the UpdTracker Off
indicator in Customizing activity Define Different Client-Specific Settings
(Customizing path: ).
The Update Tracker
tool works as follows:
At the DSAVE event of the Business Data Toolset (BDT), the system transfers the recorded changes to the Business Add-In (BAdI) BADI_ICL_CLAIM_UPDATE (enhancement spot ICL_CLAIM_UPDATE). This transfer takes place immediately before the database commit.
You then have the following options:
You can evaluate the changed claim data in the BAdI and transfer this to external systems, for example.
After you have called direct input processing, you can use function module ICL_CLAIM_DI to evaluate the data of the Update Tracker. This enables you to see which database tables have been changed. After you have called function module ICL_CLAIM_DI, you use the cl_ign_update_tracker=>get_all_changes( ) method to obtain the data of the Update Tracker.
You can use the BADI_ICL_BP_UPDATE (enhancement spot ICL_CLAIM_UPDATE) BAdI to monitor claim-relevant business partner changes. The system transfers the business partner number and a list of claims in which the business partner appears to the BAdI. In contrast to the ICL_CLAIM_UPDATE BAdI, the ICL_BP_UPDATE BAdI is not called until during the COMMIT WORK processing of a business partner change.
Note
This last option is required for External Claim Investigation, for example. If the address of a business partner changes, all claims in which this business partner occurs must be sent again to an external service provider for potential fraud investigation.