CNECP_MAINTAIN SAP Function module - RFC for maintaining ECP for a project

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

Associated Function Group: ECP_EHP3
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CNECP_MAINTAIN - CNECP MAINTAIN

CALL FUNCTION 'CNECP_MAINTAIN' "RFC for maintaining ECP for a project
  EXPORTING
    i_proj_id =                 " ps_pspid      Project Definition
    i_version =                 " versn         Version
*   i_cost_variant =            " ck_klvar      Costing Variant
*   i_wbs_costlines =           " tty_proj_element_ck_items  wbs ecp cost
*   i_net_act_costlines =       " tty_network_ck_items  network ecp cost
*   i_vsnmr =                   " vsproj_cn-vsnmr  Simulation's version
  IMPORTING
    messages =                  " bapiret2_t    Return Parameter
    .  "  CNECP_MAINTAIN

ABAP code example for Function Module CNECP_MAINTAIN

The ABAP code below is a full code listing to execute function module CNECP_MAINTAIN 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:
ld_messages  
 
 TYPE BAPIRET2_T
.


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

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

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

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

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

SELECT single VSNMR 
  FROM VSPROJ_CN 
  INTO @DATA(ld_i_vsnmr).

.

CALL FUNCTION 'CNECP_MAINTAIN'
  EXPORTING
    i_proj_id =                  ld_i_proj_id
    i_version =                  ld_i_version
*   i_cost_variant =             ld_i_cost_variant
*   i_wbs_costlines =            ld_i_wbs_costlines
*   i_net_act_costlines =        ld_i_net_act_costlines
*   i_vsnmr =                    ld_i_vsnmr
  IMPORTING
    messages =                   ld_messages
    .  "  CNECP_MAINTAIN

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_messages
 
 TYPE BAPIRET2_T ,
ld_i_proj_id
 
 TYPE PS_PSPID ,
ld_i_version
 
 TYPE VERSN ,
ld_i_cost_variant
 
 TYPE CK_KLVAR ,
ld_i_wbs_costlines
 
 TYPE TTY_PROJ_ELEMENT_CK_ITEMS ,
ld_i_net_act_costlines
 
 TYPE TTY_NETWORK_CK_ITEMS ,
ld_i_vsnmr
 
 TYPE VSPROJ_CN-VSNMR .


ld_i_proj_id = 'Check type of data required'.
ld_i_version = 'Check type of data required'.
ld_i_cost_variant = 'Check type of data required'.
ld_i_wbs_costlines = 'Check type of data required'.
ld_i_net_act_costlines = 'Check type of data required'.

SELECT single VSNMR 
  FROM VSPROJ_CN 
  INTO ld_i_vsnmr.

SAP Documentation for FM CNECP_MAINTAIN