CK_COSTINGRUN_FIND_OUT_DATES SAP Function module

CK_COSTINGRUN_FIND_OUT_DATES is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CK_COSTINGRUN_FIND_OUT_DATES into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CKCC03
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CK_COSTINGRUN_FIND_OUT_DATES - CK COSTINGRUN FIND OUT DATES

CALL FUNCTION 'CK_COSTINGRUN_FIND_OUT_DATES' "
  EXPORTING
    im_periv =                  " periv         Fiscal Year Variant
    im_date =                   " kala-kadat    Costing Date From
    im_tck16 =                  " tck16         Date Control
  CHANGING
    ch_kadat =                  " kala-kadat    Costing Date From
    ch_bidat =                  " kala-bidat    Costing Date To
    ch_aldat =                  " kala-aldat    Quantity Structure Date for Costing
    ch_bwdat =                  " kala-bwdat    Valuation Date of a Cost Estimate
    .  "  CK_COSTINGRUN_FIND_OUT_DATES

ABAP code example for Function Module CK_COSTINGRUN_FIND_OUT_DATES

The ABAP code below is a full code listing to execute function module CK_COSTINGRUN_FIND_OUT_DATES including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

 

SELECT single KADAT 
  FROM KALA 
  INTO @DATA(ld_ch_kadat).

 

SELECT single BIDAT 
  FROM KALA 
  INTO @DATA(ld_ch_bidat).

 

SELECT single ALDAT 
  FROM KALA 
  INTO @DATA(ld_ch_aldat).

 

SELECT single BWDAT 
  FROM KALA 
  INTO @DATA(ld_ch_bwdat).


DATA(ld_im_periv) = 'Check type of data required'.
 

SELECT single KADAT 
  FROM KALA 
  INTO @DATA(ld_im_date).


DATA(ld_im_tck16) = 'Check type of data required'.
.

CALL FUNCTION 'CK_COSTINGRUN_FIND_OUT_DATES'
  EXPORTING
    im_periv =                   ld_im_periv
    im_date =                    ld_im_date
    im_tck16 =                   ld_im_tck16
  CHANGING
    ch_kadat =                   ld_ch_kadat
    ch_bidat =                   ld_ch_bidat
    ch_aldat =                   ld_ch_aldat
    ch_bwdat =                   ld_ch_bwdat
    .  "  CK_COSTINGRUN_FIND_OUT_DATES

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ch_kadat
 
 TYPE KALA-KADAT ,
ld_im_periv
 
 TYPE PERIV ,
ld_ch_bidat
 
 TYPE KALA-BIDAT ,
ld_im_date
 
 TYPE KALA-KADAT ,
ld_ch_aldat
 
 TYPE KALA-ALDAT ,
ld_im_tck16
 
 TYPE TCK16 ,
ld_ch_bwdat
 
 TYPE KALA-BWDAT .



SELECT single KADAT 
  FROM KALA 
  INTO ld_ch_kadat.

ld_im_periv = 'Check type of data required'.

SELECT single BIDAT 
  FROM KALA 
  INTO ld_ch_bidat.


SELECT single KADAT 
  FROM KALA 
  INTO ld_im_date.


SELECT single ALDAT 
  FROM KALA 
  INTO ld_ch_aldat.

ld_im_tck16 = 'Check type of data required'.

SELECT single BWDAT 
  FROM KALA 
  INTO ld_ch_bwdat.