SAP SDOK_DOC_FEATURES_GET Function Module for

Search SAP Function Modules

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

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

Function SDOK_DOC_FEATURES_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 'SDOK_DOC_FEATURES_GET'"
  EXPORTING
   DOCU' ' =  "Document Area
*  CLIENT = SY-MANDT "Client
   LAISO =  "Language According to ISO 639
*  NUMBERFE = 10 "

 IMPORTING
   RCODE =  "Error Number
   ES_ERRORCODE =  "

TABLES
*  ITAB_CATPROPTY =  "
   DOCLISTTAB =  "
   RESULTFEATTAB =  "Results List for Characteristic Determination

EXCEPTIONS
   CATID_NOT_EXISTING = 1    LANGUAGE_UNKNOWN = 2    RFC_SYS_FAILURE = 3    RFC_COM_FAILURE = 4    NO_RFC_DEST = 5    XERROR = 6 

.

IMPORTING Parameters details for SDOK_DOC_FEATURES_GET

DOCUSPACE - Document Area

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

CLIENT - Client

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

LAISO - Language According to ISO 639

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

NUMBERFE -

Data type: SRETGSTRUC-NUMBERFE
Default: 10
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SDOK_DOC_FEATURES_GET

RCODE - Error Number

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

ES_ERRORCODE -

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

TABLES Parameters details for SDOK_DOC_FEATURES_GET

ITAB_CATPROPTY -

Data type: SDOKPROPTY
Optional: Yes
Call by Reference: Yes

DOCLISTTAB -

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

RESULTFEATTAB - Results List for Characteristic Determination

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

EXCEPTIONS details

CATID_NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

LANGUAGE_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

RFC_SYS_FAILURE - Communication Error

Data type:
Optional: No
Call by Reference: Yes

RFC_COM_FAILURE - Communication Error

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_DEST -

Data type:
Optional: No
Call by Reference: Yes

XERROR - Unknown Error

Data type:
Optional: No
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM SDOK_DOC_FEATURES_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