====== Partner not identifiable===

==== Problem: ====

When sending or receiving messages, the partner can not be identified.
==== Possible cause: ====

  - One reason for the problem can be, among other things, a wrong communication direction. The direction must correspond to the direction of the business process.((
^ Name ^ Meaning |
| // Outbound // | All messages to be sent by SystemPartner to TradingPartner. |
| // Inbound // | All messages to be sent by the TradingPartner to the SystemPartner. |
))
  - The constellation from type definition((Possibly also wrong RecordTag setting for CSV formats.)) with frame attributes and the analyzer setting do not correlate with each other.
==== Solution: ====

To solve the problem please proceed as follows:

  - Check the tasks for their content, there should be an indication of the not found identification.
  - Check whether the data type used the corresponding frame variables (MapFrameSender, etc.)
  - Check whether the correct recognizer or analyzer is used.
  - Check whether the direction of the documents (Inboud / Outbound) is set correctly.
  - For incoming EDIFACT messages, check whether the GLNs in the UNB segment are correct.