eBiss 3

Hilfe & Dokumentation

User Tools

Site Tools



eBiss is a system 1) for exchanging data between applications inside and outside their own enterprise. It supports the integration of different WWS applications through its comprehensible real-time data transfer and can be used for highly flexible applications in IT departments as well as in predefined integrated processes. With eBiss, there is a separation between IT staff and users, that is, Users can easily manage their own processes without the need for IT staff.

Typical process

The following diagram illustrates the typical processes 2) in eBiss in a simplified way.

Note: This is described in detail in the HowTo Set up a data link with conversion.


In order to be able to respond as flexibly as possible to customer requirements and still not have to create individual mappings for each customer, we at Pranke GmbH are pursuing with eBiss the strategy with the so-called two-stage transformation3). This provides that the INHOUSE interface is ideally always operated or queried with only one mapping4) and individual adaptations are only made in partner specific mappings from EDIFACT5) to the middleware or from middleware to EDIFACT6) if necessary.

  • Outgoing processing
    • from INHOUSE to MiddleWare preferably only one mapping(1 to 1)!7)
    • from MiddleWare to EDIFACT8) any number of mappings(1 to N)9)
  • Incoming processing
    • from EDIFACT10) to MiddleWare any number of mappings(N to 1)11)
    • from MiddleWare to INHOUSE preferably only one mapping(1 to 1)12)

Scheme of the two-stage transformation

The philosophy of eBiss usually recommends the use of MiddleWare13) Abstraction Layers. This means that all incoming and outgoing messages pass through two mappings connected in series. This is shown in the above diagram by the transformers. It can be understood in detail as shown in the following sequence diagram.

HOST->eBiss:Message(INHOUSE-OUTBOUND)Format note left of eBiss: fixed Mapping eBiss->eBiss:transform INHOUSE-OUTBOUND to eBiss.MiddleWare note left of eBiss: variable Mapping eBiss->eBiss:transform eBiss.MiddleWare to EDIFACT eBiss->PARTNER:Message(EDIFACT-OUTBOUND)Format PARTNER->eBiss:Message(EDIFACT-INBOUND)Format note left of eBiss: variable Mapping eBiss->eBiss:transform DIFACT-INBOUND to eBiss.MiddleWare note left of eBiss: fixed Mapping eBiss->eBiss:transform eBiss.MiddleWare to INHOUSE-INBOUND eBiss->HOST:Message(INHOUSE-INBOUND)Format


see also: EAI or A2A
It should be noted that the presentation describes the process for incoming and outgoing messages, which is usually displayed separately
Incoming from external format to canonized middleware and from middleware to internal format. Starting from internal format to middleware and from middleware to external format
Depending on the message direction.
5) , 6) , 8) , 10)
or other external formats
7) , 12)
Only in the absolute exceptional case you need several mappings here.
9) , 11)
Depending on specific partner requirements, in minimum one standard mapping.
The eBiss MiddleWare represents an abstraction layer between EDIFACT and custom INHOUSE message structure and allows to minimize the total number of mappings required and the maintenance effort. There are MiddleWare versions for manufacturers and retailers.
en/ueberblick/start.txt · Last modified: 2024/02/20 08:15 by