SAP BSV_GET_TEXT_VRGNG Function Module for Determine Transaction Text
BSV_GET_TEXT_VRGNG is a standard bsv get text vrgng SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Transaction Text 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 bsv get text vrgng FM, simply by entering the name BSV_GET_TEXT_VRGNG into the relevant SAP transaction such as SE37 or SE38.
Function Group: BSVT
Program Name: SAPLBSVT
Main Program: SAPLBSVT
Appliation area:
Release date: 11-Sep-1998
Mode(Normal, Remote etc): Normal Function Module
Update:
Function BSV_GET_TEXT_VRGNG 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 'BSV_GET_TEXT_VRGNG'"Determine Transaction Text.
EXPORTING
* LANGU = SY-LANGU "Language, in which Text Should be Searched for
VRGNG = "Business Transaction
IMPORTING
TXT = "Process text
TXT_LANGU = "Language, in which Text was Provided
SHORTTXT = "
IMPORTING Parameters details for BSV_GET_TEXT_VRGNG
LANGU - Language, in which Text Should be Searched for
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
VRGNG - Business Transaction
Data type: TJ01-VRGNGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BSV_GET_TEXT_VRGNG
TXT - Process text
Data type: TJ01T-TXTOptional: No
Call by Reference: Yes
TXT_LANGU - Language, in which Text was Provided
Data type: SY-LANGUOptional: No
Call by Reference: Yes
SHORTTXT -
Data type: TJ01T-SHORTTXTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BSV_GET_TEXT_VRGNG 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_txt | TYPE TJ01T-TXT, " | |||
lv_langu | TYPE SY-LANGU, " SY-LANGU | |||
lv_vrgng | TYPE TJ01-VRGNG, " | |||
lv_txt_langu | TYPE SY-LANGU, " | |||
lv_shorttxt | TYPE TJ01T-SHORTTXT. " |
  CALL FUNCTION 'BSV_GET_TEXT_VRGNG' "Determine Transaction Text |
EXPORTING | ||
LANGU | = lv_langu | |
VRGNG | = lv_vrgng | |
IMPORTING | ||
TXT | = lv_txt | |
TXT_LANGU | = lv_txt_langu | |
SHORTTXT | = lv_shorttxt | |
. " BSV_GET_TEXT_VRGNG |
ABAP code using 7.40 inline data declarations to call FM BSV_GET_TEXT_VRGNG
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 TXT FROM TJ01T INTO @DATA(ld_txt). | ||||
"SELECT single LANGU FROM SY INTO @DATA(ld_langu). | ||||
DATA(ld_langu) | = SY-LANGU. | |||
"SELECT single VRGNG FROM TJ01 INTO @DATA(ld_vrgng). | ||||
"SELECT single LANGU FROM SY INTO @DATA(ld_txt_langu). | ||||
"SELECT single SHORTTXT FROM TJ01T INTO @DATA(ld_shorttxt). | ||||
Search for further information about these or an SAP related objects