SAP ABAP Data Element ENQOBJECT1 (Name of lock object)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
Data Element | ENQOBJECT1 |
Short Description | Name of lock object |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | AS4TAB | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table | DD02L |
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 | Lock objct |
Medium | 15 | Lock object |
Long | 30 | Lock object |
Heading | 10 | LockObjct |
Documentation
Definition
The FI-GLX planning and rollup functions both block the planned or rolled-up dataset during the program run. For this, you need to define a blocking object in the Data Dictionary. You can use the blocking object EGGLT0 for table GLT0 as a reference object. The blocking object is called EGxxxxxxxE, where xxxxxxx has a maximum length of 7 characters, and is defined by the user. It is common to use the name of the summary table to be installed for xxxxxxx. Apart from the fields RPMAX and DRCRK, all key fields of the table are to be included as exclusive blocking fields. Afterwards, you have to activate the blocking object.
If you want to use the planning and rollup functions, you must enter a blocking object here.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |