RWAP3 SAP (Appointments: Planned/actual comparison) Structure details
Description: Appointments: Planned/actual comparison
Structure field list including key, data, relationships and ABAP select examples
RWAP3 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 "Appointments: Planned/actual comparison" 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_RWAP3 TYPE RWAP3.
The RWAP3 table consists of various fields, each holding specific information or linking keys about Appointments: Planned/actual comparison data available in SAP. These include MANDT (Client), VBTYP (SD document category), BELNR (Appointments: Document number), LFNDR (Appointments: Sequence number).. 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: Not classified
SAP RWAP3 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| VBTYP | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
| BELNR | Appointments: Document number | APPBN | CHAR | 10 | ALPHA | APPBN | |||
| LFNDR | Appointments: Sequence number | APPUN | CHAR | 4 | CHAR04 | ||||
| BLTYP | Appointments: Internal document category | APPBT | CHAR | 2 | APPBT | ||||
| LGNUM | Warehouse Number / Warehouse Complex | LGNUM | CHAR | 3 | T300 | LGNUM | LGN | ||
| LGTOR | Door for Warehouse Number | LGTOR | CHAR | 3 | T30B | LGTOR | |||
| DATAB | Appointments: From date | APPDA | DATS | 8 | DATUM | ||||
| DATBI | Appointments: Date to | APPDB | DATS | 8 | DATUM | ||||
| UHRAB | Appointments: Time from | APPUA | TIMS | 6 | APPUA | ||||
| UHRBI | Appointments: Time to | APPUB | TIMS | 6 | APPUB | ||||
| FTEXT | Appointments: Short text | APPFT | CHAR | 30 | APPFT | ||||
| LIFNR | Vendor to whom partner roles have been assigned | PLIEF | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
| SPDNR | Number of forwarding agent | TDLNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | F4_CARRIERS |
| DATIA | Appointments: From date (actual) | APPDA_IST | DATS | 8 | DATUM | ||||
| DATIB | Appointments: To-date (actual) | APPDB_IST | DATS | 8 | DATUM | ||||
| UHRIA | Appointments: Time from (actual) | APPUA_IST | TIMS | 6 | APPUA | ||||
| UHRIB | Appointments: Time to (actual) | APPUB_IST | TIMS | 6 | APPUB | ||||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| DATPA | Appointments: Planned from-date | APPDA_ORG | DATS | 8 | DATUM | ||||
| UHRPA | Appointments: Time from (original) | APPUA_ORG | TIMS | 6 | APPUA | ||||
| DATPB | Appointments: Date to (original) | APPDB_ORG | DATS | 8 | DATUM | ||||
| UHRPB | Appointments: Time to (actual) | APPUB_ORG | TIMS | 6 | APPUB | ||||
| APPAG | Appointments: Deviation reason | APPAG | CHAR | 2 | TWAP2 | APPAG | |||
| DIFF1 | Schedule deviation (in minutes) for unknown reason | APPDI_1 | DEC | 7 | APPDI | ||||
| DIFF2 | Appointments: Reason for deviation (in mins): own company | APPDI_2 | DEC | 7 | APPDI | ||||
| DIFF3 | Appointments: Reason for deviation (mins): service provider | APPDI_3 | DEC | 7 | APPDI | ||||
| DIFF4 | Appointments: Reason for deviation (in minutes): vendor | APPDI_4 | DEC | 7 | APPDI | ||||
| DURA1 | Appointments: Length of the activity in minutes (planned) | APPD1 | DEC | 7 | APPDI | ||||
| DURA2 | Appointments: Length of the activity (actual) | APPD2 | DEC | 7 | APPDI | ||||
| BEZEI | Appointments: Description of the deviation reason | APPBZ_AG | CHAR | 20 | TEXT20 | ||||
| BEZEI_VU | App.: Description for party responsible for sched. deviation | APPBZ_VU | CHAR | 20 | TEXT20 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RWAP3 using ABAP code?
As RWAP3 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 RWAP3 as there is no data to select.How to access SAP table RWAP3
Within an ECC or HANA version of SAP you can also view further information about RWAP3 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