Partner objects provide a way to store addresses and other partner-specific data, which are used during the processing of emails, files, attachments and compared with those of the interchanges or documents contained there. There you can specify different addresses, which are associated with the ILN / GLN stored in the partner settings. It is also possible to store several Locations for stores, stock or labels.

Three types of partners are available for the various applications ¹⁾. How the communication in detail depends on the organization of the user, on which the structure of eBiss is oriented. Below are a few examples showing different organizational forms.

The SystemPartner ²⁾ Represents the company using eBiss .

System partners must have at least one communication address and a headquarter system partnerlocations for EDI.

The trading partner ³⁾ Represents the trading partner (s).

Merchants must have at least one communication address and a headquarter system partnerlocations EDI.

The Partner template serves as a container for e.g. Standard Mappings or objects like Containerizer and communication channels , Which use a set of default mappings (defined in the parent template in the type set)). This eliminates the specific type definition for each system or trading partner for standard mappings. Only different settings are stored in the typesets of the system or trading partners.
For example, The SystemPartner is a manufacturer, the most used mappings of the WWS profile are stored with the TemplatePartner. Thus, the SystemPartner is able to access these mppings when processing messages. When e.g. Group XYZ, a document type deviating from the WWS-Profil, is displayed under Type Sets additionally stores the mapping for this deviating document type so that messages with differing documents can also be processed.