Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NPVS (Package) Application development patient management system
Basic Data
| Data Element | ANFOE |
| Short Description | IS-H: Departmental Org. Unit Requesting Service |
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 | Req.DeptOU |
| Medium | 14 | Req. Dept. OU |
| Long | 20 | Requesting Dept. OU |
| Heading | 8 | R.DeptOU |
Documentation
Definition
Departmental oranizational unit that requests the service.
Supplementary Documentation - ANFOE 0001
Use
If you want to enter planned values independent of the OU or specialty, you can enter an asterisk (*) here. Note, however, that such entries are not evaluated in the V2 and V3 statistics (programs RNSV202 and RNSV302).
Procedure
Examples
Dependencies
Supplementary Documentation - ANFOE 0002
Use
Default value for the requesting departmentatl organizational unit.
Procedure
Enter the departmental organizational unit for which the material requisition is to be made.
Examples
Dependencies
If you do not make an entry in this field, the system takes the requesting, departmental organizational unit from the movement.
This field only affects new items and not existing material requisitions. ().
Supplementary Documentation - ANFOE 0003
Use
When you enter a service without specifying the requesting departmental organizational unit (OU), the system determines the requesting departmental OU from the movement to which the service is assigned.
Depending on whether you called the service entry transaction with regard to a case or a movement, the system determines the requesting departmental OU as follows:
- You call service entry with regard to a case by choosing the required row in the case list.
- Inpatient/day patient case:
- For extended services, the system proposes the departmental OU to which the case is assigned in the admission and in subsequent inpatient movements.
- For immediate services, the system proposes the departmental OU of the admission.
- Outpatient case:
- The system proposes the departmental OU of the first outpatient visit as the requesting departmental OU.
- You call service entry with regard to a movement by choosing the movement in the case list for which you want to enter services.
- Inpatient/day patient case:
- For extended and immediate services, the system proposes the departmental OU of the chosen movement. If you chose an outpatient visit, the system proposes the departmental OU of the movement that is valid on the date of the visit instead of the departmental OU of the outpatient visit.
- Outpatient case:
- The system proposes the departmental OU of the chosen outpatient visit as the requesting departmental OU.
Procedure
Enter the service and confirm your input. The system automatically determines the requesting departmental OU.
Note that the system can no longer automatically adjust entered services in relation to changed movement data if you manually change the data for the requesting and performing OU or the validity dates of the service. For this reason, you should make changes in the corresponding movements. The system automatically transfers the changed data into the service entry transaction.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
