Hierarchy

⤷

⤷

⤷

IMG Activity
ID | ISH_HCM_SYNC_VER_AUF | Configure Express Dispatch of Admission Data |
Transaction Code | S_KK4_74000132 | IMG Activity: ISH_HCM_SYNC_VER_AUF |
Created on | 19990816 | |
Customizing Attributes | ISH_HCM_SYNC_VER_AUF | Configure Express Dispatch of Admission Data |
Customizing Activity | ISH_HCM_SYNC_VER_AUF | Configure Express Dispatch of Admission Data |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ISH_HCM_SYNC_VER_AUF |
Use
In this IMG activity, you define when and how a partner system is informed of an event using express dispatch (synchronous communication).
Activities
- To create a unique identification for the triggering event, you have to make the following specifications in the relevant fields:
- Institution (Inst field),
- Application (always 'N' in the A field)
- Event key (Event field).
- Enter the identification keys of the required organizational units (avoiding generic specifications) in the Dept. OU (departmental organizational unit) and/or Nrs. OU (nursing organizational unit) fields. This means that this message is sent to the specified recipient when the corresponding event occurs only if this (these) organizational unit(s) are concerned.
- If this message is to be sent to this recipient when the corresponding event occurs irrespective of the concerned organizational unit, enter an asterisk (*) in the organizational unit field(s).
- Enter the logical system name in the HCM Rcpt (HCM receiver) field.
- In the Remote Function Name field, enter the name of the program that receives the data on the subsystem side.
- You can define exclusions by selecting Excl.. To see how to do this, refer to the example below.
- In the Interface FM field, you can specify an interface function module of your own. It must have the same interface to IS-H as the function module ISHCM_ADMISSION_INTERFACE. You can use any interface to the partner system. You can make further restrictions concerning the transmission of data in this function module.
Prerequisites
- You can only specify those message types that are listed under Display Express Dispatch Options (SAP) (see the value help).
- You need to have activated automatic dispatch in the institution-specific system settings. To do this, refer to the Section entitled Maintain Institution-Specific Basic Control.
- The lock indicator must not be set for the partner system in question in the system attribute table. Normal dispatch must be activated and a valid RFC destination must be maintained (if necessary, create it first using transaction SM59).
For more information about this, refer to the Section entitled Maintain HCM System Attributes.
Only if the above conditions are satisfied will the system take into account the entries stored in this table and execute the specified function module.
The function module receives the data to be processed or passed on in the subsystem. It is not delivered by SAP, but has to be developed by the providers of the subsystems.
If you want to deactivate express dispatch for a partner system, you need only deselect (leave blank) the express dispatch indicator in the system attribute table (TN02S). Admission data will now only be dispatched to the subsystem by means of normal HCM (if HCM is active) and no longer via express dispatch.
Example
Inst A Event Dept.OU Nrs.OU HCM Rcpt. Rem.F.N. Excl.
1 N NP11I0 SURG * LABOR Function_A
1 N NP11I0 SURH UNIT9 LABOR x
In this example, whenever event NP11I0 (Actual Patient Admission) occurs, the system passes the patient data to the laboratory if a care unit of the surgery department is concerned. Care unit 9 represents the exception. If the patient is admitted to this care unit, a message is not dispatched.
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 205 | |
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 | ISH_HCM_SYNC_VER_AUF | 0 | I010004207 | Communication |
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 |
V_TNCD1 | V - View | ONCS | 1 | Maintain Dispatch Control for Direct Communication |
History
Last changed by/on | SAP | 19990816 |
SAP Release Created in |