COM_BAPIBUS1006060_APPRULE SAP (R3A BP: BAPI Fragment Structure of Appointment Rule) Structure details
Description: R3A BP: BAPI Fragment Structure of Appointment Rule
Related tables to COM_BAPIBUS1006060_APPRULE
Access table COM_BAPIBUS1006060_APPRULE
Structure field list including key, data, relationships and ABAP select examples
COM_BAPIBUS1006060_APPRULE 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 "R3A BP: BAPI Fragment Structure of Appointment Rule" 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_COM_BAPIBUS1006060_APPRULE TYPE COM_BAPIBUS1006060_APPRULE.
The COM_BAPIBUS1006060_APPRULE table consists of various fields, each holding specific information or linking keys about R3A BP: BAPI Fragment Structure of Appointment Rule data available in SAP. These include TIME_ZONE (R3A BP: Time Zone), MONDAY_AM_FROM (R3A BP: Tim hhmmss (in the Basis)), MONDAY_AM_TO (R3A BP: Tim hhmmss (in the Basis)), TUESDAY_AM_FROM (R3A BP: Tim hhmmss (in the Basis)).. 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 COM_BAPIBUS1006060_APPRULE 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 |
| CALENDAR | R3A BP: Factory Calendar | GB_FACID | CHAR | 2 | CHAR2 | ||||
| TIME_ZONE | R3A BP: Time Zone | GB_TIMEZ | CHAR | 6 | CHAR6 | ||||
| MONDAY_AM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| MONDAY_AM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| TUESDAY_AM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| TUESDAY_AM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| WEDNESDAY_AM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| WEDNESDAY_AM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| THURSDAY_AM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| THURSDAY_AM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| FRIDAY_AM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| FRIDAY_AM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SATURDAY_AM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SATURDAY_AM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SUNDAY_AM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SUNDAY_AM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| MONDAY_PM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| MONDAY_PM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| TUESDAY_PM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| TUESDAY_PM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| WEDNESDAY_PM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| WEDNESDAY_PM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| THURSDAY_PM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| THURSDAY_PM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| FRIDAY_PM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| FRIDAY_PM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SATURDAY_PM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SATURDAY_PM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SUNDAY_PM_FROM | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 | ||||
| SUNDAY_PM_TO | R3A BP: Tim hhmmss (in the Basis) | GB_TIME06 | CHAR | 6 | CHAR6 |
| Key field | Non-key field |
How do I retrieve data from SAP structure COM_BAPIBUS1006060_APPRULE using ABAP code?
As COM_BAPIBUS1006060_APPRULE 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 COM_BAPIBUS1006060_APPRULE as there is no data to select.How to access SAP table COM_BAPIBUS1006060_APPRULE
Within an ECC or HANA version of SAP you can also view further information about COM_BAPIBUS1006060_APPRULE 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