SAP ABAP IMG Activity SIMG_CFMENUGCU0GCI4 (Maintain Fixed 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_CFMENUGCU0GCI4 Maintain Fixed Field Movements  
Transaction Code S_ALR_87006434   IMG Activity: SIMG_CFMENUGCU0GCI4 
Created on 19981222    
Customizing Attributes SIMG_CFMENUGCU0GCI4   Maintain fixed field movements 
Customizing Activity SIMG_CFMENUGCU0GCI4   Maintain Fixed Field Movements 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUGCU0GCI4    

In this step, you can define which fields of a sender table are transferred to the fields of a FI-SL receiver table. The field assignments defined in table T800M are fixed and thus differ from the field movements you can define in the "Maintain Field Movements" step under "Master Data" in this implementation guide.

Note

  • Table T800M is updated automatically if you install a FI-SL table; you should only maintain the table manually if absolutely necessary. You should under no circumstances delete entries from this table.

    In exceptional cases, follow the directions under "Actions".

  • Coding is generated from the entries in T800M. This coding is stored in RGIMF000.

Actions

  1. Specify the name of the receiver table. The receiver table is a FI-SL table.
  2. Specify the name of the sender table.
  3. Specify the name of the receiver field. You can enter several receiver fields for each receiver table.
  4. If you want to summarize two sender fields into one receiver field, create two entries for the receiver field and the receiver table, and enter a sequential number to differentiate between the entries.
  5. Specify the name of the sender field. You can enter several sender fields for each sender table.
  6. If you want to substitute specific values when transferring data from the sender field to the receiver field, enter a substitution activity for rollups.
  7. 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 during the field movement.

    The exit routines must be defined in the following programs:

    RGIFS000: Standard exits defined by SAP for fixed field movements in table T800M

    You can find the program names for the user-defined exits belonging to fixed field movements in the application area GIMF in table T80I (see the step "Maintain Cross-Cient User Exits").

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 3   Nonrequired 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_CFMENUGCU0GCI4 0 HLA0001336 Table Definition and Installation 
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
V_T800M V - View GCI4 9999999999 Change Fixed Field Movements 
History
Last changed by/on SAP  19981222 
SAP Release Created in