SAP CHECK_GLT0 Function Module for









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

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



Function CHECK_GLT0 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 'CHECK_GLT0'"
  EXPORTING
   AMANDANT_RCLNT =  "
   JSOLLHABEN_DRCRK =  "
   KMAXPERIOD_RPMAX =  "
   BLEDGER_RLDNR =  "
   CSATZART_RRCTY =  "
   DVERSION_RVERS =  "
   EBUCHKREIS_BUKRS =  "
   FGESCHJAHR_RYEAR =  "
   GKONTONR_RACCT =  "
   HGESCHBEREICH_RBUSA =  "
   IWAEHRUNG_RTCUR =  "

 IMPORTING
   GLT0_EXISTS =  "
.



IMPORTING Parameters details for CHECK_GLT0

AMANDANT_RCLNT -

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

JSOLLHABEN_DRCRK -

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

KMAXPERIOD_RPMAX -

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

BLEDGER_RLDNR -

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

CSATZART_RRCTY -

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

DVERSION_RVERS -

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

EBUCHKREIS_BUKRS -

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

FGESCHJAHR_RYEAR -

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

GKONTONR_RACCT -

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

HGESCHBEREICH_RBUSA -

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

IWAEHRUNG_RTCUR -

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

EXPORTING Parameters details for CHECK_GLT0

GLT0_EXISTS -

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

Copy and paste ABAP code example for CHECK_GLT0 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_glt0_exists  TYPE STRING, "   
lv_amandant_rclnt  TYPE GLT0-RCLNT, "   
lv_jsollhaben_drcrk  TYPE GLT0-DRCRK, "   
lv_kmaxperiod_rpmax  TYPE GLT0-RPMAX, "   
lv_bledger_rldnr  TYPE GLT0-RLDNR, "   
lv_csatzart_rrcty  TYPE GLT0-RRCTY, "   
lv_dversion_rvers  TYPE GLT0-RVERS, "   
lv_ebuchkreis_bukrs  TYPE GLT0-BUKRS, "   
lv_fgeschjahr_ryear  TYPE GLT0-RYEAR, "   
lv_gkontonr_racct  TYPE GLT0-RACCT, "   
lv_hgeschbereich_rbusa  TYPE GLT0-RBUSA, "   
lv_iwaehrung_rtcur  TYPE GLT0-RTCUR. "   

  CALL FUNCTION 'CHECK_GLT0'  "
    EXPORTING
         AMANDANT_RCLNT = lv_amandant_rclnt
         JSOLLHABEN_DRCRK = lv_jsollhaben_drcrk
         KMAXPERIOD_RPMAX = lv_kmaxperiod_rpmax
         BLEDGER_RLDNR = lv_bledger_rldnr
         CSATZART_RRCTY = lv_csatzart_rrcty
         DVERSION_RVERS = lv_dversion_rvers
         EBUCHKREIS_BUKRS = lv_ebuchkreis_bukrs
         FGESCHJAHR_RYEAR = lv_fgeschjahr_ryear
         GKONTONR_RACCT = lv_gkontonr_racct
         HGESCHBEREICH_RBUSA = lv_hgeschbereich_rbusa
         IWAEHRUNG_RTCUR = lv_iwaehrung_rtcur
    IMPORTING
         GLT0_EXISTS = lv_glt0_exists
. " CHECK_GLT0




ABAP code using 7.40 inline data declarations to call FM CHECK_GLT0

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 RCLNT FROM GLT0 INTO @DATA(ld_amandant_rclnt).
 
"SELECT single DRCRK FROM GLT0 INTO @DATA(ld_jsollhaben_drcrk).
 
"SELECT single RPMAX FROM GLT0 INTO @DATA(ld_kmaxperiod_rpmax).
 
"SELECT single RLDNR FROM GLT0 INTO @DATA(ld_bledger_rldnr).
 
"SELECT single RRCTY FROM GLT0 INTO @DATA(ld_csatzart_rrcty).
 
"SELECT single RVERS FROM GLT0 INTO @DATA(ld_dversion_rvers).
 
"SELECT single BUKRS FROM GLT0 INTO @DATA(ld_ebuchkreis_bukrs).
 
"SELECT single RYEAR FROM GLT0 INTO @DATA(ld_fgeschjahr_ryear).
 
"SELECT single RACCT FROM GLT0 INTO @DATA(ld_gkontonr_racct).
 
"SELECT single RBUSA FROM GLT0 INTO @DATA(ld_hgeschbereich_rbusa).
 
"SELECT single RTCUR FROM GLT0 INTO @DATA(ld_iwaehrung_rtcur).
 


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!