SAP ABAP IMG Activity SIMG_CFMENUGCU0GCF2 (Maintain Field Movements)
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
IMG Activity
ID SIMG_CFMENUGCU0GCF2 Maintain Field Movements  
Transaction Code S_ALR_87006431   IMG Activity: SIMG_CFMENUGCU0GCF2 
Created on 19981222    
Customizing Attributes SIMG_CFMENUGCU0GCF2   Maintain Field Movements 
Customizing Activity SIMG_CFMENUGCU0GCF2   Maintain Field Movements 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUGCU0GCF2    

When assigning activities to your company code/ledger and global company/ledger combinations, you define a field grouping code for each combination. This field grouping code determines which dimensions from other SAP application areas are transferred to dimensions in the FI-SL system. In the "Maintain Field Movement" step you can maintain the field grouping codes for your activities.

Note

  • When you save your field movements, code will be generated. This code is stored in SAPFGIMV.
  • The receiver table depends on the ledger, the sender tables depend on the activity.

Actions

  1. Check and if necessary maintain the assignment of the receiver and sender fields.

    Using the "Proposal..." function, you can call up a list of the most frequently used field movements, and choose the field movements that you want to define from the list.

    Using the possible entries pushbutton (F4), you can select the sender and receiver fields as well as the sender table.

  2. If a direct "Sender-receiver" assignment is not possible, you can enter the name of a user exit. This exit is called up and used in the field movement. In this step, you only use standard exits or user-defined exits for variable field movements.

    Exit routines must be defined in the following programs:

    • RGIVSxxx: Standard exit defined by SAP for variable field movements in table T888M (xxx = client)
    • You will find the program names belonging to the variable field movements in the application area GIMV in table T80D (see the step"Maintain Client-Specific User Exits")

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUGCU0GCF2 0 HLA0001345 Integration Interface 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
GCF2 T - Individual transaction object GCF2 GCF2 Change Field Movement 
GCF2 T - Individual transaction object GCF3 GCF3 Display Field Movement 
GCF2 T - Individual transaction object GCF1 GCF1 Create Field Movement 
GCF2 T - Individual transaction object GCF4 GCF4 Delete Field Movement 
History
Last changed by/on SAP  19981222 
SAP Release Created in