SAP SDOK_GENERIC_INTERFACE Function Module for









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

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



Function SDOK_GENERIC_INTERFACE 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_GENERIC_INTERFACE'"
  EXPORTING
   FUNCTION_NAME =  "Function Module Name

TABLES
*  INFO_OBJECTS =  "
*  EXTENSION =  "Other Information
*  CONTEXT =  "Context Parameter
*  RELATIONS =  "Relationships
*  PROPERTIES =  "Properties
*  QUERY =  "
*  CHECK_OUT_LIST =  "
*  BAD_OBJECTS =  "Incorrect Objects
*  BAD_RELATIONS =  "Dependencies with Errors
*  BAD_PROPERTIES =  "

EXCEPTIONS
   BAD_FUNCTION_NAME = 1
.



IMPORTING Parameters details for SDOK_GENERIC_INTERFACE

FUNCTION_NAME - Function Module Name

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

TABLES Parameters details for SDOK_GENERIC_INTERFACE

INFO_OBJECTS -

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

EXTENSION - Other Information

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

CONTEXT - Context Parameter

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

RELATIONS - Relationships

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

PROPERTIES - Properties

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

QUERY -

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

CHECK_OUT_LIST -

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

BAD_OBJECTS - Incorrect Objects

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

BAD_RELATIONS - Dependencies with Errors

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

BAD_PROPERTIES -

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

EXCEPTIONS details

BAD_FUNCTION_NAME -

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

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

DATA:
lt_info_objects  TYPE STANDARD TABLE OF SDOKOBJECT, "   
lv_function_name  TYPE TFDIR-FUNCNAME, "   
lv_bad_function_name  TYPE TFDIR, "   
lt_extension  TYPE STANDARD TABLE OF SDOKCNTASC, "   
lt_context  TYPE STANDARD TABLE OF SDOKPROPTY, "   
lt_relations  TYPE STANDARD TABLE OF SDOKRELA, "   
lt_properties  TYPE STANDARD TABLE OF SDOKPROPTL, "   
lt_query  TYPE STANDARD TABLE OF SDOKQUPROP, "   
lt_check_out_list  TYPE STANDARD TABLE OF SDOKR3LLST, "   
lt_bad_objects  TYPE STANDARD TABLE OF SDOKERRMSG, "   
lt_bad_relations  TYPE STANDARD TABLE OF SDOKERRMSR, "   
lt_bad_properties  TYPE STANDARD TABLE OF SDOKERRMSP. "   

  CALL FUNCTION 'SDOK_GENERIC_INTERFACE'  "
    EXPORTING
         FUNCTION_NAME = lv_function_name
    TABLES
         INFO_OBJECTS = lt_info_objects
         EXTENSION = lt_extension
         CONTEXT = lt_context
         RELATIONS = lt_relations
         PROPERTIES = lt_properties
         QUERY = lt_query
         CHECK_OUT_LIST = lt_check_out_list
         BAD_OBJECTS = lt_bad_objects
         BAD_RELATIONS = lt_bad_relations
         BAD_PROPERTIES = lt_bad_properties
    EXCEPTIONS
        BAD_FUNCTION_NAME = 1
. " SDOK_GENERIC_INTERFACE




ABAP code using 7.40 inline data declarations to call FM SDOK_GENERIC_INTERFACE

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.

 
"SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_function_name).
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!