Sidebar
en:prozessdefinition:repositorien:analysator:partnererkennung
partner detection
| Name | Meaning |
|---|---|
| By backend reference1) | The partner is determined using the backend reference in the location. |
| By GLN2) | The partner is determined on the basis of the participant's GLN. |
| By Interchange address3) | The partner is determined on the basis of the interchange address matching the document type (i. e. for an Edifact document, an address of the type Edifact UNB, for AnsiX12 an address of the type AnsiX12 ISA).. |
| By Interchange ID and type4) | The partner is determined on the basis of the interchange ID corresponding to the document type. |
| By Interchange ID best match(7) 5) | The partner is determined using the subset (first 7 digits of the GLN) of the Interchange ID. |
| By Interchange ID ignore type6) | The partner is determined on the basis of the interchange ID, regardless of the document type, that is, all addresses are searched.. |
| By TNr7) | The partner is determined on the basis of the partner's TNr. |
| By trading partner ID18) | The partner is only determined from the location using trading partner ID1. |
| By trading partner ID1 or ID29) | The partner is determined from the location using trading partner ID1 or trading partner ID2.. |
| By trading partner ID210) | The partner is only determined from the location using trading partner ID12. |
| None | No partner recognition. |
| Set to default system/trading partner | The party that is the communication party in the message is used. |
| set to message communication partner | The partner that is assigned in the node as the default system partner is used. |
Note: When recognizing a partner by means of a Interchange, this is looked up in the Communication addresses.
en/prozessdefinition/repositorien/analysator/partnererkennung.txt · Last modified: 2024/02/20 08:15 by 127.0.0.1