SAP G_MIGRATION_MOVEMENTS_READ Function Module for Read the field movements for the conversion of tables

Search SAP Function Modules

G_MIGRATION_MOVEMENTS_READ is a standard g migration movements read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read the field movements for the conversion of tables processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for g migration movements read FM, simply by entering the name G_MIGRATION_MOVEMENTS_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: GMIG
Program Name: SAPLGMIG
Main Program:
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_MIGRATION_MOVEMENTS_READ pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'G_MIGRATION_MOVEMENTS_READ'"Read the field movements for the conversion of tables
  EXPORTING
*  ADD_FLAG = ' ' "Flag for reading RW tables(T804A,T804E)
   FROMTABLE =  "Sender table
   TOTABLE =  "Receiving table

TABLES
   CORR_FIELDS =  "Corresponding fields
   LOST_FIELDS =  "Lost fields
   NEW_FIELDS =  "New fields

EXCEPTIONS
   ILLEGAL_FROMTABLE = 1    ILLEGAL_TOTABLE = 2 

.

IMPORTING Parameters details for G_MIGRATION_MOVEMENTS_READ

ADD_FLAG - Flag for reading RW tables(T804A,T804E)

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FROMTABLE - Sender table

Data type: TGUMS-FROMTABLE
Optional: No
Call by Reference: No ( called with pass by value option)

TOTABLE - Receiving table

Data type: TGUMS-TOTABLE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for G_MIGRATION_MOVEMENTS_READ

CORR_FIELDS - Corresponding fields

Data type: RGUMSC
Optional: No
Call by Reference: No ( called with pass by value option)

LOST_FIELDS - Lost fields

Data type: RGUMSL
Optional: No
Call by Reference: No ( called with pass by value option)

NEW_FIELDS - New fields

Data type: RGUMSN
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ILLEGAL_FROMTABLE - Invalid sender table

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ILLEGAL_TOTABLE - Invalid receiving table

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for G_MIGRATION_MOVEMENTS_READ Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM G_MIGRATION_MOVEMENTS_READ

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects