====== Alternative communication =======

===== alternativ adressing =====

==== Task: Messages to alternative eGate account =====

Messages of type XYZ should be sent to an alternative address((This is e.g. necessary for INVOIC to participants belonging to a buying group.))

=== Solution ===

  - Determine the alternative communication address((This is usually stored with the trading partner who is to receive the messages.)) and store it in addition to the existing one with the trading partner of the original recipient.
  - Add a new type record to the trading partner.
    - Direction = outgoing
    - Type = message type of the outgoing message.
    - Select "Addresses" and establish the communication address added under point 1 here.
    - Save these settings.

This [[en:partnerverwaltung:typset:start|type set]] causes the alternative communication address in the envelope to be applied and used as the message recipient address when containerizing the message type((As previously defined in the type set.)).

==== Task: Set messages with alternative UNB receiving address ====

Messages of type XYZ should have an alternative UNB receiving address in the message((This is e.g. necessary for INVOIC for participants belonging to a buying group.))

=== Solution ===

  - Determine the alternative Edifact UNB address((this is then a GLN different from the standard GLN)) and store it in addition to the existing one with the trading partner of the original recipient.
  - Add a new type record to the trading partner or select a suitable one.
    - Direction = outgoing
    - Type = message type of the outgoing message.
    - Select "Addresses" and establish the Edifact UNB address added under point 1 here.
    - Save these settings.

This [[en:partnerverwaltung:typset:start|type set]] causes the alternative Edifact UNB address to be used in the UNB segment when containerizing the message type((As previously defined in the type set.)).


{{:images:sign_warning.png?nolink|}}**Note:** The type sets to be created or used here are always related to outgoing messages and their document type. Thus **no** mappings are set!\\ 
Type records for mappings always contain the source type of the mapping. However, the target type must be defined for containerization.

===== alternativ communication channel =====

==== Task: send messages via a specific communication channel ====
Normally a send job is set up with an undefined [[en:prozessdefinition:jobs:jobsteps:kommunikation:channelsender|]] job object. This unspecified ChannelSender job object looks for the [[en:kommunikation:kanal:start#outgoing_communication_channels|outbound communication channel]] to be used in the partner properties and type sets. The following cascading is processed:
  - Send channel in [[en:partnerverwaltung:typset:start|type set]] **matched** with the message type to be sent
  - Transmission channel is set in the partner property
  - Transmission channel is set in the partner property of the **template partner**.


=== Solution ===
Because eBiss cascades through the partner property and type set settings two possibilities are available:
  - **Partner specific communication channels** can be set within the partner property page.
  - **Partner-specific and document-py-specific communication channels** can be set via **outbound** [[en:partnerverwaltung:typset:start|type set]]((It is therefore possible to provide dedicated trading partners with a type set set that is set to "outbound" messages and takes the specific message type into account.))

===== alternate file path =====

==== Task: Clone incoming messages to alternative logical system ====

For a new logical system, the incoming messages are to be written again as a copy to another path and the number of communication channels minimized.
The path should have the following structure:
<code>drive:\data exchange directory\logical system\message type\tradinpartnername\messages.dat</code>

=== Solution ===
  - Setting up an alternative INHOUSE message **Containerize**, which prepend the TradingPartnerName in the file name separated by a backslash((This forces the creation of the directory when creating the file.)). <code>${TradingPartnerName}\${TradingPartnerName}_${DocumentType}_${DocumentNumber}.xml</code> Unlike the standard containerizer, which "only" has the following setting :<code>${TradingPartnerName}_${DocumentType}_${DocumentNumber}.xml</code>
  - Set up a **standard communication channel** for the new logical system, specifying the base directory <code>drive:\data exchange directory\LogicalSystem\</code>
  - Representation of the new logical system in the form of a new **SystemPartner** with suitable identification.
    - Creating type records for specific types or generally using the alternative **containerizer**.
      - optional: create additional file system addresses and assign these addresses to the type set
    - Specify the new **communication channel** for this equipment.
  - optional: setting up a **variable** of type **flag** to control whether messages to the new logical system should be generated for certain trading partners.
    - if required, instantiate this variable with "True" for the desired trading partners
  - Add the following job objects in the standard inbound job below or parallel to the regular **MessageEntityCreator**:
    - optionally: **EntityIfCase** to switch the copy to the new logical system on or off
      - **EntityIfCase** to change the **system partner**((The **EntityIfCase** provides the execution of expressions))<code>SetDocumentFrameSystemPartnerByGLN("logical system GLN")</code>
      - another **MessageEntityCreator** to re-containerize with the type set properties of the new system partner