BBP_FOLLOW_ON_AFTER_CC_REPLI SAP Function module - For creating obj links from replication response

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

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

Pattern for FM BBP_FOLLOW_ON_AFTER_CC_REPLI - BBP FOLLOW ON AFTER CC REPLI

CALL FUNCTION 'BBP_FOLLOW_ON_AFTER_CC_REPLI' "For creating obj links from replication response
  EXPORTING
    it_ctr_item_map =           " bbpt_ctr_be_item_map
*   it_messages =               " bbp_pdt_messages  Fehlermeldungen zu einer PD-Methode
    iv_core_key =               " string
*   it_srv_map =                " bbpt_srv_item_info
*   iv_do_commit_work = 'X'     " boolean       Boolean Variable (X=True, -=False, Space=Unknown)
  EXCEPTIONS
    /SAPSRM/CX_PDO_CTR_REPLI_FAIL = 1  "        Exception class for replication of contract
    .  "  BBP_FOLLOW_ON_AFTER_CC_REPLI

ABAP code example for Function Module BBP_FOLLOW_ON_AFTER_CC_REPLI

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

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

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

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

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

CALL FUNCTION 'BBP_FOLLOW_ON_AFTER_CC_REPLI'
  EXPORTING
    it_ctr_item_map =            ld_it_ctr_item_map
*   it_messages =                ld_it_messages
    iv_core_key =                ld_iv_core_key
*   it_srv_map =                 ld_it_srv_map
*   iv_do_commit_work =          ld_iv_do_commit_work
  EXCEPTIONS
    /SAPSRM/CX_PDO_CTR_REPLI_FAIL =    1
    .  "  BBP_FOLLOW_ON_AFTER_CC_REPLI

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_it_ctr_item_map
 
 TYPE BBPT_CTR_BE_ITEM_MAP ,
ld_it_messages
 
 TYPE BBP_PDT_MESSAGES ,
ld_iv_core_key
 
 TYPE STRING ,
ld_it_srv_map
 
 TYPE BBPT_SRV_ITEM_INFO ,
ld_iv_do_commit_work
 
 TYPE BOOLEAN .


ld_it_ctr_item_map = 'Check type of data required'.
ld_it_messages = 'Check type of data required'.
ld_iv_core_key = 'Check type of data required'.
ld_it_srv_map = 'Check type of data required'.
ld_iv_do_commit_work = 'Check type of data required'.