SAP TB_AT13_GET_VALUES Function Module for Check Flow Type w/regard to Assignment to Trans. Type and Flow Category
TB_AT13_GET_VALUES is a standard tb at13 get values SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Flow Type w/regard to Assignment to Trans. Type and Flow Category 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 tb at13 get values FM, simply by entering the name TB_AT13_GET_VALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_REUSE
Program Name: SAPLFTR_REUSE
Main Program: SAPLFTR_REUSE
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TB_AT13_GET_VALUES 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 'TB_AT13_GET_VALUES'"Check Flow Type w/regard to Assignment to Trans. Type and Flow Category.
EXPORTING
PI_APPLICATION = "Application
PI_TRANSACTIONTYPE = "Transaction Type
PI_PRODUCTTYPE = "Product Type
PI_FLOWCLASSIFICATION = "Klassifikation der Bewegungen
TABLES
PI_TAB_FLOWCAT_ID = "Id der Bewegungstypen
PE_TAB_FLOWTYPE = "Einträge in der AT19 (Bewegungsarten)
* PI_TAB_GROUP = "
EXCEPTIONS
NO_FLOWTYPE_FOUND = 1
IMPORTING Parameters details for TB_AT13_GET_VALUES
PI_APPLICATION - Application
Data type: AT13-RANTYPOptional: No
Call by Reference: No ( called with pass by value option)
PI_TRANSACTIONTYPE - Transaction Type
Data type: AT13-SFHAARTOptional: No
Call by Reference: No ( called with pass by value option)
PI_PRODUCTTYPE - Product Type
Data type: AT13-SGSARTOptional: No
Call by Reference: No ( called with pass by value option)
PI_FLOWCLASSIFICATION - Klassifikation der Bewegungen
Data type: AT19-SBKKLASOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TB_AT13_GET_VALUES
PI_TAB_FLOWCAT_ID - Id der Bewegungstypen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PE_TAB_FLOWTYPE - Einträge in der AT19 (Bewegungsarten)
Data type: AT19Optional: No
Call by Reference: No ( called with pass by value option)
PI_TAB_GROUP -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_FLOWTYPE_FOUND - keine Bewegungsarten selektiert
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TB_AT13_GET_VALUES 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_pi_application | TYPE AT13-RANTYP, " | |||
| lv_no_flowtype_found | TYPE AT13, " | |||
| lt_pi_tab_flowcat_id | TYPE STANDARD TABLE OF AT13, " | |||
| lt_pe_tab_flowtype | TYPE STANDARD TABLE OF AT19, " | |||
| lv_pi_transactiontype | TYPE AT13-SFHAART, " | |||
| lt_pi_tab_group | TYPE STANDARD TABLE OF AT13, " | |||
| lv_pi_producttype | TYPE AT13-SGSART, " | |||
| lv_pi_flowclassification | TYPE AT19-SBKKLAS. " |
|   CALL FUNCTION 'TB_AT13_GET_VALUES' "Check Flow Type w/regard to Assignment to Trans. Type and Flow Category |
| EXPORTING | ||
| PI_APPLICATION | = lv_pi_application | |
| PI_TRANSACTIONTYPE | = lv_pi_transactiontype | |
| PI_PRODUCTTYPE | = lv_pi_producttype | |
| PI_FLOWCLASSIFICATION | = lv_pi_flowclassification | |
| TABLES | ||
| PI_TAB_FLOWCAT_ID | = lt_pi_tab_flowcat_id | |
| PE_TAB_FLOWTYPE | = lt_pe_tab_flowtype | |
| PI_TAB_GROUP | = lt_pi_tab_group | |
| EXCEPTIONS | ||
| NO_FLOWTYPE_FOUND = 1 | ||
| . " TB_AT13_GET_VALUES | ||
ABAP code using 7.40 inline data declarations to call FM TB_AT13_GET_VALUES
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 AT13 INTO @DATA(ld_pi_application). | ||||
| "SELECT single SFHAART FROM AT13 INTO @DATA(ld_pi_transactiontype). | ||||
| "SELECT single SGSART FROM AT13 INTO @DATA(ld_pi_producttype). | ||||
| "SELECT single SBKKLAS FROM AT19 INTO @DATA(ld_pi_flowclassification). | ||||
Search for further information about these or an SAP related objects