SAP ABAP Data Element CO_COMMIT_BY_ORDER (Indicator: System functions per order in a LUW)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-CIC (Application Component) Interaction Center WinClient
⤷
CO (Package) R/3 Application development: PP Production orders

⤷

⤷

Basic Data
Data Element | CO_COMMIT_BY_ORDER |
Short Description | Indicator: System functions per order in a LUW |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FLAG | |
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 | LUW |
Medium | 15 | Order LUW |
Long | 20 | Order LUW |
Heading | 3 | LUW |
Documentation
Definition
Determines that the system tries to bundle up all function entries for an order in a Logical Unit of Work (LUW).
The sequence of function execution within the LUW is determined by the sequence number.
Use
The summary has the advantage that the data for the order must only be read once from the database. If the functions are executed in separate LUWs then the data for every function must be read in again.
The disadvantage of bundling is that a termination when executing an entry for the relevant order has the consequence that the other entries are also not executed.
Procedure
Examples
Dependencies
No function entries can be combined that belong to different groupings. Groupings are formed within a function (for example, a material availability check in a particular sequence).
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |