BPAR_M_COMM_TO_FI_TRANSFER SAP Function module

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

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

Pattern for FM BPAR_M_COMM_TO_FI_TRANSFER - BPAR M COMM TO FI TRANSFER

CALL FUNCTION 'BPAR_M_COMM_TO_FI_TRANSFER' "
  EXPORTING
    i_bpdadr =                  " bpdadr
    i_bpdadref =                " bpdadref
*   is_bapiaddr1 =              " bapiaddr1
*   is_bapiaddr2 =              " bapiaddr2
*   is_kna1 =                   " kna1
*   iv_customer =               " kunnr
  IMPORTING
    es_bapiaddr1 =              " bapiaddr1
    es_bapiaddr2 =              " bapiaddr2
    es_kna1 =                   " kna1
    .  "  BPAR_M_COMM_TO_FI_TRANSFER

ABAP code example for Function Module BPAR_M_COMM_TO_FI_TRANSFER

The ABAP code below is a full code listing to execute function module BPAR_M_COMM_TO_FI_TRANSFER 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_es_bapiaddr1  
 
 TYPE BAPIADDR1
,
ld_es_bapiaddr2  
 
 TYPE BAPIADDR2
,
ld_es_kna1  
 
 TYPE KNA1
.


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

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

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

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

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

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

CALL FUNCTION 'BPAR_M_COMM_TO_FI_TRANSFER'
  EXPORTING
    i_bpdadr =                   ld_i_bpdadr
    i_bpdadref =                 ld_i_bpdadref
*   is_bapiaddr1 =               ld_is_bapiaddr1
*   is_bapiaddr2 =               ld_is_bapiaddr2
*   is_kna1 =                    ld_is_kna1
*   iv_customer =                ld_iv_customer
  IMPORTING
    es_bapiaddr1 =               ld_es_bapiaddr1
    es_bapiaddr2 =               ld_es_bapiaddr2
    es_kna1 =                    ld_es_kna1
    .  "  BPAR_M_COMM_TO_FI_TRANSFER

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_es_bapiaddr1
 
 TYPE BAPIADDR1 ,
ld_i_bpdadr
 
 TYPE BPDADR ,
ld_es_bapiaddr2
 
 TYPE BAPIADDR2 ,
ld_i_bpdadref
 
 TYPE BPDADREF ,
ld_es_kna1
 
 TYPE KNA1 ,
ld_is_bapiaddr1
 
 TYPE BAPIADDR1 ,
ld_is_bapiaddr2
 
 TYPE BAPIADDR2 ,
ld_is_kna1
 
 TYPE KNA1 ,
ld_iv_customer
 
 TYPE KUNNR .


ld_i_bpdadr = 'Check type of data required'.
ld_i_bpdadref = 'Check type of data required'.
ld_is_bapiaddr1 = 'Check type of data required'.
ld_is_bapiaddr2 = 'Check type of data required'.
ld_is_kna1 = 'Check type of data required'.
ld_iv_customer = 'Check type of data required'.