Ansicht
Dokumentation

RFVSOLD2 - Loans: Post Planned Records

BAL Application Log Documentation   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Purpose

The automatic posting function performs the update run for the debit and credit positions. You generate both debit and credit positions for the contracts you select.

Enter the relevant selection values for the automatic posting report in the Loans: Post Planned Records screen:

The following selection values are available:

• Company code

• Contract number

• Partners

• Product type

• Loan type

• Loans class

• Contract currency

• Payment method (for customer account postings)

• List of payment methods (for postings based on payment details)

• Debit position date

• Payment date (where different to posting date)

All planned records for the above contracts with a payment date smaller than or equal to the debit position date you enter are converted into debit or credit positions.

If SEPA is active (Customizing: Loan > Basic Settings > Country/Region-Specific Requirements > SEPA Activation per Company Code), the SEPA direct debit planned records (with a payment method that requires a SEPA mandate) are posted considering the SEPA direct debit key date.

This key date represents the date on which the item shall be available for payment processing. The planned records is posted as close as possible to their due date (CML payment date) with consideration of the lead time resulting from the mandate (and other criteria, if required). See also note 1736468,

The SEPA minimum posting date sets the earliest posting date. This must be later than the current date and earlier than the SEPA key date.

The SEPA Payment Date (Up To) provides you with the option to limit the selection of SEPA direct debits using a "To-date". If you limit the selection, then only SEPA direct debits that have a payment date earlier than the "To-date" are selected. Without a "To-date", the selection is determined by the SEPA key date as before.

The parameters for posting control are

• Posting date

If it's empty the payment date is used

• Document date

• Document text

• Test run

• Log

• Output in own log (background only)

• Posting in spite of errors in individual contracts

The debit position posts either all planned records for each borrower or no planned records at all. This is not always the desired system behavior, particularly if there are several contracts for individual borrowers and only one or few of these contracts cannot be posted to (for example because of a missing release).

If you set the indicator, the system removes only the planned records of the affected contract from the posting. The system checks the planned records of the remaining contracts for the borrower, and if there are no errors, it posts them.

The flag works only for checks that happen in loans management like missing release. When the posting data has been built and sent to FI posting interface it is again an all or nothing scenario.

• Output of unposted contracts

If this flag is set, a list with all non-posted contracts is created This is useful for postprocessing purposes especially if the flag "Posting in Spite of Errors in Individual Contracts" is set.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example

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

Length: 4207 Date: 20240601 Time: 212200     sap01-206 ( 65 ms )