SAP FVII_BSID_ZUS_TEXTS_GET Function Module for
FVII_BSID_ZUS_TEXTS_GET is a standard fvii bsid zus texts get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fvii bsid zus texts get FM, simply by entering the name FVII_BSID_ZUS_TEXTS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVII
Program Name: SAPLFVII
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FVII_BSID_ZUS_TEXTS_GET 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 'FVII_BSID_ZUS_TEXTS_GET'".
EXPORTING
KALSM = "
* LANGU = SY-LANGU "
TABLES
TAB_BSID_ZUS = "
IMPORTING Parameters details for FVII_BSID_ZUS_TEXTS_GET
KALSM -
Data type: T005-KALSMOptional: No
Call by Reference: No ( called with pass by value option)
LANGU -
Data type: T002-SPRASDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FVII_BSID_ZUS_TEXTS_GET
TAB_BSID_ZUS -
Data type: BSID_ZUSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVII_BSID_ZUS_TEXTS_GET 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_kalsm | TYPE T005-KALSM, " | |||
lt_tab_bsid_zus | TYPE STANDARD TABLE OF BSID_ZUS, " | |||
lv_langu | TYPE T002-SPRAS. " SY-LANGU |
  CALL FUNCTION 'FVII_BSID_ZUS_TEXTS_GET' " |
EXPORTING | ||
KALSM | = lv_kalsm | |
LANGU | = lv_langu | |
TABLES | ||
TAB_BSID_ZUS | = lt_tab_bsid_zus | |
. " FVII_BSID_ZUS_TEXTS_GET |
ABAP code using 7.40 inline data declarations to call FM FVII_BSID_ZUS_TEXTS_GET
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 KALSM FROM T005 INTO @DATA(ld_kalsm). | ||||
"SELECT single SPRAS FROM T002 INTO @DATA(ld_langu). | ||||
DATA(ld_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects