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 | FELDMODIF |
| Short Description | Field movement |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FELDMODIF | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T888 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | GFM | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | FldMovemnt |
| Medium | 15 | Field movement |
| Long | 20 | Field movement |
| Heading | 4 | FMvt |
Documentation
Definition
The variable field movements that are transferred in addition to the fixed fields at direct posting or rollup execution are stored under a field movement (compare with Maintain fixed field movements).
You define the direct posting field movements in the FI-SL implementation guide under Maintain field movement. You can find the rollup field movements under Maintain rollup field movement.
Supplementary Documentation - FELDMODIF 1000
Use
Procedure
Examples
Dependencies
The following is possible in rollup field movements:
- Summarization by omitting fields
When you execute the rollup, only those fields that have been entered in the field movement (in addition to those defined in table T800M) are transferred to the rollup ledger. The summarization of data occurs by omitting dimensions. - Summarization using substitution
During the field movement, you can also substitute fields (for example, products are assigned to a product group) using substitution activities; this also results in a summarization of data. You must enter these substitution activities in the field movement. - Rolling up between local and global tables
If you want to roll up between local and global tables, the field movement must contain a fixed company code or a fixed global company into which data is to be summarized. - User exits
Using user exits that are entered in the field movement or in substitution activities, you can influence the processing of the individual records at three different points in time when you execute the rollup: - directly after reading the summary record
- when transferring a specific field
- directly before writing the rollup record
Note
In addition to transferring fields to the receiver table when you roll up using line items, you can also transfer fields to the relevant line item table for documentation purposes. You must make sure that the receiver field exists in table 'GLU1' and in the line item table, but not in the summary table.
Supplementary Documentation - FELDMODIF 2000
Use
Test
Procedure
Examples
Dependencies
Test
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
