SAP BBP_OUTPUT_BID_DOC_SEND_ADB Function Module for send completetion for Purchase Order









BBP_OUTPUT_BID_DOC_SEND_ADB is a standard bbp output bid doc send adb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for send completetion for Purchase Order processing and below is the pattern details for this FM, 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 output bid doc send adb FM, simply by entering the name BBP_OUTPUT_BID_DOC_SEND_ADB into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_OUTPUT_BID_DOC_SEND_ADB 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_OUTPUT_BID_DOC_SEND_ADB'"send completetion for Purchase Order
EXPORTING
IO_CONTEXT = "
IP_PROTOCOL = "
* IP_NO_PROTOCOL = 'X' "
IO_SEND = "
FLT_VAL = "

EXCEPTIONS
NO_PRINTER = 1
.



IMPORTING Parameters details for BBP_OUTPUT_BID_DOC_SEND_ADB

IO_CONTEXT -

Data type: CL_CONTEXT_PPF
Optional: No
Call by Reference: Yes

IP_PROTOCOL -

Data type: BALLOGHNDL
Optional: No
Call by Reference: Yes

IP_NO_PROTOCOL -

Data type: BOOLE_D
Default: 'X'
Optional: No
Call by Reference: Yes

IO_SEND -

Data type: CL_BCS
Optional: No
Call by Reference: Yes

FLT_VAL -

Data type: PPFSCONACT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_PRINTER - No Printer

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_OUTPUT_BID_DOC_SEND_ADB 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_io_context  TYPE CL_CONTEXT_PPF, "   
lv_no_printer  TYPE CL_CONTEXT_PPF, "   
lv_ip_protocol  TYPE BALLOGHNDL, "   
lv_ip_no_protocol  TYPE BOOLE_D, "   'X'
lv_io_send  TYPE CL_BCS, "   
lv_flt_val  TYPE PPFSCONACT. "   

  CALL FUNCTION 'BBP_OUTPUT_BID_DOC_SEND_ADB'  "send completetion for Purchase Order
    EXPORTING
         IO_CONTEXT = lv_io_context
         IP_PROTOCOL = lv_ip_protocol
         IP_NO_PROTOCOL = lv_ip_no_protocol
         IO_SEND = lv_io_send
         FLT_VAL = lv_flt_val
    EXCEPTIONS
        NO_PRINTER = 1
. " BBP_OUTPUT_BID_DOC_SEND_ADB




ABAP code using 7.40 inline data declarations to call FM BBP_OUTPUT_BID_DOC_SEND_ADB

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_ip_no_protocol) = 'X'.
 
 
 


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!