SKURS SAP (Business Event Booking Offered for Replacement/Cancellation) Structure details
Description: Business Event Booking Offered for Replacement/Cancellation
Structure field list including key, data, relationships and ABAP select examples
SKURS 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 "Business Event Booking Offered for Replacement/Cancellation" 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_SKURS TYPE SKURS.
The SKURS table consists of various fields, each holding specific information or linking keys about Business Event Booking Offered for Replacement/Cancellation data available in SAP. These include TYP_ID (Business Event Type ID of Event to be Canceled/Replaced), SHORT (Business Event Name Abbreviation), STEXT (Object Name for Business Event), LANGU (Business event language).. 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 SKURS 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 |
| ID | Business Event ID | KURS_ID | NUMC | 8 | NUM08 | ||||
| TYP_ID | Business Event Type ID of Event to be Canceled/Replaced | STYP_ID | NUMC | 8 | NUM08 | ||||
| SHORT | Business Event Name Abbreviation | KURS_SHORT | CHAR | 12 | TEXT12 | ||||
| STEXT | Object Name for Business Event | KURS_STEXT | CHAR | 40 | TEXT40 | ||||
| LANGU | Business event language | KLANGU | LANG | 1 | T002 | ISOLA | SPRAS | ||
| BEGDA | Business Event Start Date | KBEGDA | DATS | 8 | DATUM | ||||
| BIND | Hyphen | STRICH | CHAR | 1 | CHAR1 | ||||
| ENDDA | Business Event End Date | KENDDA | DATS | 8 | DATUM | ||||
| EXTRN | Display external business event | EXTERN | CHAR | 1 | CHAR1_X | ||||
| ISTAT | Status of Business Event Booking | BISTAT | CHAR | 1 | T778S | ISTAT | |||
| DELOC | Lock/Delete Flag | DELOC | CHAR | 1 | CHAR1 | ||||
| HISTO | Historical Record Flag | HISTO | CHAR | 1 | CHAR1 | ||||
| PRIOX | Booking Priority | KPRIOX | CHAR | 2 | CHAR2 | ||||
| MANZL | Number of attendances | BMANZL | DEC | 3 | DEC3 | ||||
| BUDAT | Booking date | PBUDAT | DATS | 8 | DATUM | ||||
| LOCKM | Lock flag | LOCKM | CHAR | 1 | CHAR1_X | ||||
| DELET | Delete flag | LOESCH | CHAR | 1 | CHAR1_X |
| Key field | Non-key field |
How do I retrieve data from SAP structure SKURS using ABAP code?
As SKURS 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 SKURS as there is no data to select.How to access SAP table SKURS
Within an ECC or HANA version of SAP you can also view further information about SKURS 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