Hierarchy
⤷
⤷
Basic Data
| Data Element | ADMI_INDN |
| Short Description | Name of a Property Index |
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 | 127 | |
| Decimal Places | 0 | |
| Output Length | 127 | |
| 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 | Index |
| Medium | 20 | Index Name |
| Long | 35 | Name of a Property Index |
| Heading | 35 | Name of a Property Index |
Documentation
Definition
The name of an index used in XML Data Archiving. It contains the properties of resources.
Use
A property index is used in the value-based search of resources. The name of a property index is global across the XML DAS. Therefore, it is recommended that you use either a namespace that uniquely identifies an application even outside the application system, or you should keep to the following convention for prefixes:
<archiving object>_[<sysid>_]...
If the concrete system ID <sysid> is part of the name, it will influence how the cross-system search is carried out: The system-specific property index must be specified during index create and during searches. Alternatively (if the index name does not contain the source system) you can define the system ID as a property, transfer it as a property value during a PUT and during the search preassign the value for the system ID property accordingly.
Dependencies
Example
The following name adheres to the convention explained above: BC_SBOOK_X_C11_FLIGHTS.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 630 |