SAP BUCU_CHECK_VERSION_FREEZE Function Module for Check existence of frozen budgeting version
BUCU_CHECK_VERSION_FREEZE is a standard bucu check version freeze 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 existence of frozen budgeting version 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 bucu check version freeze FM, simply by entering the name BUCU_CHECK_VERSION_FREEZE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUCU_SERVICE
Program Name: SAPLBUCU_SERVICE
Main Program: SAPLBUCU_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUCU_CHECK_VERSION_FREEZE 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 'BUCU_CHECK_VERSION_FREEZE'"Check existence of frozen budgeting version.
EXPORTING
I_VERSION = "Version
EXCEPTIONS
NO_VERSION = 1 NOT_FOUND = 2
IMPORTING Parameters details for BUCU_CHECK_VERSION_FREEZE
I_VERSION - Version
Data type: BUKU_VERSIONOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_VERSION - Version not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - No budgeting version found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BUCU_CHECK_VERSION_FREEZE 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_i_version | TYPE BUKU_VERSION, " | |||
| lv_no_version | TYPE BUKU_VERSION, " | |||
| lv_not_found | TYPE BUKU_VERSION. " |
|   CALL FUNCTION 'BUCU_CHECK_VERSION_FREEZE' "Check existence of frozen budgeting version |
| EXPORTING | ||
| I_VERSION | = lv_i_version | |
| EXCEPTIONS | ||
| NO_VERSION = 1 | ||
| NOT_FOUND = 2 | ||
| . " BUCU_CHECK_VERSION_FREEZE | ||
ABAP code using 7.40 inline data declarations to call FM BUCU_CHECK_VERSION_FREEZE
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