SAP BUKU_GET_VALTYPE Function Module for Get value type instances
BUKU_GET_VALTYPE is a standard buku get valtype SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get value type instances 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 buku get valtype FM, simply by entering the name BUKU_GET_VALTYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUKU
Program Name: SAPLBUKU
Main Program: SAPLBUKU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUKU_GET_VALTYPE 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 'BUKU_GET_VALTYPE'"Get value type instances.
EXPORTING
I_FLG_WITH_TEXTS = "If flag is set, text are rendered
* I_FM_AREA = "Financial Management Area
IMPORTING
E_T_VALTYPE = "Value types
E_T_VALTYPET = "Table of value type texts
EXCEPTIONS
WRONG_INPUT = 1
IMPORTING Parameters details for BUKU_GET_VALTYPE
I_FLG_WITH_TEXTS - If flag is set, text are rendered
Data type: XFELDOptional: No
Call by Reference: Yes
I_FM_AREA - Financial Management Area
Data type: FIKRSOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BUKU_GET_VALTYPE
E_T_VALTYPE - Value types
Data type: BUKU_T_VALTYPEOptional: No
Call by Reference: Yes
E_T_VALTYPET - Table of value type texts
Data type: BUKU_T_VALTYPETOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_INPUT - wrong input
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BUKU_GET_VALTYPE 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_e_t_valtype | TYPE BUKU_T_VALTYPE, " | |||
| lv_wrong_input | TYPE BUKU_T_VALTYPE, " | |||
| lv_i_flg_with_texts | TYPE XFELD, " | |||
| lv_i_fm_area | TYPE FIKRS, " | |||
| lv_e_t_valtypet | TYPE BUKU_T_VALTYPET. " |
|   CALL FUNCTION 'BUKU_GET_VALTYPE' "Get value type instances |
| EXPORTING | ||
| I_FLG_WITH_TEXTS | = lv_i_flg_with_texts | |
| I_FM_AREA | = lv_i_fm_area | |
| IMPORTING | ||
| E_T_VALTYPE | = lv_e_t_valtype | |
| E_T_VALTYPET | = lv_e_t_valtypet | |
| EXCEPTIONS | ||
| WRONG_INPUT = 1 | ||
| . " BUKU_GET_VALTYPE | ||
ABAP code using 7.40 inline data declarations to call FM BUKU_GET_VALTYPE
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