SAP DIMPLA MaintPlanHeader Table data and field list

DIMPLA 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 "MaintPlanHeader" 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_DIMPLA TYPE DIMPLA.

The DIMPLA table consists of various fields, each holding specific information or linking keys about MaintPlanHeader data available in SAP. These include MANDT (Client), WARPL (Maintenance Plan), ERKNZ (Creation indicator), AEKNZ (Change indicator)... 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. .

DIMPLA 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 DIMPLA 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 DIMPLA 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 WARPLCHAR12Assigned to domainALPHAWARPLMPLMPLAL
ERKNZCreation indicator ERKNZCHAR1FLAG
AEKNZChange indicator AEKNZCHAR1FLAG
ERSDTDate of creation EDATUMDATS8DATUM
ERNAMName of Person who Created the Object ERNAMCHAR12USNAM
AEDATChanged On AEDATDATS8DATUM
AENAMName of Person Who Changed Object AENAMCHAR12USNAM
WPTXTMaintenance Plan Text WPTXTCHAR40TEXT40
STRATMaintenance strategy STRATCHAR6T351WSTRASTRSTRAA
ABRHOScheduling Period ABRHONUMC3ANZTA
EQUNREquipment Number EQUNRCHAR18Assigned to domainALPHAEQUNREQNEQUI
TPLNRFunctional Location TPLNRCHAR30Assigned to domainTPLNRTPLNRIFLIFLM
KUNUMCustomer Number KUNUMCHAR10Assigned to domainALPHAKUNNRKUN
LTKNZLong Text Indicator MPLTXCHAR1XFELD
LVORMIndicator: maintenance plan locked against calls ABSTOPCHAR1XFELD
ANZPSNumber of maintenance items in the maintenance plan ANZMPOSNUMC4WPPOS
ABNUMMaintenance Plan Call Number ABNUMINT410ABNUM
LANGULanguage key of the long text MPLANGULANG1Assigned to domainISOLASPRAS
VSPOSShift Factor for Late Completion VERSCHPLUSNUMC3NUM3
VSNEGShift Factor for Early Completion VERSCHNEGNUMC3NUM3
TOPOSTolerance for Late Completion (%) TOLERPLUSNUMC3NUM3
TONEGTolerance for Early Completion (%) TOLERNEGNUMC3NUM3
SFAKTCycle modification factor SFAKTDEC3(2) SFAKT
STICHScheduling indicator TERMKNZCHAR1TERMKNZ
TGOONScheduling to reoccur when lead float reached TGONNUMC3NUM3
HORIZCall horizon for maintenance plan calls HORIZONTNUMC3NUM3
HORIZ_DAYSCall horizon for maintenance plan calls HORIZONTNUMC3NUM3
HORIZ_QUALIFIERCalculation Type of Call Horizon EAM_CC_CALLHORIZON_QUALIFIERCHAR1EAMQFEAM_CC_CALLHORIZON_QUALIFIER
ANDORIndicator for OR or AND link ANDORCHAR1RADIO
KNAUTReserved KNZABRCHAR1FLAG
BEGRUTechnical object authorization group IAUTGCHAR4T370BIAUTG
OBJNRObject number J_OBJNRCHAR22Assigned to domainJ_OBJNRONR
MPTYPMaintenance plan category MPTYPCHAR2T399WMPTYPWAT
HUNITUnit in scheduling interval HUNITUNIT3Assigned to domainCUNITMEINS
STADTStart date STADTDATS8DATUM
SZAEHStart counter reading SZAEHCCHAR22WZYKL
CALL_CONFIRMOnly Create New Call Object After Completing Predecessor CALL_CONFIRMCHAR1CHAR1
PLAN_SORTSort field for maintenance plans PLAN_SORTCHAR20T399GCHAR20
FABKLFactory calendar key FABKLCHAR2TFACDWFCID
PUFFPLead Float in Days PUFF_VORLNUMC3NUM3
PUFFNFollow-up float in days PUFF_NACHLNUMC3NUM3
.INCLU--AP 0
START_DATEStart Date for Scheduling DATE_STARTDATS8DATUM
START_TIMEStart Time for Scheduling TIME_STARTTIMS6TIME
CALL_UPDATE_INDIndicator for Adapting Basic Dates of Call Object IND_CALL_UPDATECHAR1XFELD
IND_MPLA_APIMaintenance Plan Was Created/Changed by API IND_MPLA_APICHAR2IND_API
MCP_SFShift Factor for Multiple Counter Plan MCP_SFCHAR1MCP_SF
KTEXTDescription of maintenance strategy TXWSTRACHAR30TXT30

Key field Non-key field



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

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

How to access SAP table DIMPLA

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

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

Related SAP tables and the relationships to DIMPLA

    DIMPOS - Maintenance item
        DIMPLA - MaintPlanHeader
            DIMHIS - MaintPlanCalls
        DIAUFK - PM order
        DIPLKO - Task list header
        DIILOA - Location (ILOA)
        DIOBJK - Object List

    DIMPLA - Maintenance plan header
        DIMHIS - Maintenance plan calls
        DIMPOS - Maintenance item
            DIAUFK - PM order
            DIPLKO - Task list header
            DIILOA - Location (ILOA)
            DIOBJK - Object List