Hypertext: Object Class - Class to which a document belongs.
Document Name
SIMG_ISHMED_COMPRTWS
Use
You have to define the following information for each communication partner.
Step 1: Create/maintain business partner entry for communication partner Firstly you must create a suitable business partner entry and define the associated address data.
Step 2: Maintain communication partner settings You then have to define the following information for each business partner:
Communication Partner ID: Each communication partner requires a unique ID so that it can be distinguished from other partners. You should agree on this ID with your communication partner before you define it.
If communication platforms still forward messages between your system and the partner system, the key of the partner may also have to be made known there and linked to the transfer route to the partner.
EmR to be preset for received documents: Document management requires an employee responsible (EmR) for every document. In order for this to be filled in when a document is received from a communication partner, an EmR value must be assigned to each partner in their own system.
In this field, enter the employee responsible to be preset when documents of the named communication partner are received.
Organizational unit to be preset for received objects Document management requires a documenting organizational unit (OU) for each document. In order for this to be filled in when a document is received from a partner, a documenting OU must be assigned to each communication partner in their own system.
In this field, enter the organizational unit to be preset when documents of the named communication partner are received.
Business partner reference for communication partner Enter the business partner here who belongs to the communication partner.
Logical port for document dispatch Enter the logical port that you have created at the item"Partner-Specific Logical Port for Documents".
Logical port doe confirmation dispatch Normally you can leave this field blank. If your partner system requires a separate message, enter the logical port that you have created at the item "Partner-Specific Logical Port for Confirmations".
Hierarchy 
IS-H (Software Component) SAP Healthcare
IS-HMED (Application Component) Clinical System
NMED_DOC (Package) IS-H*MED: Medical Documents
IMG Activity 
Document 
History 
