SAP SDOK_INDEX_DELIVERY Function Module for

Search SAP Function Modules

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

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

Function SDOK_INDEX_DELIVERY 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_INDEX_DELIVERY'"
  EXPORTING
   LANGUAGE =  "
*  CLIENT = SY-MANDT "Client

TABLES
   PHIO_TAB =  "
   BAD_PHIOS =  "

EXCEPTIONS
   NO_PHIOS_GIVEN = 1    RFC_SYS_FAILURE = 10    RFC_COM_FAILURE = 11    PARAMETER_ERROR = 12    MORE_THAN_ONE_CATID = 13    XERROR = 14    NO_DOCUSPACE = 2    DOCUSPACE_NOT_EXISTING = 3    OBJECT_NOT_EXISTING = 4    IDXCAT_IS_FIXED = 5    CATID_UNKNOWN = 6    INDEX_DELETE_ERROR = 7    LANGU_NOT_VALID = 8    NO_RFCDEST = 9 

.

IMPORTING Parameters details for SDOK_INDEX_DELIVERY

LANGUAGE -

Data type: SY-LANGU
Optional: No
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)

TABLES Parameters details for SDOK_INDEX_DELIVERY

PHIO_TAB -

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

BAD_PHIOS -

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

EXCEPTIONS details

NO_PHIOS_GIVEN -

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

RFC_SYS_FAILURE -

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

RFC_COM_FAILURE -

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

PARAMETER_ERROR -

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

MORE_THAN_ONE_CATID -

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

XERROR -

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

NO_DOCUSPACE -

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

DOCUSPACE_NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_EXISTING - Document does not exist

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

IDXCAT_IS_FIXED -

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

CATID_UNKNOWN -

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

INDEX_DELETE_ERROR -

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

LANGU_NOT_VALID -

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

NO_RFCDEST -

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

Copy and paste ABAP code example for SDOK_INDEX_DELIVERY 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_INDEX_DELIVERY

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