SAP Function Modules

SKWF_PHIO_STORE_CONTENT SAP Function module - Save Content of a Physical Object from an Internal Table







SKWF_PHIO_STORE_CONTENT 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 SKWF_PHIO_STORE_CONTENT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SKWF_CONTENT
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM SKWF_PHIO_STORE_CONTENT - SKWF PHIO STORE CONTENT





CALL FUNCTION 'SKWF_PHIO_STORE_CONTENT' "Save Content of a Physical Object from an Internal Table
  EXPORTING
    phio =                      " skwf_io       SDOK: BOR key for information object
*   x_raw_mode =                " skwf_flag     Screens, display user entry
*   x_text_as_stream =          " skwf_flag     Screens, display user entry
*   vscan_profile = '/SCMS/KPRO_CREATE'  " vscan_profile
  IMPORTING
    error =                     " skwf_error    KW Framework: Error Object
* TABLES
*   file_access_info =          " sdokfilaci    SDOK: Entries for document contents in internal tables
*   file_access_url =           " sdokcompru    SDOK: Component Properties mit Access URL
*   file_content_ascii =        " sdokcntasc    SDOK: Line of text document content for WWW server
*   file_content_binary =       " sdokcntbin    SDOK: Line of binary document content for WWW server
    .  "  SKWF_PHIO_STORE_CONTENT

ABAP code example for Function Module SKWF_PHIO_STORE_CONTENT





The ABAP code below is a full code listing to execute function module SKWF_PHIO_STORE_CONTENT 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:
ld_error  TYPE SKWF_ERROR ,
it_file_access_info  TYPE STANDARD TABLE OF SDOKFILACI,"TABLES PARAM
wa_file_access_info  LIKE LINE OF it_file_access_info ,
it_file_access_url  TYPE STANDARD TABLE OF SDOKCOMPRU,"TABLES PARAM
wa_file_access_url  LIKE LINE OF it_file_access_url ,
it_file_content_ascii  TYPE STANDARD TABLE OF SDOKCNTASC,"TABLES PARAM
wa_file_content_ascii  LIKE LINE OF it_file_content_ascii ,
it_file_content_binary  TYPE STANDARD TABLE OF SDOKCNTBIN,"TABLES PARAM
wa_file_content_binary  LIKE LINE OF it_file_content_binary .

DATA(ld_phio) = 'Check type of data required'.
DATA(ld_x_raw_mode) = 'Check type of data required'.
DATA(ld_x_text_as_stream) = 'Check type of data required'.
DATA(ld_vscan_profile) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_file_access_info to it_file_access_info.

"populate fields of struture and append to itab
append wa_file_access_url to it_file_access_url.

"populate fields of struture and append to itab
append wa_file_content_ascii to it_file_content_ascii.

"populate fields of struture and append to itab
append wa_file_content_binary to it_file_content_binary. . CALL FUNCTION 'SKWF_PHIO_STORE_CONTENT' EXPORTING phio = ld_phio * x_raw_mode = ld_x_raw_mode * x_text_as_stream = ld_x_text_as_stream * vscan_profile = ld_vscan_profile IMPORTING error = ld_error * TABLES * file_access_info = it_file_access_info * file_access_url = it_file_access_url * file_content_ascii = it_file_content_ascii * file_content_binary = it_file_content_binary . " SKWF_PHIO_STORE_CONTENT
IF SY-SUBRC EQ 0. "All OK 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_error  TYPE SKWF_ERROR ,
ld_phio  TYPE SKWF_IO ,
it_file_access_info  TYPE STANDARD TABLE OF SDOKFILACI ,
wa_file_access_info  LIKE LINE OF it_file_access_info,
ld_x_raw_mode  TYPE SKWF_FLAG ,
it_file_access_url  TYPE STANDARD TABLE OF SDOKCOMPRU ,
wa_file_access_url  LIKE LINE OF it_file_access_url,
ld_x_text_as_stream  TYPE SKWF_FLAG ,
it_file_content_ascii  TYPE STANDARD TABLE OF SDOKCNTASC ,
wa_file_content_ascii  LIKE LINE OF it_file_content_ascii,
ld_vscan_profile  TYPE VSCAN_PROFILE ,
it_file_content_binary  TYPE STANDARD TABLE OF SDOKCNTBIN ,
wa_file_content_binary  LIKE LINE OF it_file_content_binary.

ld_phio = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_file_access_info to it_file_access_info.
ld_x_raw_mode = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_file_access_url to it_file_access_url.
ld_x_text_as_stream = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_file_content_ascii to it_file_content_ascii.
ld_vscan_profile = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_file_content_binary to it_file_content_binary.

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 SKWF_PHIO_STORE_CONTENT or its description.