SAP PRSS_MESSAGE Structure type for PRS message handling Table data and field list

PRSS_MESSAGE 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 "Structure type for PRS message handling" 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_PRSS_MESSAGE TYPE PRSS_MESSAGE.

The PRSS_MESSAGE table consists of various fields, each holding specific information or linking keys about Structure type for PRS message handling data available in SAP. These include MSG_TYPE (3-Byte field)... 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. .

PRSS_MESSAGE structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)

SAP PRSS_MESSAGE structure fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the PRSS_MESSAGE table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.

Key field

Non-key field

How do I retrieve data from SAP structure PRSS_MESSAGE using ABAP code?

As PRSS_MESSAGE 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 PRSS_MESSAGE as there is no data to select.

How to access SAP table PRSS_MESSAGE

Within an ECC or HANA version of SAP you can also view further information about PRSS_MESSAGE and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).