SAP ABAP Data Element N2COMM_PART_WS (Communication Partner for Web Service Document Dispatch)
Hierarchy
☛
IS-H (Software Component) SAP Healthcare
⤷
IS-HMED (Application Component) Clinical System
⤷
NMED_DOC (Package) IS-H*MED: Medical Documents
IS-H (Software Component) SAP Healthcare⤷
IS-HMED (Application Component) Clinical System⤷
NMED_DOC (Package) IS-H*MED: Medical Documents
Basic Data
| Data Element | N2COMM_PART_WS |
| Short Description | Communication Partner for Web Service Document Dispatch |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | N2COMM_PART_WS | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | TN2COM_PART_WS |
Further Characteristics
| Search Help: Name | N2COMM_PART_WS | |
| Search Help: Parameters | COMM_PART | |
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Comm.Part. |
| Medium | 20 | Comm. Partner |
| Long | 40 | Communication Partner |
| Heading | 0 |
Documentation
Definition
Each communication partner requires a unique ID in order to differentiate him from other partners.
Use
You should discuss this ID with your communication partner before saving it.
If communication platforms handle the forwarding of messages between your system and the partner system, you may need to declare the partner's key there and connect it to the partner with the transfer route.
Dependencies
Example
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
