BBP_PD_CTR_TRANSFER SAP Function module

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

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

Pattern for FM BBP_PD_CTR_TRANSFER - BBP PD CTR TRANSFER

CALL FUNCTION 'BBP_PD_CTR_TRANSFER' "
  EXPORTING
    iv_header_guid =            " bbp_guid
    iv_save_db = SPACE          " xfeld
*   iv_be_pur_org_partner_id =   " bu_partner
*   iv_logical_system =         " logsys
*   iv_object_id =              " crmd_orderadm_h-object_id
*   iv_dist_set_guid =          " bbp_guid
*   iv_porg_partner_id =        " bu_partner
*   iv_location_id =            " bu_partner
*   iv_be_objtype =             " bbp_trgt_objtyp
*   iv_unlock_ind =             " xfeld
*   iv_reconciliation_requested =   " xfeld
  EXCEPTIONS
    NO_SYSTEM_FOUND = 1         "
    .  "  BBP_PD_CTR_TRANSFER

ABAP code example for Function Module BBP_PD_CTR_TRANSFER

The ABAP code below is a full code listing to execute function module BBP_PD_CTR_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_iv_header_guid) = 'Check type of data required'.

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

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

DATA(ld_iv_logical_system) = 'some text here'.
 

SELECT single OBJECT_ID 
  FROM CRMD_ORDERADM_H 
  INTO @DATA(ld_iv_object_id).


DATA(ld_iv_dist_set_guid) = 'some text here'.

DATA(ld_iv_porg_partner_id) = 'some text here'.

DATA(ld_iv_location_id) = 'some text here'.

DATA(ld_iv_be_objtype) = 'some text here'.

DATA(ld_iv_unlock_ind) = 'some text here'.

DATA(ld_iv_reconciliation_requested) = 'some text here'.
.

CALL FUNCTION 'BBP_PD_CTR_TRANSFER'
  EXPORTING
    iv_header_guid =             ld_iv_header_guid
    iv_save_db =                 ld_iv_save_db
*   iv_be_pur_org_partner_id =    ld_iv_be_pur_org_partner_id
*   iv_logical_system =          ld_iv_logical_system
*   iv_object_id =               ld_iv_object_id
*   iv_dist_set_guid =           ld_iv_dist_set_guid
*   iv_porg_partner_id =         ld_iv_porg_partner_id
*   iv_location_id =             ld_iv_location_id
*   iv_be_objtype =              ld_iv_be_objtype
*   iv_unlock_ind =              ld_iv_unlock_ind
*   iv_reconciliation_requested =    ld_iv_reconciliation_requested
  EXCEPTIONS
    NO_SYSTEM_FOUND =            1
    .  "  BBP_PD_CTR_TRANSFER

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_iv_header_guid
 
 TYPE BBP_GUID ,
ld_iv_save_db
 
 TYPE XFELD ,
ld_iv_be_pur_org_partner_id
 
 TYPE BU_PARTNER ,
ld_iv_logical_system
 
 TYPE LOGSYS ,
ld_iv_object_id
 
 TYPE CRMD_ORDERADM_H-OBJECT_ID ,
ld_iv_dist_set_guid
 
 TYPE BBP_GUID ,
ld_iv_porg_partner_id
 
 TYPE BU_PARTNER ,
ld_iv_location_id
 
 TYPE BU_PARTNER ,
ld_iv_be_objtype
 
 TYPE BBP_TRGT_OBJTYP ,
ld_iv_unlock_ind
 
 TYPE XFELD ,
ld_iv_reconciliation_requested
 
 TYPE XFELD .


ld_iv_header_guid = 'some text here'.
ld_iv_save_db = 'some text here'.
ld_iv_be_pur_org_partner_id = 'some text here'.
ld_iv_logical_system = 'some text here'.

SELECT single OBJECT_ID 
  FROM CRMD_ORDERADM_H 
  INTO ld_iv_object_id.

ld_iv_dist_set_guid = 'some text here'.
ld_iv_porg_partner_id = 'some text here'.
ld_iv_location_id = 'some text here'.
ld_iv_be_objtype = 'some text here'.
ld_iv_unlock_ind = 'some text here'.
ld_iv_reconciliation_requested = 'some text here'.