SAP /SDF/CMO_RESOLVE_OBJ Function Module for Resolve object in versionable subobjects
/SDF/CMO_RESOLVE_OBJ is a standard /sdf/cmo resolve obj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Resolve object in versionable subobjects 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 /sdf/cmo resolve obj FM, simply by entering the name /SDF/CMO_RESOLVE_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SDF/CMO_COMP_VERS
Program Name: /SDF/SAPLCMO_COMP_VERS
Main Program: /SDF/SAPLCMO_COMP_VERS
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SDF/CMO_RESOLVE_OBJ 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 '/SDF/CMO_RESOLVE_OBJ'"Resolve object in versionable subobjects.
EXPORTING
* IS_E071 = "
TABLES
* TT_VRSO = "
EXCEPTIONS
NOT_VERSIONABLE = 1 COMMUNICATION_ERROR = 2
IMPORTING Parameters details for /SDF/CMO_RESOLVE_OBJ
IS_E071 -
Data type: /SDF/CMO_E071Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for /SDF/CMO_RESOLVE_OBJ
TT_VRSO -
Data type: VRSOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_VERSIONABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /SDF/CMO_RESOLVE_OBJ 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_is_e071 | TYPE /SDF/CMO_E071, " | |||
| lt_tt_vrso | TYPE STANDARD TABLE OF VRSO, " | |||
| lv_not_versionable | TYPE VRSO, " | |||
| lv_communication_error | TYPE VRSO. " |
|   CALL FUNCTION '/SDF/CMO_RESOLVE_OBJ' "Resolve object in versionable subobjects |
| EXPORTING | ||
| IS_E071 | = lv_is_e071 | |
| TABLES | ||
| TT_VRSO | = lt_tt_vrso | |
| EXCEPTIONS | ||
| NOT_VERSIONABLE = 1 | ||
| COMMUNICATION_ERROR = 2 | ||
| . " /SDF/CMO_RESOLVE_OBJ | ||
ABAP code using 7.40 inline data declarations to call FM /SDF/CMO_RESOLVE_OBJ
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