SAP BBP_OUTPUT_INV_PREVIEW_ADB Function Module for Druckvorschau Rechnung
BBP_OUTPUT_INV_PREVIEW_ADB is a standard bbp output inv preview 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 Druckvorschau Rechnung 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 inv preview adb FM, simply by entering the name BBP_OUTPUT_INV_PREVIEW_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_INV_PREVIEW_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_INV_PREVIEW_ADB'"Druckvorschau Rechnung.
EXPORTING
IV_GUID = "
* IV_SMARTFORM = "
* IV_LOCAL = '' "
* IS_PARAMETERS = "
* IV_SCENARIO = "
IMPORTING
ES_PDF = "
EV_DOC_DESCR = "
EXCEPTIONS
NO_SMARTFORM = 1 NO_MEDIUM = 10 NO_MEDIA_MAP = 11 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_INV_PREVIEW_ADB
IV_GUID -
Data type: BBP_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_SMARTFORM -
Data type: TDSFNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOCAL -
Data type: XFELDDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_PARAMETERS -
Data type: BBPS_MESSAGE_PARAMETERSOptional: Yes
Call by Reference: Yes
IV_SCENARIO -
Data type: BBP_PREVIEW_SMART_SCENARIOOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_OUTPUT_INV_PREVIEW_ADB
ES_PDF -
Data type: XSTRINGOptional: No
Call by Reference: Yes
EV_DOC_DESCR -
Data type: SO_OBJ_DESOptional: 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: Yes
NO_MEDIA_MAP -
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: Yes
NO_MEDIACOLL -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_OUTPUT_INV_PREVIEW_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_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_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_no_printer | TYPE BBP_PREVIEW_SMART_SCENARIO, " | |||
| lv_no_triggertypecoll | TYPE BBP_PREVIEW_SMART_SCENARIO, " | |||
| lv_no_mediacoll | TYPE BBP_PREVIEW_SMART_SCENARIO. " |
| CALL FUNCTION 'BBP_OUTPUT_INV_PREVIEW_ADB' "Druckvorschau Rechnung |
| 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 | |
| IMPORTING | ||
| ES_PDF | = lv_es_pdf | |
| EV_DOC_DESCR | = lv_ev_doc_descr | |
| EXCEPTIONS | ||
| NO_SMARTFORM = 1 | ||
| NO_MEDIUM = 10 | ||
| NO_MEDIA_MAP = 11 | ||
| 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_INV_PREVIEW_ADB | ||
ABAP code using 7.40 inline data declarations to call FM BBP_OUTPUT_INV_PREVIEW_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_iv_local) | = ''. | |||
Search for further information about these or an SAP related objects