SAP ABAP Data Element NO_COMMIT (Do not execute COMMIT)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷
IS-U (Application Component) SAP Utilities
⤷
EE00 (Package) IS-U: General (Domains and General Objects)
⤷
⤷
Basic Data
| Data Element | NO_COMMIT |
| Short Description | Do not execute COMMIT |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KENNZX | |
| 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 | No COMMIT |
| Medium | 15 | No COMMIT |
| Long | 20 | No COMMIT |
| Heading | 2 | NC |
Documentation
Definition
This field specifies, whether a COMMIT should be done (with X_UPD_ONLINE = 'X') within an object function module.
Note the following:
- X_UPD_ONLINE = 'X' and X_NO_COMMIT = 'X'
No COMMIT WORK is done in the object function module.
Background: The object is dependent on other objects, which have to manage the main screen. A COMMIT WORK would lead to inconsistent data. - X_UPD_ONLINE = 'X' and X_NO_COMMIT = SPACE:
A COMMIT WORK is done in the object function module.
Background: The subscreen object can act as an independent object.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |