SAP UPC_MULTIAREA Multi-Planning Areas Table data and field list

UPC_MULTIAREA is a standard SAP Table which is used to store Multi-Planning Areas data in SAP systems, such as SAP R/3, S/4HANA, depending on the version and release level.

The UPC_MULTIAREA table consists of various fields, each holding specific information or linking keys about Multi-Planning Areas data available in SAP. These include MAREA (Planning Area), AREA (Planning Area)... 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. .

UPC_MULTIAREA table Technical Details:

Delivery Class: L - Table for storing temporary data, is delivered empty
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced


SAP UPC_MULTIAREA 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 UPC_MULTIAREA 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 MANDTCLNT3T000MANDT
MAREAPlanning Area UPC_Y_AREACHAR8Assigned to domainUPC_AREA
AREAPlanning Area UPC_Y_AREACHAR8Assigned to domainUPC_AREA

Key field Non-key field



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

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

SELECT SINGLE *
FROM UPC_MULTIAREA
INTO CORRESPONDING FIELDS OF WA_UPC_MULTIAREA
WHERE...

How to access SAP table UPC_MULTIAREA

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

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