SAP CK_F_FIND_COSTING_PRICE_UPD Function Module for

Search SAP Function Modules

CK_F_FIND_COSTING_PRICE_UPD is a standard ck f find costing price upd 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 ck f find costing price upd FM, simply by entering the name CK_F_FIND_COSTING_PRICE_UPD into the relevant SAP transaction such as SE37 or SE38.

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

Function CK_F_FIND_COSTING_PRICE_UPD 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 'CK_F_FIND_COSTING_PRICE_UPD'"
  EXPORTING
   P_MATNR =  "
   P_WERKS =  "
   P_BWTAR =  "
   P_MKALK =  "
   P_KADKY =  "
   F_CKIPRICESUPDATE =  "

 IMPORTING
   F_KEKO_BWTAR =  "
   F_MACK2_BWTAR =  "
   F_MACK2_EIGEN =  "Client
   F_XDATA_CKSO_BWTAR =  "
   F_XDATA_CKSO_EIGEN =  "Executed

TABLES
   T_KEPH_BWTAR =  "

.

IMPORTING Parameters details for CK_F_FIND_COSTING_PRICE_UPD

P_MATNR -

Data type: MARC-MATNR
Optional: No
Call by Reference: Yes

P_WERKS -

Data type: MARC-WERKS
Optional: No
Call by Reference: Yes

P_BWTAR -

Data type: MBEW-BWTAR
Optional: No
Call by Reference: Yes

P_MKALK -

Data type: KEKO-MKALK
Optional: No
Call by Reference: Yes

P_KADKY -

Data type: KEKO-KADKY
Optional: No
Call by Reference: Yes

F_CKIPRICESUPDATE -

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

EXPORTING Parameters details for CK_F_FIND_COSTING_PRICE_UPD

F_KEKO_BWTAR -

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

F_MACK2_BWTAR -

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

F_MACK2_EIGEN - Client

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

F_XDATA_CKSO_BWTAR -

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

F_XDATA_CKSO_EIGEN - Executed

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

TABLES Parameters details for CK_F_FIND_COSTING_PRICE_UPD

T_KEPH_BWTAR -

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

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

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