RS_HDSYS_MAINTAIN_GXTIMG3 SAP Function module

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

Associated Function Group: RSIMG
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM RS_HDSYS_MAINTAIN_GXTIMG3 - RS HDSYS MAINTAIN GXTIMG3

CALL FUNCTION 'RS_HDSYS_MAINTAIN_GXTIMG3' "
* EXPORTING
*   return_filename = 'X'       " flag
*   enable_editing = 'X'        " flag
  IMPORTING
    filename =                  " char128
    lock_user =                 " syuname       SAP System, User Logon Name
  EXCEPTIONS
    ERROR = 1                   "               Unspecified error
    ABORTED = 2                 "
    EXIT = 3                    "
    CANCELLED = 4               "
    LOCKED = 5                  "
    ROOTID_INVALID = 6          "
    NAME_BAD_FORMAT = 7         "
    .  "  RS_HDSYS_MAINTAIN_GXTIMG3

ABAP code example for Function Module RS_HDSYS_MAINTAIN_GXTIMG3

The ABAP code below is a full code listing to execute function module RS_HDSYS_MAINTAIN_GXTIMG3 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_filename  
 
 TYPE CHAR128
,
ld_lock_user  
 
 TYPE SYUNAME
.


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

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

CALL FUNCTION 'RS_HDSYS_MAINTAIN_GXTIMG3'
* EXPORTING
*   return_filename =            ld_return_filename
*   enable_editing =             ld_enable_editing
  IMPORTING
    filename =                   ld_filename
    lock_user =                  ld_lock_user
  EXCEPTIONS
    ERROR =                      1
    ABORTED =                    2
    EXIT =                       3
    CANCELLED =                  4
    LOCKED =                     5
    ROOTID_INVALID =             6
    NAME_BAD_FORMAT =            7
    .  "  RS_HDSYS_MAINTAIN_GXTIMG3

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 7. "Exception
  "Add code for exception here
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_filename
 
 TYPE CHAR128 ,
ld_return_filename
 
 TYPE FLAG ,
ld_lock_user
 
 TYPE SYUNAME ,
ld_enable_editing
 
 TYPE FLAG .


ld_return_filename = 'Check type of data required'.
ld_enable_editing = 'Check type of data required'.