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
IMG Activity
| ID | SIMG_ISHMED_ANFTYP | Request Type Definition |
| Transaction Code | S_KK4_96000546 | IMG Activity: SIMG_ISHMED_ANFTYP |
| Created on | 20020307 | |
| Customizing Attributes | SIMG_ISHMED_ANFTYP | Request Type Definition |
| Customizing Activity | SIMG_ISHMED_ANFTYP | Request Type Definition |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_ANFTYP |
The request type determines the properties of a request. It is provided by an organizational unit (OU) and defined for the desired request scenario. The request type is defined from the performing organizational unit. The request type is like the paper "request form". The service facility which receives the request, defines how the request should appear and what should be included.
You can define the following request type attributes:
- Name of Request Type.
You should give the request type a self-explanatory name. This name will appear in various areas of IS-H*MED (Patient Organizer, request selection hit list, etc.).
- Availability of Request Type
Which organizational unit can make requests of this type?
- Structure
On which tab pages should this request type be available?
- Service Hit List
- Further Definitions
Indicators and required entry fields which control the behavior of the requests of this type.
Requirements
You should note that you can either assign the request type to a care unit, an outpatient clinic or an entire department. In particular, if care units with patients from several departments can request in your installation, SAP recommends that you define the assignment based on departmental organizational units.
Standard settings
Activities
Note: The request type will only be available to a department, care unit or outpatient clinic, if you activate the Available pushbutton to the left of each line.
Example
Further notes
- Each request type can be assigned a separate number range, which is controlled using the object ISH_N1AFNR.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_ISHMED_ANFTYP | 0 | I041002042 | Preregistration |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| N1AE | T - Individual transaction object | N1AE |
History
| Last changed by/on | SAP | 20020311 |
| SAP Release Created in | 463B |
