G_RW_PROGRAM_GET_INFO SAP Function module

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

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

Pattern for FM G_RW_PROGRAM_GET_INFO - G RW PROGRAM GET INFO

CALL FUNCTION 'G_RW_PROGRAM_GET_INFO' "
* EXPORTING
*   i_program_name =            " sy-repid
  IMPORTING
    e_program_id =              " rssg_uni_idc25
    e_program_class =           " grwj_progclass
    e_report_group =            " t803j-rgjnr
    e_program_version =         " grwj_progvers
    e_client =                  " sy-mandt
  EXCEPTIONS
    INVALID_PROGRAM_NAME = 1    "
    INVALID_PROGRAM_CLASS = 2   "
    NO_RESULT = 3               "
    .  "  G_RW_PROGRAM_GET_INFO

ABAP code example for Function Module G_RW_PROGRAM_GET_INFO

The ABAP code below is a full code listing to execute function module G_RW_PROGRAM_GET_INFO 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_program_id  
 
 TYPE RSSG_UNI_IDC25
,
ld_e_program_class  
 
 TYPE GRWJ_PROGCLASS
,
ld_e_report_group  
 
 TYPE T803J-RGJNR
,
ld_e_program_version  
 
 TYPE GRWJ_PROGVERS
,
ld_e_client  
 
 TYPE SY-MANDT
.


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

CALL FUNCTION 'G_RW_PROGRAM_GET_INFO'
* EXPORTING
*   i_program_name =             ld_i_program_name
  IMPORTING
    e_program_id =               ld_e_program_id
    e_program_class =            ld_e_program_class
    e_report_group =             ld_e_report_group
    e_program_version =          ld_e_program_version
    e_client =                   ld_e_client
  EXCEPTIONS
    INVALID_PROGRAM_NAME =       1
    INVALID_PROGRAM_CLASS =      2
    NO_RESULT =                  3
    .  "  G_RW_PROGRAM_GET_INFO

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
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_program_id
 
 TYPE RSSG_UNI_IDC25 ,
ld_i_program_name
 
 TYPE SY-REPID ,
ld_e_program_class
 
 TYPE GRWJ_PROGCLASS ,
ld_e_report_group
 
 TYPE T803J-RGJNR ,
ld_e_program_version
 
 TYPE GRWJ_PROGVERS ,
ld_e_client
 
 TYPE SY-MANDT .


ld_i_program_name = 'Check type of data required'.