SAP Function Modules

comments icon Comments

RESOLVE_LOGICAL_OBJECT SAP Function module - Break down logical objects into elementary objects (new version)







RESOLVE_LOGICAL_OBJECT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RESOLVE_LOGICAL_OBJECT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SLGO
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM RESOLVE_LOGICAL_OBJECT - RESOLVE LOGICAL OBJECT 





CALL FUNCTION 'RESOLVE_LOGICAL_OBJECT' "Break down logical objects into elementary objects (new version)
  EXPORTING
    e071_entry =                " e071          an E071 entry which contains a log
*   selection = ' '             " trpari-flag   Selection switch for TLOGO-PROCFLA
*   iv_no_tadir_object = ' '    " c
*   iv_languages = ' '          " c
*   iv_client = ''              " trclient
  TABLES
    e071k_tab =                 " e071k         Key of basic objects of the logica
    e071_tab =                  " e071          Basic objects of logical object
  EXCEPTIONS
    NO_LOGICAL_OBJECT = 1       "               the E071 entry is no logical objec
    LOGICAL_OBJECT_WITH_TADIR = 2  "
    .  "  RESOLVE_LOGICAL_OBJECT

ABAP code example for Function Module RESOLVE_LOGICAL_OBJECT





The ABAP code below is a full code listing to execute function module RESOLVE_LOGICAL_OBJECT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_e071k_tab    TYPE STANDARD TABLE OF E071K,"TABLES PARAM
wa_e071k_tab  LIKE LINE OF it_e071k_tab
,
it_e071_tab    TYPE STANDARD TABLE OF E071,"TABLES PARAM
wa_e071_tab  LIKE LINE OF it_e071_tab
.




DATA(ld_e071_entry) = 'Check type of data required'.


DATA(ld_selection) = some text here

DATA(ld_iv_no_tadir_object) = 'Check type of data required'.

DATA(ld_iv_languages) = 'Check type of data required'.

DATA(ld_iv_client) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_e071k_tab to it_e071k_tab.
 

"populate fields of struture and append to itab
append wa_e071_tab to it_e071_tab.
.

CALL FUNCTION 'RESOLVE_LOGICAL_OBJECT'
  EXPORTING
    e071_entry =                 ld_e071_entry
*   selection =                  ld_selection
*   iv_no_tadir_object =         ld_iv_no_tadir_object
*   iv_languages =               ld_iv_languages
*   iv_client =                  ld_iv_client
  TABLES
    e071k_tab =                  it_e071k_tab
    e071_tab =                   it_e071_tab
  EXCEPTIONS
    NO_LOGICAL_OBJECT =          1
    LOGICAL_OBJECT_WITH_TADIR =    2
    .  "  RESOLVE_LOGICAL_OBJECT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_e071_entry  TYPE E071 ,
it_e071k_tab  TYPE STANDARD TABLE OF E071K ,
wa_e071k_tab  LIKE LINE OF it_e071k_tab,
ld_selection  TYPE TRPARI-FLAG ,
it_e071_tab  TYPE STANDARD TABLE OF E071 ,
wa_e071_tab  LIKE LINE OF it_e071_tab,
ld_iv_no_tadir_object  TYPE C ,
ld_iv_languages  TYPE C ,
ld_iv_client  TYPE TRCLIENT .




ld_e071_entry = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_e071k_tab to it_e071k_tab.

ld_selection = some text here 

"populate fields of struture and append to itab
append wa_e071_tab to it_e071_tab.
ld_iv_no_tadir_object = 'Check type of data required'.
ld_iv_languages = 'Check type of data required'.
ld_iv_client = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name RESOLVE_LOGICAL_OBJECT or its description.


   
 

RESOLVE_LOGICAL_OBJECT - Break down logical objects into elementary objects (new version)
RESOLVE_LDBA - 
RESOLVE_INTF - 
RESOLVE_FUNC - 
RESOLVE_FUGR - 
RESOLVE_DTEL -