Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-SCR (Application Component) SAPscript⤷
STXD (Package) SAPscript
Basic Data
| Data Element | TDBOOL |
| Short Description | Checkbox (yes or no) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TDBOOL | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
Supplementary Documentation - TDBOOL 0001
Use
You use the Text Node attribute to determine whether to display the text as a new paragraph (default), in a new line or whether to append it directly to the previously displayed text.
Dependencies
Example
Supplementary Documentation - TDBOOL 0002
Use
A text node can refer to the contents of another text module as include text. The system includes the contents of the include text only at the moment it processes the text for output.
If the text key of the include text is incorrect, the system issues an error message. You can use this checkbox to suppress this error message.
Dependencies
Example
Supplementary Documentation - TDBOOL 0003
Use
You must not specify the graphic type (grid screen black/white or color) statically. Instead, you can pass it dynamically using a symbol.
Dependencies
Example
Supplementary Documentation - TDBOOL 0004
Use
If in the general attributes of a paragraph node the field "Data - Repeat processing" is set, a new tab Data appears. This tab distinguishes for repeated processing between a simple DO loop and a LOOP on an internal table. This repeats processing for the entire paragraph node, for one table line at a time.
Dependencies
Example
Supplementary Documentation - TDBOOL 0005
Use
If in the general attributes of a node the field "Output type - table" is set, a new tab Table appears. This tab allows you to maintain the layout of a dynamic table structure.
Each table has a fixed table width and at least one line type. Each line type can have a different number of columns, but the overall width (total of all columns) must be constant. For each column, specify a width. You can also use a tool for graphical layout of the table.
Dependencies
Example
Supplementary Documentation - TDBOOL 0006
Use
If in the general attibutes of a paragraph node the field "Output type - template" is set, a new tab Template appears. This tab allows you to maintain the layout of a static table, whose size is always fixed.
You use templates to mirror a static complex layout, for example, tax forms. A template offers the same formatting options as a table, except that the height of each cell is static, which means that any longer text is truncated. The overall height of the template is constant as well and restricted to one page. In contrast to tables, templates allow output in any sequence.
Dependencies
Example
Supplementary Documentation - TDBOOL 0007
Use
If in the general attibutes of a paragraph node the field "Output type - unstructured" is set, the node is a folder. In contrast to tables or templates a folder only serves to combine several subnodes, and retrieves data, if required, in a loop. The folder does not need any other attributes, therefore no new tab page appears.
Dependencies
Example
Supplementary Documentation - TDBOOL 0008
Use
The address type (organization, person, work place address) must not be specified statically. You can also pass it dynamically using a symbol.
Dependencies
Example
Supplementary Documentation - TDBOOL 0009
Use
You need not specify use of a street or P.O. box for address formatting statically. You can also pass it dynamically using a symbol.
Dependencies
Example
Supplementary Documentation - TDBOOL 0010
Use
In a section, output of a header or footer can be determined using events. To do this, select a header and/or footer on the Events tab of the section node. In the form tree, the corresponding event node appears.
You can display the header at the start of a section and/or after a page break, the footer before a page break and/or at the section end. For the footer, you must specify a height to tell the composer how much space to reserve for the footer. You typically use a footer to display subtotals, since this area is processed only at the moment of the page break. Under the event node, you can append, for example, texts for the heading or footer line of a section (even with their own line type in the output attributes of the texts).
Dependencies
You are not allowed to nest events. After defining a header or footer for a section, no other subordinate section can have its own header or footer. In addition. if you use both header and footer, you must always define them together in the same section.
Example
Supplementary Documentation - TDBOOL 0011
Use
You can flag one line type as default line type. If a subnode of the table has no assigned line type, the system uses the default line type.
Dependencies
Example
Supplementary Documentation - TDBOOL 0012
Use
When you copy a text module, the system usually also copies the corresponding style and enters it into the output options of the text node. You can overwrite or delete this setting in the options. If the style name is initial, the style is inherited from the output options of superior paragraph nodes or from the form attributes. If you mark the field "Always copy style from text module" you can overrule this, which means that paragraph and character formats are then always taken from the style specified in the text module.
This field is of special importance if you enter the text module dynamically using a field name. In this case, the style name is determined only at runtime and is still unknown when you create the form. Therefore, in the copy action, the system cannot enter a style name into the output options of the text node. This means that the style name is at first initial and would be inherited from the superior node, which is what you prevent by using the checkbox.
Dependencies
Example
Supplementary Documentation - TDBOOL 0013
Use
The grid that can be chosen at will, is a visual help for editing forms or tables. It is also used by the function 'Align with grid'.
Dependencies
Example
Supplementary Documentation - TDBOOL 0014
Use
The main grid is an extra help that can be activated in addition to the normal grid; it can be defined at will.
Dependencies
Example
Supplementary Documentation - TDBOOL 0015
Use
The ruler indicates the cursor position and the position of the marked window or table.
Dependencies
Example
Supplementary Documentation - TDBOOL 0016
Use
As an option, the ruler can indicate the grid positions.
Dependencies
Example
Supplementary Documentation - TDBOOL 0017
Use
If automatic zooming is active, always the entire area of the Form Painter or Table Painter is displayed. The zoom factor, therefore, depends on the space available for this area.
Dependencies
Example
Supplementary Documentation - TDBOOL 0018
Use
With this setting, newly painted windows in the Form Painter as well as moved windows in the Form or Table Painter are always aligned with the grid. Any changes to position or size can only be performed in accordance with the predefined grid.
Dependencies
Example
Supplementary Documentation - TDBOOL 0019
Use
This setting activates the paint mode, in which you can create new windows in the Form Painter as in any paint program.
Dependencies
Example
Supplementary Documentation - TDBOOL 0020
Use
With transparent windows or transparent tables, the predefined grids and main grids show through. If you defined a background graphic, it also shows through. This allows you to exactly position windows and tables.
Dependencies
Example
Supplementary Documentation - TDBOOL 0021
Use
This setting allows you to draw new lines and columns within tables and templates in the graphical Table Painter.
Dependencies
Example
Supplementary Documentation - TDBOOL 0022
Use
The enabled crosshair within Form Painter and Table Painter appears at the current mouse position. Thus, you can read the current mouse position also from the ruler.
Dependencies
Example
Supplementary Documentation - TDBOOL 0023
Use
The Table Painter can display the predefined table pattern of a table or template.
Dependencies
Example
Supplementary Documentation - TDBOOL 0024
Use
The Form Painter in Smart Forms appears at the right margin after it is activated. It is then available throughout the entire form processing.
Dependencies
Example
Supplementary Documentation - TDBOOL 0025
Use
In graphic windows in the Form Painter, you have the option of displaying placeholders instead of the assigned graphic.
Dependencies
Example
Supplementary Documentation - TDBOOL 0026
Use
As an option, you can suppress or display the toolbar above the Form Painter and Table Painter. This toolbar contains frequently used functions.
Dependencies
Example
Supplementary Documentation - TDBOOL 0027
Use
As an option, you can draw a box around the Form Painter and Table Painter which creates a three-dimensional effect. In the 'New Visual Design' this box consists of a thick line without the three-dimensional effect.
Dependencies
Example
Supplementary Documentation - TDBOOL 0028
Initialize for a Calculation.
Use
Activate this setting if you want the target field name to be reset to the initial value before the loop starts.
See also: Extended Help in the SAP Library.
Dependencies
Example
Supplementary Documentation - TDBOOL 0029
Use
Activates or deactivates the Undo / Redo function for form changes.
If it is active, you can undo all form changes until you save or activate the form.
You can redo undone form changes until you continue editing the form.
You can undo and redo several times, which means that you cannot only undo the previous form change, but any form changes before that as well.
Deactivating the Undo / Redo function can improve performance. This depends, among other things, on the size of the form. If you notice a decrease in performance during form processing, you can deactivate the Undo / Redo function. It is not possible to avoid the decrease in performance any other way, because the temporary saving of the form always takes up some runtime.
Dependencies
Example
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
