BAPIPREBO SAP (Attendee Prebookings) Structure details
Description: Attendee Prebookings
Structure field list including key, data, relationships and ABAP select examples
BAPIPREBO is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Attendee Prebookings" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BAPIPREBO TYPE BAPIPREBO.
The BAPIPREBO table consists of various fields, each holding specific information or linking keys about Attendee Prebookings data available in SAP. These include ETYID (Business event type: key), ETSHT (Business event type abbreviation), ETSTX (Name of business event type), BEGDA (Start date of prebooking period).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP BAPIPREBO structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| PLVAR | Plan Version | PLVAR | CHAR | 2 | T778P | PLVAR | POP | ||
| ETYID | Business event type: key | ETYID | NUMC | 8 | PLOGI | HROBJID | |||
| ETSHT | Business event type abbreviation | VTSHT | CHAR | 12 | TEXT12 | ||||
| ETSTX | Name of business event type | EVTTX | CHAR | 40 | TEXT40 | ||||
| BEGDA | Start date of prebooking period | HRVOBEG | DATS | 8 | DATUM | ||||
| ENDDA | End date of the prebooking period | HRVOEND | DATS | 8 | DATUM | ||||
| ISTAT | Planning Status | ISTAT_D | CHAR | 1 | T778S | ISTAT | PST | ||
| LANGU | Business event language | KLANGU | LANG | 1 | T002 | ISOLA | SPRAS | ||
| LOCID | Business Event Location | LOCID | NUMC | 8 | PLOGI | HROBJID | |||
| LOCTX | Name of the business event location | LOCTX | CHAR | 40 | TEXT40 | ||||
| PRIOX | Priority | PRIOX | CHAR | 2 | CHAR2 | ||||
| BUDAT | Booking date | PBUDAT | DATS | 8 | DATUM | ||||
| MANZL | Number of attendances | BMANZL | DEC | 3 | DEC3 | ||||
| KKOST | Attendance or cancellation fee | KKOST | CURR | 16(2) | CURR16 | ||||
| KWAER | Currency key for fees | EXWAER | CUKY | 5 | TCURC | WAERS |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPIPREBO using ABAP code?
As BAPIPREBO is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on BAPIPREBO as there is no data to select.How to access SAP table BAPIPREBO
Within an ECC or HANA version of SAP you can also view further information about BAPIPREBO and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects