Description
This report program generates the records for loan transactions in CashManagement.
You can indicate whether an update run or a test run should be carriedout. Before you carry out the update run, you should make sure thatnone of the data that will be generated by the program is already onthe database (tables FDD1, FDSB and FDSR - see below for moreinformation). If the data already exists, the program will beterminated.
You should carry out a test run before the update run and correct anyerrors which occur. No data is updated during a test run.
A number of selection options are available. The system checks whetherauthorization to insert records in Cash Management exists for thecompany code and business area.
If an error does not result in termination of the program, the systemdisplays a log generated by the program. Errors can also be listed inthis log.
You are recommended to proceed as follows:
Check whether the prerequisites for the Cash Management update arefulfilled:
Cash Management is set to active for the company code (View V_001_I).
Planning levels are assigned for Financial Assets Management (viewsV_T036V and V_T036W).
The relevant flow types are flagged as 'Relevant to CM' and have anactivity indicator between '01' and '04'.
A cash management group is defined in the customer master records forthe customers defined in the loan (main borrower and alternativepayer).
If you want the bank account to be updated (instead of the customer), aplanning level must have been maintained for this account in theaccount master data. You can only update the bank account if the loanis not managed on the basis of customer accounts. For these loans, youcan specify the house bank and house bank account in the paymentdetails. The system then updates this account, provided that theplanning level has been maintained.
If no disbursement has been entered for the contract, check Customizingto see whether planned cash flows are written to the database beforedisbursement (IMG activity: Company Code-Dependent Settings forProduct Type). If not, Cash Management is not updated.
If one of these prerequisites is not fulfilled, the system does notdisplay an error message. The record is simply ignored during theupdate.
Start the program as a test run (in the background if you have largeamounts of data).
Check the job log to see if the program was terminated.
Check the spool log for possible errors.
Correct any errors and restart the run.
Delete the data to be regenerated from the Cash Management tables FDD1,FDSB and FDSR. You can delete table FDD1 completely if you intend torun the report program without making any selections. In tables FDSB(bank account totals records) and FDSR (customer and vendor totalsrecords), you should only delete the records which will subsequently beregenerated, and not the records resulting from FI, MM or SD postings,payment advices or memo records. Via the cash position and liquidityforecast, you can determine the level at which the loans update hastaken place and then delete these records. To do this, you need to usea 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 toselect a planning group which contains all levels and all relevantaccounts or planning groups.
Start the program as an update run (in the background, where possible).
Check the job log and the spool log.
If errors occur, use the cash position/liquidity forecast to checkwhether records have already been updated in Cash Management. You haveto delete any such records before you restart the run.
If no errors occurred during the run, look at the cash position/liquidity forecast to check if the data has been transferred to CashManagement.