SAP G_TRANSPORT_PROPERTIES_GET Function Module for









G_TRANSPORT_PROPERTIES_GET is a standard g transport properties get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 transport properties get FM, simply by entering the name G_TRANSPORT_PROPERTIES_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function G_TRANSPORT_PROPERTIES_GET 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_TRANSPORT_PROPERTIES_GET'"
EXPORTING
* LIBRARY = "
* DATA_SET_ENTRY = "
* RW_TABLE = "
* REPORT = "
* MODEL = "
* STANDARD_LAYOUT = "
* REPORT_GROUP = "
* REPORT_TEXT = "
* TEXT_TYPE = "
* SET = "
* VARIABLE = "

IMPORTING
DEVELOPMENT_CLASS = "
MASTER_LANGUAGE = "
.



IMPORTING Parameters details for G_TRANSPORT_PROPERTIES_GET

LIBRARY -

Data type: RGRWL-LIB
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATA_SET_ENTRY -

Data type: RGRWZ-DSENTRY
Optional: Yes
Call by Reference: No ( called with pass by value option)

RW_TABLE -

Data type: T804A-TAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

REPORT -

Data type: RGRWD-RNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODEL -

Data type: TKES1-FORM
Optional: Yes
Call by Reference: No ( called with pass by value option)

STANDARD_LAYOUT -

Data type: RGRWF-SNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

REPORT_GROUP -

Data type: RGRWJ-JOB
Optional: Yes
Call by Reference: No ( called with pass by value option)

REPORT_TEXT -

Data type: RTXTH-TEXT_NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

TEXT_TYPE -

Data type: RTXTH-TEXT_TYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SET -

Data type: RGSBS-SETNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

VARIABLE -

Data type: RGSGM-GLOBAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for G_TRANSPORT_PROPERTIES_GET

DEVELOPMENT_CLASS -

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

MASTER_LANGUAGE -

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

Copy and paste ABAP code example for G_TRANSPORT_PROPERTIES_GET 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.

DATA:
lv_library  TYPE RGRWL-LIB, "   
lv_development_class  TYPE TDEVC-DEVCLASS, "   
lv_data_set_entry  TYPE RGRWZ-DSENTRY, "   
lv_rw_table  TYPE T804A-TAB, "   
lv_report  TYPE RGRWD-RNAME, "   
lv_master_language  TYPE T002-SPRAS, "   
lv_model  TYPE TKES1-FORM, "   
lv_standard_layout  TYPE RGRWF-SNAME, "   
lv_report_group  TYPE RGRWJ-JOB, "   
lv_report_text  TYPE RTXTH-TEXT_NAME, "   
lv_text_type  TYPE RTXTH-TEXT_TYPE, "   
lv_set  TYPE RGSBS-SETNR, "   
lv_variable  TYPE RGSGM-GLOBAL. "   

  CALL FUNCTION 'G_TRANSPORT_PROPERTIES_GET'  "
    EXPORTING
         LIBRARY = lv_library
         DATA_SET_ENTRY = lv_data_set_entry
         RW_TABLE = lv_rw_table
         REPORT = lv_report
         MODEL = lv_model
         STANDARD_LAYOUT = lv_standard_layout
         REPORT_GROUP = lv_report_group
         REPORT_TEXT = lv_report_text
         TEXT_TYPE = lv_text_type
         SET = lv_set
         VARIABLE = lv_variable
    IMPORTING
         DEVELOPMENT_CLASS = lv_development_class
         MASTER_LANGUAGE = lv_master_language
. " G_TRANSPORT_PROPERTIES_GET




ABAP code using 7.40 inline data declarations to call FM G_TRANSPORT_PROPERTIES_GET

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.

"SELECT single LIB FROM RGRWL INTO @DATA(ld_library).
 
"SELECT single DEVCLASS FROM TDEVC INTO @DATA(ld_development_class).
 
"SELECT single DSENTRY FROM RGRWZ INTO @DATA(ld_data_set_entry).
 
"SELECT single TAB FROM T804A INTO @DATA(ld_rw_table).
 
"SELECT single RNAME FROM RGRWD INTO @DATA(ld_report).
 
"SELECT single SPRAS FROM T002 INTO @DATA(ld_master_language).
 
"SELECT single FORM FROM TKES1 INTO @DATA(ld_model).
 
"SELECT single SNAME FROM RGRWF INTO @DATA(ld_standard_layout).
 
"SELECT single JOB FROM RGRWJ INTO @DATA(ld_report_group).
 
"SELECT single TEXT_NAME FROM RTXTH INTO @DATA(ld_report_text).
 
"SELECT single TEXT_TYPE FROM RTXTH INTO @DATA(ld_text_type).
 
"SELECT single SETNR FROM RGSBS INTO @DATA(ld_set).
 
"SELECT single GLOBAL FROM RGSGM INTO @DATA(ld_variable).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!