SAP UMV_X_CHECKED_OBJ_USAGE Function Module for
UMV_X_CHECKED_OBJ_USAGE is a standard umv x checked obj usage 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 umv x checked obj usage FM, simply by entering the name UMV_X_CHECKED_OBJ_USAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UMV_X
Program Name: SAPLUMV_X
Main Program: SAPLUMV_X
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UMV_X_CHECKED_OBJ_USAGE 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 'UMV_X_CHECKED_OBJ_USAGE'".
EXPORTING
I_OBJ_TYPE = "
I_OBJ_KEY = "
IMPORTING
E_IS_USED = "
IMPORTING Parameters details for UMV_X_CHECKED_OBJ_USAGE
I_OBJ_TYPE -
Data type: UMB_Y_OBJ_TYPEOptional: No
Call by Reference: Yes
I_OBJ_KEY -
Data type: UMB_Y_OBJ_KEYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UMV_X_CHECKED_OBJ_USAGE
E_IS_USED -
Data type: AS4FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UMV_X_CHECKED_OBJ_USAGE 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_is_used | TYPE AS4FLAG, " | |||
| lv_i_obj_type | TYPE UMB_Y_OBJ_TYPE, " | |||
| lv_i_obj_key | TYPE UMB_Y_OBJ_KEY. " |
|   CALL FUNCTION 'UMV_X_CHECKED_OBJ_USAGE' " |
| EXPORTING | ||
| I_OBJ_TYPE | = lv_i_obj_type | |
| I_OBJ_KEY | = lv_i_obj_key | |
| IMPORTING | ||
| E_IS_USED | = lv_e_is_used | |
| . " UMV_X_CHECKED_OBJ_USAGE | ||
ABAP code using 7.40 inline data declarations to call FM UMV_X_CHECKED_OBJ_USAGE
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