Hierarchy
⤷ 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_ISHCM_REPORTS | Overview of Auxiliary Programs and Other Utilities |
Transaction Code | S_KK4_74000159 | IMG Activity: SIMG_ISHCM_REPORTS |
Created on | 19990816 | |
Customizing Attributes | SIMG_ISHCM_REPORTS | Overview of Auxiliary Programs and Other Utilities |
Customizing Activity | SIMG_ISHCM_REPORTS | Overview of Auxiliary Programs and Other Utilities |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_ISHCM_REPORTS |
IS-HCM Overview of Auxiliary Programs and Other Utilities
Status: IS-H Release 4.03, May 1999
Auxiliary programs
- RNCBLD00 IS-HCM Message Formatting Program
This program reads orders ready for dispatch from table NC01 and formats them as messages ready for dispatch in table NC02.
The program should be run cyclically in the background (for instance, every six minutes).
- RNCEDIC1 IS-HCM Message Structure Tree
Message structures displayed in an arborescence.
- RNCGEN00 IS-HCM Generator for all S* Message structures
This program must be called after you have maintained S* messages types or segments. It regenerates the segment data retrieval programs from the data in the IS-HCM control tables. Runs automatically after each IS-H upgrade. Otherwise not required.
- RNCGEN90 IS-HCM Generator for all CUSTOMER message structures
This program must (!) be called after you have maintained customer message types or segments. It regenerates the segment data retrieval programs from the data in the IS-HCM control tables. Runs automatically after each IS-H upgrade.
Must be executed after customer messages are changed. Only successfully generated customer-specific message structures can be used.
- RNCGET00 IS-HCM Central Program Called For Message Delivery
This program only contains FORM routines for the transfer of data from partner systems to the IS-H System. In the IS-H System it is the 'contact' for the SAP communication module in the SAP system. The partner program (caller) is the send_tab program. The connection is established via the SAP communication module.
Inbound messages are processed according to their type in a separate FORM routine.
Messages supported:
- Diagnoses (FORM GET_DIAGS, transaction NP61),
- Case-related services (FORM GET_SERVS, transaction NL10),
- Surgeries (FORM GET_SURGS, transaction NP37),
- OU-related services (FORM GET_OUSRV, transaction NL04).
The data is always written immediately to the database.
- RNCGET01 IS-HCM Retrieval Of Case-Related Services From Partner Systems
This program retrieves the case-related service data from (selected) partner systems. You can choose between creating batch input sessions or having the data written to the IS-H database immediately.
The connection is established via the SAP communication module.
The program should run cyclically in the background (for instance, every evening), in order to transfer the accumulated messages (for a day) into the IS-H System.
- RNCGET02 IS-HCM Retrieval Of Diagnoses From Partner Systems
This program retrieves diagnoses from (selected) partner systems. You can choose between creating batch input sessions or having data written to the IS-H database immediately.
The connection is established via the SAP communication module.
The program can run cyclically in the background (for instance, every hour) in order to transfer the accumulated diagnoses into the IS-H System.
- RNCGET03 IS-HCM Retrieval Of ADT Data From Partner Systems
- Not yet functional under IS-H Release 3.03 -
This program retrieves ADT data from (selected) partner systems. You can then choose between creating batch input sessions or having the data written to the IS-H database immediately.
The connection is established via the SAP communication module.
The program can run cyclically in the background (for instance, every hour) in order to transfer the accumulated data into the IS-H System.
- RNCGET04 IS-HCM Retrieval Of OU-Related Services From Partner Systems
This program retrieves the OU-related service data from (selected) partner systems. You can then choose between creating batch input sessions or having the data written immediately to the IS-H database.
The connection is established via the SAP communication module.
The program should be run cyclically (for instance, every evening) in order to transfer the accumulated services (for a day) into the IS-H system.
- RNCGET05 IS-HCM Retrieval Of Surgery Data From Partner Systems
This program retrieves surgery data from (selected) partner systems. You can then choose between creating batch input sessions or having the data written immediately to the IS-H database.
The connection is established via the SAP communication module.
The program should be run cyclically (for instance, every evening) in order to transfer the accumulated surgeries (for a day) into the IS-H system.
- RNCSND01 IS-HCM Message Dispatch
This program reads all messages that are ready for dispatch from table NC02 and tries to deliver them to the receivers. The connection is established via the SAP communication module.
Messages delivered successfully are logged in table NC00. If delivery fails, the messages simply remain in table NC02.
The program should run cyclically in the background (for instance, every six minutes) in order to always ensure prompt transmission.
- RNCSND02 IS-HCM Selective Message Dispatch
This program is identical to RNCSND01. Please no longer use this program. It will be deleted in a future Release.
Utilities
- RNCCDERR Transfers Outstanding Acknowledgments Of Receipt To Subsystems
This program scans table TNCRESPO for outstanding aknowledgment messages. If such messages are found, the outstanding acknowledgments are transferred to the respective subsystems. On successful completion of this action, the TNCRESPO entry is deleted. Otherwise it is retained.
- RNCCHK01 IS-HCM Installation Check For Partner Systems.
Checks for errors and irregularities in the installation of a partner system. If error messages occur for a partner system, communication with this system cannot function.
Important utility for partner system installation.
- RNCLST01 IS-HCM Configuration Overview Of Partner System
This program lists the Customizing entries for a selected IS-H partner system. Apparent Customizing errors are included in this overview. Essentially used to produce a hardcopy of the Customizing settings of tested installations. Can also be used for troubleshooting.
- RNCUTL00 IS-HCM Message Standards (Maintained Message Types)
Selective display of all existing message types of the message standards or versions. Indicates which message types actually exist along with their status.
Executing this program generates a list of HCM format descriptions.
- RNCUTL01 IS-HCM Message Types (Composition)
Selective display of the message segments composing message types. Indicates which message segments make up a message type, together with their status and further relevant data.
- RNCUTL02 IS-HCM Message Segments (Composition)
Selective display of message fields composing message segments. Indicates which message fields make up a message segment. Also lists information relevant to the fields.
Executing this program generates a list of HCM format descriptions.
- RNCUTL03 IS-HCM Message Fields
Selective display of message fields.
- RNCUTL04 IS-HCM Display Messages Ready For Dispatch (Table NC02)
Displays messages ready for dispatch in table NC02. This may be necessary for control purposes since the message content cannot be displayed with transaction SE16.
All control information is shown along with the messages ready for dispatch. Each message is displayed in a line comprising 70 characters. All messages composed of more than 1024 characters are saved in blocks for every 1024 characters and are listed here accordingly.
- RNCUTL06 IS-HCM Create A Message Type Copy Under Different Owner Code
Create a copy of the messages types under another owner code. Can also be initiated from the HCM Communication menu by choosing Messages -> Types -> Create.
- RNCUTL07 IS-HCM Create A Segment Copy Under Different Owner Code
Create a copy of a message segment under a different owner code. Can also be initiated from the HCM Communication menu by choosing Messages -> Segments -> Create.
- RNCUTL08 IS-HCM Display Dispatch Logs
Selective display of dispatched messages in table NC00. This may be necessary for control purposes, since the message content cannot be displayed with transaction SE16.
Can also be initiated from the HCM Communication menu by choosing Dispatch control -> Dispatch logs -> Display.
All control information is shown along with the messages ready for dispatch. Each message is displayed in a line comprising 70 characters. All messages composed of more than 1024 characters are saved in blocks for every 1024 characters and are listed here accordingly.
- RNCUTL09 or RNCUTL09A IS-HCM Delete Dispatch Logs
Selective deletion of dispatched messages from table NC00. This should be executed at regular intervals in the background. Messages older than 2 days should be selected by this program.
Can also be initiated from the HCM Communication menu by choosing Dispatch control -> Dispatch logs -&g
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 | SIMG_ISHCM_REPORTS | 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 |
IMGDUMMY | D - Dummy object | NRCM | 4 | Auxiliary Programs - Display Utilities |
History
Last changed by/on | SAP | 20021206 |
SAP Release Created in |