SAP EAM_S_PERMIT_ISSUE permit issue for API Table data and field list

EAM_S_PERMIT_ISSUE 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 "permit issue for API" 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_EAM_S_PERMIT_ISSUE TYPE EAM_S_PERMIT_ISSUE.

The EAM_S_PERMIT_ISSUE table consists of various fields, each holding specific information or linking keys about permit issue for API data available in SAP. These include GENVNAME (Permit Issued By)... 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. .

EAM_S_PERMIT_ISSUE structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced

SAP EAM_S_PERMIT_ISSUE 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 EAM_S_PERMIT_ISSUE 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 EAM_S_PERMIT_ISSUE using ABAP code?

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

How to access SAP table EAM_S_PERMIT_ISSUE

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

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