SAP SDOK_PHIO_READ_HIERARCHY Function Module for Read book structure









SDOK_PHIO_READ_HIERARCHY is a standard sdok phio read hierarchy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read book structure 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 sdok phio read hierarchy FM, simply by entering the name SDOK_PHIO_READ_HIERARCHY into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDCH
Program Name: SAPLSDCH
Main Program: SAPLSDCH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SDOK_PHIO_READ_HIERARCHY 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 'SDOK_PHIO_READ_HIERARCHY'"Read book structure
EXPORTING
OBJECT_ID = "Identify Physical Object
* X_ROOT_ONLY = "

TABLES
CONTENTS = "

EXCEPTIONS
NOT_EXISTING = 1 NOT_ALLOWED = 2 NOT_AUTHORIZED = 3
.



IMPORTING Parameters details for SDOK_PHIO_READ_HIERARCHY

OBJECT_ID - Identify Physical Object

Data type: SDOKOBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

X_ROOT_ONLY -

Data type: SY-DATAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SDOK_PHIO_READ_HIERARCHY

CONTENTS -

Data type: SDOKHIER
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_EXISTING - Object Does Not Exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_AUTHORIZED - No Authorization

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SDOK_PHIO_READ_HIERARCHY 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_contents  TYPE STANDARD TABLE OF SDOKHIER, "   
lv_object_id  TYPE SDOKOBJECT, "   
lv_not_existing  TYPE SDOKOBJECT, "   
lv_not_allowed  TYPE SDOKOBJECT, "   
lv_x_root_only  TYPE SY-DATAR, "   
lv_not_authorized  TYPE SY. "   

  CALL FUNCTION 'SDOK_PHIO_READ_HIERARCHY'  "Read book structure
    EXPORTING
         OBJECT_ID = lv_object_id
         X_ROOT_ONLY = lv_x_root_only
    TABLES
         CONTENTS = lt_contents
    EXCEPTIONS
        NOT_EXISTING = 1
        NOT_ALLOWED = 2
        NOT_AUTHORIZED = 3
. " SDOK_PHIO_READ_HIERARCHY




ABAP code using 7.40 inline data declarations to call FM SDOK_PHIO_READ_HIERARCHY

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 DATAR FROM SY INTO @DATA(ld_x_root_only).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!