FG_CON_DATA_GET_CHANGED_FIELD SAP Function module - To get the modified field names in Control data.

FG_CON_DATA_GET_CHANGED_FIELD is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FG_CON_DATA_GET_CHANGED_FIELD into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FG_CONTROL_DATA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FG_CON_DATA_GET_CHANGED_FIELD - FG CON DATA GET CHANGED FIELD

CALL FUNCTION 'FG_CON_DATA_GET_CHANGED_FIELD' "To get the modified field names in Control data.
  EXPORTING
    im_objtype =                " ionr-obart    Object number
  IMPORTING
    ex_changed_fieldnames_proj =   " changed_fieldnames_tt  Table type to hold the changed field names
    ex_changed_fieldnames_wbs =   " changed_fieldnames_tt  Table type to hold the changed field names
    ex_changed_fieldnames_net =   " changed_fieldnames_tt  Table type to hold the changed field names
    ex_changed_fieldnames_act =   " changed_fieldnames_tt  Table type to hold the changed field names
    .  "  FG_CON_DATA_GET_CHANGED_FIELD

ABAP code example for Function Module FG_CON_DATA_GET_CHANGED_FIELD

The ABAP code below is a full code listing to execute function module FG_CON_DATA_GET_CHANGED_FIELD including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ex_changed_fieldnames_proj  
 
 TYPE CHANGED_FIELDNAMES_TT
,
ld_ex_changed_fieldnames_wbs  
 
 TYPE CHANGED_FIELDNAMES_TT
,
ld_ex_changed_fieldnames_net  
 
 TYPE CHANGED_FIELDNAMES_TT
,
ld_ex_changed_fieldnames_act  
 
 TYPE CHANGED_FIELDNAMES_TT
.



DATA(ld_im_objtype) = some text here
.

CALL FUNCTION 'FG_CON_DATA_GET_CHANGED_FIELD'
  EXPORTING
    im_objtype =                 ld_im_objtype
  IMPORTING
    ex_changed_fieldnames_proj =    ld_ex_changed_fieldnames_proj
    ex_changed_fieldnames_wbs =    ld_ex_changed_fieldnames_wbs
    ex_changed_fieldnames_net =    ld_ex_changed_fieldnames_net
    ex_changed_fieldnames_act =    ld_ex_changed_fieldnames_act
    .  "  FG_CON_DATA_GET_CHANGED_FIELD

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ex_changed_fieldnames_proj
 
 TYPE CHANGED_FIELDNAMES_TT ,
ld_im_objtype
 
 TYPE IONR-OBART ,
ld_ex_changed_fieldnames_wbs
 
 TYPE CHANGED_FIELDNAMES_TT ,
ld_ex_changed_fieldnames_net
 
 TYPE CHANGED_FIELDNAMES_TT ,
ld_ex_changed_fieldnames_act
 
 TYPE CHANGED_FIELDNAMES_TT .



ld_im_objtype = some text here