SAP SDOK_PHIO_XML_SAVE Function Module for

Search SAP Function Modules

SDOK_PHIO_XML_SAVE is a standard sdok phio xml save 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 sdok phio xml save FM, simply by entering the name SDOK_PHIO_XML_SAVE into the relevant SAP transaction such as SE37 or SE38.

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

Function SDOK_PHIO_XML_SAVE 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 'SDOK_PHIO_XML_SAVE'"
  EXPORTING
   PHIO_ID =  "
*  LOIO_ID =  "
   COMPONENT =  "
   CONTENT =  "
*  DTD_LOIO_ID =  "
*  XML_MODE = 'EUH' "
*  CLIENT = SY-MANDT "Client
*  VSCAN_PROFILE =  "

 IMPORTING
   PROPERTIES =  "

EXCEPTIONS
   NOT_EXISTING = 1    BAD_PROPERTIES = 2    MISSING_PROPERTIES = 3    BAD_RELATIONS = 4    NOT_AUTHORIZED = 5    EXCEPTION_IN_EXIT = 6    NO_STRUCTURE = 7    XML_ERROR = 8    BLOCKED_BY_POLICY = 9 

.

IMPORTING Parameters details for SDOK_PHIO_XML_SAVE

PHIO_ID -

Data type: SDOKOBJECT
Optional: No
Call by Reference: Yes

LOIO_ID -

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

COMPONENT -

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

CONTENT -

Data type: XSTRING
Optional: No
Call by Reference: Yes

DTD_LOIO_ID -

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

XML_MODE -

Data type: STRING
Default: 'EUH'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLIENT - Client

Data type: SY-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

VSCAN_PROFILE -

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

EXPORTING Parameters details for SDOK_PHIO_XML_SAVE

PROPERTIES -

Data type: SDOKPROPTYS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_EXISTING - Document does not exist

Data type:
Optional: No
Call by Reference: Yes

BAD_PROPERTIES -

Data type:
Optional: No
Call by Reference: Yes

MISSING_PROPERTIES -

Data type:
Optional: No
Call by Reference: Yes

BAD_RELATIONS -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED - No Authorization

Data type:
Optional: No
Call by Reference: Yes

EXCEPTION_IN_EXIT - Exception in Application Exit

Data type:
Optional: No
Call by Reference: Yes

NO_STRUCTURE -

Data type:
Optional: No
Call by Reference: Yes

XML_ERROR -

Data type:
Optional: No
Call by Reference: Yes

BLOCKED_BY_POLICY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SDOK_PHIO_XML_SAVE 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.

ABAP code using 7.40 inline data declarations to call FM SDOK_PHIO_XML_SAVE

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