SAP ABAP IMG Activity ISH_UE_SAP (Display SAP User Exits)
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
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 | ISH_UE_SAP | Display SAP User Exits |
| Transaction Code | S_KK4_74000405 | IMG Activity: ISH_UE_SAP |
| Created on | 19990816 | |
| Customizing Attributes | ISH_UE_SAP | Display SAP User Exits |
| Customizing Activity | ISH_UE_SAP | Display SAP User Exits |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISH_UE_SAP |
You can include your own functionality in the IS-H System via predefined interfaces. The events for which these user exits can be called in the form of function modules are stored in the SAP User Exit table. You can find out the exact point in the SAP program at which your functions can be invoked and display a description of the corresponding interface by selecting an event, and then choosing Goto -> Long Text.
Most events already have corresponding SAP entries. If you write your own function modules, you can use these SAP entries as templates. You have to enter the function modules you write yourself for the respective event in the IMG activity Configure Customer User Exits.
Example
- SAP supports the import mechanism commercialized by CHERRY by default for importing the healthcare smart card. Once the import transaction has executed, a file with a specific record structure is created. The function module specified for the event RKVK in the SAP User Exits table is used to transfer this record structure into the IS-H System.
- SAP provides another function module for the import mechanism commercialized by ORGA. You can specify this function module directly in the event RKVK.
- If you use a different import mechanism, you may have to write your own function module to convert the healthcare smart card data into the IS-H format. The best way of doing this is to use the SAP function module as a template. Once you have created your own function module, enter it for the event RKVK in the Customer User Exits table.
Business Attributes
| ASAP Roadmap ID | 104 | |
| Mandatory / Optional | 3 | Nonrequired 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 | ISH_UE_SAP | 0 | I010004200 | SAP Healthcare - Industry-Specific Components for Hospitals |
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 |
| TNE00 | S - Table (with text table) | ONB6 | 1 | IS-H: SAP User Exits |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
