SAP TB_AT13_CHECK Function Module for Check Flow Type w/regard to Assignment to Trans. Type and Flow Category

Search SAP Function Modules

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

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

Function TB_AT13_CHECK 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_CHECK'"Check Flow Type w/regard to Assignment to Trans. Type and Flow Category
  EXPORTING
   APPLICATION =  "Application
   DEALTYPE =  "Transaction Type
   FLOWTYPE =  "
*  GROUP = '0' "Direction of transaction
   PRODUCTTYPE =  "Product Type

 IMPORTING
   ENTRY_AT19 =  "Eintrag in der AT19
   ENTRY_TZB0A =  "Eintrag in der TZB0A

TABLES
   TYPES =  "Gewünschte Bewegungstypen der Klasse 1

EXCEPTIONS
   FLOWTYPE_NOT_ASSIGNED = 1    FLOWTYPE_NOT_DEFINED = 2    FLOWTYPE_WRONG_GROUP = 3    FLOWTYPE_WRONG_TYPE = 4 

.

IMPORTING Parameters details for TB_AT13_CHECK

APPLICATION - Application

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

DEALTYPE - Transaction Type

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

FLOWTYPE -

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

GROUP - Direction of transaction

Data type: AT13-RKONDGR
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PRODUCTTYPE - Product Type

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

EXPORTING Parameters details for TB_AT13_CHECK

ENTRY_AT19 - Eintrag in der AT19

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

ENTRY_TZB0A - Eintrag in der TZB0A

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

TABLES Parameters details for TB_AT13_CHECK

TYPES - Gewünschte Bewegungstypen der Klasse 1

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

EXCEPTIONS details

FLOWTYPE_NOT_ASSIGNED - BwgArt ist der Geschäftsart nicht zugeordnet

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

FLOWTYPE_NOT_DEFINED - BwgArt ist für die Anwendung nicht definiert

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

FLOWTYPE_WRONG_GROUP - BwgArt ist der falschen Seite zugeordnet

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

FLOWTYPE_WRONG_TYPE - BwgArt paßt nicht zu den vorgegebenen Typen

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

Copy and paste ABAP code example for TB_AT13_CHECK 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.

ABAP code using 7.40 inline data declarations to call FM TB_AT13_CHECK

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.

Search for further information about these or an SAP related objects