SAP ABAP IMG Activity SIMG_ISHMED_RAD_ADT0 (Patient Management with MITRA PACS Broker)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NMED (Package) R/3MED: Medical documentation GSD
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NMED (Package) R/3MED: Medical documentation GSD
IMG Activity
ID | SIMG_ISHMED_RAD_ADT0 | Patient Management with MITRA PACS Broker |
Transaction Code | S_KK4_96000401 | IMG ADT |
Created on | 20010312 | |
Customizing Attributes | SIMG_ISHMED_RAD_ADT0 | IS-H*MED RAD: Patient Management via MSI |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_ISHMED_RAD_ADT0 |
Generally all IS-H HCM events can be defined (refer to HCM Communication). In the transfer control, you can set the HCM events OU-related or without a reference.
- The report RN2_MSI_ADT is to be planned as a periodic batch
- The MS Windows NT command file msiput.cmd transfers files to an FTP Server.
If this task is to be performed periodically, it is recommended that you plan the call as a job step in a periodic batchjob.
Example
Requirements
Standard settings
Recommendation
Activities
- You must plan the report as a periodic batchjob with the transaction sm36.
In the Selection Parameter HCM - Source File, you specify the complete directory name of the HCM results file. Example: \usr\sap\work\ishcm\pacs\.
In the selection parameter Logical Name MSI Destination File, you enter the maintained logical file name in the transaction FILE. The supplied logical file name is ISH_MED_RAD_MSI_FILE. The converted MSI files are written into this directory which the PACS Broker reads or are transported by FTP. You must maintain the physical destination path in the transaction FILE - File transfer via FTP
If the files are transferred to the PACS Broker via FTP, a job step must be planned that starts the external NT-Shellscript msiput.cmd with the parameters FTP-destination directory and MSI-file-name extension to the destination drive.
Call Parameters are
Syntax: msiput.cmd [<destpath>] [<destext>]
With destpath - FTP destination path, destext - file name extension, Standard is msi.
You must set the following environment variables in the file msiput.cmd:
Name Meaning Sample Value
dest FTP Host BROKER
destuser FTP User Anonymous
destpwd Password <eMail Adresse>
wpath Local Directory C:\MSI\
If you set the environment variable DEBUG to 1, you will receive displays of the defined commands.
Further notes
Planning the periodic batchjob in five-minute intervals is recommended.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional 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_ISHMED_RAD_ADT0 | 0 | CI40000006 | Communication |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20010312 |
SAP Release Created in | 463 |