Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
Basic Data
| Data Element | CFENQUEUE |
| Short Description | Report execution locked? |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| 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 | Lock |
| Medium | 15 | Lock |
| Long | 20 | Lock |
| Heading | 1 | E |
Documentation
Definition
If the flag is set, then both the underlying form and the report itself are blocked when executing a report. This means that a change to the form (or the report) is not possible, as long as the execution of the report has not finished.
If the flag is not set, then a form (or the report) can be changed, if the relevant report is directly displayed or executed. In the case of a change to the report, the relevant form, as before, is blocked. A change to the form is then not possible. This relaxation to the blocking concept does, however, have the following disadvantage:
Example:
A report is executed and at the same time the assigned form is changed and the changed form also saved. Now, the execution of the report may be ended with the runtime error 'LOAD_PROGRAM_LOST'. The cause of the runtime error cannot be seen by the person executing the report but is determined by the simultaneous change to the form.
History
| Last changed by/on | SAP | 19971104 |
| SAP Release Created in |
