Ansicht
Dokumentation

IDCFMHU_OFF_BALANCE_FW - Off-Balance Posting - FX and FRA (Hungary)

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Purpose

In accordance with the Hungarian legal requirements, forward exchange (FX) and forward rate agreement (FRA) transactions must be posted off-balance for each flow type and in the corresponding foreign exchange on the contract date. These transactions must be posted back to the G/L accounts in the balance sheet on the maturity date (FX transactions) or on the fixing date (FRA transactions).

The standard SAP Treasury and Risk Management (FIN-FSCM-TRM) functions generate the postings relevant for the cash flow, however, they cannot handle off-balance postings. This report can perform these off-balance postings.

You use this report as follows:

1. On the contract date, when the transaction has been settled, you execute this report with the posting option enabled.
2. On the maturity date (FX transactions) or on the fixing date (FRA transactions), you use the standard Treasury: Post Flows (transaction TBB1) program to post the transactions to the balance sheet accounts.
3. On the same date, you use the current report to withdraw the transaction from the off-balance accounts by making opposite off-balance postings.

The report can also reverse items in case the relevant transaction is reversed after it has been posted off-balance.

You can run this report periodically (daily, weekly, or monthly) as required, both online or in background processing.

Integration

Prerequisites

You have made the settings in Customizing for Financial Supply Chain Management, under Treasury and Risk Management -> Transaction Manager -> Country-Specific Functions -> Hungary -> Off-Balance Postings, in the following activities:

• Define Parameters for Off-Balance Postings

• Assign G/L Accounts for Off-Balance Postings

Features

Selection

On the selection screen, you must enter the company code and the base date. If you only fill these obligatory fields, the system modifies the base date during execution and its new value will be the date of the current execution.

Optionally, you can select one or more specific transactions. In this case, the program does not update the base date during execution. This is to avoid that in the next run, the program selects only these transactions with the new base date and it might ignore some relevant transactions.

On the selection screen, you can also specify whether you want to execute the report in test run or with real postings. In case of test run, the system does not generate any posting document.

Standard Variants

Output

The output of the report is displayed either in a standard format with a header or in an ALV grid, depending on your selection.

The output shows the details of each transaction and if the report has performed any posting, the posting document number is displayed in the Document Number field. If the report cannot perform posting for a given item, the padlock in the Document Status field is in closed position.

The output also shows reversed items, but the report does not generate a document for these items. The report only generates a document if the transaction was reversed after it had been posted off-balance. In this case, the relevant reversal document number is shown in the Reversal field.

Activities

When you execute the report with the posting option enabled, it performs the following tasks:

1. Based on your selections, it reads the following:

• New or changed transactions since the base date

• Previous items with errors

• All open items

1. It maps G/L accounts to the processed items based on your Customizing settings.
2. It performs posting and generates a posting document in case the following conditions are fulfilled:

• The transaction is active.

• The transaction is settled (off-balance) or posted (withdrawal).

• The posting date is not in the future (the value date of the posting document is not later than the system date).

• G/L accounts are available.

• The amount to be posted is bigger than zero.

1. It reads and pairs previous data with the current data.
2. It reverses the previous document in case the following conditions are fulfilled:

• The previous document exists.

• Any key fields have been changed (amount, transaction currency, G/L account, transaction date).

• It is not allowed to post the item.

• The item has a reversal error.

1. It flags reversed and posted items.
2. It displays data in the output according to the selection parameters.

Example

ABAP Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 6285 Date: 20240520 Time: 084456     sap01-206 ( 84 ms )