Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-ADK (Application Component) Archive Development Kit⤷
SARC (Package) Archive Development Kit
Basic Data
| Data Element | ADMI_ASTOR_ADK |
| Short Description | ILM Store |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 50 | |
| Decimal Places | 0 | |
| Output Length | 50 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | ILM Store |
| Medium | 20 | ILM Store |
| Long | 40 | ILM Store |
| Heading | 40 | ILM Store |
Documentation
Definition
Name for a storage area within a storage system used for collections and resources in the context of ADK archiving.
Use
When archive files are stored using the WebDAV interface of ADK, an archive store is used to write the files to a specific area in a concrete storage system (WebDAV System). You define the physical storage area in the XML DAS Administration through an archive store root and the address of an existing storage system. When you synchronize the home paths from Customizing with the XML DAS, you specify the archive store; this is to abstract from the physical system coordinates.
Typically the home paths of archiving objects only lie in the same archive store, when the different object types have the same retention periods or the archived data is to be stored "closely together" due to other administrative reasons. Whether or not the same storage medium is to be used for the same archive store (for example the same CD, volume, ....) is ultimately determined by the concrete storage system.
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 710 |
