SAP REQEL Receipts of the Requirements Element Table data and field list

REQEL 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 "Receipts of the Requirements Element" 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_REQEL TYPE REQEL.

The REQEL table consists of various fields, each holding specific information or linking keys about Receipts of the Requirements Element data available in SAP. These include LFUHR (Time of delivery), OUTPO (Single-Character Indicator), JCPOS (Single-Character Indicator), TANUM (Transfer Order 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. .

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

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

How to access SAP table REQEL

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

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