SAP SDOK_PHIO_CREATE_NEW_VERSION Function Module for Create a New Version of a Physical Document

Search SAP Function Modules

SDOK_PHIO_CREATE_NEW_VERSION is a standard sdok phio create new version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create a New Version of a Physical Document 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 sdok phio create new version FM, simply by entering the name SDOK_PHIO_CREATE_NEW_VERSION into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDCL
Program Name: SAPLSDCL
Main Program: SAPLSDCL
Appliation area: S
Release date: 29-Oct-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SDOK_PHIO_CREATE_NEW_VERSION 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_CREATE_NEW_VERSION'"Create a New Version of a Physical Document
  EXPORTING
   OLD_OBJECT_ID =  "BOR Key of Old Object
*  OBJECT_UNIQUE_ID =  "
*  X_ENQUEUE =  "Flag for Locking New Document
*  CLIENT = SY-MANDT "Client
*  X_SUPPRESS_PARTNER_CHECK =  "(Only for Internal Use)
*  NEW_STOR_CAT_REQ =  "Requested Category for New Version

 IMPORTING
   NEW_OBJECT_ID =  "BOR Key of New Object
   NEW_STOR_CAT =  "Category for New PHIO

EXCEPTIONS
   NOT_EXISTING = 1    BAD_CLASS = 2    INITIAL = 3    CHECKED_OUT = 4    NOT_AUTHORIZED = 5    DUPLICATE_OBJECT_ID = 6    ENQUEUE_FAILURE = 7    EXCEPTION_IN_EXIT = 8    MIMETYPE_NOT_ALLOWED = 9 

.

IMPORTING Parameters details for SDOK_PHIO_CREATE_NEW_VERSION

OLD_OBJECT_ID - BOR Key of Old Object

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

OBJECT_UNIQUE_ID -

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

X_ENQUEUE - Flag for Locking New Document

Data type: SY-DATAR
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)

X_SUPPRESS_PARTNER_CHECK - (Only for Internal Use)

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

NEW_STOR_CAT_REQ - Requested Category for New Version

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

EXPORTING Parameters details for SDOK_PHIO_CREATE_NEW_VERSION

NEW_OBJECT_ID - BOR Key of New Object

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

NEW_STOR_CAT - Category for New PHIO

Data type: SDOKPHIO-STOR_CAT
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_EXISTING - Object does not exist

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

BAD_CLASS - Object class unknown

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

INITIAL - Object is Initial

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

CHECKED_OUT - Object is Reserved or Has Been Checked Out

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

NOT_AUTHORIZED - No Authorization

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

DUPLICATE_OBJECT_ID - Object already exists

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

ENQUEUE_FAILURE - Locking error

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

EXCEPTION_IN_EXIT - Exception in application exit

Data type:
Optional: No
Call by Reference: Yes

MIMETYPE_NOT_ALLOWED - MIME Type Not Permitted

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SDOK_PHIO_CREATE_NEW_VERSION 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_CREATE_NEW_VERSION

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