Kontakt

Ansicht
Dokumentation

RICL_VVKKCFREC_CHECK - Report for Checking Table VVKKCFREC

RICL_VVKKCFREC_CHECK - Report for Checking Table VVKKCFREC

Vendor Master (General Section)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With cash receipts for recovery or subrogation receivables in FS-CD, there might be complex disagreement between the actual receivables clearing (table DFKKOP, field BETRW), the trigger table (VVVKKCFREC, field AUGBO) and the cash receipt registered in FS-CM (table ICLPAY, field AMTDONE).

You can use report RICL_VVKKCFREC_CHECK together with report RICL_AMTDONE_CD_CHECK to analyze the situation.

Report RICL_VVKKCFREC_CHECK determines why existing data records have not been processed with transaction ICL_RECOVERY_FETCH (Report Receipts from Collections to Claims Management system). Transaction ICL_RECOVERY_FETCH is a daily background job that should have normally deleted the data records concerned. Since the log of transaction ICL_RECOVERY_FETCH only contains some of the possible errors, further investigation is possible with the help of report RICL_VVKKCFREC_CHECK.

Integration

Prerequisites

To be able to use report RICL_VVKKCFREC_CHECK in a sensible manner, you must be familiar with the technical basics, particularly with the name and significance of the relevant database fields. Only users with such knowledge are able to evaluate the results of the report.

Features

Report RICL_VVKKCFREC_CHECK performs the following checks:

  • Check for errors in the amount received (table VVVKKCFREC, field AUGBO)
    The report checks the amounts received as follows:
  • Amount = zero

Is always evaluated as an error
  • Amount is negative

Is always evaluated as an error
  • Amount is too high (meaning the amount is more than the difference between the amount requested and the amount already received (table ICLPAY, field AMTDONE).

The report does not check whether the value in field AUGBO matches the amount received (table DFKKOP, field BETRW). For this check, use report RICL_AMTDONE_CD_CHECK.
  • Check on associated payment (entry in table ICLPAY, field DOCUMENTREF = entry in table VVKKCFREC, field OPBEL) for the following errors:
  • No associated payment exists

  • Several associated payments exist

  • The record type of the payment (table ICLPAY, field PAYCAT) is neither 1 (Repayment) nor 2 (Payment Request from Subro/Recovery).
    Exception: There is no error if the record type is either 5 (Payment Request from Salvage) or 7 (Statistical Posting for Salvage).

  • The payment status (table ICLPAY, field STATUS) is neither 8 (Requested) nor C (Partially Received).

  • Check on claim reference (table DFKKOP, field VTREF) including conversion in the implementation of BAdI BADI_ICLF_CD, method RECEIVED_AMOUNT_READ for the following errors:
  • VTREF is not delivered

  • VTREF is delivered with the wrong prefix

  • The associated payment (VTREF and table DFKKOP, field REFCLAIM) does not exist

  • The associated payment (VTREF and REFCLAIM) exists, but does not match the FS-CD document (entry in table ICLPAY, field DOCUMENTREF does not match the entry in table VVKKCFREC, field OPBEL)

Selection

Use the following fields to define which data records of table VVKKCFREC should be analyzed:

  • Time at which the table entry was created (field CREATETIME)
  • Document number (field OPBEL)

Standard Variants

Output

The system lists the selected data records and displays the errors found.

Activities

The main purpose of the report is so that SAP can analyze customer problems. With different or additional analysis requirements, you must create a customer-specific program with correspondingly modified coding.

Example






PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5293 Date: 20240531 Time: 113605     sap01-206 ( 76 ms )