SAP SKWF_PHIO_LOAD_CONTENT Function Module for Load Content of a Physical Object into an Internal Table
SKWF_PHIO_LOAD_CONTENT is a standard skwf phio load content SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Load Content of a Physical Object into an Internal Table 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 skwf phio load content FM, simply by entering the name SKWF_PHIO_LOAD_CONTENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SKWF_CONTENT
Program Name: SAPLSKWF_CONTENT
Main Program: SAPLSKWF_CONTENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SKWF_PHIO_LOAD_CONTENT 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 'SKWF_PHIO_LOAD_CONTENT'"Load Content of a Physical Object into an Internal Table.
EXPORTING
PHIO = "SDOK: BOR key for information object
* X_AS_IS_MODE = "Screens, display user entry
* X_TEXT_AS_STREAM = "
* X_RAW_MODE = "
IMPORTING
ERROR = "KW Framework: Error Object
TABLES
* FILE_ACCESS_INFO = "SDOK: Entries for document contents in internal tables
* FILE_CONTENT_ASCII = "SDOK: Line of text document content for WWW server
* FILE_CONTENT_BINARY = "SDOK: Line of binary document content for WWW server
IMPORTING Parameters details for SKWF_PHIO_LOAD_CONTENT
PHIO - SDOK: BOR key for information object
Data type: SKWF_IOOptional: No
Call by Reference: No ( called with pass by value option)
X_AS_IS_MODE - Screens, display user entry
Data type: SKWF_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
X_TEXT_AS_STREAM -
Data type: SKWF_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
X_RAW_MODE -
Data type: SKWF_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SKWF_PHIO_LOAD_CONTENT
ERROR - KW Framework: Error Object
Data type: SKWF_ERROROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SKWF_PHIO_LOAD_CONTENT
FILE_ACCESS_INFO - SDOK: Entries for document contents in internal tables
Data type: SDOKFILACIOptional: Yes
Call by Reference: Yes
FILE_CONTENT_ASCII - SDOK: Line of text document content for WWW server
Data type: SDOKCNTASCOptional: Yes
Call by Reference: Yes
FILE_CONTENT_BINARY - SDOK: Line of binary document content for WWW server
Data type: SDOKCNTBINOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SKWF_PHIO_LOAD_CONTENT 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_phio | TYPE SKWF_IO, " | |||
| lv_error | TYPE SKWF_ERROR, " | |||
| lt_file_access_info | TYPE STANDARD TABLE OF SDOKFILACI, " | |||
| lv_x_as_is_mode | TYPE SKWF_FLAG, " | |||
| lt_file_content_ascii | TYPE STANDARD TABLE OF SDOKCNTASC, " | |||
| lv_x_text_as_stream | TYPE SKWF_FLAG, " | |||
| lt_file_content_binary | TYPE STANDARD TABLE OF SDOKCNTBIN, " | |||
| lv_x_raw_mode | TYPE SKWF_FLAG. " |
|   CALL FUNCTION 'SKWF_PHIO_LOAD_CONTENT' "Load Content of a Physical Object into an Internal Table |
| EXPORTING | ||
| PHIO | = lv_phio | |
| X_AS_IS_MODE | = lv_x_as_is_mode | |
| X_TEXT_AS_STREAM | = lv_x_text_as_stream | |
| X_RAW_MODE | = lv_x_raw_mode | |
| IMPORTING | ||
| ERROR | = lv_error | |
| TABLES | ||
| FILE_ACCESS_INFO | = lt_file_access_info | |
| FILE_CONTENT_ASCII | = lt_file_content_ascii | |
| FILE_CONTENT_BINARY | = lt_file_content_binary | |
| . " SKWF_PHIO_LOAD_CONTENT | ||
ABAP code using 7.40 inline data declarations to call FM SKWF_PHIO_LOAD_CONTENT
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