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 | N1WP11ANFOE |
| Short Description | Initiating Department |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ORGID | |
| Data Type | CHAR | Character String |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| Value Table | NORG |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | REQ_DEPT_OU | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Init.Dept |
| Medium | 14 | Initiat. Dept |
| Long | 30 | Initiating Department |
| Heading | 9 | Init.Dept |
Documentation
Definition
The initiating department is defined in the surgery request. As a rule it is the department of the patient's current stay (case) in the hospital.
Supplementary Documentation - N1WP11ANFOE0001
Use
If you wish to enter cross-OU or cross-departmental plan values you can enter a '*' here. You should note, however, that such entries will not be evaluated in the V2 and V3 statistics (reports RNSV202 und RNSV302).
Procedure
Examples
Dependencies
Supplementary Documentation - N1WP11ANFOE0002
Use
Proposal Value for the Requesting Departmental Organizational Unit
Procedure
You enter the departmental organizational unit which the material request is for.
Examples
Dependencies
If this field remains blank, the system will use the requesting departmental organizational unit from the movement.
This field has no effect on existing material requests, only on new items. ()
Supplementary Documentation - N1WP11ANFOE0003
Use
If you enter a service without entering the departmental requesting organizational unit (OU), the system will determine the departmental requesting OU from the movement to which the service is assigned.
Depending on whether you called the service entry function as case-related or movement-related, the system will determine the departmental requesting OU as follows:
- You call the service entry as case-related by selecting the case line in the case list.
- Inpatient/Day Patient Case:
- For extended services, the system will propose the departmental OU to which the case is assigned in the admission and in subsequent inpatient movements.
- For immediate services, the system will propose the departmental OU of the admission.
- Outpatient Case:
- The system will propose the departmental OU of the first outpatient visit as the departmental requesting OU.
- You call the service entry function as movement-related by selecting the movement, for which you wish to enter services, in the case list.
- Inpatient/Day Patient Case:
- For extended and immediate services, the system will propose the departmental OU of the selected movement. If you selected an outpatient visit, the system will not propose the departmental OU of the outpatient visit, but the departmental OU of the movement which is valid at the time of the visit.
- Outpatient Case:
- The system will propose the departmental OU of the selected outpatient visit as the departmental requesting OU.
Procedure
You enter the service and confirm your entries. The system will automatically determine the departmental requesting OU.
You should note that the system can no longer adapt entered services to suit changed movement data, if you have changed requesting or performing OU data or data concerning the validity of the service. You should therefore make changes in the relevant movements. The system will automatically transfer the changed data to the service entry.
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in | 471 |
