Ansicht
Dokumentation

RFFMSEURO_ANA - Euro Conversion Clearing Program for Actuals Documents in FM

ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Title

Reconciliation Program for Euro Conversion of Actuals Documents in FM

Purpose

This program reconciles rounding errors that occurred in actual data in Funds Management (FM) as a result of euro conversion. If errors occur, the program corrects expenditure postings (and payment postings too, if necessary) between the Funds Management and Financial Accounting components and posts the correction amounts to a special dummy FM account assignment.

You can also use this program when preparing for local currency conversion as the Prepare Actual Data Reconciliation IMG activity. In this activity, you can use this program only in the test run and, therefore, no correction postings are made.

Integration

During euro conversion, the program is run automatically in the RECON-Phase as RFFMSEURO_RECON and posts corrections made to rounding differences.

After euro conversion and as part of post processing operations, run program RFFMRC04 to Reconcile Line Items and Totals Records.

Prerequisites

You created a dummy FM account assignment for the correction postings and made the necessary settings in the Define Settings for Reconciliation of FI Documents IMG activity.

Features

The program corrects the amounts in table FMIFIIT. For performance and economic reasons, only those documents that have line items for the current fiscal year are reconciled. No other documents are taken into consideration.

Basically, expenditures are reconciled against FI (as far as possible). If you are using update profile 000400 or active payment reconciliation in your FM area, the payment records are also reconciled against FI.

Correction Records

If the program finds errors in the expenditures or during payment reconciliation, correction records are created. These can viewed in transaction FMPA (for payment reconciliation records) and transaction FMRC (for expenditure reconciliation records). All records are recorded statistically in the dummy FM account assignment you specify. This dummy FM account assignment must not be part of your operational budget!

• The correction records for expenditure reconciliation are recorded in the current fiscal year and cannot be carried forward in fiscal year change operations.

• For technical reasons, the correction records for the payment reconciliation are recorded in the posting date of the payment and not in the previous fiscal years (This should not cause problems because of the dummy account assignment and should not affect your budget).

Note:
This program may not reconcile all rounding errors that result from euro conversion. This particularly applies for documents from old (closed) fiscal years and for the type of payment selection:

Here are a few examples that are not reconciled by the program:

Example 1: Rounding error during fiscal year change operations

BTART	WRTTP	GJAHR	USD	EURO	Paymt ref.	Inv. ref.
100	54	1999	100	51,13	1	1
200	54	1999	50-	25,56-	2	1
250	57	1999	50	25,56	2	1
300	54	1999	50-	25,56-	1	1
350	54	2000	50	25,56	1	1

The example above shows that, in fiscal year 1999, this invoice has an amount of 51.13 euro after euro conversion and is then reduced by 25.56 euro and the same amount is carried forward to the next year. This means that in 1999 the invoice is reduced by 51,12 instead of 51,13 euro and an open amount of one cent remains. This type of rounding difference is not corrected as it occurs in a closed fiscal year and is therefore not relevant.

Example 2: Rounding error in payment reconciliation

If you are using the payment selection of the original function (see also: Note 360667), you also have rounding differences in payments. Though this does not have a negative effect as these payment selections do not support payment reconciliation, instead they express open invoice amounts.

When invoices are already closed, this problem does not occur and when invoices are open, the problem is corrected with the next payment (with the closing payment at the latest).

If you are using payment selection with enhanced functions, rounding errors may occur during conversion that the system cannot solve, for example:

An invoice of 100 USD has one vendor and two expenditure lines. The invoice was posted in USD and then converted into euros. Then, a payment of 51.13 euro is made:

BTART	WRTTP	GJAHR	USD	EURO	Paymt ref.	Inv. ref.
100	54	2000	50	25,56-	1	1
100	54	2000	50	25,56-	1	1
200	54	2000		25,56	2	1
250	57	2000		25,56-	2	1
200	54	2000		25,57	2	1
250	57	2000		25,57-	2	1

This example shows that S200 converted the amount of the payment correctly. Payment reconciliation and day-end closing are correct. The payment status (PAYFLG) is set and the invoice is consequently not carried forward as part of fiscal year change operations.

But:
After rounding, the total of the expenditures is only 51.12 euro, however it has been reduced by 51.13 euro. Though this has no effect on the assigned values, as the 200 and 250 records are balanced. In this case, the fact that either the payment reconciliation is correct or the expenditure is reduced to zero applies. Mathematically, both cannot apply together.

Selection

The settings you made in the preparations you made in the Define Settings for Reconciling FI Documents IMG activity are copied for the automatic call in the RECON-Phase.

For test purposes, we recommend you restrict your selection to single FI documents in the Document Selection screen area and the Company Code, Fiscal Year and Document Number fields in order to check correction postings made by this program.

Output

We recommend that you restrict the list display to show errors by setting the Only display errors indicator.

Activities

1. Enter your FM area and the current fiscal year (fiscal year for FM documents that have not been converted).
2. Run the program.

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 10545 Date: 20240601 Time: 025035     sap01-206 ( 132 ms )