SAP BBP_WS_IMPORT_BUPA_DATA Function Module for
BBP_WS_IMPORT_BUPA_DATA is a standard bbp ws import bupa data 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 ws import bupa data FM, simply by entering the name BBP_WS_IMPORT_BUPA_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_WS_API
Program Name: SAPLBBP_WS_API
Main Program: SAPLBBP_WS_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_WS_IMPORT_BUPA_DATA 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_WS_IMPORT_BUPA_DATA'".
EXPORTING
* IV_WEBSERVICE_ID = "
* IO_BSP_RUNTIME = "
* IO_HTTP_SERVER = "
* IV_NO_BUPA_CREATE = "
* IV_USER = "
* IV_PURCH_ORG = "
* IV_BU_ROLE = "
IMPORTING
EV_VENDOR_ROOT_NODE = "
TABLES
* IT_FORM_FIELDS = "
* ET_BUPA_DATA = "
* ET_OPI_DATA = "
* ET_MESSAGES = "
EXCEPTIONS
WS_NOT_FOUND = 1
IMPORTING Parameters details for BBP_WS_IMPORT_BUPA_DATA
IV_WEBSERVICE_ID -
Data type: BBP_WS_SERVICE_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IO_BSP_RUNTIME -
Data type: IF_BSP_RUNTIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IO_HTTP_SERVER -
Data type: IF_HTTP_SERVEROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_BUPA_CREATE -
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_USER -
Data type: SY-UNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PURCH_ORG -
Data type: BBP_PROC_ORGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_BU_ROLE -
Data type: BU_ROLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_WS_IMPORT_BUPA_DATA
EV_VENDOR_ROOT_NODE -
Data type: BBP_CAT_VENDOR_ROOT_NODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_WS_IMPORT_BUPA_DATA
IT_FORM_FIELDS -
Data type: SAVWCTXTOptional: Yes
Call by Reference: Yes
ET_BUPA_DATA -
Data type: BBPT_OPI_BUPAOptional: Yes
Call by Reference: Yes
ET_OPI_DATA -
Data type: BBP_WS_OPI_ITEM_SOptional: Yes
Call by Reference: Yes
ET_MESSAGES -
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
WS_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_WS_IMPORT_BUPA_DATA 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_ws_not_found | TYPE STRING, " | |||
| lt_it_form_fields | TYPE STANDARD TABLE OF SAVWCTXT, " | |||
| lv_iv_webservice_id | TYPE BBP_WS_SERVICE_ID, " | |||
| lv_ev_vendor_root_node | TYPE BBP_CAT_VENDOR_ROOT_NODE, " | |||
| lt_et_bupa_data | TYPE STANDARD TABLE OF BBPT_OPI_BUPA, " | |||
| lv_io_bsp_runtime | TYPE IF_BSP_RUNTIME, " | |||
| lt_et_opi_data | TYPE STANDARD TABLE OF BBP_WS_OPI_ITEM_S, " | |||
| lv_io_http_server | TYPE IF_HTTP_SERVER, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_iv_no_bupa_create | TYPE XFELD, " | |||
| lv_iv_user | TYPE SY-UNAME, " | |||
| lv_iv_purch_org | TYPE BBP_PROC_ORG, " | |||
| lv_iv_bu_role | TYPE BU_ROLE. " |
|   CALL FUNCTION 'BBP_WS_IMPORT_BUPA_DATA' " |
| EXPORTING | ||
| IV_WEBSERVICE_ID | = lv_iv_webservice_id | |
| IO_BSP_RUNTIME | = lv_io_bsp_runtime | |
| IO_HTTP_SERVER | = lv_io_http_server | |
| IV_NO_BUPA_CREATE | = lv_iv_no_bupa_create | |
| IV_USER | = lv_iv_user | |
| IV_PURCH_ORG | = lv_iv_purch_org | |
| IV_BU_ROLE | = lv_iv_bu_role | |
| IMPORTING | ||
| EV_VENDOR_ROOT_NODE | = lv_ev_vendor_root_node | |
| TABLES | ||
| IT_FORM_FIELDS | = lt_it_form_fields | |
| ET_BUPA_DATA | = lt_et_bupa_data | |
| ET_OPI_DATA | = lt_et_opi_data | |
| ET_MESSAGES | = lt_et_messages | |
| EXCEPTIONS | ||
| WS_NOT_FOUND = 1 | ||
| . " BBP_WS_IMPORT_BUPA_DATA | ||
ABAP code using 7.40 inline data declarations to call FM BBP_WS_IMPORT_BUPA_DATA
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.| "SELECT single UNAME FROM SY INTO @DATA(ld_iv_user). | ||||
Search for further information about these or an SAP related objects