Ansicht
Dokumentation

RFFDTR00 - Cash Management Layout Report for Treasury

RFFDTR00 - Cash Management Layout Report for Treasury

Addresses (Business Address Services)   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Description

The report sets up Cash Management and Forecast in the foreign exchange, money market, derivatives, and securities area (the planned flows in securities are set up by program RTPM_CM_UPDATE).

The report is not relevant if you have activated the update via position management (table TRCC_SWITCH). In this case, you should use report RTPM_CM_UPDATE.

Before you run the report, you must make sure that no data to be set up by this report is already available in the database (table FDT1, FDSB2 and FDSR2 - see below for further information), otherwise the report will be terminated.

Unlike the setup programs for planned flows in securities, you cannot carry out a test run before the productive run using this program (since the function modules used have different update logic).

If termination does not occur due to an error, a log created by the report is displayed. Errors can also be listed in this log:

We recommend you proceed as follows:

  1. Check whether the prerequisites for the update in Cash Management and Forecast have been met:
    1. The allocation of planning levels has to be maintained for Financial Assets Management (views V_T036V and V_T036W)
    2. You have to select the field "Relev.to CMF" in the appropriate flow types.
    3. If the update is made in the bank account in Cash Management and Forecast, a planning level has to be maintained for this account in the G/L account master record. Here, this level only determines whether Cash Management and Forecast should be updated or not. The level used for the update is specified by the allocation table mentioned above (view V_T036V and V_T036W).
    4. If the update is made in Cash Management and Forecast via the business partner, a customer has to be allocated to this business partner and a planning group has to be maintained in the customer master record.
  • An error message does not appear if one of these prerequisites is not fulfilled. The record is simply ignored during the update.
  1. Delete the data which should be set up again from the Cash Management and Forecast tables FDT1, FDSB2 and FDSR2.
Table FDT1 can be completely deleted if you run the report without making any selection options.
In FDSB2 (bank account totals record table) and FDSR2 (customer and vendor totals record table), you may only delete the records which will subsequently be set up again and not the records which result from FI, MM or SD postings, payment advices or memo records. Via the cash position and the liquidity forecast, you can determine on what level the update for foreign exchange, money market and derivatives has taken place and then delete these records. In order to do this you have to write a small program which contains for example, the instruction DELETE FROM FDSB2 WHERE BUKRS = '0001' AND EBENE = 'TS' (see Note 156239).
When you call up the cash position/liquidity forecast, you enter a group which contains all levels and all relevant accounts or planning groups.
(If you use the same levels for securities transactions and planned securities movements, you cannot restrict deletion of tables FDSB2 and FDSR2 to securities transactions only - you delete the records for the planned movements too. In this event, it is best if you also delete table FDC1 in full and then access program RTPM_CM_UPDATE again.)
  1. Start the program (in the background, if you have large amounts of data).
  2. Check the job log to see if the program was terminated.
  3. Check the spool log for possible errors.
  4. Check whether updates were terminated.
  5. If errors occurred, you have to delete the records which have already been updated from Cash Management and Forecast and then repeat the run.
  6. If no errors occurred during the run, you can check whether the data was transferred to Cash Management and Forecast by viewing the cash position and the liquidity forecast.





General Data in Customer Master   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4327 Date: 20240520 Time: 131505     sap01-206 ( 78 ms )