SAP EXIT_SAPLCOKO1_004 Function Module for Check whether changes to order header/item are allowed in the dialog









EXIT_SAPLCOKO1_004 is a standard exit saplcoko1 004 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check whether changes to order header/item are allowed in the dialog processing and below is the pattern details for this FM, 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 exit saplcoko1 004 FM, simply by entering the name EXIT_SAPLCOKO1_004 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPLCOKO1_004 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 'EXIT_SAPLCOKO1_004'"Check whether changes to order header/item are allowed in the dialog
  EXPORTING
   IS_HEADER_NEW =  "Order header before change
   IS_HEADER_OLD =  "Order header after change
   IS_ITEM_NEW =  "Order item for order header before change
   IS_ITEM_OLD =  "Order item for order header after change

EXCEPTIONS
   NO_CHANGES_ALLOWED = 1
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
CO_KO1_CHECK_PROJN Überprüfung und Ermittlung von PSP-Elementdaten
CO_KO1_DYNP_0100 For testing only - Do not use!
CO_KO1_DYNP_0110 For testing only - Do not use!
CO_KO1_DYNP_0115 For testing only - Do not use!
CO_KO1_DYNP_0120 For testing only - Do not use!
CO_KO1_DYNP_0130 For testing only - Do not use!
CO_KO1_DYNP_0140 For testing only - Do not use!
CO_KO1_DYNP_0190 For testing only - Do not use!
CO_KO1_DYNP_0210 For testing only - Do not use!
CO_KO1_DYNP_0220 For testing only - Do not use!
CO_KO1_DYNP_0240 For testing only - Do not use!
CO_KO1_DYNP_0800 For testing only - Do not use!
CO_KO1_DYNP_TRANS For testing only - Do not use!
CO_KO1_FHM_AVAILABILITY_CHK Verfügbarkeitsprüfung der FHM zu einem auftrag
CO_KO1_GET_HEADER Bereitstellung Auftragskopf für ext. Modulpools
CO_KO1_GET_RC27S Lesen der Steuerleiste rc27s aus coko1
CO_KO1_ORDER_ENTRY_EXT Einstieg in die Auftragsbearbeitung aus externer Anwendung
CO_KO1_ORDER_OK_CODE_EXT Externe OK-Code Verarbeitung
CO_KO1_SET_HEADER Übergeben CAUFVD an SAPLCOKO zwecks SUBSCREEN-Anzeige
CO_KO1_SET_RC27S Ändern der Steuerleiste rc27s in COKO1

IMPORTING Parameters details for EXIT_SAPLCOKO1_004

IS_HEADER_NEW - Order header before change

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

IS_HEADER_OLD - Order header after change

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

IS_ITEM_NEW - Order item for order header before change

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

IS_ITEM_OLD - Order item for order header after change

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

EXCEPTIONS details

NO_CHANGES_ALLOWED - Changes are not allowed

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

Copy and paste ABAP code example for EXIT_SAPLCOKO1_004 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_is_header_new  TYPE CAUFVD, "   
lv_no_changes_allowed  TYPE CAUFVD, "   
lv_is_header_old  TYPE CAUFVD, "   
lv_is_item_new  TYPE AFPOD, "   
lv_is_item_old  TYPE AFPOD. "   

  CALL FUNCTION 'EXIT_SAPLCOKO1_004'  "Check whether changes to order header/item are allowed in the dialog
    EXPORTING
         IS_HEADER_NEW = lv_is_header_new
         IS_HEADER_OLD = lv_is_header_old
         IS_ITEM_NEW = lv_is_item_new
         IS_ITEM_OLD = lv_is_item_old
    EXCEPTIONS
        NO_CHANGES_ALLOWED = 1
. " EXIT_SAPLCOKO1_004




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLCOKO1_004

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



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!