SAP BAPI_BUS_EVENT_LOCATION Function Module for Business event locations

Search SAP Function Modules

BAPI_BUS_EVENT_LOCATION is a standard bapi bus event location SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Business event locations 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 bus event location FM, simply by entering the name BAPI_BUS_EVENT_LOCATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHVI
Program Name: SAPLRHVI
Main Program:
Appliation area: H
Release date: 16-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_BUS_EVENT_LOCATION 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_BUS_EVENT_LOCATION'"Business event locations
  EXPORTING
*  PLVAR =  "Plan version
*  OBJID =  "Current business event location (key)
*  BEGIN_DATE =  "Start date of selection period
*  END_DATE =  "End date of selection period

 IMPORTING
   RETURN =  "Structure for Return Parameters (Code, Text)

TABLES
   LOCATION_LIST =  "List of valid business event locations

EXCEPTIONS
   ROOT_NOT_FOUND = 1    NO_ACTIVE_PLVAR = 2    UNKNOWN_EXCEPTION = 3 

.

IMPORTING Parameters details for BAPI_BUS_EVENT_LOCATION

PLVAR - Plan version

Data type: BAPILOCDAT-PLVAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJID - Current business event location (key)

Data type: BAPILOCDAT-LOCID
Optional: Yes
Call by Reference: No ( called with pass by value option)

BEGIN_DATE - Start date of selection period

Data type: BAPIDATE-BEGDA
Optional: Yes
Call by Reference: No ( called with pass by value option)

END_DATE - End date of selection period

Data type: BAPIDATE-ENDDA
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_BUS_EVENT_LOCATION

RETURN - Structure for Return Parameters (Code, Text)

Data type: BAPIRETURN
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_BUS_EVENT_LOCATION

LOCATION_LIST - List of valid business event locations

Data type: BAPILOCDAT
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ROOT_NOT_FOUND - Current business event location does not exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_ACTIVE_PLVAR - There is no active plan version

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

UNKNOWN_EXCEPTION - Other error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_BUS_EVENT_LOCATION 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.

ABAP code using 7.40 inline data declarations to call FM BAPI_BUS_EVENT_LOCATION

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