Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-SSF (Application Component) Smart Forms⤷
SMART (Package) SAP Smart Forms
Basic Data
| Data Element | TDSFMFLAG |
| Short Description | Smart Forms: Migration |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TDSFFLAG | |
| 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 | Indicator |
| Medium | 15 | Indicator |
| Long | 20 | Indicator |
| Heading | 4 | Ind. |
Supplementary Documentation - TDSFMFLAG 0001
Generate Interface
Use
Creates an interface for the migration or overwrites an existing interface overwritten (after confirmation).
If you do not want to migrate the interface (if it has already been migrated and was modified manually, for example), do not select this option.
Dependencies
The form can only be migrated if the corresponding interface exists.
Example
Supplementary Documentation - TDSFMFLAG 0002
Generate Context
Use
Creates the context of the form. If the context already exists, it is overwritten (after confirmation).
Dependencies
For a form object to be created, an interface must exist or be created during the migration.
The form layout can be migrated only if the context has been created.
Example
Supplementary Documentation - TDSFMFLAG 0003
Generate Layout
Use
Creates the layout of the form.
Dependencies
You can set this flag only if you have previously set the Generate Context flag. This is because the layout of a form can be generated only if the appropriate context is generated at the same time.
Set this flag if you have set the Texts flag and want to display the migrated texts in the layout.
Example
Supplementary Documentation - TDSFMFLAG 0004
Texts
Use
Migrates all text nodes (text elements, text modules, and SAPscript texts) of the Smart Form.
Text elements are converted from ITF format to XHTML. For text modules and SAPscript texts, the elements are converted at runtime, while the form is being processed.
Text elements are displayed as static texts (XFA element <draw>) in the layout.
Text modules and SAPscript texts are displayed as text fields (XFA element <field>) in the layout. These fields are linked to appropriate text nodes in the context. These nodes contain information about the text module or SAPscript text.
Dependencies
If you set this flag and also want to include the migrated texts in the layout, you must also the Generate Layout flag.
Example
Supplementary Documentation - TDSFMFLAG 0005
Append Mode
Use
Uses scripting to map the append moduses of the texts in the layout. To do this, each text is packed in a subform. This subform also contains a field (append_mode__) generated during the migration. The scripting generated for this field contains the information about the append mode of the text. It is read at runtime.
A text is appended to the preceding text in accordance with the append mode:
- A - Append directly
- N - New line
- P - New paragraph
For more information, see the Smart Forms documentation.
We recommend that you perform the migration without an append mode, since this mode is a special Smart Forms feature that is not currently supported by Adobe Designer or Adobe Document Services.
Dependencies
If you set this flag, you must also set the Layout flag.
Example
The text node %TEXT1 is migrated from Smart Forms to the text node X25_TEXT1. The migrated node and the append_mode__ field are displayed in XML Forms Architecture (XFA) as follows:
<subform name="X25_TEXT1" w="10cm">
<field name="append_mode__" presence="hidden"><bind match="none"/>
<value><text maxChars="1">P</text></value>
</field>
<draw name="X25_TEXT1" w="10cm">
<value><exData contentType="text/html">
<div xmlns="http://www.w3.org/1999/xhtml"
xmlns:xfa="http://www.xfa.org/schema/xfa-template/2.1/">
Some text goes here
</div>
</exData></value>
</draw>
</subform>
Supplementary Documentation - TDSFMFLAG 0006
Field Display (Data Binding or Placeholder)
Use
- Generate Data Binding for Context
Displays fields from static texts (text elements) as data nodes in the context. For fields from structures, each data node is assigned to a folder node that has the same name as the structure. These fields are also displayed in the layout and are linked to the appropriate context nodes (data binding).
Exceptions are SFSY fields (Smart Forms system fields such as SFSY-PAGE and SFSY_FORMPAGES) and some SY fields (such as SY-DATUM and SY-UZEIT). These fields are read in the layout directly at runtime, and are not displayed in the context.
Since the syntax for fields in Smart Forms differs from the syntax in the XFA template (layout), the field names are renamed if necessary (&MYSTRUCT-MYFIELD& becomes MYSTRUCT.MYFIELD, for example).
- Display Fields as Placeholders
Specifies that no automatic data binding takes place. The fields from the static texts are not displayed in the context. Instead, they are just displayed as placeholders in the layout ( {MYSTRUCT-MYFIELD}, for example). The field name remains unconverted and is enclosed in braces.
After the migration you must replace these placeholders with fields that are bound to the context.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0007
Addresses (Also Address Windows)
Use
Addresses are displayed as fields in the layout. These fields are linked to an address node in the context. At runtime, the addresses are read from the SAP system, and copied to Adobe Document Services as plain text. If you want formatted text, you must format it manually in the layout after the migration.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0008
Graphics (Also Graphic Windows)
Use
Displays graphics in the layout as fields. These fields are bound to a graphic node in the context. The graphic nodes in the context represent a URL to the migrated graphic (a URL to the MIME Repository). At runtime, the graphic URLs are taken from the SAP system, and are copied to Adobe Document Services (ADS).
If you do not want an automatic migration to graphic URLS, remove this flag. You can include static graphics from Smart Forms in the layout manually after the migration.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0009
Folder
Use
Displays folder nodes of a Smart Form as folder nodes in the context and as the XFA <subform> in the layout.
If this option is deactivated, the folder nodes from the Smart Form are ignored. Any subnodes of the folders are still migrated, if the appropriate flag is set. Texts below a folder node are migrated, for example, if the Texts option is set, even if the Folder option is not set.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0010
Templates
Use
Displays template nodes of a Smart Form as folder nodes in the context, and as the XFA <subform> with the underlying cells in the layout.
If this option is deactivated, the template nodes (with the whole cell distribution) from the Smart Form are ignored. Any subnodes of the template are migrated, if the appropriate flags are set. Texts of a template cell, for example, are migrated if the Texts option is set, even if the Templates option is deactivated.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0011
Tables and Loops
Use
Displays table or loop nodes of a Smart Form as nodes in the context and as the XFA <subform> in the layout. In the context, the work area of the table/loop is copied from the Smart Form.
If this option is deactivated, the table, row, cell, and loop nodes from the Smart Form are ignored. Any subnodes are migrated, if the appropriate flags are set. Texts of a loop, for example, are migrated if the Texts option is set, even if the Tables and Loops option is deactivated.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0012
Output Options
Use
Migrates the output options of every Smart Form node to the layout. The output options affect borders, shading, and page protection.
Exceptions:
Output options of Window Nodes are always migrated, regardless of this flag.
Output options of Table and Templates are handled differently in Smart Forms and are ignored here.
Dependencies
If you want to migrate the output options, you must set the Layout option.
Example
Supplementary Documentation - TDSFMFLAG 0013
Header/Footer Events
Use
Displays headers and footers of a Smart Form as leaders and trailers (XFA element subform) in the layout of the PDF-based form.
If this option is deactivated, all header and footer nodes from the Smart Form are ignored. The subnodes are migrated if the appropriate flags are set. Texts of a header/footer event are migrated, for example, if the Texts option is set, even if the option Header/Footer Events is deactivated.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0014
Conditions
Use
Migrates Smart Form conditions. These conditions can be created for all nodes except window and event nodes.
Smart Forms can use two different types of conditions:
- Layout-driven conditions, which are dependent on the current layout information (Only on First Page, for example)
- Data-driven conditions (logical expressions), which are dependent on data values (CARRIER = 'LH', for example)
These conditions are handled differently in the migration.
Background: Data-driven conditions are evaluated when the PDF-based form is processed in SAP WebAS ABAP. Layout-driven conditions are evaluated by the Adobe Document Services that run in SAP WebAS Java.
The migration maps a data-driven condition in Smart Forms to a condition in the context of the PDF-based form.
The migration maps a layout-driven condition in Smart Forms to an XFA element <subform> with the special field subform_condition__ in the layout of the PDF-based form in the migration. Use scripting to create the condition in this field. For more information, see the Online Help in Adobe Designer.
To simplify the migration, we recommend that you identify all the conditions in the form before the migration, and transfer them to separate forms.
Dependencies
Set this flag to make additional settings for layout-driven or data-driven conditions. This flag is relevant only if at least one condition type is selected.
Example
Supplementary Documentation - TDSFMFLAG 0015
Alternatives
Use
Migrates alternative nodes from Smart Forms. Alternative nodes in Smart Forms always have two subnodes: TRUE and FALSE.
If this option is deactivated, all alternative nodes from the Smart Form and the TRUE and FALSE nodes are ignored. Subnodes of the alternatives are migrated, if the appropriate flags are set. Texts below an alternative node, for example, are migrated if the Texts option is set, even if the Alternatives option is not set.
Choose the TRUE and FALSE option to migrate the TRUE and FALSE nodes, including their subnodes.
Choose the TRUE Only option to just migrate the TRUE node and its subnodes. The FALSE node and its subnodes will not be migrated. migrated.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0016
Page Breaks
Use
Includes command nodes in the layout of the PDF-based form, if the Go to New Page flag is set for these nodes.
Dependencies
Example
Supplementary Documentation - TDSFMFLAG 0017
Program Nodes
Use
Includes program nodes from the Smart Form in the context of the PDF-based form.
Since program nodes are permitted in migrated forms only, this option is deactivated by default. We recommend that you map the functions of the program nodes in other ways (scripting in the layout, for example).
Dependencies
Example
History
| Last changed by/on | SAP | 20041216 |
| SAP Release Created in | 700 |
