Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-SSF (Application Component) Smart Forms⤷
SMART (Package) SAP Smart Forms
Basic Data
| Data Element | TDSFOPD |
| Short Description | SAP Smart Forms: Operand |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TDSFOPD | |
| Data Type | CHAR | Character String |
| Length | 132 | |
| Decimal Places | 0 | |
| Output Length | 132 | |
| 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 | Operand |
| Medium | 15 | Operand |
| Long | 20 | Operand |
| Heading | 7 | Operand |
Documentation
Definition
Specification of a field name or operand
Supplementary Documentation - TDSFOPD 0001
Use
When writing ABAP program lines to initialize the form or each coding node, the program lines are considered as the body of a form routine. This means that you can declare local data that is known only within the entered coding and cannot be accessed from outside.
Within the program lines, you can access data from the form interface and globally defined data. However, the data must be specified explicitly as input or output parameters of the coding. This is necessary to allow a data flow analysis (which fields have defined values at a certain event). The data flow analysis is part of the overall check of a form.
You can use any data structures for the parameters. This means that you can also use nested structures and tables.
Dependencies
Example
Supplementary Documentation - TDSFOPD 0002
Use
Within a Smart Form a node and all inferior nodes are processed only if the respective output condition is true. A condition can either be a logical expression on field values or consist of events or position queries in the form processing.
You can determine a condition as logical expression using a table control. Each line of the table control consists of a field name, a comparison operator, and a comparison value. The comparison value can itself be a field name. As compariosn operators, the ABAP operators =, <>, <, >, <=, >=, CP (contains pattern) and NP (not contains pattern) are allowed.
All lines of the table control are linked with the logical AND. In addition, you can use a pushbutton of the table control to insert an OR link for comparisons. In the table control, it is displayed as line with gray background. The Check function checks whether all field names that appear in the comparisons are declared in the form interface or in the global data of the form.
See also: Determining OutputConditions
Dependencies
Example
Supplementary Documentation - TDSFOPD 0003
Use
Within a loop for data retrieval a table line is evaluated only if the corresponding WHERE condition is true. A WHERE condition can be any logical expression, provided that the first field for every comaprison is part of the line structure of the internal table. This also applies for field names that you specify as sort criteria for the internal table.
You can determine a WHERE condition as a logical expression using a table control. Each line of the table control consists of a field name, a comparison operator, and a comparison value which can again be a field name. As comparison operators, the ABAP operators =,<>, <, >, <=, >=, CP (contains pattern) and NP (not contains pattern) are allowed.
All lines of the table control are linked by logical AND. In addition, you can use a pushbutton in the table control to insert a logical OR link between comparisons. In the table control, it is displayed as a line with gray background. You use the Check function to check whether all field names that appear in the comparisons are declared as fields of the line structure of the relevant internal table.
Dependencies
Example
Supplementary Documentation - TDSFOPD 0004
Use
Within a loop for data retrieval, you must specify at least the table name and an output area with assignment type (INTO or ASSIGNING). If you use an internal table with header line, you must choose INTO as assignment type and enter as work area the same table name as in the input field internal table.
With ASSIGNING, the field symbol specified in the work area points to the selected entry, which means, there is no copy operation (important for large tables). Note that in this case the field symbol must be declared in the global data of the form.
Dependencies
You define a table with header line by entering it into the Tables tab in the form interface.
Example
Supplementary Documentation - TDSFOPD 0005
Use
The field name is a sort criterion. It must be part of the line structure that was declared as internal table within the loop for data retrieval.
See also: The Data Tab
Dependencies
Example
Supplementary Documentation - TDSFOPD 0006
Use
The field name must correspond to a text field that was used on the General Attributes tab in the assigned text node. This declares the field as input-enabled in the XSF interface of Smart Forms.
As an alternative, you can use a pushbutton to directly copy all fields of a text node.
The Field Length attribute determines the initial length of an input field. The length specifies the number of characters in the input field.
The Maximum Length attribute specifies the maximum number of characters the user can enter into the field. If the maximum length exceeds the field length, the HTML browser should offer scrolling. The field length must always be less than or equal to the maximum length.
The Display Only attribute ensures that the value of an input field cannot be changed in the display of an HTML browser.
See also: Extended Help in the SAP Library
Dependencies
Example
Supplementary Documentation - TDSFOPD 0007
Use
The selected operation is executed on this field name. With summing, for example, the values of this field name are added together.
The field name must not necessarily be a field of the line structure that was declared as internal table within the data retrieval loop. It can also be a field name from the form interface or the global definitions.
See also: Extended Help in the SAP Library
Dependencies
Example
Supplementary Documentation - TDSFOPD 0008
Use
The target field name stores the result of the selected operation.
See also: Extended Help in the SAP Library.
Dependencies
Example
Supplementary Documentation - TDSFOPD 0009
Use
If you set the event for the calculation to 'Before Sorting' or 'After Sorting' you must enter the relevant sort criterion here.
See also: Extended Help in the SAP Library.
Dependencies
Example
Supplementary Documentation - TDSFOPD 0010
Use
If you set the event for the reset to 'Sort Criterion' you must enter the relevant sort criterion here.
See also: Extended Help in the SAP Library.
Dependencies
Example
Supplementary Documentation - TDSFOPD 0011
Use
Using the group name, you can group several input fields together for fields (radio buttons) or list boxes. You cannot define the group name as a fixed value, rather it is a field name whose value is calculated dynamically at form runtime.
The corresponding attribute default value also determines which of the grouped input fields is used for the selection fields or list boxes. For selection fields, the default value corresponds to the attribute "checked" in the HTML element OPTION, for list boxes it corresponds to the attribute "selected" in the HTML element INPUT.
Dependencies
Example
Supplementary Documentation - TDSFOPD 0012
Use
You can assign a currency field or a quantity field to a table field in the ABAP Dictionary if a currency or a quantity is involved. Smart Forms consider the assigned currency or unit when such fields are output:
- If the value field is in the same table as the corresponding currency field or quantity field, Smart Forms automatically recognizes the reference and formats the value field according to the currency or unit in the assigned field when the field is output.
- If the value field and the currency field or quantity field are in different tables, you can define reference fields explicitly in the global definitions of a form.
A reference table has to be specified for fields that contain currency amounts (data type CURR) or quantity specifications (data type QUAN). This reference table has to contain a field (reference field) with the currency key format (data type CUKY) or the format for quantity units (data type UNIT). A program assigns the field to the reference field but not until runtime.
The field name and the reference field have to be defined in the form. This is checked when the form is activated (and in the local check). The reference field can either refer to a data type in the Data Dictionary or to local types within the form.
Dependencies
Example
If a field is filled with currency amounts, the corresponding currency is determined from the assigned reference field, that is, the value currently entered in the reference field determines the currency.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
