Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NBAS (Package) Appl. development Hospital System master data, catalogs
Basic Data
| Data Element | N_SUBKEY |
| Short Description | IS-HCM: Additional Key for Event-Object Determination |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | N_SUBKEY | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Add. Key |
| Medium | 15 | Additional Key |
| Long | 20 | Additional Key |
| Heading | 10 | Add. Key |
Documentation
Definition
The additional key is used to identify subobjects in single event processing. The specification merely describes which key part is concerned by a particular event.
An additional key is not required for the 'typical' basic events. These basic events are distinguished by the fact that the main keys that are transferred directly as parameters to event processing are sufficient to identify the object concerned by the event.
In contrast to this, for single events certain situations may require you to specify additional keys to ensure that the subobjects in question are identified uniquely.
If more than one additional key is required for a subobject, or if several subobjects are affected by the single event, the corresponding keys must be transferred in the correct sequence (specified at event definition). The sequence of the specified keys is of prime importance.
You can subsequently only change the additional keys in the event definition if you also modify all involved programs accordingly.
Example
A single service for a case was changed. The main keys of the event (institution, case number) are transferred as such to event processing directly. To identify the service uniquely, by convention when a change is made to a single service, the service code (ID) and the sequential number of the service are transferred as the additional key for the event.
If more than one service is modified in a transaction, the single change event is triggered several times. In each case, the service code (ID) and the sequential number of the service are transferred as the additional key for the event.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
