SAP DIMHIO Call Objects from Maintenance Plan for Logical Database Table data and field list

DIMHIO 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 "Call Objects from Maintenance Plan for Logical Database" 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_DIMHIO TYPE DIMHIO.

The DIMHIO table consists of various fields, each holding specific information or linking keys about Call Objects from Maintenance Plan for Logical Database data available in SAP. These include MANDT (Client), WARPL (Maintenance Plan), ABNUM (Maintenance Plan Call Number), WPPOS (Maintenance item)... 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. .

DIMHIO structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)


SAP DIMHIO 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 DIMHIO 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
WARPLMaintenance Plan WARPLCHAR12MPLAALPHAWARPLMPLMPLAL
ABNUMMaintenance Plan Call Number ABNUMINT410ABNUM
WPPOSMaintenance item WAPOSCHAR16ALPHAPOSNUMPSMPOSL
AUFNROrder Number AUFNRCHAR12AUFKALPHAAUFNRANR
ADDATCompletion Date for Call Object MHIO_ADDATDATS8DATUM
LBLNIEntry Sheet Number LBLNICHAR10Assigned to domainALPHALBLNILBLESSR
TSENQScheduling status: call horizon not reached TSENQCHAR1XFLAG
TSTATScheduling status TSTATCHAR1FLAG
GSTRPBasic start date CO_GSTRPDATS8DATUM
SORTFSort field for maintenance item scheduling call MHIO_SORTFCHAR30CHAR30
QMNUMNotification No QMNUMCHAR12QMELALPHAQMNUMIQM
ADTIMECompletion Time for Call Object MHIO_ADUHRTIMS6TIME
PRUEFLOSInspection Lot Number QPLOSNUMC12Assigned to domainQPLOSQLSQALS
USERMODScheduling determined by user USERMODCHAR1CHAR1
IND_MPLA_APIMaintenance Plan Was Created/Changed by API IND_MPLA_APICHAR2IND_API
.INCLU--AP 0
DEMAND_IDDemand Id ADMSP_D_DMND_IDCHAR22ADMSP_DOM_DMND_ID
DEMAND_NOAPO Demand Number ADMSP_D_DMND_NOCHAR12CHAR12
REVISION_NORevision for Plant Maintenance and Customer Service REVNICHAR8Assigned to domainREVNI
REV_PLANTMaintenance Planning Plant IWERKCHAR4Assigned to domainWERKSIWK
CALL_STATUSDescription of Scheduling Type and Call Status CALL_STATUSCHAR45CHAR45
NPLDANext planned date NPLDADATS8DATUM
ABRNAName of the person who made the call ABRNACHAR12USNAM
HORDACall date HORDADATS8DATUM
LRMDTDate of last completion in maintenance plan LRMDTDATS8DATUM

Key field Non-key field



How do I retrieve data from SAP structure DIMHIO using ABAP code?

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

How to access SAP table DIMHIO

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

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