SAP BBP_OUTPUT_BID_PREVIEW_SMART Function Module for









BBP_OUTPUT_BID_PREVIEW_SMART is a standard bbp output bid preview smart 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 output bid preview smart FM, simply by entering the name BBP_OUTPUT_BID_PREVIEW_SMART into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_OUTPUT_BID_PREVIEW_SMART 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_PREVIEW_SMART'"
EXPORTING
IV_GUID = "
* IV_SMARTFORM = "
* IV_LOCAL = '' "
* IS_PARAMETERS = "
* IV_SCENARIO = "
* IV_PARTNER_NO = "

IMPORTING
ES_PDF = "
EV_DOC_DESCR = "

EXCEPTIONS
NO_SMARTFORM = 1 NO_MEDIUM = 10 NO_MEDIA_MAP = 11 ARCHIV_ERROR = 12 NO_PARTNER = 2 NO_DATA = 3 PSF_ERROR = 4 OTF_ERROR = 5 ITS_ERROR = 6 NO_PRINTER = 7 NO_TRIGGERTYPECOLL = 8 NO_MEDIACOLL = 9
.



IMPORTING Parameters details for BBP_OUTPUT_BID_PREVIEW_SMART

IV_GUID -

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

IV_SMARTFORM -

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

IV_LOCAL -

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

IS_PARAMETERS -

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

IV_SCENARIO -

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

IV_PARTNER_NO -

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

EXPORTING Parameters details for BBP_OUTPUT_BID_PREVIEW_SMART

ES_PDF -

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

EV_DOC_DESCR -

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

EXCEPTIONS details

NO_SMARTFORM -

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

NO_MEDIUM -

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

NO_MEDIA_MAP -

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

ARCHIV_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_PARTNER -

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

NO_DATA -

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

PSF_ERROR -

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

OTF_ERROR -

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

ITS_ERROR -

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

NO_PRINTER -

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

NO_TRIGGERTYPECOLL -

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

NO_MEDIACOLL -

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

Copy and paste ABAP code example for BBP_OUTPUT_BID_PREVIEW_SMART 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_es_pdf  TYPE XSTRING, "   
lv_iv_guid  TYPE BBP_GUID, "   
lv_no_smartform  TYPE BBP_GUID, "   
lv_no_medium  TYPE BBP_GUID, "   
lv_no_media_map  TYPE BBP_GUID, "   
lv_archiv_error  TYPE BBP_GUID, "   
lv_no_partner  TYPE BBP_GUID, "   
lv_ev_doc_descr  TYPE SO_OBJ_DES, "   
lv_iv_smartform  TYPE TDSFNAME, "   
lv_no_data  TYPE TDSFNAME, "   
lv_iv_local  TYPE XFELD, "   ''
lv_psf_error  TYPE XFELD, "   
lv_is_parameters  TYPE BBPS_MESSAGE_PARAMETERS, "   
lv_otf_error  TYPE BBPS_MESSAGE_PARAMETERS, "   
lv_iv_scenario  TYPE BBP_PREVIEW_SMART_SCENARIO, "   
lv_its_error  TYPE BBP_PREVIEW_SMART_SCENARIO, "   
lv_iv_partner_no  TYPE CRMT_PARTNER_NO, "   
lv_no_printer  TYPE CRMT_PARTNER_NO, "   
lv_no_triggertypecoll  TYPE CRMT_PARTNER_NO, "   
lv_no_mediacoll  TYPE CRMT_PARTNER_NO. "   

  CALL FUNCTION 'BBP_OUTPUT_BID_PREVIEW_SMART'  "
    EXPORTING
         IV_GUID = lv_iv_guid
         IV_SMARTFORM = lv_iv_smartform
         IV_LOCAL = lv_iv_local
         IS_PARAMETERS = lv_is_parameters
         IV_SCENARIO = lv_iv_scenario
         IV_PARTNER_NO = lv_iv_partner_no
    IMPORTING
         ES_PDF = lv_es_pdf
         EV_DOC_DESCR = lv_ev_doc_descr
    EXCEPTIONS
        NO_SMARTFORM = 1
        NO_MEDIUM = 10
        NO_MEDIA_MAP = 11
        ARCHIV_ERROR = 12
        NO_PARTNER = 2
        NO_DATA = 3
        PSF_ERROR = 4
        OTF_ERROR = 5
        ITS_ERROR = 6
        NO_PRINTER = 7
        NO_TRIGGERTYPECOLL = 8
        NO_MEDIACOLL = 9
. " BBP_OUTPUT_BID_PREVIEW_SMART




ABAP code using 7.40 inline data declarations to call FM BBP_OUTPUT_BID_PREVIEW_SMART

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


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!