Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-H-PM (Application Component) Patient Management⤷
N1BASE (Package) IS-H: Basic Functionality; TSA Development
Basic Data
| Data Element | N1COMPENDDT |
| Short Description | CORD/PREG: Component - Validity End |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RI_DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| 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 | Valid To |
| Medium | 14 | Valid To |
| Long | 20 | Valid To |
| Heading | 10 | Valid To |
Documentation
Definition
Component's valid-to date.
Use
Clinical application components can only be defined within their validity periods in clinical order types.
Integration in existing order types is retained regardless of this validity. This means that to prevent the further use of the functionality of a component, you have to deactivate the implementing order types.
The validity thus relates to the component's usability in the master data definition and not to its usability at movement (transactional data) level.
Note on clinical order and preregistration: The preregistration is a kind of clinical order. SAP Patient Management (IS-H) only uses Preregistration, whereas ISHMED also uses other kinds of clinical order. Therefore explanations for IS-H always concern the preregistration.
Dependencies
Example
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in | 472 |
