VBDBDM_DATA_COPY_REF_PO_TO_IM SAP Function module

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

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

Pattern for FM VBDBDM_DATA_COPY_REF_PO_TO_IM - VBDBDM DATA COPY REF PO TO IM

CALL FUNCTION 'VBDBDM_DATA_COPY_REF_PO_TO_IM' "
  EXPORTING
    i_key =                     " migo_global_counter
    i_matnr =                   " matnr
    i_werks =                   " werks_d
    i_ebeln_ref =               " ebeln
    i_ebelp_ref =               " ebelp
*   is_docubatch_com =          " docubatch_com
  IMPORTING
    e_docubatch_control =       " docubatch_control
    e_docubatch_charg =         " docubatch_charg
    e_mult_entries =            " xfeld
    .  "  VBDBDM_DATA_COPY_REF_PO_TO_IM

ABAP code example for Function Module VBDBDM_DATA_COPY_REF_PO_TO_IM

The ABAP code below is a full code listing to execute function module VBDBDM_DATA_COPY_REF_PO_TO_IM 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_e_docubatch_control  
 
 TYPE DOCUBATCH_CONTROL
,
ld_e_docubatch_charg  
 
 TYPE DOCUBATCH_CHARG
,
ld_e_mult_entries  
 
 TYPE XFELD
.


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

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

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

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

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

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

CALL FUNCTION 'VBDBDM_DATA_COPY_REF_PO_TO_IM'
  EXPORTING
    i_key =                      ld_i_key
    i_matnr =                    ld_i_matnr
    i_werks =                    ld_i_werks
    i_ebeln_ref =                ld_i_ebeln_ref
    i_ebelp_ref =                ld_i_ebelp_ref
*   is_docubatch_com =           ld_is_docubatch_com
  IMPORTING
    e_docubatch_control =        ld_e_docubatch_control
    e_docubatch_charg =          ld_e_docubatch_charg
    e_mult_entries =             ld_e_mult_entries
    .  "  VBDBDM_DATA_COPY_REF_PO_TO_IM

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_e_docubatch_control
 
 TYPE DOCUBATCH_CONTROL ,
ld_i_key
 
 TYPE MIGO_GLOBAL_COUNTER ,
ld_e_docubatch_charg
 
 TYPE DOCUBATCH_CHARG ,
ld_i_matnr
 
 TYPE MATNR ,
ld_e_mult_entries
 
 TYPE XFELD ,
ld_i_werks
 
 TYPE WERKS_D ,
ld_i_ebeln_ref
 
 TYPE EBELN ,
ld_i_ebelp_ref
 
 TYPE EBELP ,
ld_is_docubatch_com
 
 TYPE DOCUBATCH_COM .


ld_i_key = 'Check type of data required'.
ld_i_matnr = 'Check type of data required'.
ld_i_werks = 'Check type of data required'.
ld_i_ebeln_ref = 'Check type of data required'.
ld_i_ebelp_ref = 'Check type of data required'.
ld_is_docubatch_com = 'Check type of data required'.