SAP K_OPEN_ITEM_CF_PROJECT Function Module for Commitment Carryforward









K_OPEN_ITEM_CF_PROJECT is a standard k open item cf project SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Commitment Carryforward 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 k open item cf project FM, simply by entering the name K_OPEN_ITEM_CF_PROJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function K_OPEN_ITEM_CF_PROJECT 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_OPEN_ITEM_CF_PROJECT'"Commitment Carryforward
EXPORTING
* PD_STORNO = ' ' "
PD_GJAHR = "Fiscal Year
* PD_LMONA = "Fiscal Year Variant

TABLES
T_COOI = "
T_COEP = "

EXCEPTIONS
NO_DATA = 1 WRONG_GJAHR = 2 NO_LMONA = 3
.



IMPORTING Parameters details for K_OPEN_ITEM_CF_PROJECT

PD_STORNO -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

PD_GJAHR - Fiscal Year

Data type: COOI-GJAHR
Optional: No
Call by Reference: Yes

PD_LMONA - Fiscal Year Variant

Data type: TKA01-LMONA
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for K_OPEN_ITEM_CF_PROJECT

T_COOI -

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

T_COEP -

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

EXCEPTIONS details

NO_DATA -

Data type:
Optional: No
Call by Reference: Yes

WRONG_GJAHR -

Data type:
Optional: No
Call by Reference: Yes

NO_LMONA -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for K_OPEN_ITEM_CF_PROJECT 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:
lt_t_cooi  TYPE STANDARD TABLE OF COOI, "   
lv_no_data  TYPE COOI, "   
lv_pd_storno  TYPE C, "   ' '
lt_t_coep  TYPE STANDARD TABLE OF COEP, "   
lv_pd_gjahr  TYPE COOI-GJAHR, "   
lv_wrong_gjahr  TYPE COOI, "   
lv_no_lmona  TYPE COOI, "   
lv_pd_lmona  TYPE TKA01-LMONA. "   

  CALL FUNCTION 'K_OPEN_ITEM_CF_PROJECT'  "Commitment Carryforward
    EXPORTING
         PD_STORNO = lv_pd_storno
         PD_GJAHR = lv_pd_gjahr
         PD_LMONA = lv_pd_lmona
    TABLES
         T_COOI = lt_t_cooi
         T_COEP = lt_t_coep
    EXCEPTIONS
        NO_DATA = 1
        WRONG_GJAHR = 2
        NO_LMONA = 3
. " K_OPEN_ITEM_CF_PROJECT




ABAP code using 7.40 inline data declarations to call FM K_OPEN_ITEM_CF_PROJECT

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.

 
 
DATA(ld_pd_storno) = ' '.
 
 
"SELECT single GJAHR FROM COOI INTO @DATA(ld_pd_gjahr).
 
 
 
"SELECT single LMONA FROM TKA01 INTO @DATA(ld_pd_lmona).
 


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!