SAP UPS_VERSION Versions/Session for Status Tracking Table data and field list

UPS_VERSION is a standard SAP Table which is used to store Versions/Session for Status Tracking data in SAP systems, such as SAP R/3, S/4HANA, depending on the version and release level.

The UPS_VERSION table consists of various fields, each holding specific information or linking keys about Versions/Session for Status Tracking data available in SAP. These include VERSION (Planning Session/Version)... 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. .

UPS_VERSION table Technical Details:

Delivery Class: C - Customising table, maintenance only by cust
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)

Text table = UPS_VERSION_T


SAP UPS_VERSION table 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 UPS_VERSION table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
MANDTClient MANDTCLNT3Assigned to domainMANDT
VERSIONPlanning Session/Version UPS_Y_VERSIONNUMC3

Key field Non-key field



How do I retrieve data from SAP table UPS_VERSION using ABAP code

The following ABAP code Example will allow you to do a basic selection on UPS_VERSION to SELECT all data from the table
DATA: WA_UPS_VERSION TYPE UPS_VERSION.

SELECT SINGLE *
FROM UPS_VERSION
INTO CORRESPONDING FIELDS OF WA_UPS_VERSION
WHERE...

How to access SAP table UPS_VERSION

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

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