Ansicht
Dokumentation

RFFDDA00 - Cash Management Structure Report-Loans

Description

This report program generates the records for loan transactions in Cash Management.

You can indicate whether an update run or a test run should be carried out. Before you carry out the update run, you should make sure that none of the data that will be generated by the program is already on the database (tables FDD1, FDSB and FDSR - see below for more information). If the data already exists, the program will be terminated.

You should carry out a test run before the update run and correct any errors which occur. No data is updated during a test run.

A number of selection options are available. The system checks whether authorization to insert records in Cash Management exists for the company code and business area.

If an error does not result in termination of the program, the system displays a log generated by the program. Errors can also be listed in this log.

You are recommended to proceed as follows:

1. Check whether the prerequisites for the Cash Management update are fulfilled:
1. Cash Management is set to active for the company code (View V_001_I).
2. Planning levels are assigned for Financial Assets Management (views V_T036V and V_T036W).
3. The relevant flow types are flagged as 'Relevant to CM' and have an activity indicator between '01' and '04'.
4. A cash management group is defined in the customer master records for the customers defined in the loan (main borrower and alternative payer).
5. If you want the bank account to be updated (instead of the customer), a planning level must have been maintained for this account in the account master data. You can only update the bank account if the loan is not managed on the basis of customer accounts. For these loans, you can specify the house bank and house bank account in the payment details. The system then updates this account, provided that the planning level has been maintained.
6. If no disbursement has been entered for the contract, check Customizing to see whether planned cash flows are written to the database before disbursement (IMG activity: Company Code-Dependent Settings for Product Type). If not, Cash Management is not updated.
   

If one of these prerequisites is not fulfilled, the system does not display an error message. The record is simply ignored during the update.

1. Start the program as a test run (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. Correct any errors and restart the run.
5. Delete the data to be regenerated from the Cash Management tables FDD1, FDSB and FDSR. You can delete table FDD1 completely if you intend to run the report program without making any selections. In tables FDSB (bank account totals records) and FDSR (customer and vendor totals records), you should only delete the records which will subsequently be regenerated, and not the records resulting from FI, MM or SD postings, payment advices or memo records. Via the cash position and liquidity forecast, you can determine the level at which the loans update has taken place and then delete these records. To do this, you need to use a short report program, which might, for example, contain the command: DELETE FROM FDSB WHERE BUKRS = '0001' AND EBENE = 'DP'(-> Note 156239). When you call up the cash position and liquidity forecast, you need to select a planning group which contains all levels and all relevant accounts or planning groups.
6. Start the program as an update run (in the background, where possible).
7. Check the job log and the spool log.
8. If errors occur, use the cash position/liquidity forecast to check whether records have already been updated in Cash Management. You have to delete any such records before you restart the run.
9. If no errors occurred during the run, look at the cash position/ liquidity forecast to check if the data has been transferred to Cash Management.