SAP ABAP IMG Activity SIMG_CFMENUNMO4ONCR (Configure Normal Dispatch Control with OU Dependency)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
NBAS (Package) Appl. development Hospital System master data, catalogs

⤷

⤷

⤷

IMG Activity
ID | SIMG_CFMENUNMO4ONCR | Configure Normal Dispatch Control with OU Dependency |
Transaction Code | S_KK4_74000134 | IMG Activity: SIMG_CFMENUNMO4ONCR |
Created on | 19990816 | |
Customizing Attributes | SIMG_CFMENUNMO4ONCR | Configure Normal Dispatch Control with OU Dependency |
Customizing Activity | SIMG_CFMENUNMO4ONCR | Configure Normal Dispatch Control with OU Dependency |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUNMO4ONCR |
Use
In this IMG activity, you determine when and how a partner system is informed of an event using normal dispatch (asynchronous communication).
Activities
- To specify a unique identification for the triggering event, you must make the following entries in the appropriate fields:
- Institution (Inst. field)
- Application (A field, always "N" for IS-H)
- Event key (Event field).
- Enter the key of the organizational unit (generic entry not allowed) in the Affct. OU field. This means that this message is sent to the specified recipient when the corresponding event occurs only if this organizational unit is affected.
If this message is to be sent to this recipient when the corresponding event occurs irrespective of the affected organizational unit, enter an asterisk (*) in the Affct. OU field.
- Enter the logical system name (not the TXCOM name) in the HCM Rcv. (HCM receiving system) field.
- You can specify message types of the supported standard in relation to the event. Select the appropriate standard from the value help.
- Determine the format of the transmitted data using the message type owner code OC.
- You should only specify special characters if you do not use those predefined by the standard. At present, special characters are not supported by the SAP HCM-standard.
Dependencies
- You can only specify those message types listed in the section entitled Display Normal Dispatch Options (SAP) (call the value help).
- The system only takes the entries in this IMG activity into account if you set the attribute "dispatch with OU-dependency" in the dispatch options.
At present, dispatch with OU dependency is supported for all but the following events:
- NP0100 Create Patient Master Data
- NP01K0 Quick Admission: Create Patient Master Data
- NP01N0 Emergency Admission: Create Patient Master Data
- NP0201 Change Patient Master Data
- NP02K1 Quick Admission: Change Patient Master Data
- NP02N1 Emergency Admission: Change Patient Master Data
- NP020S Cancel Patient Master Data
- NP0600 Merge Patient Master Data
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 | SIMG_CFMENUNMO4ONCR | 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_TNCO2 | V - View | SM30 | 1 | Maintain Dispatch Control with Org. Unit Dependency |
History
Last changed by/on | SAP | 19990816 |
SAP Release Created in |