SAP ABAP Data Element N1PLSKZ (OE1 May Request from OU2 in Patient Routing System)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
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 | N1PLSKZ |
| Short Description | OE1 May Request from OU2 in Patient Routing System |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | PRS |
| Medium | 14 | Pat. Rout. Sys |
| Long | 20 | Indicator Req. (PRS) |
| Heading | 1 | P |
Documentation
Definition
When the indicator Patient routing system (P) is checked off, this determines that the combination of services from the requester and performer is also valid in the IS-H*MED Patient routing system. By confirming treatment in the waiting list, a sequence of outpatient visits can be defined for a patient. By setting this indicator, a pushbutton is made available in 'specify Being treated' of the requesting organizational unit, through which an outpatient visit to the performing organizational unit can be created.
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in |