SAP CY_CAPACITY_COMMITMENT_GET Function Module for NOTRANSL: Satz aus Kapazitätsbelegung lesen









CY_CAPACITY_COMMITMENT_GET is a standard cy capacity commitment get 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: Satz aus Kapazitätsbelegung lesen 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 capacity commitment get FM, simply by entering the name CY_CAPACITY_COMMITMENT_GET 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_CAPACITY_COMMITMENT_GET 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_CAPACITY_COMMITMENT_GET'"NOTRANSL: Satz aus Kapazitätsbelegung lesen
EXPORTING
* I_DATE = 0 "Predefined Type
* I_FLG_FORWARD = ' ' "Forwards
* I_INDEX_COMM = 0 "ABAP System Field: Row Index of Internal Tables
I_KAPID = "Capacity used
* I_TIME = 0 "Start time in seconds (internal)
* I_TAB_KEY = ' ' "Generic Type
* I_KAPAVO = ' ' "Indicator: Several operations can use capacity

IMPORTING
E_INDEX_COMM = "Index
E_INDEX_COMM_SUCC = "ABAP System Field: Row Index of Internal Tables
E_COMMITMENT_SUM = "Structure of capacity usage summary
E_COMMITMENT_SUM_SUCC = "Structure of capacity usage summary
.



IMPORTING Parameters details for CY_CAPACITY_COMMITMENT_GET

I_DATE - Predefined Type

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

I_FLG_FORWARD - Forwards

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

I_INDEX_COMM - ABAP System Field: Row Index of Internal Tables

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

I_KAPID - Capacity used

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

I_TIME - Start time in seconds (internal)

Data type: KAPA-BEGZT
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_KAPAVO - Indicator: Several operations can use capacity

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

EXPORTING Parameters details for CY_CAPACITY_COMMITMENT_GET

E_INDEX_COMM - Index

Data type: SY-TABIX
Optional: No
Call by Reference: Yes

E_INDEX_COMM_SUCC - ABAP System Field: Row Index of Internal Tables

Data type: SY-TABIX
Optional: No
Call by Reference: Yes

E_COMMITMENT_SUM - Structure of capacity usage summary

Data type: CYKAPASBEL
Optional: No
Call by Reference: Yes

E_COMMITMENT_SUM_SUCC - Structure of capacity usage summary

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

Copy and paste ABAP code example for CY_CAPACITY_COMMITMENT_GET 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_date  TYPE I, "   0
lv_e_index_comm  TYPE SY-TABIX, "   
lv_i_flg_forward  TYPE C, "   SPACE
lv_e_index_comm_succ  TYPE SY-TABIX, "   
lv_i_index_comm  TYPE SY-TABIX, "   0
lv_e_commitment_sum  TYPE CYKAPASBEL, "   
lv_i_kapid  TYPE KAKO-KAPID, "   
lv_e_commitment_sum_succ  TYPE CYKAPASBEL, "   
lv_i_time  TYPE KAPA-BEGZT, "   0
lv_i_tab_key  TYPE C, "   SPACE
lv_i_kapavo  TYPE KAKO-KAPAVO. "   SPACE

  CALL FUNCTION 'CY_CAPACITY_COMMITMENT_GET'  "NOTRANSL: Satz aus Kapazitätsbelegung lesen
    EXPORTING
         I_DATE = lv_i_date
         I_FLG_FORWARD = lv_i_flg_forward
         I_INDEX_COMM = lv_i_index_comm
         I_KAPID = lv_i_kapid
         I_TIME = lv_i_time
         I_TAB_KEY = lv_i_tab_key
         I_KAPAVO = lv_i_kapavo
    IMPORTING
         E_INDEX_COMM = lv_e_index_comm
         E_INDEX_COMM_SUCC = lv_e_index_comm_succ
         E_COMMITMENT_SUM = lv_e_commitment_sum
         E_COMMITMENT_SUM_SUCC = lv_e_commitment_sum_succ
. " CY_CAPACITY_COMMITMENT_GET




ABAP code using 7.40 inline data declarations to call FM CY_CAPACITY_COMMITMENT_GET

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 TABIX FROM SY INTO @DATA(ld_e_index_comm).
 
DATA(ld_i_flg_forward) = ' '.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_e_index_comm_succ).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_i_index_comm).
 
 
"SELECT single KAPID FROM KAKO INTO @DATA(ld_i_kapid).
 
 
"SELECT single BEGZT FROM KAPA INTO @DATA(ld_i_time).
 
DATA(ld_i_tab_key) = ' '.
 
"SELECT single KAPAVO FROM KAKO INTO @DATA(ld_i_kapavo).
DATA(ld_i_kapavo) = ' '.
 


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!