SAP G_TRANS_LINES Function Module for









G_TRANS_LINES is a standard g trans lines 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 trans lines FM, simply by entering the name G_TRANS_LINES into the relevant SAP transaction such as SE37 or SE38.

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



Function G_TRANS_LINES 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_TRANS_LINES'"
EXPORTING
* FLAG = ' ' "
MASTERNAME = "Object name for version management
* MASTERTYPE = 'TABU' "Object type of the element
* OBJECT = 'TABU' "
* OBJFUNC = ' ' "
OBJ_NAME = "Table name
* PGMID = 'R3TR' "
* SORTFLAG = '2' "General Indicator
* VIEWNAME = ' ' "View name

TABLES
KORRTAB = "
.



IMPORTING Parameters details for G_TRANS_LINES

FLAG -

Data type: E071K-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MASTERNAME - Object name for version management

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

MASTERTYPE - Object type of the element

Data type: E071K-MASTERTYPE
Default: 'TABU'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT -

Data type: TADIR-OBJECT
Default: 'TABU'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJFUNC -

Data type: E071-OBJFUNC
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJ_NAME - Table name

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

PGMID -

Data type: TADIR-PGMID
Default: 'R3TR'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SORTFLAG - General Indicator

Data type: E071K-SORTFLAG
Default: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VIEWNAME - View name

Data type: E071K-VIEWNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for G_TRANS_LINES

KORRTAB -

Data type: RGTRATAB
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for G_TRANS_LINES 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_flag  TYPE E071K-FLAG, "   SPACE
lt_korrtab  TYPE STANDARD TABLE OF RGTRATAB, "   
lv_mastername  TYPE E071K-MASTERNAME, "   
lv_mastertype  TYPE E071K-MASTERTYPE, "   'TABU'
lv_object  TYPE TADIR-OBJECT, "   'TABU'
lv_objfunc  TYPE E071-OBJFUNC, "   SPACE
lv_obj_name  TYPE E071, "   
lv_pgmid  TYPE TADIR-PGMID, "   'R3TR'
lv_sortflag  TYPE E071K-SORTFLAG, "   '2'
lv_viewname  TYPE E071K-VIEWNAME. "   SPACE

  CALL FUNCTION 'G_TRANS_LINES'  "
    EXPORTING
         FLAG = lv_flag
         MASTERNAME = lv_mastername
         MASTERTYPE = lv_mastertype
         OBJECT = lv_object
         OBJFUNC = lv_objfunc
         OBJ_NAME = lv_obj_name
         PGMID = lv_pgmid
         SORTFLAG = lv_sortflag
         VIEWNAME = lv_viewname
    TABLES
         KORRTAB = lt_korrtab
. " G_TRANS_LINES




ABAP code using 7.40 inline data declarations to call FM G_TRANS_LINES

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 FLAG FROM E071K INTO @DATA(ld_flag).
DATA(ld_flag) = ' '.
 
 
"SELECT single MASTERNAME FROM E071K INTO @DATA(ld_mastername).
 
"SELECT single MASTERTYPE FROM E071K INTO @DATA(ld_mastertype).
DATA(ld_mastertype) = 'TABU'.
 
"SELECT single OBJECT FROM TADIR INTO @DATA(ld_object).
DATA(ld_object) = 'TABU'.
 
"SELECT single OBJFUNC FROM E071 INTO @DATA(ld_objfunc).
DATA(ld_objfunc) = ' '.
 
 
"SELECT single PGMID FROM TADIR INTO @DATA(ld_pgmid).
DATA(ld_pgmid) = 'R3TR'.
 
"SELECT single SORTFLAG FROM E071K INTO @DATA(ld_sortflag).
DATA(ld_sortflag) = '2'.
 
"SELECT single VIEWNAME FROM E071K INTO @DATA(ld_viewname).
DATA(ld_viewname) = ' '.
 


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!