SAP FMCU_GET_VERSION Function Module for Get budgeting versions in FM

Search SAP Function Modules

FMCU_GET_VERSION is a standard fmcu get version 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 budgeting versions in FM 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 fmcu get version FM, simply by entering the name FMCU_GET_VERSION into the relevant SAP transaction such as SE37 or SE38.

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

Function FMCU_GET_VERSION 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 'FMCU_GET_VERSION'"Get budgeting versions in FM
  EXPORTING
   I_FM_AREA =  "Financial management area

 IMPORTING
   E_T_VERSION =  "Transfer type for version

.

IMPORTING Parameters details for FMCU_GET_VERSION

I_FM_AREA - Financial management area

Data type: FIKRS
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FMCU_GET_VERSION

E_T_VERSION - Transfer type for version

Data type: BUKU_T_VERSION
Optional: No
Call by Reference: Yes

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

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