SAP Function Modules

RKEV_POST_CB_PLAN_DATA SAP Function module







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

Associated Function Group: KEEX_BCT
Released Date: Not Released
Processing type: Remote-Enabled + BasXML supported
remote enabled with basXML set


Pattern for FM RKEV_POST_CB_PLAN_DATA - RKEV POST CB PLAN DATA





CALL FUNCTION 'RKEV_POST_CB_PLAN_DATA' "
  EXPORTING
    i_testrun = 'X'             " flag
*   i_post_delta = 'X'          " flag
*   i_derive = 'X'              " flag
*   i_valuate = 'X'             " flag
*   i_check_characteristics =   " flag
*   i_check_org_units =         " flag
*   i_pllev =                   " rke_pllev
*   i_plpck =                   " rke_plpck
*   it_sel_fields =             " rke_yot_fnam
*   it_seltab =                 " copa_yt_seltab
*   it_value_fields =           " rke_yt_fnam
*   i_trace_item = 0            " int4
  TABLES
    xt_ce0 =                    " cest0
    et_error =                  " rke_ys_post_log
  EXCEPTIONS
    ERROR_OCCURED = 1           "
    .  "  RKEV_POST_CB_PLAN_DATA

ABAP code example for Function Module RKEV_POST_CB_PLAN_DATA





The ABAP code below is a full code listing to execute function module RKEV_POST_CB_PLAN_DATA 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).

DATA:
it_xt_ce0  TYPE STANDARD TABLE OF CEST0,"TABLES PARAM
wa_xt_ce0  LIKE LINE OF it_xt_ce0 ,
it_et_error  TYPE STANDARD TABLE OF RKE_YS_POST_LOG,"TABLES PARAM
wa_et_error  LIKE LINE OF it_et_error .

DATA(ld_i_testrun) = 'Check type of data required'.
DATA(ld_i_post_delta) = 'Check type of data required'.
DATA(ld_i_derive) = 'Check type of data required'.
DATA(ld_i_valuate) = 'Check type of data required'.
DATA(ld_i_check_characteristics) = 'Check type of data required'.
DATA(ld_i_check_org_units) = 'Check type of data required'.
DATA(ld_i_pllev) = 'Check type of data required'.
DATA(ld_i_plpck) = 'Check type of data required'.
DATA(ld_it_sel_fields) = 'Check type of data required'.
DATA(ld_it_seltab) = 'Check type of data required'.
DATA(ld_it_value_fields) = 'Check type of data required'.
DATA(ld_i_trace_item) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_xt_ce0 to it_xt_ce0.

"populate fields of struture and append to itab
append wa_et_error to it_et_error. . CALL FUNCTION 'RKEV_POST_CB_PLAN_DATA' EXPORTING i_testrun = ld_i_testrun * i_post_delta = ld_i_post_delta * i_derive = ld_i_derive * i_valuate = ld_i_valuate * i_check_characteristics = ld_i_check_characteristics * i_check_org_units = ld_i_check_org_units * i_pllev = ld_i_pllev * i_plpck = ld_i_plpck * it_sel_fields = ld_it_sel_fields * it_seltab = ld_it_seltab * it_value_fields = ld_it_value_fields * i_trace_item = ld_i_trace_item TABLES xt_ce0 = it_xt_ce0 et_error = it_et_error EXCEPTIONS ERROR_OCCURED = 1 . " RKEV_POST_CB_PLAN_DATA
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here 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_testrun  TYPE FLAG ,
it_xt_ce0  TYPE STANDARD TABLE OF CEST0 ,
wa_xt_ce0  LIKE LINE OF it_xt_ce0,
ld_i_post_delta  TYPE FLAG ,
it_et_error  TYPE STANDARD TABLE OF RKE_YS_POST_LOG ,
wa_et_error  LIKE LINE OF it_et_error,
ld_i_derive  TYPE FLAG ,
ld_i_valuate  TYPE FLAG ,
ld_i_check_characteristics  TYPE FLAG ,
ld_i_check_org_units  TYPE FLAG ,
ld_i_pllev  TYPE RKE_PLLEV ,
ld_i_plpck  TYPE RKE_PLPCK ,
ld_it_sel_fields  TYPE RKE_YOT_FNAM ,
ld_it_seltab  TYPE COPA_YT_SELTAB ,
ld_it_value_fields  TYPE RKE_YT_FNAM ,
ld_i_trace_item  TYPE INT4 .

ld_i_testrun = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_xt_ce0 to it_xt_ce0.
ld_i_post_delta = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_error to it_et_error.
ld_i_derive = 'Check type of data required'.
ld_i_valuate = 'Check type of data required'.
ld_i_check_characteristics = 'Check type of data required'.
ld_i_check_org_units = 'Check type of data required'.
ld_i_pllev = 'Check type of data required'.
ld_i_plpck = 'Check type of data required'.
ld_it_sel_fields = 'Check type of data required'.
ld_it_seltab = 'Check type of data required'.
ld_it_value_fields = 'Check type of data required'.
ld_i_trace_item = 'Check type of data required'.

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 RKEV_POST_CB_PLAN_DATA or its description.