Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-SL-IS (Application Component) Information System⤷
GRWT (Package) Report Painter / Report Writer
Basic Data
| Data Element | TEXT_TABLE |
| Short Description | Transfer structure for master data interface |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AS4TAB | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | DD02L |
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 | TransfStr. |
| Medium | 15 | Transfer struc. |
| Long | 20 | Transfer structure |
| Heading | 10 | TransfStr. |
Documentation
Definition
The transfer structure enables you to transfer field values from database records to the master data interface. Via this interface, master data texts are supplied for Report Writer reports, and intervals of master data are broken down into single values.
If the logical 'super table' defined in table T804E consists of several physical database tables, the transfer structure should contain all relevant fields for all tables.
Normally, a structure is created in the ABAP/4 Dictionary with the same name as the super table. This structure then contains all fields of the tables that are defined in T804E for the super table. Examples include the super table CCSS (CO application) and the super table GLT1 (FI-GLX application).
If the super table is the same as the physical database table, this table can also be used as the transfer structure. Example: GLT0 (FI-GLX application).
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in |
