SAP ABA_BUPA_CALL_PROXY Function Module for









ABA_BUPA_CALL_PROXY is a standard aba bupa call proxy 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 aba bupa call proxy FM, simply by entering the name ABA_BUPA_CALL_PROXY into the relevant SAP transaction such as SE37 or SE38.

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



Function ABA_BUPA_CALL_PROXY 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 'ABA_BUPA_CALL_PROXY'"
EXPORTING
IS_ABABUSINESS_PARTNER = "
* IV_QUEUE_ID = "
* IT_RECEIVER_LIST = "

IMPORTING
EV_MESSAGE_ID = "
ET_MESSNUM = "

CHANGING
ES_BUS_EI_MAIN = "
.



IMPORTING Parameters details for ABA_BUPA_CALL_PROXY

IS_ABABUSINESS_PARTNER -

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

IV_QUEUE_ID -

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

IT_RECEIVER_LIST -

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

EXPORTING Parameters details for ABA_BUPA_CALL_PROXY

EV_MESSAGE_ID -

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

ET_MESSNUM -

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

CHANGING Parameters details for ABA_BUPA_CALL_PROXY

ES_BUS_EI_MAIN -

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

Copy and paste ABAP code example for ABA_BUPA_CALL_PROXY 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_ev_message_id  TYPE SXMSMGUID, "   
lv_es_bus_ei_main  TYPE BUS_EI_MAIN, "   
lv_is_ababusiness_partner  TYPE ABABUSINESS_PARTNER, "   
lv_et_messnum  TYPE MDM00_T_MESSNUM, "   
lv_iv_queue_id  TYPE PRX_SCNT, "   
lv_it_receiver_list  TYPE SXI_ADDRESSES. "   

  CALL FUNCTION 'ABA_BUPA_CALL_PROXY'  "
    EXPORTING
         IS_ABABUSINESS_PARTNER = lv_is_ababusiness_partner
         IV_QUEUE_ID = lv_iv_queue_id
         IT_RECEIVER_LIST = lv_it_receiver_list
    IMPORTING
         EV_MESSAGE_ID = lv_ev_message_id
         ET_MESSNUM = lv_et_messnum
    CHANGING
         ES_BUS_EI_MAIN = lv_es_bus_ei_main
. " ABA_BUPA_CALL_PROXY




ABAP code using 7.40 inline data declarations to call FM ABA_BUPA_CALL_PROXY

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.

 
 
 
 
 
 


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!