SAP K_ORDER_CHECK_SET Function Module for









K_ORDER_CHECK_SET is a standard k order check set 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 k order check set FM, simply by entering the name K_ORDER_CHECK_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function K_ORDER_CHECK_SET 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 'K_ORDER_CHECK_SET'"
  EXPORTING
*  ALLOWED_AUTYP = ' ' "Valid order types
*  AUART = ' ' "Order type
*  AUFGR = ' ' "
*  AUFNR = ' ' "
*  ENQUEUE = ' ' "
*  KOKRS = ' ' "
*  VRGNG = ' ' "
*  ACTVT = '02' "

 IMPORTING
   SET_TITLE =  "Text on order set
   E_TABIX =  "

EXCEPTIONS
   AMBIGUOUS_INPUT = 1    INSUFFICIENT_INPUT = 2
.



IMPORTING Parameters details for K_ORDER_CHECK_SET

ALLOWED_AUTYP - Valid order types

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

AUART - Order type

Data type: T003O-AUART
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

AUFGR -

Data type: CODIA-AUFGR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

AUFNR -

Data type: AUFK-AUFNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENQUEUE -

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

KOKRS -

Data type: TKA01-KOKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

VRGNG -

Data type: TJ01-VRGNG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACTVT -

Data type: TACT-ACTVT
Default: '02'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for K_ORDER_CHECK_SET

SET_TITLE - Text on order set

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

E_TABIX -

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

EXCEPTIONS details

AMBIGUOUS_INPUT - Both AUFGR and AUFNR are filled

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

INSUFFICIENT_INPUT - Neither AUFGR nor AUFNR is filled

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

Copy and paste ABAP code example for K_ORDER_CHECK_SET 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_set_title  TYPE SETINFO-TITLE, "   
lv_allowed_autyp  TYPE SETINFO, "   SPACE
lv_ambiguous_input  TYPE SETINFO, "   
lv_auart  TYPE T003O-AUART, "   SPACE
lv_e_tabix  TYPE SY-TABIX, "   
lv_insufficient_input  TYPE SY, "   
lv_aufgr  TYPE CODIA-AUFGR, "   SPACE
lv_aufnr  TYPE AUFK-AUFNR, "   SPACE
lv_enqueue  TYPE AUFK, "   SPACE
lv_kokrs  TYPE TKA01-KOKRS, "   SPACE
lv_vrgng  TYPE TJ01-VRGNG, "   SPACE
lv_actvt  TYPE TACT-ACTVT. "   '02'

  CALL FUNCTION 'K_ORDER_CHECK_SET'  "
    EXPORTING
         ALLOWED_AUTYP = lv_allowed_autyp
         AUART = lv_auart
         AUFGR = lv_aufgr
         AUFNR = lv_aufnr
         ENQUEUE = lv_enqueue
         KOKRS = lv_kokrs
         VRGNG = lv_vrgng
         ACTVT = lv_actvt
    IMPORTING
         SET_TITLE = lv_set_title
         E_TABIX = lv_e_tabix
    EXCEPTIONS
        AMBIGUOUS_INPUT = 1
        INSUFFICIENT_INPUT = 2
. " K_ORDER_CHECK_SET




ABAP code using 7.40 inline data declarations to call FM K_ORDER_CHECK_SET

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 TITLE FROM SETINFO INTO @DATA(ld_set_title).
 
DATA(ld_allowed_autyp) = ' '.
 
 
"SELECT single AUART FROM T003O INTO @DATA(ld_auart).
DATA(ld_auart) = ' '.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_e_tabix).
 
 
"SELECT single AUFGR FROM CODIA INTO @DATA(ld_aufgr).
DATA(ld_aufgr) = ' '.
 
"SELECT single AUFNR FROM AUFK INTO @DATA(ld_aufnr).
DATA(ld_aufnr) = ' '.
 
DATA(ld_enqueue) = ' '.
 
"SELECT single KOKRS FROM TKA01 INTO @DATA(ld_kokrs).
DATA(ld_kokrs) = ' '.
 
"SELECT single VRGNG FROM TJ01 INTO @DATA(ld_vrgng).
DATA(ld_vrgng) = ' '.
 
"SELECT single ACTVT FROM TACT INTO @DATA(ld_actvt).
DATA(ld_actvt) = '02'.
 


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!