1. Can you suggest a solution/concept for a separate update process? How do we do a separate commit that works independently of the main update process?
2. Or.. Do you know if there is a tool for tracking users accessing views in CRM_IC? (SAP standard is to track all changes but now we want to track each display).
<b>Background</b>
The authorities wants us to track what each CRM-user is watching/accessing in our system. For exampel in the search result for a customer they want us to put a timestamp in a table ie:
ZLOGG-table in DB2
- SAPuser
- timestamp
-Customer number/partner of the selected data
An insert could be done at certain INIT-methods of the views
<b>The problem</b>
In a normal situation/program we write a insert + a commit/update to store the data. Maybe we even put the code in a function module in a update task.
In this situation we want to an update in ZLOGG without disturbing the main update process. Is it possible?
<b>One example of the flow </b>
View one
-Log the data
- change of the SAP standard data
view two
-log the data
-changes of the SAP standard data
- The user does not want to save the data and a rollback is done (or the program crashes - we still want have the access logged). We want to keep the data in the logg-file.