SAP BUPA_INTERFACE_GET_FUS Function Module for
BUPA_INTERFACE_GET_FUS is a standard bupa interface get fus 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 bupa interface get fus FM, simply by entering the name BUPA_INTERFACE_GET_FUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUPA_INTERFACE_SERVICE
Program Name: SAPLBUPA_INTERFACE_SERVICE
Main Program: SAPLBUPA_INTERFACE_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUPA_INTERFACE_GET_FUS 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 'BUPA_INTERFACE_GET_FUS'".
EXPORTING
* IV_OBJAP = 'BUPA' "Data Exchange: Application Object
IV_ZTPKT = "Data Exchange: Event
TABLES
ET_FU_LIST = "CBP: Function Module Name
IMPORTING Parameters details for BUPA_INTERFACE_GET_FUS
IV_OBJAP - Data Exchange: Application Object
Data type: CRMT_BU_OBJAPDefault: 'BUPA'
Optional: No
Call by Reference: Yes
IV_ZTPKT - Data Exchange: Event
Data type: CRMT_BU_ZTPKTOptional: No
Call by Reference: Yes
TABLES Parameters details for BUPA_INTERFACE_GET_FUS
ET_FU_LIST - CBP: Function Module Name
Data type: BUS0FNAMEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BUPA_INTERFACE_GET_FUS 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_objap | TYPE CRMT_BU_OBJAP, " 'BUPA' | |||
| lt_et_fu_list | TYPE STANDARD TABLE OF BUS0FNAME, " | |||
| lv_iv_ztpkt | TYPE CRMT_BU_ZTPKT. " |
|   CALL FUNCTION 'BUPA_INTERFACE_GET_FUS' " |
| EXPORTING | ||
| IV_OBJAP | = lv_iv_objap | |
| IV_ZTPKT | = lv_iv_ztpkt | |
| TABLES | ||
| ET_FU_LIST | = lt_et_fu_list | |
| . " BUPA_INTERFACE_GET_FUS | ||
ABAP code using 7.40 inline data declarations to call FM BUPA_INTERFACE_GET_FUS
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_objap) | = 'BUPA'. | |||
Search for further information about these or an SAP related objects