SAP CALL_EXIT_SAPLGVTR_001 Function Module for









CALL_EXIT_SAPLGVTR_001 is a standard call exit saplgvtr 001 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 call exit saplgvtr 001 FM, simply by entering the name CALL_EXIT_SAPLGVTR_001 into the relevant SAP transaction such as SE37 or SE38.

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



Function CALL_EXIT_SAPLGVTR_001 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 'CALL_EXIT_SAPLGVTR_001'"
EXPORTING
LEDGER_DATA = "

CHANGING
ACCOUNT_INDICATOR = "
ACCOUNT_TYPE = "
CHART_OF_ACCOUNTS = "
.



IMPORTING Parameters details for CALL_EXIT_SAPLGVTR_001

LEDGER_DATA -

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

CHANGING Parameters details for CALL_EXIT_SAPLGVTR_001

ACCOUNT_INDICATOR -

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

ACCOUNT_TYPE -

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

CHART_OF_ACCOUNTS -

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

Copy and paste ABAP code example for CALL_EXIT_SAPLGVTR_001 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_ledger_data  TYPE GLU1, "   
lv_account_indicator  TYPE SKA1-XBILK, "   
lv_account_type  TYPE SKA1-GVTYP, "   
lv_chart_of_accounts  TYPE SKA1-KTOPL. "   

  CALL FUNCTION 'CALL_EXIT_SAPLGVTR_001'  "
    EXPORTING
         LEDGER_DATA = lv_ledger_data
    CHANGING
         ACCOUNT_INDICATOR = lv_account_indicator
         ACCOUNT_TYPE = lv_account_type
         CHART_OF_ACCOUNTS = lv_chart_of_accounts
. " CALL_EXIT_SAPLGVTR_001




ABAP code using 7.40 inline data declarations to call FM CALL_EXIT_SAPLGVTR_001

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 XBILK FROM SKA1 INTO @DATA(ld_account_indicator).
 
"SELECT single GVTYP FROM SKA1 INTO @DATA(ld_account_type).
 
"SELECT single KTOPL FROM SKA1 INTO @DATA(ld_chart_of_accounts).
 


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!