SAP Function Modules

CK_COSTINGRUN_STATE_SET SAP Function module







CK_COSTINGRUN_STATE_SET 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_STATE_SET into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM CK_COSTINGRUN_STATE_SET - CK COSTINGRUN STATE SET





CALL FUNCTION 'CK_COSTINGRUN_STATE_SET' "
  EXPORTING
    i_kalaid =                  " kala-kalaid   Name of costing run
    i_kaladat =                 " kala-kaladat  Costing run date
*   i_date_in_past = 'A'        " ckcc_kala_state-date_in_past
*   i_not_posted = 'A'          " ckcc_kala_state-not_posted
*   i_selected = 'A'            " ckcc_kala_state-selected
*   i_not_found = 'A'           " ckcc_kala_state-not_found
*   i_no_mark = 'A'             " ckcc_kala_state-no_mark
*   i_no_release = 'A'          " ckcc_kala_state-no_release
*   i_no_main_data = 'A'        " ckcc_kala_state-no_main_data
    .  "  CK_COSTINGRUN_STATE_SET

ABAP code example for Function Module CK_COSTINGRUN_STATE_SET





The ABAP code below is a full code listing to execute function module CK_COSTINGRUN_STATE_SET 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 KALAID
FROM KALA
INTO @DATA(ld_i_kalaid).


SELECT single KALADAT
FROM KALA
INTO @DATA(ld_i_kaladat).


DATA(ld_i_date_in_past) = some text here

DATA(ld_i_not_posted) = some text here

DATA(ld_i_selected) = some text here

DATA(ld_i_not_found) = some text here

DATA(ld_i_no_mark) = some text here

DATA(ld_i_no_release) = some text here

DATA(ld_i_no_main_data) = some text here . CALL FUNCTION 'CK_COSTINGRUN_STATE_SET' EXPORTING i_kalaid = ld_i_kalaid i_kaladat = ld_i_kaladat * i_date_in_past = ld_i_date_in_past * i_not_posted = ld_i_not_posted * i_selected = ld_i_selected * i_not_found = ld_i_not_found * i_no_mark = ld_i_no_mark * i_no_release = ld_i_no_release * i_no_main_data = ld_i_no_main_data . " CK_COSTINGRUN_STATE_SET
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_i_kalaid  TYPE KALA-KALAID ,
ld_i_kaladat  TYPE KALA-KALADAT ,
ld_i_date_in_past  TYPE CKCC_KALA_STATE-DATE_IN_PAST ,
ld_i_not_posted  TYPE CKCC_KALA_STATE-NOT_POSTED ,
ld_i_selected  TYPE CKCC_KALA_STATE-SELECTED ,
ld_i_not_found  TYPE CKCC_KALA_STATE-NOT_FOUND ,
ld_i_no_mark  TYPE CKCC_KALA_STATE-NO_MARK ,
ld_i_no_release  TYPE CKCC_KALA_STATE-NO_RELEASE ,
ld_i_no_main_data  TYPE CKCC_KALA_STATE-NO_MAIN_DATA .


SELECT single KALAID
FROM KALA
INTO ld_i_kalaid.


SELECT single KALADAT
FROM KALA
INTO ld_i_kaladat.


ld_i_date_in_past = some text here

ld_i_not_posted = some text here

ld_i_selected = some text here

ld_i_not_found = some text here

ld_i_no_mark = some text here

ld_i_no_release = some text here

ld_i_no_main_data = some text here

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CK_COSTINGRUN_STATE_SET or its description.