PKERALT SAP (Error Log for Kanban Alert) Structure details
Description: Error Log for Kanban Alert
Structure field list including key, data, relationships and ABAP select examples
PKERALT 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 "Error Log for Kanban Alert" 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_PKERALT TYPE PKERALT.
The PKERALT table consists of various fields, each holding specific information or linking keys about Error Log for Kanban Alert data available in SAP. These include PKKEY (Identification Number), PKNUM (Control cycle number), PKPOS (Kanban item number / control cycle item), SAEDT (Date of last change).. 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 PKERALT 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 | |||
| PKKEY | Identification Number | PKKEY | NUMC | 10 | PKPS | PKKEY | |||
| PKNUM | Control cycle number | PKNUM | CHAR | 7 | Assigned to domain | ALPHA | PKNUM | PKNUM | |
| PKPOS | Kanban item number / control cycle item | PKPOS | NUMC | 3 | PKPOS | ||||
| SAEDT | Date of last change | SAEDT | DATS | 8 | DATUM | ||||
| SAEUZ | Time of the last status change | SAEUZ | TIMS | 6 | UZEIT | ||||
| MSGID | Application Area | ARBGB | CHAR | 20 | T100A | ARBGB | MAG | ||
| MSGNR | Message number | MSGNR | CHAR | 3 | T100 | MSGNR | |||
| MSGTY | Message Type | MSGTY | CHAR | 1 | MSGAR | ||||
| MSGV1 | Message variable 01 | MSGV1 | CHAR | 50 | CHAR50 | ||||
| MSGV2 | Message variable 02 | MSGV2 | CHAR | 50 | CHAR50 | ||||
| MSGV3 | Message variable 03 | MSGV3 | CHAR | 50 | CHAR50 | ||||
| MSGV4 | Message variable 04 | MSGV4 | CHAR | 50 | CHAR50 | ||||
| MESSAGE | Long Text in Kanban Message | PKMSGLONG | CHAR | 220 | TEXT220 | ||||
| SFGSN | Status should be set / was set to status ... | SFGSN | CHAR | 1 | PKBST | ||||
| SFGSV | Status should be set / was set from status | SFGSV | CHAR | 1 | PKBST |
| Key field | Non-key field |
How do I retrieve data from SAP structure PKERALT using ABAP code?
As PKERALT 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 PKERALT as there is no data to select.How to access SAP table PKERALT
Within an ECC or HANA version of SAP you can also view further information about PKERALT 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