BUPA_TEMPLATE_CHANGE SAP Function module

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

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

Pattern for FM BUPA_TEMPLATE_CHANGE - BUPA TEMPLATE CHANGE

CALL FUNCTION 'BUPA_TEMPLATE_CHANGE' "
  EXPORTING
    iv_partnerguid =            " bu_partner_guid
    iv_templ_type =             " bu_templ_type
    is_data =                   " bus_template_data
    is_datax = 'X'              " bus_template_datax
*   iv_x_save = 'X'             " bapi4001_1-save_addr
* TABLES
*   et_return =                 " bapiret2
    .  "  BUPA_TEMPLATE_CHANGE

ABAP code example for Function Module BUPA_TEMPLATE_CHANGE

The ABAP code below is a full code listing to execute function module BUPA_TEMPLATE_CHANGE 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_et_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_et_return
 
 LIKE LINE OF it_et_return
.


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

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

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

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


DATA(ld_iv_x_save) = some text here
 

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
.

CALL FUNCTION 'BUPA_TEMPLATE_CHANGE'
  EXPORTING
    iv_partnerguid =             ld_iv_partnerguid
    iv_templ_type =              ld_iv_templ_type
    is_data =                    ld_is_data
    is_datax =                   ld_is_datax
*   iv_x_save =                  ld_iv_x_save
* TABLES
*   et_return =                  it_et_return
    .  "  BUPA_TEMPLATE_CHANGE

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_iv_partnerguid
 
 TYPE BU_PARTNER_GUID ,
it_et_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_et_return
 
 LIKE LINE OF it_et_return,
ld_iv_templ_type
 
 TYPE BU_TEMPL_TYPE ,
ld_is_data
 
 TYPE BUS_TEMPLATE_DATA ,
ld_is_datax
 
 TYPE BUS_TEMPLATE_DATAX ,
ld_iv_x_save
 
 TYPE BAPI4001_1-SAVE_ADDR .


ld_iv_partnerguid = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
ld_iv_templ_type = 'Check type of data required'.
ld_is_data = 'Check type of data required'.
ld_is_datax = 'Check type of data required'.

ld_iv_x_save = some text here