SAP ALINK_KPRO_ENTRIES_QUERY Function Module for









ALINK_KPRO_ENTRIES_QUERY is a standard alink kpro entries query 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 alink kpro entries query FM, simply by entering the name ALINK_KPRO_ENTRIES_QUERY into the relevant SAP transaction such as SE37 or SE38.

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



Function ALINK_KPRO_ENTRIES_QUERY 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 'ALINK_KPRO_ENTRIES_QUERY'"
  EXPORTING
*  CLIENT = SY-MANDT "Client
   DOCU' ' =  "Document Area

TABLES
   QUERYTAB =  "SDOK: Fields for query
*  RESULT =  "SDOK: BOR key for information object
*  L_PROPERTIES_REQUEST =  "SDOK: Object, attribute name and feature
*  L_PROPERTIES_RESULT =  "SDOK: Name of object attributes
*  P_PROPERTIES_REQUEST =  "SDOK: Name of object attributes
*  P_PROPERTIES_RESULT =  "SDOK: Object, attribute name and feature

EXCEPTIONS
   BAD_CLASS = 1    BAD_QUERY = 2    NO_QUERY = 3
.



IMPORTING Parameters details for ALINK_KPRO_ENTRIES_QUERY

CLIENT - Client

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

DOCUSPACE - Document Area

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

TABLES Parameters details for ALINK_KPRO_ENTRIES_QUERY

QUERYTAB - SDOK: Fields for query

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

RESULT - SDOK: BOR key for information object

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

L_PROPERTIES_REQUEST - SDOK: Object, attribute name and feature

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

L_PROPERTIES_RESULT - SDOK: Name of object attributes

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

P_PROPERTIES_REQUEST - SDOK: Name of object attributes

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

P_PROPERTIES_RESULT - SDOK: Object, attribute name and feature

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

EXCEPTIONS details

BAD_CLASS - Incorrect class

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

BAD_QUERY -

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

NO_QUERY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ALINK_KPRO_ENTRIES_QUERY 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:
lv_client  TYPE TOAV0-MANDT, "   SY-MANDT
lt_querytab  TYPE STANDARD TABLE OF SDOKQUPROP, "   
lv_bad_class  TYPE SDOKQUPROP, "   
lt_result  TYPE STANDARD TABLE OF SDOKLOGPHY, "   
lv_bad_query  TYPE SDOKLOGPHY, "   
lv_docuspace  TYPE TOAKPRO-DOCUSPACE, "   
lv_no_query  TYPE TOAKPRO, "   
lt_l_properties_request  TYPE STANDARD TABLE OF SDOKPROPTN, "   
lt_l_properties_result  TYPE STANDARD TABLE OF SDOKPROPTL, "   
lt_p_properties_request  TYPE STANDARD TABLE OF SDOKPROPTN, "   
lt_p_properties_result  TYPE STANDARD TABLE OF SDOKPROPTL. "   

  CALL FUNCTION 'ALINK_KPRO_ENTRIES_QUERY'  "
    EXPORTING
         CLIENT = lv_client
         DOCUSPACE = lv_docuspace
    TABLES
         QUERYTAB = lt_querytab
         RESULT = lt_result
         L_PROPERTIES_REQUEST = lt_l_properties_request
         L_PROPERTIES_RESULT = lt_l_properties_result
         P_PROPERTIES_REQUEST = lt_p_properties_request
         P_PROPERTIES_RESULT = lt_p_properties_result
    EXCEPTIONS
        BAD_CLASS = 1
        BAD_QUERY = 2
        NO_QUERY = 3
. " ALINK_KPRO_ENTRIES_QUERY




ABAP code using 7.40 inline data declarations to call FM ALINK_KPRO_ENTRIES_QUERY

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 MANDT FROM TOAV0 INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
 
 
 
 
"SELECT single DOCUSPACE FROM TOAKPRO INTO @DATA(ld_docuspace).
 
 
 
 
 
 


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!