⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NORD (Package) R/3MED: Services processing EDV-G
|ID||SIMG_ISHMED_PTS_FST||Specify transport order status|
|Customizing Attributes||SIMG_ISHMED_PTS_FST||Specify transport order status|
|Customizing Activity||SIMG_ISHMED_PTS_FST||Maintain Planning Object Classes|
|Document Class||SIMG||Hypertext: Object Class - Class to which a document belongs.|
With this work step, you determine the number of the possible statuses of a transport order. Each transport order has exactly one status from this quantity at a certain point in time. In the course of the processing of a transport order, the status changes, and the system creates a history of the status of each order.
The names, presentations and, to a certain extent, the number of statuses are freely definable.
Examples for transport order status:
- Order created
- Order assigned to a transporter
- Order received by a transporter
- Order completed
The patient transport service provides the functions for managing transport orders and setting the transport order status. These functions are divided into two categories:
- Functions which can set an explicitly defined status for a transport order:
- Create transport order (initial status): When you create a transport order, the system will assign this status.
- Assign transport order to a transporter: When you assign the transport order to a transporter for execution, the system will assign this status. You can assign the transport order to a transporter when creating the transport order. The initial status is then omitted. You can also assign the transport order to a transporter using a function in the dispatcher work station. There can be only one status with the "Transport Assigned" status type.
- Complete transport order: When a transporter has completed a transport order, the system assigns this status.
- Cancel transport order: When you cancel a transport order, the system assigns this status.
Each of these functions corresponds to a status type which the selected function uses to recognize the status to be set. Exactly one status is intended for each of the functions mentioned. When defining the status, you should make sure that there is a unique definition of exactly one status for each of these status types.
- Transporter informed
- Transport order received by transporter
- Patient received by transporter
- Transport order refused by transporter
- Transport order canceled
The availability of these functions is based on the definition of the status that should be set by the functions. If statuses are defined with a status type that does not correspond to the functions explained in item 1, then the system will supply functions for setting this status.
In contrast to the functions explained in item 1, the number of the statuses for these functions is freely definable.
In order to enable use of the elementary functions of the patient transport service, exactly one status, with the entered internal status, must be defined for each of the following status types:
- Initial status - Internal status '01'
- Transporter assigned - Internal status '02'
- Order completed - Internal status '08'
- Order canceled - Internal status '09'
|ASAP Roadmap ID||250||Define Number Range and Basic Structures|
|Mandatory / Optional||1||Mandatory activity|
|Critical / Non-Critical||1||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_PTS_FST||0||I500000210||Patient Transport Service|
|Maintenance object type||C||Customizing Object|
|Customizing Object||Object Type||Transaction Code||Sub-object||Do not Summarize||Skip Subset Dialog Box||Description for multiple selections|
|V_N1FST||V - View||SM30||Specify Transport Order Status|
|Last changed by/on||SAP||20000731|
|SAP Release Created in||462|