Hierarchy
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
Data Element | XSUMA_KK |
Short Description | Asynchronous Updating of Totals Records |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Async.updt |
Medium | 15 | Asynch.update |
Long | 35 | Asynchronous updating of totals |
Heading | 10 | Async.updt |
Documentation
Definition
This indicator determines whether the totals records in Contract Accounts Receivable and Payable can be updated asynchronously for mass postings (such as document transfer, payment run, payment lot).
Use
The totals records form the basis for updating G/L accounting. The advantage of using an asynchronous update is that the system performance is better.
However, if you are updating asynchronously for mass postings and a system termination occurs, the data that arises may be inconsitent. The posting totals produced may be incomplete.
In this case, the reconciliation key concerned is marked accordingly. Before the transfer to the general ledger however, you have to manually close the reconciliation key and then correct the totals records using reports RFKKABS1 ad RFKKABS2.
Procedure
Only set the indicator for asynchronous updating if you have performance problems when creating documents during mass processing. In this case, check whether performance actually does improve after setting the indicator.
If however, the affect on performance is only minor, then deselect this indicator and use sychronous updating.
Examples
Dependencies
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |