SAP ABAP Data Element PCA_BTC (Batch: Synchronous update)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE1 (Package) Profit Center Accounting
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE1 (Package) Profit Center Accounting
Basic Data
Data Element | PCA_BTC |
Short Description | Batch: Synchronous update |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
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 | BTC | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Background |
Medium | 20 | Batch: Synch. update |
Long | 30 | Batch: Synchronous update |
Heading | 40 | Batch: Synchronous update |
Documentation
Definition
With this indicator, you can control update module callup.
If the indicator is not set, data is updated asynchronously. This is the default setting, and should not be changed if possible.
If errors occur with data updating when you need to access the same data repeatedly in quick succession, and this data is locked by a previous update call, you can set this indicator. By doing so, you switch to synchronous updating. Note that this increases the time required to update data, so increasing the program's runtime. This is because, with every posting, you have to wait until the previous posting has been completed before the program can continue.
History
Last changed by/on | SAP | 19990326 |
SAP Release Created in |