SAP CY_KBED_COMMITMENT_READ Function Module for NOTRANSL: Reads commitment-tables if certain entry can be found and delete

Search SAP Function Modules

CY_KBED_COMMITMENT_READ is a standard cy kbed commitment read 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: Reads commitment-tables if certain entry can be found and delete 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 cy kbed commitment read FM, simply by entering the name CY_KBED_COMMITMENT_READ 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 CY_KBED_COMMITMENT_READ 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 'CY_KBED_COMMITMENT_READ'"NOTRANSL: Reads commitment-tables if certain entry can be found and delete
  EXPORTING
*  I_FLG_FORWARD = 'X' "Generic Type
*  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_KAPID =  "Capacity ID

TABLES
*  I_OPR_TO_MOVE =  "Order-/operation structure
*  I_KAKO_TAB =  "Capacity Header Data with Short Text

EXCEPTIONS
   NOT_FOUND = 1 

.

IMPORTING Parameters details for CY_KBED_COMMITMENT_READ

I_FLG_FORWARD - Generic Type

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

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_KAPID - Capacity ID

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

TABLES Parameters details for CY_KBED_COMMITMENT_READ

I_OPR_TO_MOVE - Order-/operation structure

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

I_KAKO_TAB - Capacity Header Data with Short Text

Data type: RKAKO_A
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)

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

ABAP code using 7.40 inline data declarations to call FM CY_KBED_COMMITMENT_READ

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