AMHIS SAP (Scheduling history table --> Display) Structure details
Description: Scheduling history table --> Display
Structure field list including key, data, relationships and ABAP select examples
AMHIS 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 "Scheduling history table --> Display" 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_AMHIS TYPE AMHIS.
The AMHIS table consists of various fields, each holding specific information or linking keys about Scheduling history table --> Display data available in SAP. These include MANDT (Client), WARPL (Maintenance Plan), ABNUM (Maintenance Plan Call Number), ZAEHL (Maintenance Package Number).. 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. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP AMHIS structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
WARPL | Maintenance Plan | WARPL | CHAR | 12 | MPLA | ALPHA | WARPL | MPL | MPLAL |
ABNUM | Maintenance Plan Call Number | ABNUM | INT4 | 10 | ABNUM | ||||
ZAEHL | Maintenance Package Number | PAKETZAEHL | NUMC | 2 | Assigned to domain | PAKZAE | |||
NPLDA | Next planned date | NPLDA | DATS | 8 | DATUM | ||||
TERMA | Scheduling type | TERMA | CHAR | 1 | CHAR1 | ||||
STADT | Start date | STADT | DATS | 8 | DATUM | ||||
LRMDT | Date of last completion in maintenance plan | LRMDT | DATS | 8 | DATUM | ||||
OFFZE | Offset in current cycle | OFFZE | FLTP | 16(16) | FLTP | ||||
OFFZO | Previous offset | OFFZO | FLTP | 16(16) | FLTP | ||||
ABRUD | Date of the call | ABRUD | DATS | 8 | DATUM | ||||
ABRNA | Name of the person who made the call | ABRNA | CHAR | 12 | USNAM | ||||
SFAKT | Cycle modification factor | SFAKT | DEC | 3(2) | SFAKT | ||||
TERMK | Scheduling indicator | TERMKNZ | CHAR | 1 | TERMKNZ | ||||
VERSCH | Shift Factor for Late Completion | VERSCHPLUS | NUMC | 3 | NUM3 | ||||
TOLER | Tolerance for Late Completion (%) | TOLERPLUS | NUMC | 3 | NUM3 | ||||
KNNRM | Indicator for negative completion confirmation | KNNRM | CHAR | 1 | XFLAG | ||||
KNPRM | Indicator: planned counter reading set manually | KNPRM | CHAR | 1 | XFLAG | ||||
NPLDO | Last planned date | NPLDO | DATS | 8 | DATUM | ||||
NPLDZ | Completion for Predecessor | NPLDZ | DATS | 8 | DATUM | ||||
MANDA | Manual call date | MANDA | DATS | 8 | DATUM | ||||
OFFLE | Estimated annual performance | OFFLE | FLTP | 16(16) | FLTP | ||||
OFFLO | Shift factor | OFFLO | FLTP | 16(16) | FLTP | ||||
KNAUT | Reserved | KNZABR | CHAR | 1 | FLAG | ||||
KNASR | Indicator for leading cycle (multi-counter plan) -> internal | KNZSTILL | CHAR | 1 | FLAG | ||||
TSABR | Scheduling status: planned date called | TSABR | CHAR | 1 | XFLAG | ||||
TSVBT | Scheduling status: call outstanding | TSVBT | CHAR | 1 | XFLAG | ||||
TSENQ | Scheduling status: call horizon not reached | TSENQ | CHAR | 1 | XFLAG | ||||
TSENM | Scheduling status: stopped manually | TSENM | CHAR | 1 | XFLAG | ||||
HORDA | Call date | HORDA | DATS | 8 | DATUM | ||||
TSTAT | Scheduling status | TSTAT | CHAR | 1 | FLAG | ||||
FIXDU | Fixed or skipped by | FIXDU | CHAR | 12 | USNAM | ||||
FIXDA | Fixed/skipped on | FIXDA | DATS | 8 | DATUM | ||||
VGNUM | Previous maintenance plan call | VGNUM | INT4 | 10 | Assigned to domain | OBJKN | |||
ZYKZT | Maintenance package cycle/offset | DZYK_ZEIT | FLTP | 16(16) | FLTP | ||||
ZYKLS | Total counter reading on call date | DZYK_LEIST | FLTP | 16(16) | FLTP | ||||
PUFFP | Lead Float in Days | PUFF_VORL | NUMC | 3 | NUM3 | ||||
PUFFN | Follow-up float in days | PUFF_NACHL | NUMC | 3 | NUM3 | ||||
SZAEH | Start counter reading | SZAEH | FLTP | 16(16) | FLTP | ||||
RZAEH | Counter reading confirmation | RZAEH | FLTP | 16(16) | FLTP | ||||
NZAEH | Next planned counter reading | NZAEH | FLTP | 16(16) | FLTP | ||||
USERMOD | Scheduling determined by user | USERMOD | CHAR | 1 | CHAR1 | ||||
.INCLU--AP | 0 | ||||||||
DEMAND_ID | Demand Id | ADMSP_D_DMND_ID | CHAR | 22 | ADMSP_DOM_DMND_ID | ||||
DEMAND_NO | APO Demand Number | ADMSP_D_DMND_NO | CHAR | 12 | CHAR12 | ||||
REVISION_NO | Revision for Plant Maintenance and Customer Service | REVNI | CHAR | 8 | Assigned to domain | REVNI | |||
REV_PLANT | Maintenance Planning Plant | IWERK | CHAR | 4 | Assigned to domain | WERKS | IWK | ||
.INCLU--AP | 0 | ||||||||
ADPOINT | Measuring Point | IMRC_POINT | CHAR | 12 | Assigned to domain | ALPHA | IMRC_POINT | IPT | IMPM |
ADANDOR | Indicator for OR or AND link | ANDOR | CHAR | 1 | RADIO | ||||
ADTGOON | Scheduling to reoccur when lead float reached | TGON | NUMC | 3 | NUM3 | ||||
ADCYCLE | Maintenance package cycle/offset | DZYK_ZEIT | FLTP | 16(16) | FLTP | ||||
ADUNIT | Unit for the performance of maintenance tasks | DZEIEH | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
ADOFFSET | Start offset of a time-based maintenance package | DZYK_OFFZT | FLTP | 16(16) | FLTP | ||||
ADNZAEH | Next planned counter reading | NZAEH | FLTP | 16(16) | FLTP | ||||
ADSTTIME | Start Time for Scheduling | TIME_START | TIMS | 6 | TIME | ||||
ADCONFTIME | Time of Last Completion in Maintenance Plan | TIME_CONF | TIMS | 6 | TIME | ||||
CYCLESEQIND | Cycle Set Sequence | CYCLESETSEQ | NUMC | 2 | NUMC2 | ||||
ADEXTSTARTDATE | Maintenance Plan Start Date Set Externally | DATE_START_EX | DATS | 8 | DATUM | ||||
ADEXTSTARTTIME | Maintenance Plan Start Time Set Externally | TIME_START_EX | TIMS | 6 | TIME | ||||
ADSYSTARTDATE | System Date for Maintenance Plan Start | DATE_START_SYST | DATS | 8 | DATUM | ||||
ADSYSTARTTIME | System Time for Maintenance Plan Start | TIME_START_SYST | TIMS | 6 | TIME | ||||
ADOBJECT | Object number | J_OBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
SETREPEATIND | Repeat Factor for Cycle Set Sequence | IND_SET_REPEAT | NUMC | 2 | NUMC2 | ||||
IND_MPLA_API | Maintenance Plan Was Created/Changed by API | IND_MPLA_API | CHAR | 2 | IND_API | ||||
DUE_DATE_TIME | Start Time for Scheduling | TIME_START | TIMS | 6 | TIME | ||||
DBKNZ | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 |
Key field | Non-key field |
How do I retrieve data from SAP structure AMHIS using ABAP code?
As AMHIS 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 AMHIS as there is no data to select.How to access SAP table AMHIS
Within an ECC or HANA version of SAP you can also view further information about AMHIS and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects