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 | TGUMS_DEF |
| Short Description | Ind.: Maintain field movements for the conversion |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | MtnFldMvmt |
| Medium | 15 | Maint. fld mvmt |
| Long | 30 | Maintain field movements |
| Heading | 9 | MtnFldMvt |
Documentation
Definition
With this function, you define the field movements for the conversion.
The field movements for the conversion define the rules on how the individual fields of the source table are converted to the target table.
Since the field movements are valid for both the summary table(s) and the line item table(s), you only need to create these field movements for the summary table(s) to be converted.
You must ensure that key fields whose names change during the conversion (for example, BUKRS -> RBUKRS) are entered in these field movements. In addition, all key fields that exist in the target table, but do not exist in the source table must also be entered here (for example, SBUKRS).
Key fields whose names do not change during the conversion must not be entered; they are transferred automatically (for example, RACCT). All data fields (for example, TSL01) are also transferred automatically.
Using the field movements, tables do not have to be converted on a 1:1 basis. You can also omit fields (only omit those fields that are not used in any Fi-SL application), include new fields, or modify specific fields using a user exit during the conversion. However, you should take into account that all modifications to fields are made during the conversion of the transaction data, but these changes are not taken into account in the individual application areas. For example, a summarization of accounts to account groups using a user exit would take place during the conversion of the transaction data, but an automatic conversion of the sets for the field 'account' would not take place.
For more detailed information on field movements, refer to the online help for the individual fields of table TGUMS.
History
| Last changed by/on | SAP | 19940827 |
| SAP Release Created in |
