Procedure for System Administration
V3 Update
The totals tables are updated using the posting function modules thathave 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 eachtotals table. V1 and V2 updates are not affected by this. The mainadvantages of a V3 update are that the manual trigger can be scheduledfor the triggering process and the database accesses can be optimizedagain 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 todetermine X by testing. X is dependent on the number of key fields ineach totals table and the average number of commission cases per COMMITin the EDT or online mode. The higher the number of key fields, and thehigher the number of commission cases per COMMIT, the lower the numberof function modules should be after which a COMMIT is to take place inthe 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 thefact that it is possible to schedule the totals tables update for theprocess.
The totals tables that have already been updated are not affected.
You need to ensure that the V3 modules are processed using theCACS_TRIGGER_V3 report at least once a day. It is recommended that youdo so more often.