SAP SKWF_PHIO_CONTENT_URL_GET Function Module for









SKWF_PHIO_CONTENT_URL_GET is a standard skwf phio content url get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 content url get FM, simply by entering the name SKWF_PHIO_CONTENT_URL_GET 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_CONTENT_URL_GET 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_CONTENT_URL_GET'"
  EXPORTING
   PHIO =  "SDOK: BOR key for information object
*  X_STANDARD_URL_ONLY =  "Screens, display user entry
*  X_DATA_PROVIDER_URL_ONLY =  "Screens, display user entry
*  X_WEB_APPLIC_SERVER_URL_ONLY =  "
*  URL_LIFETIME =  "
*  URL_USED_AT =  "Usage of URL: At Frontend or Backend
*  X_NO_CACHE =  "Screens, display user entry
*  X_URL_FOR_GET =  "

 IMPORTING
   DOCUMENT_URL =  "SAP ArchiveLink: Data Element for Absolute URI
   ERROR =  "KW Framework: Error Object

TABLES
*  REQUESTED_COMPONENTS =  "SDOK: Name of Document Component (as Structure)
*  URLS =  "SDOK: Component and corresponding URL
.



IMPORTING Parameters details for SKWF_PHIO_CONTENT_URL_GET

PHIO - SDOK: BOR key for information object

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

X_STANDARD_URL_ONLY - Screens, display user entry

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

X_DATA_PROVIDER_URL_ONLY - Screens, display user entry

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

X_WEB_APPLIC_SERVER_URL_ONLY -

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

URL_LIFETIME -

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

URL_USED_AT - Usage of URL: At Frontend or Backend

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

X_NO_CACHE - Screens, display user entry

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

X_URL_FOR_GET -

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

EXPORTING Parameters details for SKWF_PHIO_CONTENT_URL_GET

DOCUMENT_URL - SAP ArchiveLink: Data Element for Absolute URI

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

ERROR - KW Framework: Error Object

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

TABLES Parameters details for SKWF_PHIO_CONTENT_URL_GET

REQUESTED_COMPONENTS - SDOK: Name of Document Component (as Structure)

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

URLS - SDOK: Component and corresponding URL

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

Copy and paste ABAP code example for SKWF_PHIO_CONTENT_URL_GET 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_document_url  TYPE SAEURI, "   
lt_requested_components  TYPE STANDARD TABLE OF SDOKCOMPNM, "   
lt_urls  TYPE STANDARD TABLE OF SDOKCOMURL, "   
lv_error  TYPE SKWF_ERROR, "   
lv_x_standard_url_only  TYPE SKWF_FLAG, "   
lv_x_data_provider_url_only  TYPE SKWF_FLAG, "   
lv_x_web_applic_server_url_only  TYPE SKWF_FLAG, "   
lv_url_lifetime  TYPE SKWF_URLLT, "   
lv_url_used_at  TYPE SDOK_FBURL, "   
lv_x_no_cache  TYPE SKWF_FLAG, "   
lv_x_url_for_get  TYPE SKWF_FLAG. "   

  CALL FUNCTION 'SKWF_PHIO_CONTENT_URL_GET'  "
    EXPORTING
         PHIO = lv_phio
         X_STANDARD_URL_ONLY = lv_x_standard_url_only
         X_DATA_PROVIDER_URL_ONLY = lv_x_data_provider_url_only
         X_WEB_APPLIC_SERVER_URL_ONLY = lv_x_web_applic_server_url_only
         URL_LIFETIME = lv_url_lifetime
         URL_USED_AT = lv_url_used_at
         X_NO_CACHE = lv_x_no_cache
         X_URL_FOR_GET = lv_x_url_for_get
    IMPORTING
         DOCUMENT_URL = lv_document_url
         ERROR = lv_error
    TABLES
         REQUESTED_COMPONENTS = lt_requested_components
         URLS = lt_urls
. " SKWF_PHIO_CONTENT_URL_GET




ABAP code using 7.40 inline data declarations to call FM SKWF_PHIO_CONTENT_URL_GET

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



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!