Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NORD (Package) R/3MED: Services processing EDV-G
Basic Data
Data Element | N1LKPTARID |
Short Description | Service Group - Catalog Identification |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TARID | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table | TNK01 |
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 | SrvGrp.Cat |
Medium | 14 | SrvGrp.Catalog |
Long | 20 | Serv. Group Catalog |
Heading | 2 | Ct |
Documentation
Definition
At master data level you can group services of clinical orders together. A group may contain one or more services and is used to structure clinical orders in the various views of the clinical work station and the day-based planning.
Example:
- A patient can have orders for various knee procedures. All clinical orders which exist for knee surgery should appear as one group in the view.
- To do this, you assign any services which represent knee procedures to a Knee service group. When you display the order in a view, the system will recognize that the service is assigned to the Knee group and will insert the service into the Knee group.
Service groups are managed in catalogs and the unique identifier consists of: service catalog identification and service identification. This field contains the service catalog identification. This may be the in-house catalog of your institution or another catalog.
Note: You can use service groups in various ways. For the structuring described here for the view or day-based planning, the system will only use the service groups with services assigned using a certain assignment type. You must store this assignment type in the system parameter N1LKPZUO.
History
Last changed by/on | SAP | 20050409 |
SAP Release Created in | 463B |