Ansicht
Dokumentation

SIMG_ISISFICA_VC_TKKV_R - SIMG ISISFICA VC TKKV R

SIMG_ISISFICA_VC_TKKV_R - SIMG ISISFICA VC TKKV R

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book


In this activity, you define criteria both for transactions to be investigated as part of the money laundering law and for transactions to be classed as suspicious.

You can define the terms under which a transaction is considered suspicious for each company code, insurance type and document type (see below). The degree of suspicion is then determined by a check which runs when line items are cleared. Transactions which are found by this check to be suspicious are sent on to the clarification worklist for money laundering where they are then processed manually.

At present the following criteria are supported, dependent on amount limits and the payment amount which are defined in the account, contract or document:

  • Returns: A return occurs for a document that was already cleared
  • Payment: A document is paid by an externally initiated payment. Example: the payment method agreed upon was debit memo, but a check appears instead.
  • Clearing: An outstanding premium on a life insurance policy is paid by the credit from a propoerty insurance policy.
  • Amount: The amount limit agreed upon is exceeded.

You have to have set the money laundering indicator in table TKKVBASIC. Choose System -> Services -> Table maintenance -> Ext. table maint.

Enter your criteria for suspicious transactions and transactions to be investigated.






BAL_S_LOG - Application Log: Log header data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 1602 Date: 20240524 Time: 014649     sap01-206 ( 39 ms )