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_CFMENUNMO4NC10 | Create Message Types |
| Transaction Code | S_KK4_74000208 | IMG Activity: SIMG_CFMENUNMO4NC10 |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_CFMENUNMO4NC10 | Create Message Types |
| Customizing Activity | SIMG_CFMENUNMO4NC10 | Create Message Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUNMO4NC10 |
In this IMG activity, you create new customer-defined message types. Each customer-defined message type must be referenced to a standard message type. This assignment is established automatically when you create the new customer-specific message type by specifying the message type number and copying a template. You can use any message type with the same number as a template.
You identify your message type by assigning it a new owner code. You can also enter your own short text for the message type. If you want to use the standard short text as a template, at first don't make an entry in the corresponding field. One you have specified the template, and pressed Enter, the system proposes the short text of the template here. You can then modify this text to satisfy your own requirements.
When you choose Create, the system creates your message type with a structure identical to that of the template. Only the owner code and short text are different.
Recommendation
Only use owner codes that begin with "Y" or "Z". These name ranges are reserved for you and will not be overwritten by SAP.
On no account should you use owner codes that begin with "S". This name range is reserved for SAP.
For technical reasons, the first character of the owner code must be a letter.
Note
Report IS-HCM: Delete Selected Customer Message Components (RNCUTL11) lets you delete message types you have created but don't need any more (it is useful to add this report to HCM utilities). This is the only means of ensuring that all structures involved are deleted consistently from the database. You should then generate customer structures. This deletes all structures and data retrieval procedures that are no longer required.
Activities
- Before creating a new message type, decide on its exact structure.
- Find out which owner codes you can use in your healthcare facility.
Business Attributes
| ASAP Roadmap ID | 205 | |
| Mandatory / Optional | 2 | Optional 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_CFMENUNMO4NC10 | 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 |
| NC10 | T - Individual transaction object | NC10 | 1 | Create Message Types |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
