SAP K_UNITCOSTING_FILTER_APPLY Function Module for









K_UNITCOSTING_FILTER_APPLY is a standard k unitcosting filter apply SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 unitcosting filter apply FM, simply by entering the name K_UNITCOSTING_FILTER_APPLY into the relevant SAP transaction such as SE37 or SE38.

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



Function K_UNITCOSTING_FILTER_APPLY 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_UNITCOSTING_FILTER_APPLY'"
EXPORTING
FILTER_DIALOG = "Filter
IT_KIS1 = "

IMPORTING
ET_POSNR = "
E_LINE_FOUND = "
.



IMPORTING Parameters details for K_UNITCOSTING_FILTER_APPLY

FILTER_DIALOG - Filter

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

IT_KIS1 -

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

EXPORTING Parameters details for K_UNITCOSTING_FILTER_APPLY

ET_POSNR -

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

E_LINE_FOUND -

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

Copy and paste ABAP code example for K_UNITCOSTING_FILTER_APPLY 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_et_posnr  TYPE KKEK0_POSNR_LIST, "   
lv_filter_dialog  TYPE KKEK3_FILTER_DIALOG, "   
lv_it_kis1  TYPE KKEK0_KIS1_TAB, "   
lv_e_line_found  TYPE XFLAG. "   

  CALL FUNCTION 'K_UNITCOSTING_FILTER_APPLY'  "
    EXPORTING
         FILTER_DIALOG = lv_filter_dialog
         IT_KIS1 = lv_it_kis1
    IMPORTING
         ET_POSNR = lv_et_posnr
         E_LINE_FOUND = lv_e_line_found
. " K_UNITCOSTING_FILTER_APPLY




ABAP code using 7.40 inline data declarations to call FM K_UNITCOSTING_FILTER_APPLY

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!