Kontakt

Ansicht
Dokumentation

RICL_AMTDONE_CD_CHECK - Report for Comparison of Incoming Payment from FS-CD and FS-CM

RICL_AMTDONE_CD_CHECK - Report for Comparison of Incoming Payment from FS-CD and FS-CM

CPI1466 during Backup   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
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_AMTDONE_CD_CHECK together with report RICL_VVKKCFREC_CHECK to analyze the situation.

Integration

Prerequisites

To be able to use report RICL_AMTDONE_CD_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

The report executes the following activities. The report works with the records in table ICLPAY (claim payment).

The report compares the incoming payment registered in FS-CM (table ICLPAY, field AMTDONE) with the total of incoming payments in FS-CD (table DFKKOP, field BETRW).

The following applies:

  • The report only reads data records with the same document number, in other words the entry in table DFKKOP, field OPBEL is identical to the entry in table ICLPAY, field DOCUMENTREF.
  • The report only reads data records with the status Cleared, in other words the entry in the table DFKKOP, field AUGST = 9.
  • The following rules apply for the plus/minus signs:
  • Table DFKKOP, field BETRW: Positive incoming payments

  • Table ICLPAY, field AMTDONE: Negative incoming payments

For each ICLPAY data record, the following report results are possible:

  • Payments with incoming payment (in other words, at least one DFKKOP data record with AUGST= 9 exists)
  • Absolute amount in AMTDONE is correct (corresponds to FS-CD incoming payment)

  • Absolute amount in AMTDONE is too low

Sources of error: either because of an outstanding notification (see below under "Reading of outstanding incoming payment notifications (table VVKKCFREC)") or because of an FS-CM error
  • Absolute amount in AMTDONE is too high, in other words the FS-CD total >= 0

Sources of error: FS-CM error
  • Absolute amount in AMTDONE is negative, in other words the FS-CD total < 0

Sources of error: FS-CD error
  • Payments without incoming payment (no DFKKOP data record with AUGST= 9 exists)
  • The FS-CD document is open.

  • If the payment status in table ICLPAY, field STATUS is 9 (Received) or C (Partially Received), then there is an inconsistency.

Sources of error: FS-CM error
  • If the payment status is not 9, or C, this is not considered as an error.

  • No FS-CD document exists.

The system evaluates this as follows:
- correct, if the payment status is G (Parked) or A (Deleted)
- as an error if the payment status is not G or A (provided a posting has taken place)

Check for major inconsistencies

The report also checks for the following situations that are not permitted:

  • Total of requested amounts >= 0, if the payment status is not G (Parked)
This amount must always be negative after a posting
  • The value in table ICLPAY, field AMTDONE is > 0.
An "inverse" incoming payment is not possible.
  • The value in field AMTDONE is < 0 when the payment status is 8 (Requested).
This is an inconsistency.

Reading of outstanding incoming payment notifications (table VVKKCFREC)

The report also reads any possible outstanding incoming payment notifications (data records in table VVKKCFREC that have not yet been processed in transaction ICL_RECOVERY_FETCH).

The amounts there (total in field AUGBO per OPBEL) might be as follows:

  • Explain the result "Absolute amount in AMTDONE is too low (see above "Comparison of incoming payment FS-CM with incoming payment FS-CD")
  • Be too high (individually or in total)
  • Have no effect at all because AUGBO = 0
  • Not be capable of being processed because AUGBO is negative

Note: For a direct analysis of table VVKKCFREC, use report RICL_VVKKCFREC_CHECK.

Selection

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

  • Payment record type (field PAYCAT)
    Important here are the entries 1 (Repayment) and 2 (Subrogation Receivable).
  • Time changed (field CHANGETIME)
  • Document number (field DOCUMENTREF)
  • Internal payment status = database status (field STATUS)

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 customer-specific programs with correspondingly modified coding

Example






TXBHW - Original Tax Base Amount in Local Currency   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 7156 Date: 20240520 Time: 065110     sap01-206 ( 75 ms )