SAP IO_C_CREATE_PHIO Function Module for Create physical info object









IO_C_CREATE_PHIO is a standard io c create phio SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create physical info object 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 io c create phio FM, simply by entering the name IO_C_CREATE_PHIO into the relevant SAP transaction such as SE37 or SE38.

Function Group: SI61
Program Name: SAPLSI61
Main Program: SAPLSI61
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function IO_C_CREATE_PHIO 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 'IO_C_CREATE_PHIO'"Create physical info object
EXPORTING
INFO_CLASS = "
* GUID = "

IMPORTING
OBJECT_ID = "
ERROR_MSG = "

TABLES
* PROPERTIES = "
* RELATIONS = "
.



IMPORTING Parameters details for IO_C_CREATE_PHIO

INFO_CLASS -

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

GUID -

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

EXPORTING Parameters details for IO_C_CREATE_PHIO

OBJECT_ID -

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

ERROR_MSG -

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

TABLES Parameters details for IO_C_CREATE_PHIO

PROPERTIES -

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

RELATIONS -

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

Copy and paste ABAP code example for IO_C_CREATE_PHIO 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_object_id  TYPE SDOKOBJECT, "   
lv_info_class  TYPE SDOKPHCL-PH_CLASS, "   
lt_properties  TYPE STANDARD TABLE OF SDOKPROPTY, "   
lv_guid  TYPE SDOKPHIO-PHIO_ID, "   
lv_error_msg  TYPE IWERRORMSG, "   
lt_relations  TYPE STANDARD TABLE OF SDOKRELIST. "   

  CALL FUNCTION 'IO_C_CREATE_PHIO'  "Create physical info object
    EXPORTING
         INFO_CLASS = lv_info_class
         GUID = lv_guid
    IMPORTING
         OBJECT_ID = lv_object_id
         ERROR_MSG = lv_error_msg
    TABLES
         PROPERTIES = lt_properties
         RELATIONS = lt_relations
. " IO_C_CREATE_PHIO




ABAP code using 7.40 inline data declarations to call FM IO_C_CREATE_PHIO

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 PH_CLASS FROM SDOKPHCL INTO @DATA(ld_info_class).
 
 
"SELECT single PHIO_ID FROM SDOKPHIO INTO @DATA(ld_guid).
 
 
 


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!