The ERP profile, as the common EDI profile of Pranke’s partners – both Retail Management Systems and ERP Systems, is available for download in both English and German.

EDIFACT-Specifications for Retail Management-, and ERP Systems.


ERP profile

Beginning with version 2.0 of the ERP EDI profile, several hundred actual and several thousands of potential installations can be reached, both on retail and supplier side. By this it has an equal importance as the profiles of the big cooperations or retail chains.

This profile can be used free of charge by enterprises in retail and production industry. The detailed conditions can be found in the Copyright / Contact document (Chapter IV, Appendix).

The use of the profile is open to new partners at any time.



Sorry, this entry is only available in Deutsch.

Gemäß der ZUGFeRD-Spezifikation sind EDIFACT INVOIC mit den BGM-Qualifiern 380, 84 und 389 zulässig.

Für Pranke Elektronische Rechnung (PER)  werden Gutschriften vom Typ 381 in Rechnungskorrekturen vom Typ 380 umgewandelt.

Auszug aus “Das ZUGFeRD-Format_1p0.pdf”:

891  5.1 Definierte Rechnungsarten
892  Es werden bei ZUGFeRD die folgenden Rechnungsarten unterstützt:
893  ZUGFeRD Basic
894  • Handelsrechnung (Rechnung für Waren und Dienstleistungen) mit dem Code 380
895  • Bescheide (z. B. Zahlungsaufforderung von Behörden) mit dem Code 380
896  Kaufmännische Gutschrift (z.B. Rechnungskorrektur/Storno) mit negativen Werten (Code 380)
897  In ZUGFeRD Comfort zusätzlich:
898  • Wertbelastung/Wertrechnung ohne Warenbezug (Code 84)
899  • Wertgutschrift ohne Warenbezug mit negativen Werten (Code 84)
900  In ZUGFeRD Extended zusätzlich:
901 • Selbst ausgestellte Rechnung (Steuerrechtliche Gutschrift/Gutschriftsverfahren, Code 389)
902  • Selbst ausgestellte Gutschrift mit negativen Werten (Code 389)


IT terms
Cross Docking Procedure in which goods pre-picked for a final destination in a distribution warehouse are only redistributed at package level.
CRP program The Cyclic Replenishment Program is a procedure for the regular replenishment of articles.
EAN The international (formerly European) article number is an internationally unique article identification.
EANCOM A subset of EDIFACT, carried by EAN.UCC, specifically for retail and consumer goods.
EAN International The umbrella organisation for the allocation of article and company identifications looks after various standards, including EANCOM.
EAN.UCC The umbrella organization of EAN International and UCC.
EDI Electronic Data Interchange is a generic term for the structured exchange of data between applications.
EDIFACT Electronic Data Interchange For Administration, Commerce and Transport is an internationally standardized basic standard of EDI, supported by UN and ISO.
GLN The Global Location Number is an internationally unique identification of a company and is assigned by the EAN.UCC.
GTIN The Global Trade Item Number is the successor of the EAN and UPC.
Material EDI The profile of the DTB for data exchange between producer and supplier.
NCTS The New Computerized Transit System is a computerized transit system in Europe in connection with customs.
PLV The passive contract processing.
SSCC The Serial Shipping Container Code is an EAN package identifier.
Subset A subrange of a standard, e.g. EANCOM from EDIFACT.
UPC The Universal Product Code is an equivalent of the EAN in the USA.
VAN The Value added network is a value-added service, i.e. networks with additional services to the pure connection.
WWS profile EANCOM application profile for lifestyle retail
XML/EDI Electronic Data Interchange using eXtensible Markup Language describes electronic data interchange using XML or approaches such as ebXML, Bizztalk, but not yet a standard.

There are a number of commercial editors for EDIFACT messages. A free editor is also sufficient.

Notepad++ has proved its worth. This makes it easy to insert a line break after the segment separator to make the file easier to read.

In this case, it is preferable to record a macro inside Notepad++ that performs the search and replace of the quotation mark with quotation mark and line-switching to keyboard shortcuts.

In the FAQ How to highlight EDIFACT segments? in color is also mentioned how to highlight EDIFACT segments in color.


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.


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


For reading Edifact files, you can use the free editor Notepad++.

It supports the creation of your own language definitions.

We did this for Edifact and provide this language definition file.


It is common practice in the industry to sell lots. Normally, the pre-order phase is interactive between buyer and seller. With EDI, the lots in the ORDRSP are then resolved directly and treated individually. Some manufacturers also have EANs for these shopping lots, but these do not usually appear in the messages.

There are possibilities to process this lot topic in some enterprise resource planning systems. However, this usually only takes place in close cooperation with, for example, Intersport dealers with the dedicated Intersport merchandise management solution.

See also: 7143 Item ty43 Item type identification code (Code: SG)



In all UN/EDIFACT Interchanges (UNA:+.? ‘) defines the separators as the first Advise segment of the message. The colon (:) becomes the Component Separator, the plus sign (+) becomes the Separator element, the dot (.) becomes the decimal separator, the question mark (?) becomes the Release Indicator, the space sign (invisible white space) remains a space, and the apostrophe () is the Terminator segment.

In the EDIFACT subset EANCOM, four special characters (extracted from UNOA) have a special meaning and serve as default separators for EANCOM:

  • Apostroph = Segment Separator
  • Plus sign + = separator between segment identifiers and data elements contained therein.
  • Colon : = Separator within a data element group.
  • Question mark ? = Release character; if the question mark is immediately before one of the service characters, this character regains its normal meaning. For example, 10?+10=20 means 10+10=20. A question mark is represented by ??

If the trading partners agree on the use of the character sets B to F (inclusive) and the standard separators, the UNA segment must be used to explicitly indicate the use of the standard separators.

Further information on the UNA segment can be found at

UNA, Service String advice

Function: To define the characters selected for use as delimiters and indicators in the rest of the interchange that follows:
The specifications in the Service string advice take precedence over the specifications for delimiters etc. in segment UNB. See clause 4.

When transmitted, the Service string advice must appear immediately before the Interchange Header (UNB) segment and begin with the upper
case characters UNA immediately followed by the six characters selected by the sender to indicate, in sequence, the following functions:

Type & LengthCardinality NameRemarks
alpha numeric, 1 mandatoryCOMPONENT DATA ELEMENT SEPARATOR
alpha numeric, 1 mandatoryDATA ELEMENT SEPARATOR
alpha numeric, 1 mandatoryDECIMAL NOTATIONComma or full stop
alpha numeric, 1 mandatoryRELEASE INDICATOR
alpha numeric, 1 mandatory
alpha numeric, 1 mandatorySEGMENT TERMINATOR