SAP CY16_OPR_COMMITMENT_DELETE Function Module for NOTRANSL: Delete operations from commitment tables









CY16_OPR_COMMITMENT_DELETE is a standard cy16 opr commitment delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Delete operations from commitment tables 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 cy16 opr commitment delete FM, simply by entering the name CY16_OPR_COMMITMENT_DELETE into the relevant SAP transaction such as SE37 or SE38.

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



Function CY16_OPR_COMMITMENT_DELETE 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 'CY16_OPR_COMMITMENT_DELETE'"NOTRANSL: Delete operations from commitment tables
EXPORTING
* I_INDEX = "Index to object order operation
* I_FLGKBED = ' ' "Index is capacity requirements index
* I_KEY1 = "ID of the Capacity Requirements Record
* I_KEY2 = "Internal counter
* I_KEY3 = "Counters for cap. rqmts. records (various caps. + indiv.caps
* I_TAB_KEY = ' ' "Generic Type
* I_KBED_STR = "Capacity requirements: dialog table for KBED

TABLES
* I_OPR_DEL_TAB = "Order-/operation structure

EXCEPTIONS
NOT_FOUND = 1 KEYS_NOT_VALID = 2 KEYS_NOT_UNIQUE = 3 NO_BASIC_LOAD_FILLED = 4
.



IMPORTING Parameters details for CY16_OPR_COMMITMENT_DELETE

I_INDEX - Index to object order operation

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

I_FLGKBED - Index is capacity requirements index

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

I_KEY1 - ID of the Capacity Requirements Record

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

I_KEY2 - Internal counter

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

I_KEY3 - Counters for cap. rqmts. records (various caps. + indiv.caps

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

I_TAB_KEY - Generic Type

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

I_KBED_STR - Capacity requirements: dialog table for KBED

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

TABLES Parameters details for CY16_OPR_COMMITMENT_DELETE

I_OPR_DEL_TAB - Order-/operation structure

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

EXCEPTIONS details

NOT_FOUND -

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

KEYS_NOT_VALID -

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

KEYS_NOT_UNIQUE -

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

NO_BASIC_LOAD_FILLED -

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

Copy and paste ABAP code example for CY16_OPR_COMMITMENT_DELETE 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_i_index  TYPE CYKAPABEL-INDEX, "   
lv_not_found  TYPE CYKAPABEL, "   
lt_i_opr_del_tab  TYPE STANDARD TABLE OF CYOPR_M, "   
lv_i_flgkbed  TYPE CYKAPABEL-FLGKBED, "   SPACE
lv_keys_not_valid  TYPE CYKAPABEL, "   
lv_i_key1  TYPE CYKAPABEL-KEY1, "   
lv_keys_not_unique  TYPE CYKAPABEL, "   
lv_i_key2  TYPE CYKAPABEL-KEY2, "   
lv_no_basic_load_filled  TYPE CYKAPABEL, "   
lv_i_key3  TYPE CYKAPABEL-KEY3, "   
lv_i_tab_key  TYPE C, "   SPACE
lv_i_kbed_str  TYPE KBEDD. "   

  CALL FUNCTION 'CY16_OPR_COMMITMENT_DELETE'  "NOTRANSL: Delete operations from commitment tables
    EXPORTING
         I_INDEX = lv_i_index
         I_FLGKBED = lv_i_flgkbed
         I_KEY1 = lv_i_key1
         I_KEY2 = lv_i_key2
         I_KEY3 = lv_i_key3
         I_TAB_KEY = lv_i_tab_key
         I_KBED_STR = lv_i_kbed_str
    TABLES
         I_OPR_DEL_TAB = lt_i_opr_del_tab
    EXCEPTIONS
        NOT_FOUND = 1
        KEYS_NOT_VALID = 2
        KEYS_NOT_UNIQUE = 3
        NO_BASIC_LOAD_FILLED = 4
. " CY16_OPR_COMMITMENT_DELETE




ABAP code using 7.40 inline data declarations to call FM CY16_OPR_COMMITMENT_DELETE

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 INDEX FROM CYKAPABEL INTO @DATA(ld_i_index).
 
 
 
"SELECT single FLGKBED FROM CYKAPABEL INTO @DATA(ld_i_flgkbed).
DATA(ld_i_flgkbed) = ' '.
 
 
"SELECT single KEY1 FROM CYKAPABEL INTO @DATA(ld_i_key1).
 
 
"SELECT single KEY2 FROM CYKAPABEL INTO @DATA(ld_i_key2).
 
 
"SELECT single KEY3 FROM CYKAPABEL INTO @DATA(ld_i_key3).
 
DATA(ld_i_tab_key) = ' '.
 
 


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!