Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
ICM (Application Component) Incentive and Commission Management (ICM)⤷
CACSDO (Package) ICM: Commission Document 'Light' 
Attribute
| Message class |  |
CACSAC | |
| Short Description |  |
Messages for Read Modules for Commission Documents | |
| Message Number |  |
102 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20130531 |
Message Text
Help Document
Procedure for System Administration
V3 Update
The totals tables are updated using the posting function modules that have the collective run characteristic.
Note
This must be triggered at LEAST once a day
When a V3 update process is cancelled, a rollback is triggered for each totals table. V1 and V2 updates are not affected by this. The main advantages of a V3 update are that the manual trigger can be scheduled for the triggering process and the database accesses can be optimized again due to an additional COLLECT order.
SAP recommends the following values when you run the report:
COMMIT after X function modules.
Since it is not possible to provide a fixed default for X, you need to determine X by testing. X is dependent on the number of key fields in each totals table and the average number of commission cases per COMMIT in the EDT or online mode. The higher the number of key fields, and the higher the number of commission cases per COMMIT, the lower the number of function modules should be after which a COMMIT is to take place in the CACS_TRIGGER_V3 report.
The client is a required entry.
You can use the SM13 transaction to monitor the update flow.
Performance of the triggering process should be improved due to the fact that it is possible to schedule the totals tables update for the process.
The totals tables that have already been updated are not affected.
You need to ensure that the V3 modules are processed using the CACS_TRIGGER_V3 report at least once a day. It is recommended that you do so more often.
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in |
