SAP TRANSACTION_TYPE_SELECT Function Module for NOTRANSL: Selektion der Bewegungsart
TRANSACTION_TYPE_SELECT is a standard transaction type select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Selektion der Bewegungsart 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 transaction type select FM, simply by entering the name TRANSACTION_TYPE_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVZS
Program Name: SAPLFVZS
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TRANSACTION_TYPE_SELECT 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 'TRANSACTION_TYPE_SELECT'"NOTRANSL: Selektion der Bewegungsart.
EXPORTING
I_RANTYP = "Contract Type
I_SBEWZITI = "Flow category
* I_SKOGRP = '000' "Condition Group
IMPORTING
E_SBEWART_HABEN = "Credit Flow Type
E_SBEWART_SOLL = "Debit Flow Type
E_TZB0A_HABEN = "Definition of flow types
E_TZB0A_SOLL = "Definition of flow types
EXCEPTIONS
SBEWART_1_2_NOT_FOUND = 1 SBEWZITI_NOT_FOUND = 2
IMPORTING Parameters details for TRANSACTION_TYPE_SELECT
I_RANTYP - Contract Type
Data type: TZBBB-RANTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_SBEWZITI - Flow category
Data type: TZBBB-SBEWZITIOptional: No
Call by Reference: No ( called with pass by value option)
I_SKOGRP - Condition Group
Data type: TZK04-SKOGRPDefault: '000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TRANSACTION_TYPE_SELECT
E_SBEWART_HABEN - Credit Flow Type
Data type: TZB0A-SBEWARTOptional: No
Call by Reference: No ( called with pass by value option)
E_SBEWART_SOLL - Debit Flow Type
Data type: TZB0A-SBEWARTOptional: No
Call by Reference: No ( called with pass by value option)
E_TZB0A_HABEN - Definition of flow types
Data type: TZB0AOptional: No
Call by Reference: No ( called with pass by value option)
E_TZB0A_SOLL - Definition of flow types
Data type: TZB0AOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SBEWART_1_2_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SBEWZITI_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRANSACTION_TYPE_SELECT 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_i_rantyp | TYPE TZBBB-RANTYP, " | |||
| lv_e_sbewart_haben | TYPE TZB0A-SBEWART, " | |||
| lv_sbewart_1_2_not_found | TYPE TZB0A, " | |||
| lv_i_sbewziti | TYPE TZBBB-SBEWZITI, " | |||
| lv_e_sbewart_soll | TYPE TZB0A-SBEWART, " | |||
| lv_sbewziti_not_found | TYPE TZB0A, " | |||
| lv_i_skogrp | TYPE TZK04-SKOGRP, " '000' | |||
| lv_e_tzb0a_haben | TYPE TZB0A, " | |||
| lv_e_tzb0a_soll | TYPE TZB0A. " |
|   CALL FUNCTION 'TRANSACTION_TYPE_SELECT' "NOTRANSL: Selektion der Bewegungsart |
| EXPORTING | ||
| I_RANTYP | = lv_i_rantyp | |
| I_SBEWZITI | = lv_i_sbewziti | |
| I_SKOGRP | = lv_i_skogrp | |
| IMPORTING | ||
| E_SBEWART_HABEN | = lv_e_sbewart_haben | |
| E_SBEWART_SOLL | = lv_e_sbewart_soll | |
| E_TZB0A_HABEN | = lv_e_tzb0a_haben | |
| E_TZB0A_SOLL | = lv_e_tzb0a_soll | |
| EXCEPTIONS | ||
| SBEWART_1_2_NOT_FOUND = 1 | ||
| SBEWZITI_NOT_FOUND = 2 | ||
| . " TRANSACTION_TYPE_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM TRANSACTION_TYPE_SELECT
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 RANTYP FROM TZBBB INTO @DATA(ld_i_rantyp). | ||||
| "SELECT single SBEWART FROM TZB0A INTO @DATA(ld_e_sbewart_haben). | ||||
| "SELECT single SBEWZITI FROM TZBBB INTO @DATA(ld_i_sbewziti). | ||||
| "SELECT single SBEWART FROM TZB0A INTO @DATA(ld_e_sbewart_soll). | ||||
| "SELECT single SKOGRP FROM TZK04 INTO @DATA(ld_i_skogrp). | ||||
| DATA(ld_i_skogrp) | = '000'. | |||
Search for further information about these or an SAP related objects