SAP LOAN_GET_VORGTYP Function Module for Gets the Transaction Category for a Flow Type









LOAN_GET_VORGTYP is a standard loan get vorgtyp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets the Transaction Category for a Flow Type processing and below is the pattern details for this FM, 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 loan get vorgtyp FM, simply by entering the name LOAN_GET_VORGTYP into the relevant SAP transaction such as SE37 or SE38.

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



Function LOAN_GET_VORGTYP 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 'LOAN_GET_VORGTYP'"Gets the Transaction Category for a Flow Type
EXPORTING
I_SBEWART = "Flow Type

IMPORTING
E_VORGTYP = "gefundener Vorgangstyp

EXCEPTIONS
SBEWART_NOT_FOUND = 1 VORGTYP_NOT_FOUND = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLTRDB_001 User-Exit segement text for transfer in FI documents

IMPORTING Parameters details for LOAN_GET_VORGTYP

I_SBEWART - Flow Type

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

EXPORTING Parameters details for LOAN_GET_VORGTYP

E_VORGTYP - gefundener Vorgangstyp

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

EXCEPTIONS details

SBEWART_NOT_FOUND - Die Bewegungsart ist nicht vorhanden

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

VORGTYP_NOT_FOUND - Der Vorgangstyp ist nicht in der Bewegungsart

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

Copy and paste ABAP code example for LOAN_GET_VORGTYP 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_e_vorgtyp  TYPE TZB0S-VORGTYP, "   
lv_i_sbewart  TYPE TZB0A-SBEWART, "   
lv_sbewart_not_found  TYPE TZB0A, "   
lv_vorgtyp_not_found  TYPE TZB0A. "   

  CALL FUNCTION 'LOAN_GET_VORGTYP'  "Gets the Transaction Category for a Flow Type
    EXPORTING
         I_SBEWART = lv_i_sbewart
    IMPORTING
         E_VORGTYP = lv_e_vorgtyp
    EXCEPTIONS
        SBEWART_NOT_FOUND = 1
        VORGTYP_NOT_FOUND = 2
. " LOAN_GET_VORGTYP




ABAP code using 7.40 inline data declarations to call FM LOAN_GET_VORGTYP

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 VORGTYP FROM TZB0S INTO @DATA(ld_e_vorgtyp).
 
"SELECT single SBEWART FROM TZB0A INTO @DATA(ld_i_sbewart).
 
 
 


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!