ADMI_FILST SAP (Archive Files: Header Information, Jobs, and Status) Structure details
Description: Archive Files: Header Information, Jobs, and Status
Structure field list including key, data, relationships and ABAP select examples
ADMI_FILST 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 "Archive Files: Header Information, Jobs, and Status" 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_ADMI_FILST TYPE ADMI_FILST.
The ADMI_FILST table consists of various fields, each holding specific information or linking keys about Archive Files: Header Information, Jobs, and Status data available in SAP. These include DOCUMENT (Archiving Session Number), ARCHIV_KEY (Key for Archive File), CREAT_DATE (Creation Date of Archive File), CREAT_TIME (Time when an archive file was generated).. 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: Cannot Be Enhanced
SAP ADMI_FILST 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 |
| DOCUMENT | Archiving Session Number | ADMI_RUN_D | CHAR | 6 | ADMI_RUN | ||||
| ARCHIV_KEY | Key for Archive File | ARKEY | CHAR | 20 | ARKEY | ||||
| CREAT_DATE | Creation Date of Archive File | ADMI_CDATE | DATS | 8 | ADMI_DATE | ||||
| CREAT_TIME | Time when an archive file was generated | ADMI_TIME | TIMS | 6 | RKZ_TIME | ||||
| OBJ_COUNT | Number of objects in an archive file | ADMI_COUNT | INT4 | 10 | U_INT_4 | ||||
| FILE_SIZE | Size of an Archive File in Bytes | ADMI_SIZE | FLTP | 16(16) | FLOATING | ||||
| FILENAME | File name of archive file | ADMI_FILE | CHAR | 255 | TEXT255 | ||||
| STATUS_OPT | Status of archive in storage | ADMI_STOPT | CHAR | 1 | STOPT | ADMI_STOPT | |||
| STATUS_FIL | Status of an individual archive file of an archive session | ADMI_STFIL | CHAR | 1 | STFIL | ADMI_STFIL | |||
| COMMENTS | Note for an archive file | ADMI_TXT_F | CHAR | 60 | TEXT60 | ||||
| STATUS_IDX | Archive status for index | ADMI_STIDX | CHAR | 1 | STIDX | ADMI_STIDX | |||
| PATHINTERN | Logical path name | PATHINTERN | CHAR | 60 | FILEPATH | PATHINTERN | |||
| CREP | Storage Repository for Physical Objects | SCMS_CREP | CHAR | 30 | Assigned to domain | SCMS_CREP | |||
| ARCH_DOCID | Document ID of the stored file (ArchiveLink or CMS) | ARCH_DOCID | CHAR | 40 | |||||
| DELETING | Delete Is Running or Is Scheduled | ADMI_DELTI | CHAR | 1 | X | ||||
| ACCESSIBLE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| ST_DEL_JOB | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| DEL_JOB | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| C_DEL_JOB | Job ID | BTCJOBCNT | CHAR | 8 | CHAR8 | ||||
| ST_IDX_JO | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| IDX_JOB | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| C_IDX_JOB | Job ID | BTCJOBCNT | CHAR | 8 | CHAR8 | ||||
| ST_STO_JOB | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| STO_JOB | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| C_STO_JOB | Job ID | BTCJOBCNT | CHAR | 8 | CHAR8 | ||||
| ST_RET_JOB | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| RET_JOB | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| C_RET_JOB | Job ID | BTCJOBCNT | CHAR | 8 | CHAR8 | ||||
| JOB_ACT | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure ADMI_FILST using ABAP code?
As ADMI_FILST 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 ADMI_FILST as there is no data to select.How to access SAP table ADMI_FILST
Within an ECC or HANA version of SAP you can also view further information about ADMI_FILST 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