Entering content frame

Function documentation Running a Cash Concentration Locate the document in its SAP Library structure

Use

Depending on your requirements, you can either run a cash concentration for a single master contract or for a particular number of master contracts in a parallelized mass run (in end-of-day processing, for example).

The reports used are methods in the business object Master Contract. You are provided with the following reports for the cash concentration run:

·        RBCA_CC_START_SNG (single run for cash concentration)

·        RBCA_CCON_RUN_PACK_PP (mass run for cash concentration with package template)

·        RBCA_CCON_RUN_PP (mass run for cash concentration without package template)

For more information on the reports, see the report documentation in the system by choosing This graphic is explained in the accompanying text.

You start the single run from the SAP Easy Access menu by choosing Account Management ® Master Contract ® Cash Concentration for a Master Contract ® Start Cash Concentration.

You can start the mass runs from the SAP Easy Access screen, by choosing Account Management  ® Periodic Tasks  ® Cash Concentration ® Start Mass Run with Package Template or Start Mass Run Without Package Template.

For more information about Cash Concentration, see Cash Concentration.

Prerequisites

The cash concentration can be run only for accounts that belong to a master contract.

Before you can use the mass run for the cash concentration with a package template, you need to create the package templates. For more information, see Create Package Templates for Mass Run for Cash Concentration.

...

...

Result

The system displays a processing log in SAP Easy Access, under Account Management ® Logs  ® Cash Concentration ® Application Log for Cash Concentration.

Once you have corrected the errors, you can restart the cash concentration run.

Responses to Errors in the Mass Run

If a participant account is incorrectly processed during a parallelized cash concentration, its master contract is always flagged for a restart, and a postprocessing order (PPO-Order) is created.

The way in which the system continues processing depends on the following:

·        The type of error: There are individual errors and fatal errors.

·        Whether the Partial Execution indicator is set in the master contract.

An individual error occurs if, for example, a participant account cannot be cleared due to an exceeded limit or a posting lock.

If the error is an individual one, the system only continues processing the affected master contracts if the Partial Execution indicator is set. Otherwise, the system immediately continues processing the next master contract in the package. The system generates a PPO order for the affected master contract.

A fatal error occurs, if for example, there is a database inconsistency.

If a fatal error occurs, processing stops for all of the master contracts in this package. All of the master contracts that have not been processed for this reason are placed in a PPO order for postprocessing.

All accounts that are affected by an error (accounts from a whole branch or all accounts in the master contract) are given an internal lock. This lock only applies within a package during the runtime, and prevents these accounts from being processed again in the same cash concentration run. This means that an account, which is assigned to two master contract as a participant, cannot be processed in the second master contract after an error during the execution of the first master contract.

See also:

Displaying and Editing Next CC Dates

Displaying Cash Concentration Postings

Leaving content frame