Kontakt

Ansicht
Dokumentation

UKM_MASSDATA_RECONCILE - SAP Credit Management: Credit Exposure Reconciliation

UKM_MASSDATA_RECONCILE - SAP Credit Management: Credit Exposure Reconciliation

rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With this program you can compare the credit exposure between the sending systems (FI-AR system, SD system) and the receiving system in which SAP Credit Management is running.

Integration

Prerequisites

Background Information

Reading the data for the reconciliation is technically implemented with SAP Query. In the Global Area query area (cross-client), the following queries are available:

  • /GRC/FINB FSCM_CR_50_Q1 for reading the data of the SAP Credit Management system
  • /GRC/APPL FSCM_CR_51_Q1 for SD data in the sending system
  • /GRC/APPL FSCM_CR_52_Q1 for FI-AR data in the sending system

Preparations

So that the program can read the data from a particular system, you have carried out the following activities in the SAP Credit Management system:

  1. You have created the user group FSCM_RECON (transaction SQ03).
  2. You have assigned the InfoSet /GRC/FSCM_CR_50 (transaction SQ03).
  3. You have created the following 3 proxy queries by copying the query FSCM_CR_50_Q1 to the user group (transaction SQ01):
  • Query CR_PROXY

  • Query SD_PROXY

  • Query AR_PROXY

  1. You have edited the logical destination of the FI-AR system and the SD system (transaction SM59).
  2. You have changed query SD_PROXY (transaction SQ01) as follows: Under Goto -> Report Assignment -> Insert External Report you insert the query from the SD system using the report-report interface. Enter the logical destination of the FI-AR system and the query (user group /GRC/APPL, name FSCM_CR_51_Q1).
  3. You have changed query AR_PROXY (transaction SQ01) as follows: Under Goto -> Report Assignment -> Insert External Report you insert the query from the FI-AR system using the report-report interface. Enter the logical destination of the SD system and the query (user group /GRC/APPL, name FSCM_CR_52_Q1).
  4. You can connect further separate queries to the proxy query, as the system calls all of the queries defined using the report-report interface. This way you can reconcile customer-defined credit exposure updates.

Features

You can decide whether you access the data of the database or the data of an extract. If you use both of these variants, you can exclude discrepancies that are caused by the time delay through the asynchronous sending of the data.

Selection

For the business partner numbers, the system proceeds according to the following logic:

  • Areas of business partner numbers are transferred to the queries unchanged.
  • Single values are if necessary converted to customer numbers, and transferred to the queries.
  • Custom Selections are only taken into account in the SAP Credit Management system. The system creates a list of business partners from this, that it then treats as single values.
  • If credit segments in the sending system are determined from several attributes, for example from the material and the credit control area, you are recommended not to select any credit segments, because among other things false data could be determined in the sending system.

Standard Variants

For performance and memory usage reasons, it can be better to examine the credit exposure first in total for each credit account, and after that undertake a detailed analysis for any accounts that stand out. Create queries AR_PROXY_SUM and SD_PROXY_SUM in the sending system. Call the corresponding query (FSCM_CR_52_Q1, FSCM_CR_51_Q1) with the totals variant SUM.

Output

In the standard delivery, you only see the differences. However, you can set the display so that you can see all of the data from the systems.

Activities

Example

  1. In a first step, start the reconciliation with a totals variant that only displays the differences. The result is written to an extract. You can see there all of the accounts that have differing values in the sending and receiving system.
Some of these differences can be traced back to the time delay between the update in the sending system and the asynchronous sending of the data to the SAP Credit Management system.
  1. This means it is sensible to use the above-mentioned extract as a selection basis at a later point. In this case, the system only checks the accounts that stand out. Any accounts that in the meantime have been correctly updated are no longer displayed in this subsequent run. This provides you with a reliable basis for further postprocessing the differences.





PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5541 Date: 20240601 Time: 080204     sap01-206 ( 89 ms )