Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-PWB (Application Component) Print Workbench⤷
EEPW (Package) Print Workbench
Basic Data
| Data Element | EFG_DTE_OCL_CONTROL |
| Short Description | Control of Open/Close Optimization |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EFG_OCL_CONTROL | |
| 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 | ControlOCL |
| Medium | 15 | OCL Control |
| Long | 20 | O/C Optim. Control |
| Heading | 10 | ControlOCL |
Documentation
Definition
Used in adjusting OPEN/CLOSE optimization to the requirements of the form class or application form.
Use
In the standard system, OPEN/CLOSE optimization is controlled by the print parameters.
If the form class requires the deactivation of OPEN/CLOSE optimization, this can be displayed in the attributes of the form class.
A deactivation can be required, for example, when printing of an attached payment medium is integrated in the form class. If you want the attached payment medium to always be created, then, for technical reasons, you have to deactivate the OPEN/CLOSE optimization in the attributes of the form class. However, if the system can dynamically decide to create an attached payment medium (for instance, dependent on the application data), then OPEN/CLOSE optimization must be controlled by the print parameters.
In the form class, the indicator serves as a means of documentation and it is automatically adopted when the application form is created. When you create an application form, you have to adjust the control of open/close optimization, depending on the active hierarchy levels of data procurement and on program enhancements. Using the example above, if you suppress printing of an attached payment medium that is integrated in the application form, then OPEN/CLOSE optimization should be controlled by the print parameters.
In application forms, the indicator is evaluated in the print process where it has the highest priority.
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 710 |
