SAP MHIS_CD Preventive Maintenance Plan History (Change Documents) Table data and field list

MHIS_CD 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 "Preventive Maintenance Plan History (Change Documents)" 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_MHIS_CD TYPE MHIS_CD.

The MHIS_CD table consists of various fields, each holding specific information or linking keys about Preventive Maintenance Plan History (Change Documents) data available in SAP. These include WARPL (Maintenance Plan), ABNUM (Maintenance plan call number), ZAEHL (Maintenance Package Number), NPLDA (Next planned date)... 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. .

MHIS_CD 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 MHIS_CD 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 MHIS_CD 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
WARPLMaintenance Plan WARPLCHAR12Assigned to domainALPHAWARPLMPLMPLAL
ABNUMMaintenance plan call number ABNUM_CDNUMC10
ZAEHLMaintenance Package Number PAKETZAEHLNUMC2Assigned to domainPAKZAE
NPLDANext planned date NPLDADATS8DATUM
TERMAScheduling type TERMACHAR1CHAR1
STADTStart date STADTDATS8DATUM
LRMDTDate of last completion in maintenance plan LRMDTDATS8DATUM
OFFZEOffset in current cycle OFFZEFLTP16(16) FLTP
OFFZOPrevious offset OFFZOFLTP16(16) FLTP
ABRUDDate of the call ABRUDDATS8DATUM
ABRNAName of the person who made the call ABRNACHAR12USNAM
SFAKTCycle modification factor SFAKTDEC3(2) SFAKT
TERMKScheduling indicator TERMKNZCHAR1TERMKNZ
VERSCHShift Factor for Late Completion VERSCHPLUSNUMC3NUM3
TOLERTolerance for Late Completion (%) TOLERPLUSNUMC3NUM3
KNNRMIndicator for negative completion confirmation KNNRMCHAR1XFLAG
KNPRMIndicator: planned counter reading set manually KNPRMCHAR1XFLAG
NPLDOLast planned date NPLDODATS8DATUM
NPLDZCompletion for Predecessor NPLDZDATS8DATUM
MANDAManual call date MANDADATS8DATUM
OFFLEEstimated annual performance OFFLEFLTP16(16) FLTP
OFFLOShift factor OFFLOFLTP16(16) FLTP
KNAUTReserved KNZABRCHAR1FLAG
KNASRIndicator for leading cycle (multi-counter plan) -> internal KNZSTILLCHAR1FLAG
TSABRScheduling status: planned date called TSABRCHAR1XFLAG
TSVBTScheduling status: call outstanding TSVBTCHAR1XFLAG
TSENQScheduling status: call horizon not reached TSENQCHAR1XFLAG
TSENMScheduling status: stopped manually TSENMCHAR1XFLAG
HORDACall date HORDADATS8DATUM
TSTATScheduling status TSTATCHAR1FLAG
FIXDUFixed or skipped by FIXDUCHAR12USNAM
FIXDAFixed/skipped on FIXDADATS8DATUM
VGNUMPrevious maintenance plan call VGNUM_CDNUMC10
ZYKZTMaintenance package cycle/offset DZYK_ZEITFLTP16(16) FLTP
ZYKLSTotal counter reading on call date DZYK_LEISTFLTP16(16) FLTP
PUFFPLead Float in Days PUFF_VORLNUMC3NUM3
PUFFNFollow-up float in days PUFF_NACHLNUMC3NUM3
SZAEHStart counter reading SZAEHFLTP16(16) FLTP
RZAEHCounter reading confirmation RZAEHFLTP16(16) FLTP
NZAEHNext planned counter reading NZAEHFLTP16(16) FLTP
USERMODScheduling determined by user USERMODCHAR1CHAR1
.INCLU--AP 0
ADPOINTMeasuring Point IMRC_POINTCHAR12Assigned to domainALPHAIMRC_POINTIPTIMPM
ADANDORIndicator for OR or AND link ANDORCHAR1RADIO
ADTGOONScheduling to reoccur when lead float reached TGONNUMC3NUM3
ADCYCLEMaintenance package cycle/offset DZYK_ZEITFLTP16(16) FLTP
ADUNITUnit for the performance of maintenance tasks DZEIEHUNIT3Assigned to domainCUNITMEINS
ADOFFSETStart offset of a time-based maintenance package DZYK_OFFZTFLTP16(16) FLTP
ADNZAEHNext planned counter reading NZAEHFLTP16(16) FLTP
ADSTTIMEStart Time for Scheduling TIME_STARTTIMS6TIME
ADCONFTIMETime of Last Completion in Maintenance Plan TIME_CONFTIMS6TIME
CYCLESEQINDCycle Set Sequence CYCLESETSEQNUMC2NUMC2
ADEXTSTARTDATEMaintenance Plan Start Date Set Externally DATE_START_EXDATS8DATUM
ADEXTSTARTTIMEMaintenance Plan Start Time Set Externally TIME_START_EXTIMS6TIME
ADSYSTARTDATESystem Date for Maintenance Plan Start DATE_START_SYSTDATS8DATUM
ADSYSTARTTIMESystem Time for Maintenance Plan Start TIME_START_SYSTTIMS6TIME
ADOBJECTObject number J_OBJNRCHAR22Assigned to domainJ_OBJNRONR
SETREPEATINDRepeat Factor for Cycle Set Sequence IND_SET_REPEATNUMC2NUMC2
IND_MPLA_APIMaintenance Plan Was Created/Changed by API IND_MPLA_APICHAR2IND_API

Key field Non-key field



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

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

How to access SAP table MHIS_CD

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

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