SDOK_PHIO_RELOCATE_CONTENT SAP Function module - Convert Content of a Physical Document

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

Associated Function Group: SDCL
Released Date: 29.10.2001
Processing type: Remote-Enabled

Pattern for FM SDOK_PHIO_RELOCATE_CONTENT - SDOK PHIO RELOCATE CONTENT

CALL FUNCTION 'SDOK_PHIO_RELOCATE_CONTENT' "Convert Content of a Physical Document
  EXPORTING
    object_id =                 " sdokobject    Identify Physical Object
    destination =               " sdokstca-stor_cat  Destination Category
*   client = SY-MANDT           " sy-mandt      Client
  EXCEPTIONS
    NOT_EXISTING = 1            "               Object Does Not Exist
    NOT_AUTHORIZED = 2          "               No Authorization
    NO_CONTENT = 3              "               No Files for this Physical Object
    BAD_STORAGE = 4             "               Incorrect Storage Type
    SOURCE_EQUAL_DESTINATION = 5  "             Source and Destination Match
    .  "  SDOK_PHIO_RELOCATE_CONTENT

ABAP code example for Function Module SDOK_PHIO_RELOCATE_CONTENT

The ABAP code below is a full code listing to execute function module SDOK_PHIO_RELOCATE_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_object_id) = 'Check type of data required'.
 

SELECT single STOR_CAT 
  FROM SDOKSTCA 
  INTO @DATA(ld_destination).


DATA(ld_client) = 'Check type of data required'.
.

CALL FUNCTION 'SDOK_PHIO_RELOCATE_CONTENT'
  EXPORTING
    object_id =                  ld_object_id
    destination =                ld_destination
*   client =                     ld_client
  EXCEPTIONS
    NOT_EXISTING =               1
    NOT_AUTHORIZED =             2
    NO_CONTENT =                 3
    BAD_STORAGE =                4
    SOURCE_EQUAL_DESTINATION =    5
    .  "  SDOK_PHIO_RELOCATE_CONTENT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
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_object_id
 
 TYPE SDOKOBJECT ,
ld_destination
 
 TYPE SDOKSTCA-STOR_CAT ,
ld_client
 
 TYPE SY-MANDT .


ld_object_id = 'Check type of data required'.

SELECT single STOR_CAT 
  FROM SDOKSTCA 
  INTO ld_destination.

ld_client = 'Check type of data required'.