Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FBAS (Package) Financial accounting 'Basis'
Basic Data
Data Element | XSYUP_FZ |
Short Description | Indicator: Synchronous database updates |
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 | 0 | |
Medium | 0 | |
Long | 25 | Synchronous updating |
Heading | 25 | Synchronous updating |
Documentation
Definition
Indicator that the documents generated by the payment program are posted synchronously rather than asynchronously in a separate process.
Use
If you set the indicator, then you can guarantee that all payment documents will have been posted when the payment run has ended.
This way it is possible to schedule creation of the forms and data media without any problems in the same job.
The following problems can occur with asynchronous posting:
- The print programs or data medium programs check whether payment documents exist but not all documents have yet been updated. The forms or data media are incomplete.
- The print programs or data medium programs do not check whether payment documents exist. If a termination occurs when updating a document, then the payment document is not posted but the payment form or the record is created on the data medium.
Dependencies
With synchronous updating, the runtime of the payment program is generally increased since the whole process has to be carried out using a background process. With asynchronous updating, the process is divided up between a background process and several update processes.
The total burden on the system from database accesses is reduced slightly.
Procedure
Before you generally decide on synchronous updating, you should, if possible, compare the amount of time needed for both options in the test system.
History
Last changed by/on | SAP | 19960409 |
SAP Release Created in |