SAP GET_UDMO_FOR_VERSIONS Function Module for

Search SAP Function Modules

GET_UDMO_FOR_VERSIONS is a standard get udmo for versions 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 get udmo for versions FM, simply by entering the name GET_UDMO_FOR_VERSIONS into the relevant SAP transaction such as SE37 or SE38.

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

Function GET_UDMO_FOR_VERSIONS 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 'GET_UDMO_FOR_VERSIONS'"
  EXPORTING
   DMONAME =  "Data model name
*  STATUS = 'A' "
*  V_LANGU = SY-LANGU "

TABLES
   VM40V =  "
   VM41S =  "

EXCEPTIONS
   NOT_FOUND = 1    NO_MOD_DD = 2 

.

IMPORTING Parameters details for GET_UDMO_FOR_VERSIONS

DMONAME - Data model name

Data type: DM40L-DMOID
Optional: No
Call by Reference: No ( called with pass by value option)

STATUS -

Data type: DM40L-AS4LOCAL
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

V_LANGU -

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GET_UDMO_FOR_VERSIONS

VM40V -

Data type: DM40V
Optional: No
Call by Reference: No ( called with pass by value option)

VM41S -

Data type: DM41S
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_FOUND - Data model does not exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_MOD_DD - No Modification Available

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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