SAP RESOLVE_LOGICAL_OBJECT Function Module for Break down logical objects into elementary objects (new version)
RESOLVE_LOGICAL_OBJECT is a standard resolve logical object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Break down logical objects into elementary objects (new version) 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 resolve logical object FM, simply by entering the name RESOLVE_LOGICAL_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLGO
Program Name: SAPLSLGO
Main Program: SAPLSLGO
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RESOLVE_LOGICAL_OBJECT 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 'RESOLVE_LOGICAL_OBJECT'"Break down logical objects into elementary objects (new version).
EXPORTING
E071_ENTRY = "an E071 entry which contains a log
* SELECTION = ' ' "Selection switch for TLOGO-PROCFLA
* IV_NO_TADIR_OBJECT = ' ' "
* IV_LANGUAGES = ' ' "
* IV_CLIENT = '' "
TABLES
E071K_TAB = "Key of basic objects of the logica
E071_TAB = "Basic objects of logical object
EXCEPTIONS
NO_LOGICAL_OBJECT = 1 LOGICAL_OBJECT_WITH_TADIR = 2
IMPORTING Parameters details for RESOLVE_LOGICAL_OBJECT
E071_ENTRY - an E071 entry which contains a log
Data type: E071Optional: No
Call by Reference: No ( called with pass by value option)
SELECTION - Selection switch for TLOGO-PROCFLA
Data type: TRPARI-FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_TADIR_OBJECT -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LANGUAGES -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CLIENT -
Data type: TRCLIENTDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RESOLVE_LOGICAL_OBJECT
E071K_TAB - Key of basic objects of the logica
Data type: E071KOptional: No
Call by Reference: No ( called with pass by value option)
E071_TAB - Basic objects of logical object
Data type: E071Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_LOGICAL_OBJECT - the E071 entry is no logical objec
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOGICAL_OBJECT_WITH_TADIR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RESOLVE_LOGICAL_OBJECT 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_e071k_tab | TYPE STANDARD TABLE OF E071K, " | |||
| lv_e071_entry | TYPE E071, " | |||
| lv_no_logical_object | TYPE E071, " | |||
| lt_e071_tab | TYPE STANDARD TABLE OF E071, " | |||
| lv_selection | TYPE TRPARI-FLAG, " ' ' | |||
| lv_logical_object_with_tadir | TYPE TRPARI, " | |||
| lv_iv_no_tadir_object | TYPE C, " ' ' | |||
| lv_iv_languages | TYPE C, " ' ' | |||
| lv_iv_client | TYPE TRCLIENT. " '' |
|   CALL FUNCTION 'RESOLVE_LOGICAL_OBJECT' "Break down logical objects into elementary objects (new version) |
| EXPORTING | ||
| E071_ENTRY | = lv_e071_entry | |
| SELECTION | = lv_selection | |
| IV_NO_TADIR_OBJECT | = lv_iv_no_tadir_object | |
| IV_LANGUAGES | = lv_iv_languages | |
| IV_CLIENT | = lv_iv_client | |
| TABLES | ||
| E071K_TAB | = lt_e071k_tab | |
| E071_TAB | = lt_e071_tab | |
| EXCEPTIONS | ||
| NO_LOGICAL_OBJECT = 1 | ||
| LOGICAL_OBJECT_WITH_TADIR = 2 | ||
| . " RESOLVE_LOGICAL_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM RESOLVE_LOGICAL_OBJECT
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.| "SELECT single FLAG FROM TRPARI INTO @DATA(ld_selection). | ||||
| DATA(ld_selection) | = ' '. | |||
| DATA(ld_iv_no_tadir_object) | = ' '. | |||
| DATA(ld_iv_languages) | = ' '. | |||
| DATA(ld_iv_client) | = ''. | |||
Search for further information about these or an SAP related objects