SAP BUPA_EXISTENCE_CHECK Function Module for
BUPA_EXISTENCE_CHECK is a standard bupa existence check 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 existence check FM, simply by entering the name BUPA_EXISTENCE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUBA_4
Program Name: SAPLBUBA_4
Main Program: SAPLBUBA_4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BUPA_EXISTENCE_CHECK 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_EXISTENCE_CHECK'".
EXPORTING
* IV_PARTNER = "Business Partner Number
* IV_PARTNER_GUID = "Business Partner GUID
TABLES
* ET_RETURN = "Messages
IMPORTING Parameters details for BUPA_EXISTENCE_CHECK
IV_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PARTNER_GUID - Business Partner GUID
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BUPA_EXISTENCE_CHECK
ET_RETURN - Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BUPA_EXISTENCE_CHECK 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: | ||||
lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lv_iv_partner | TYPE BU_PARTNER, " | |||
lv_iv_partner_guid | TYPE BU_PARTNER_GUID. " |
  CALL FUNCTION 'BUPA_EXISTENCE_CHECK' " |
EXPORTING | ||
IV_PARTNER | = lv_iv_partner | |
IV_PARTNER_GUID | = lv_iv_partner_guid | |
TABLES | ||
ET_RETURN | = lt_et_return | |
. " BUPA_EXISTENCE_CHECK |
ABAP code using 7.40 inline data declarations to call FM BUPA_EXISTENCE_CHECK
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