SAP BBP_PARTNER_SEND Function Module for









BBP_PARTNER_SEND is a standard bbp partner send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bbp partner send FM, simply by entering the name BBP_PARTNER_SEND into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_BD_SIMPLE_META_CALL
Program Name: SAPLBBP_BD_SIMPLE_META_CALL
Main Program: SAPLBBP_BD_SIMPLE_META_CALL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 2



Function BBP_PARTNER_SEND pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BBP_PARTNER_SEND'"
EXPORTING
IV_PARTNER = "
* IV_METHOD = 'U' "
* IV_COMPANY = "
* IS_DESTINATION = "
* IV_COMMIT = ' ' "

TABLES
* ET_MESSAGES = "
* ET_CONTROL_RECORD = "
.



IMPORTING Parameters details for BBP_PARTNER_SEND

IV_PARTNER -

Data type: BU_PARTNER
Optional: No
Call by Reference: No ( called with pass by value option)

IV_METHOD -

Data type: CHAR1
Default: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_COMPANY -

Data type: BU_PARTNER
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_DESTINATION -

Data type: BBP_BACKEND_DEST
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_COMMIT -

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BBP_PARTNER_SEND

ET_MESSAGES -

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

ET_CONTROL_RECORD -

Data type: BBP_CONTROL_RECORD
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BBP_PARTNER_SEND Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_iv_partner  TYPE BU_PARTNER, "   
lt_et_messages  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_method  TYPE CHAR1, "   'U'
lt_et_control_record  TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, "   
lv_iv_company  TYPE BU_PARTNER, "   
lv_is_destination  TYPE BBP_BACKEND_DEST, "   
lv_iv_commit  TYPE XFELD. "   ' '

  CALL FUNCTION 'BBP_PARTNER_SEND'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_METHOD = lv_iv_method
         IV_COMPANY = lv_iv_company
         IS_DESTINATION = lv_is_destination
         IV_COMMIT = lv_iv_commit
    TABLES
         ET_MESSAGES = lt_et_messages
         ET_CONTROL_RECORD = lt_et_control_record
. " BBP_PARTNER_SEND




ABAP code using 7.40 inline data declarations to call FM BBP_PARTNER_SEND

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
DATA(ld_iv_method) = 'U'.
 
 
 
 
DATA(ld_iv_commit) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!