SAP BAPI_PREBOOK_ATTENDANCE Function Module for Prebook attendance

Search SAP Function Modules

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

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

Function BAPI_PREBOOK_ATTENDANCE 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_PREBOOK_ATTENDANCE'"Prebook attendance
  EXPORTING
   PLVAR =  "Plan version
*  END_DATE =  "End date of prebook period
   ATTENDEEID =  "Attendee key (personnel number etc.)
   ATTENDEETYPE =  "Participant Type
   EVENTTYPEID =  "Key of business event type
*  PREBOOK_LANGUAGE =  "Requested language of prebooking
*  PREBOOK_LOCATION =  "Requested location of prebooking
*  PREBOOK_PRIORITY =  "Booking priority of prebooking
*  PREBOOK_COUNT =  "Number of requested bookings
*  BEGIN_DATE =  "Start date of prebook period

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

.

IMPORTING Parameters details for BAPI_PREBOOK_ATTENDANCE

PLVAR - Plan version

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

END_DATE - End date of prebook period

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

ATTENDEEID - Attendee key (personnel number etc.)

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

ATTENDEETYPE - Participant Type

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

EVENTTYPEID - Key of business event type

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

PREBOOK_LANGUAGE - Requested language of prebooking

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

PREBOOK_LOCATION - Requested location of prebooking

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

PREBOOK_PRIORITY - Booking priority of prebooking

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

PREBOOK_COUNT - Number of requested bookings

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

BEGIN_DATE - Start date of prebook period

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

EXPORTING Parameters details for BAPI_PREBOOK_ATTENDANCE

RETURN - Structure for Return Parameters (Code, Text)

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

Copy and paste ABAP code example for BAPI_PREBOOK_ATTENDANCE 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_PREBOOK_ATTENDANCE

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