SAP TRANSACTIONS_TEXT Function Module for NOTRANSL: Ermittlung des Bewegungsartentextes (TZB0T)

Search SAP Function Modules

TRANSACTIONS_TEXT is a standard transactions text 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: Ermittlung des Bewegungsartentextes (TZB0T) 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 transactions text FM, simply by entering the name TRANSACTIONS_TEXT into the relevant SAP transaction such as SE37 or SE38.

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

Function TRANSACTIONS_TEXT 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 'TRANSACTIONS_TEXT'"NOTRANSL: Ermittlung des Bewegungsartentextes (TZB0T)
  EXPORTING
   LANGUAGE =  "Language
   RANTYP =  "Contract Type
   SBEWART =  "Flow type
*  SBEWZITI = ' ' "Flow category

 IMPORTING
   TEXT =  "Name of flow type

EXCEPTIONS
   NO_SBEWART = 1    NO_TEXT_FOUND = 2 

.

IMPORTING Parameters details for TRANSACTIONS_TEXT

LANGUAGE - Language

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

RANTYP - Contract Type

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

SBEWART - Flow type

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

SBEWZITI - Flow category

Data type: TZB0A-SBEWZITI
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TRANSACTIONS_TEXT

TEXT - Name of flow type

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

EXCEPTIONS details

NO_SBEWART - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NO_TEXT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

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

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