SAP SVRS_RESOLVE_E071_OBJ Function Module for Resolve an E071 entry into versionable objects
SVRS_RESOLVE_E071_OBJ is a standard svrs resolve e071 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 an E071 entry into versionable objects 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 svrs resolve e071 obj FM, simply by entering the name SVRS_RESOLVE_E071_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SVRO
Program Name: SAPLSVRO
Main Program: SAPLSVRO
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SVRS_RESOLVE_E071_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 'SVRS_RESOLVE_E071_OBJ'"Resolve an E071 entry into versionable objects.
EXPORTING
E071_OBJ = "
TABLES
OBJ_TAB = "
EXCEPTIONS
NOT_VERSIONABLE = 1
IMPORTING Parameters details for SVRS_RESOLVE_E071_OBJ
E071_OBJ -
Data type: E071Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SVRS_RESOLVE_E071_OBJ
OBJ_TAB -
Data type: VRSOOptional: No
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)
Copy and paste ABAP code example for SVRS_RESOLVE_E071_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: | ||||
lt_obj_tab | TYPE STANDARD TABLE OF VRSO, " | |||
lv_e071_obj | TYPE E071, " | |||
lv_not_versionable | TYPE E071. " |
  CALL FUNCTION 'SVRS_RESOLVE_E071_OBJ' "Resolve an E071 entry into versionable objects |
EXPORTING | ||
E071_OBJ | = lv_e071_obj | |
TABLES | ||
OBJ_TAB | = lt_obj_tab | |
EXCEPTIONS | ||
NOT_VERSIONABLE = 1 | ||
. " SVRS_RESOLVE_E071_OBJ |
ABAP code using 7.40 inline data declarations to call FM SVRS_RESOLVE_E071_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