Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | TOFIELD1 |
| Short Description | Target field |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FDNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | DD03L |
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 | Target Fld |
| Medium | 15 | Target Field |
| Long | 20 | Target Field |
| Heading | 10 | Target Fld |
Documentation
Definition
Enter the name of the target field to which the source field is to be moved (converted).
When performing this activity, take note of the following:
Key fields whose names change during the conversion (for example BUKRS -> RBUKRS), must absolutely be included in the field movements. All the key fields available in the target table, but not in the source table, also must be entered here as target fields (for example SBUKRS).
Key fields whose names do not change during the conversion, must not be included in the field movement; they are automatically converted (for example RACCT). All data fields (for example TSL01) are also transferred automatically.
Using field movements, tables can not only be converted 1:1, but the possibility also exists to leave fields out (summarization) or to modify certain fields using a user exit (compare with online documentation for field exits) during the conversion.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
