SAP CKTC10_CONCURRENT_COST_CREATE Function Module for NOTRANSL: Anlegen einer Concurrent Costing zu einer iPPE-Variante

Search SAP Function Modules

CKTC10_CONCURRENT_COST_CREATE is a standard cktc10 concurrent cost create 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: Anlegen einer Concurrent Costing zu einer iPPE-Variante 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 cktc10 concurrent cost create FM, simply by entering the name CKTC10_CONCURRENT_COST_CREATE into the relevant SAP transaction such as SE37 or SE38.

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

Function CKTC10_CONCURRENT_COST_CREATE 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 'CKTC10_CONCURRENT_COST_CREATE'"NOTRANSL: Anlegen einer Concurrent Costing zu einer iPPE-Variante
  EXPORTING
   IM_OBJECT_KEY =  "Key for Costing Numbers Concurrent Costing
*  IM_COSTING_DATE_FROM =  "Costing Date From
*  IM_COSTING_DATE_TO =  "Costing Date To
*  IM_COSTING_VERSION = '01' "Costing Version
*  IM_SAVING_ALLOWED = 'X' "Checkbox
*  IM_CUOBJ_PASSING_THRU = 'X' "Checkbox
   IM_PLANT =  "Plant
*  IM_MATERIAL_NUMBER =  "Material Number
   IM_PGUID =  "Internal Identification for PVS Objects
   IM_OTYPE =  "iPPE Object Type
   IM_QUANTITY =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   IM_COSTING_VARIANT =  "Costing Variant
*  IM_VALUATION_DATE = SY-DATUM "Valuation Date of a Cost Estimate
*  IM_QUANTITY_STRUCTURE_DATE = SY-DATUM "Quantity Structure Date for Costing

EXCEPTIONS
   CALL_INVALID = 1 

.

IMPORTING Parameters details for CKTC10_CONCURRENT_COST_CREATE

IM_OBJECT_KEY - Key for Costing Numbers Concurrent Costing

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

IM_COSTING_DATE_FROM - Costing Date From

Data type: CK_ABDAT
Optional: Yes
Call by Reference: Yes

IM_COSTING_DATE_TO - Costing Date To

Data type: CK_BIDAT
Optional: Yes
Call by Reference: Yes

IM_COSTING_VERSION - Costing Version

Data type: CK_TVERS
Default: '01'
Optional: No
Call by Reference: Yes

IM_SAVING_ALLOWED - Checkbox

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IM_CUOBJ_PASSING_THRU - Checkbox

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IM_PLANT - Plant

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

IM_MATERIAL_NUMBER - Material Number

Data type: MARA-MATNR
Optional: Yes
Call by Reference: Yes

IM_PGUID - Internal Identification for PVS Objects

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

IM_OTYPE - iPPE Object Type

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

IM_QUANTITY - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IM_COSTING_VARIANT - Costing Variant

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

IM_VALUATION_DATE - Valuation Date of a Cost Estimate

Data type: CK_BWDAT
Default: SY-DATUM
Optional: No
Call by Reference: Yes

IM_QUANTITY_STRUCTURE_DATE - Quantity Structure Date for Costing

Data type: CK_BRDAT
Default: SY-DATUM
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CALL_INVALID - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

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

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