CO2H_NETWORK_CHANGE_STRU SAP Function module

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

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

Pattern for FM CO2H_NETWORK_CHANGE_STRU - CO2H NETWORK CHANGE STRU

CALL FUNCTION 'CO2H_NETWORK_CHANGE_STRU' "
  EXPORTING
    i_aufnr =                   " caufvd-aufnr
*   i_xnot_sap_aufnr = SPACE    " co1m_xpar
*   i_version_destination =     " vskopf-vsnmr
    i_caufvd_new =              " caufvd
*   i_caufvd_upd =              " caufvd_update
*   i_without_upd_stru =        " rc27x-flg_sel
  EXCEPTIONS
    ERROR_OCCURED = 1           "
    .  "  CO2H_NETWORK_CHANGE_STRU

ABAP code example for Function Module CO2H_NETWORK_CHANGE_STRU

The ABAP code below is a full code listing to execute function module CO2H_NETWORK_CHANGE_STRU 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_i_aufnr) = some text here

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

SELECT single VSNMR 
  FROM VSKOPF 
  INTO @DATA(ld_i_version_destination).


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

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


DATA(ld_i_without_upd_stru) = some text here
.

CALL FUNCTION 'CO2H_NETWORK_CHANGE_STRU'
  EXPORTING
    i_aufnr =                    ld_i_aufnr
*   i_xnot_sap_aufnr =           ld_i_xnot_sap_aufnr
*   i_version_destination =      ld_i_version_destination
    i_caufvd_new =               ld_i_caufvd_new
*   i_caufvd_upd =               ld_i_caufvd_upd
*   i_without_upd_stru =         ld_i_without_upd_stru
  EXCEPTIONS
    ERROR_OCCURED =              1
    .  "  CO2H_NETWORK_CHANGE_STRU

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_aufnr
 
 TYPE CAUFVD-AUFNR ,
ld_i_xnot_sap_aufnr
 
 TYPE CO1M_XPAR ,
ld_i_version_destination
 
 TYPE VSKOPF-VSNMR ,
ld_i_caufvd_new
 
 TYPE CAUFVD ,
ld_i_caufvd_upd
 
 TYPE CAUFVD_UPDATE ,
ld_i_without_upd_stru
 
 TYPE RC27X-FLG_SEL .



ld_i_aufnr = some text here
ld_i_xnot_sap_aufnr = 'Check type of data required'.

SELECT single VSNMR 
  FROM VSKOPF 
  INTO ld_i_version_destination.

ld_i_caufvd_new = 'Check type of data required'.
ld_i_caufvd_upd = 'Check type of data required'.

ld_i_without_upd_stru = some text here