SAP RDATE_RANGE Range for Date Values Table data and field list

RDATE_RANGE 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 "Range for Date Values" 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_RDATE_RANGE TYPE RDATE_RANGE.

The RDATE_RANGE table consists of various fields, each holding specific information or linking keys about Range for Date Values data available in SAP. These include OPTION (Type of OPTION component in row type of a Ranges type), LOW (Field of type DATS), HIGH (Field of type DATS)... 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. .

RDATE_RANGE structure Technical Details:

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

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

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

How to access SAP table RDATE_RANGE

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

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