Hierarchy
⤷ BC-CCM-ADK (Application Component) Archive Development Kit
⤷ SARC (Package) Archive Development Kit
Basic Data
Data Element | ADMI_HOME |
Short Description | Home Path |
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 | 255 | |
Decimal Places | 0 | |
Output Length | 255 | |
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 | 15 | Home Path |
Medium | 15 | Home Path |
Long | 20 | Home Path |
Heading | 20 | Home Path |
Documentation
Definition
The highest position in the hierarchy of collections of an XML Data Archiving Service, from which point on you can archive application-specific collections or resources for a specific archiving object.
Use
The home path of an archiving object determines the minimum mandatory path with which URIs of collections or resources of an archiving object must begin. Generally, the collections that are created by archiving sessions are written to the home collection. The home path is used to logically place the data of an application inside the XML DAS hierarchy. In addition, the archiving-object-specific authorization check prevents accesses from applications with different home paths.
The following placeholders are replaced when report SYNC_HOME_PATH is executed, if they occur in the home path:
- <SYSID> ... current system ID
- <CLIENT> ... current client
- <OBJECT> ... archiving object for which the report is synchronizing the home path with the XML DAS
The home path can be changed in Customizing and can be synchronized with the XML DAS after data has already been archived. If this is done, the next resources that are archived are assigned to a different place in the hierarchy. Moreover, the archiving-object-specific authorization check is expanded to more than the initial home path.
Dependencies
To guaranty a disjunctive separation between the hierarchical position and the application-specific authorization check, no two archiving objects can have the same home path assigned to them, after the placeholders have been dissolved.
Example
During synchronization with the XML DAS from system C11, client 000, for archiving object BC_SBOOK_X, the home path /<SYSID>/<CLIENT>/<OBJECT>/MY_HOME/ becomes /C11/000/BC_SBOOK_X/MY_HOME/.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 630 |