SAP IO_C_LOIOS_GET_FOR_PHIOS Function Module for Get LOIO for a Phio
IO_C_LOIOS_GET_FOR_PHIOS is a standard io c loios get for phios SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get LOIO for a Phio 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 loios get for phios FM, simply by entering the name IO_C_LOIOS_GET_FOR_PHIOS 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_LOIOS_GET_FOR_PHIOS 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_LOIOS_GET_FOR_PHIOS'"Get LOIO for a Phio.
TABLES
PHYS_OBJECTS = "
RESULT = "
* BAD_OBJECTS = "
TABLES Parameters details for IO_C_LOIOS_GET_FOR_PHIOS
PHYS_OBJECTS -
Data type: SDOKOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
RESULT -
Data type: IWLOIOPHIOOptional: No
Call by Reference: No ( called with pass by value option)
BAD_OBJECTS -
Data type: IWERROBJCTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IO_C_LOIOS_GET_FOR_PHIOS 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_phys_objects | TYPE STANDARD TABLE OF SDOKOBJECT, " | |||
| lt_result | TYPE STANDARD TABLE OF IWLOIOPHIO, " | |||
| lt_bad_objects | TYPE STANDARD TABLE OF IWERROBJCT. " |
|   CALL FUNCTION 'IO_C_LOIOS_GET_FOR_PHIOS' "Get LOIO for a Phio |
| TABLES | ||
| PHYS_OBJECTS | = lt_phys_objects | |
| RESULT | = lt_result | |
| BAD_OBJECTS | = lt_bad_objects | |
| . " IO_C_LOIOS_GET_FOR_PHIOS | ||
ABAP code using 7.40 inline data declarations to call FM IO_C_LOIOS_GET_FOR_PHIOS
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