SAP BAPI_BUS2170_EXISTENCE_CHECK Function Module for DO NOT USE!!!
BAPI_BUS2170_EXISTENCE_CHECK is a standard bapi bus2170 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 for DO NOT USE!!! 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 bapi bus2170 existence check FM, simply by entering the name BAPI_BUS2170_EXISTENCE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: DPR_BUS2170
Program Name: SAPLDPR_BUS2170
Main Program: SAPLDPR_BUS2170
Appliation area:
Release date: 10-Jan-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_BUS2170_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 'BAPI_BUS2170_EXISTENCE_CHECK'"DO NOT USE!!!.
EXPORTING
GUID = "Development Projects: Unique Object Key (CHAR 32)
TABLES
RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_BUS2170_EXISTENCE_CHECK
GUID - Development Projects: Unique Object Key (CHAR 32)
Data type: DPR_TV_GUID_BAPIOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_BUS2170_EXISTENCE_CHECK
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_BUS2170_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: | ||||
lv_guid | TYPE DPR_TV_GUID_BAPI, " | |||
lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
  CALL FUNCTION 'BAPI_BUS2170_EXISTENCE_CHECK' "DO NOT USE!!! |
EXPORTING | ||
GUID | = lv_guid | |
TABLES | ||
RETURN | = lt_return | |
. " BAPI_BUS2170_EXISTENCE_CHECK |
ABAP code using 7.40 inline data declarations to call FM BAPI_BUS2170_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