Posting: Mass Processing (SAP Library - Loans Management (FS-CML))

Posting: Mass Processing

Usage

This function processes all the selected planned records for which automatic posting is permitted (posting control key 01).

The planned records are posted according to the settings in account determination and converted to actual records. The resulting posting is displayed in posting log and the planned records are deleted. The actual records correspond to the posting documents.

The system displays the resulting posting in a posting log. The posting run skips any contracts which produce errors and lists them in an error log.

The following steps describe how to prepare for and post mass processing.

Prerequisites

Before you can start an automatic posting run, you must make the following preparations:

Update condition-based planned records.

Choose Execute Posting ® Mass Processing ® Preparation ® Update Planned Records. You should do this at least every six months. Planned records are generated for the CM period but not beyond the end of the fixed interest period.

If you have foreign currency loans or use reference interest rates, you should run the planned record update before the automatic posting run to ensure that the current values are posted.

Features

Automatic posting activities

You can only execute the automatic posting run on the basis of planned records. Planned records are flows flagged for posting.

The following types of planned record exist:

Condition-based planned records (for the loan position)

Condition-based planned records are generated at a certain stage in the loan process (or loan status, usually with the first disbursement) for a defined CM period (usually 2 years) according to the settings in Customizing. To update the planned records later on, you must trigger the update yourself.

Planned records resulting from conditions can only be posted with the automatic posting function if the posting control key is 01 for the condition item. In most cases, the mass processing function would be used to post the condition flows.

Example

Examples of condition-based planned records:

Interest
Charges (periodic)
Repayments

and so on

Other planned records (from posting applications for individual contracts)

You can use the automatic posting function to process planned records saved by other posting applications.

Alternatively, you can use the respective posting applications to post other planned records for individual contracts (immediately, or at a later point in time).

Example

Examples of these are:

Payables and receivables that do not result from conditions (such as unscheduled repayments entered with the Individual Processing function)

Disbursements and withholdings for overdue items (planned records from the disbursement)

Waivers and write-offs (planned records from open item processing)

Other automatic posting activities involve generating and posting additional planned records. This depends on the following contract conditions and special indicators in the planned record:

Clear receivables
Clear advance payments
Split receivables to post subsidies

Note

For more information, see Mass Processing: Posting.

If you only save planned records for automatic posting when you disburse the loan, the following planned records may need to be generated and posted during the automatic posting run:

Drawings on disbursement
Withholdings
Withholdings for overdue items

Note

For more information, see Mass Processing: Posting.

Activities

Starting the program

You usually start the automatic posting run as a background job. Depending on the size of your loan portfolio, the program runtime can be very long. You should therefore avoid using the mass processing function when the system is in use. You can also run the program online, particularly for individual contracts. During the run, these contracts must not be processed.

Simulation run

The automatic posting function also lets you perform a simulation run. The posting log for the simulation run does not contain document numbers.

Postprocessing

For loans given, you need to run the program for clearing any overpayments and run the payment program to collect the receivables by direct debit after the automatic posting run. (Execute Postings ® Mass Processing ® Postprocessing ® Clear Overpayments Automatically).

Note

You must ensure that you clear any overpayments before you carry out the direct debit run.

Other payments (for example, by bank transfer) are posted to the general ledger and subledger via the FI bank statement (choose Receivables/Payments Management ® Incoming Bank Statement ® Enter Manually/Import).

For loans taken use the function Automatic Payment Transactions – Payment Request.