SAUNIT_UPDATE_META_DATA SAP Function module - INTERNAL: Modify Meta Data within the update task

SAUNIT_UPDATE_META_DATA 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 SAUNIT_UPDATE_META_DATA into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM SAUNIT_UPDATE_META_DATA - SAUNIT UPDATE META DATA

CALL FUNCTION 'SAUNIT_UPDATE_META_DATA' "INTERNAL:  Modify Meta Data within the update task
  EXPORTING
    compiler_infos =            " scr_glrefs    Table of References
    prog_name =                 " progname      Object Name in Object Directory
    p_state =                   " r3state       CHAR01 data element for SYST
*   include =                   " sobj_name     Object Name in Object Directory
*   p_request_enqueue =         " flag          Request Enqueue Lock - Skip if not Possible
  IMPORTING
    e_update_done =             " sap_bool      Data Changed on DB Level
    .  "  SAUNIT_UPDATE_META_DATA

ABAP code example for Function Module SAUNIT_UPDATE_META_DATA

The ABAP code below is a full code listing to execute function module SAUNIT_UPDATE_META_DATA 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_e_update_done  
 
 TYPE SAP_BOOL
.


DATA(ld_compiler_infos) = 'Check type of data required'.

DATA(ld_prog_name) = 'Check type of data required'.

DATA(ld_p_state) = 'Check type of data required'.

DATA(ld_include) = 'Check type of data required'.

DATA(ld_p_request_enqueue) = 'Check type of data required'.
.

CALL FUNCTION 'SAUNIT_UPDATE_META_DATA'
  EXPORTING
    compiler_infos =             ld_compiler_infos
    prog_name =                  ld_prog_name
    p_state =                    ld_p_state
*   include =                    ld_include
*   p_request_enqueue =          ld_p_request_enqueue
  IMPORTING
    e_update_done =              ld_e_update_done
    .  "  SAUNIT_UPDATE_META_DATA

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_e_update_done
 
 TYPE SAP_BOOL ,
ld_compiler_infos
 
 TYPE SCR_GLREFS ,
ld_prog_name
 
 TYPE PROGNAME ,
ld_p_state
 
 TYPE R3STATE ,
ld_include
 
 TYPE SOBJ_NAME ,
ld_p_request_enqueue
 
 TYPE FLAG .


ld_compiler_infos = 'Check type of data required'.
ld_prog_name = 'Check type of data required'.
ld_p_state = 'Check type of data required'.
ld_include = 'Check type of data required'.
ld_p_request_enqueue = 'Check type of data required'.