SAP COMPOSITE_RETRIEVE_VERSION Function Module for

Search SAP Function Modules

COMPOSITE_RETRIEVE_VERSION is a standard composite retrieve version 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 composite retrieve version FM, simply by entering the name COMPOSITE_RETRIEVE_VERSION into the relevant SAP transaction such as SE37 or SE38.

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

Function COMPOSITE_RETRIEVE_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 'COMPOSITE_RETRIEVE_VERSION'"
  EXPORTING
   IM_COMPOSITE =  "
   IM_VERSNO =  "
*  IM_SCWB_CALL = ABAP_FALSE "
*  I_GET_TEMP_VERS = ABAP_TRUE "

 IMPORTING
   EX_COMPOSITE_OBJ =  "

CHANGING
*  CR_OBJECT =  "

EXCEPTIONS
   CX_ENH_MOD_NOT_ALLOWED = 1    CX_ENH_IO_ERROR = 2    CX_ENH_PERMISSION_DENIED = 3    CX_ENH_IS_LOCKED = 4    CX_ENH_CREATE_ERROR = 5    CX_ENH_CANCELED = 6    CX_ENH_INTERNAL_ERROR = 7 

.

IMPORTING Parameters details for COMPOSITE_RETRIEVE_VERSION

IM_COMPOSITE -

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

IM_VERSNO -

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

IM_SCWB_CALL -

Data type: ENHBOOLEAN
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

I_GET_TEMP_VERS -

Data type: ENHBOOLEAN
Default: ABAP_TRUE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for COMPOSITE_RETRIEVE_VERSION

EX_COMPOSITE_OBJ -

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

CHANGING Parameters details for COMPOSITE_RETRIEVE_VERSION

CR_OBJECT -

Data type: IF_ENH_OBJECT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

CX_ENH_MOD_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

CX_ENH_IO_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CX_ENH_PERMISSION_DENIED -

Data type:
Optional: No
Call by Reference: Yes

CX_ENH_IS_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

CX_ENH_CREATE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CX_ENH_CANCELED -

Data type:
Optional: No
Call by Reference: Yes

CX_ENH_INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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