Posts

What is Pranke eBiss?

Pranke eBiss is a software for electronic data interchange (EDI) and the seamless integration of enterprise applications (EAI).
It was developed to simplify the integration of various ERP applications, as well as other processes.

What does Pranke eBiss stand for?

Pranke eBiss combines internal and external processes.
Companies are able to bring together a wide range of areas such as ERP, merchandise management, logistics, financial accounting and much more under one roof. And of course the converter can also do EDI, as that is how everything started.

Reduce interfaces

Pranke eBiss replaces numerous interfaces and thus creates a concise IT landscape. Error sources are eliminated. Important operating environments are coordinated, resources are unblocked.

Two-level mapping

The principle of two-step mapping is simple to understand.
Imagine a converter that transforms data from one format to another. For example, from an in-house format to middleware, which is what we call the Pranke eBiss format.
First we formulate the general rules of how data should be “translated”. These rules are the same for all trading partners and serve as the basis for the conversion.
They ensure that all data is correctly interpreted and transferred into the desired target format.

In the second mapping stage, we realise adjustments for trading partners with Pranke eBiss. These are almost always special mappings with specific requirements for the diverse in-house systems.

Advantages of the two-level mapping concept

  • Separation of general mappings and special mappings.
  • Specific requirements are implemented more easily and quickly.
  • Many mappings are already in the “pool” and do not have to be created each time.
  • When changing an ERP system or an merchandise management system, only the in-house mappings are adapted, everything else (as a rule) remains the same.

The two-stage mapping concept offers flexibility, efficiency and future-proofing for your digitisation projects.

The seamless integration of data and processes results in many advantages for your company. Instead of transferring files, interface processes around reading, writing and posting data become interconnected.

Integration, real time

The data integration in Pranke eBiss works in real time. The software links operations such as reading, writing and posting with each other.

Compliance and security

The software is able to ensure that data transmission complies with applicable regulations and security standards, which is particularly important in regulated industries.

Modules

Pranke eBiss grows with your company. New challenges? New ideas? Expand processes according to your ideas with the Pranke eBiss modules!

 

eBiss 3 can map structures into variables!

For example, if you set a selection in a rule that selects a typed value (incl. whole trees), you can save it as $$VariableName on the right-hand side. Later on, you can access this structure directly in the entire document and carry out further work with it.

For example, save the entire folder document:

Rule: /Orders => $$doc

Call it later in a mapping:

Rule: $doc/@SupplerGLN

or better and faster with the XVar function:

Rule: XVar (‘ doc’)/@SupplierGLN

or the total of the item quantities stored in the document:

Rule: sum (XVar (‘ doc’)/Items/@Quantity)

For more information, see the variables help.

 

FAQs

Question

As a rule, the containerizer generates the UNB segment. However, if the UNB segment is to be influenced in an Edifact document, the UNB segment must be triggered in the corresponding mapping with a rule record and the desired data element must be operated with a mapping rule. The remaining UNB data elements are then created/operated by the containerizer.

Attention

The default setting of the syntax version number is 3. The EDIFACT containerizer in eBiss checks the syntax version number. If it is greater 3, the date format in the UNB segment will be adapted. In addition, a * is set in UNA segment instead of a space. Finally, you must ensure that the outgoing Edifact document corresponds to the syntax version according to ISO 9735:1998

In the requested case, you need a mapping rule like in this snapshot:

UNB Segment im Mapping

UNB Segment in mapping