Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
ICM (Application Component) Incentive and Commission Management (ICM)⤷
CACSSE (Package) ICM: Settlement
IMG Activity
| ID | _CACS_V_TCACS_UPD_MO | Edit Update Mode For Totals Tables |
| Transaction Code | S_KK4_08000452 | (empty) |
| Created on | 20011121 | |
| Customizing Attributes | _CACS_V_TCACS_UPD_MO | Edit Update Mode For Totals Tables |
| Customizing Activity | _CACS_V_TCACS_UPD_MO | Edit Update Mode For Totals Tables |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _CACS_V_TCACS_UPD_MO |
Use
In this activity, you can specify the update mode for the database update for each totals table. During the runtime, Customizing is read and the update function module that you defined is run.
You can use the following update modes:
V1 Update
The totals tables are updated with the update function modules that start immediately. These function modules are immediately started on after the COMMIT WORK, which ends the SAP LUW dialog part. If an error occurs in the whole V1 update process of this SAP LUW, a rollback is triggered, which also applies to the document.
V2 Update
The totals tables are updated with the update function modules that have a delayed start. These function modules are processed once all V1 update function modules that belong to the SAP LUW have been successfully processed. If a V2 update process is cancelled, only a rollback is triggered for the relevant totals table. The V1 updates and the remaining V2 updates are not affected.
V3 Update
The totals tables are updated with update function modules that have the collective run characteristic. These function modules have to manually processed with the CACS_TRIGGER_V3 report.
Note
You need to trigger this at least ONCE a day
If a V3 update process is cancelled, a rollback is only triggered for the relevant totals table. V1 and V2 updates are not affected. The main advantages of a V3 update are that the manual trigger can be delayed for the triggering process, and database access can be improved due to an additional COLLECT command.
SAP recommends that you use the following values to run the report:
COMMIT after X function modules
Since a fixed default is not possible for X, you need to determine this value by testing. X depends 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.
You can improve performance for the processing of the triggering process because it is possible to schedule the totals table update for the process with a time delay.
The totals tables that have already been updated are not affected.
You need to ensure that the V3 function modules are processed using the CACS_TRIGGER_V3 report at least once a day. It is recommended that you do so more often.
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _CACS_V_TCACS_UPD_MO | 0 | KK40000031 | Incentive and Commission Management (ICM) |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| CACS_APPL_BH | T - Individual transaction object | CACS_APPL_BH |
History
| Last changed by/on | SAP | 20030321 |
| SAP Release Created in | 464 |
