Below you will find the possible standard exchange formats that 2BA supports. New formats and/or versions developed by the industry are phased in and introduced in agreement with software firms, data suppliers and data customers.
Format | Import | Export | Description |
---|---|---|---|
DICO (SALES005) | Exchange format (XML) developped and managed by Ketenstandaard Bouw en Techniek. | ||
ETIM xChange V1.0 / V1.1 | Exchange format (JSON) developped and managed by ETIM International. | ||
BMECat 2005 V5.0 | Exchange format (XML) Guideline 5.0 developped and managed by ETIM International. | ||
The 2BA Webservices developped by 2BA are basic, lightweight and fast services to integrate your systems with the 2BA database. |
Format | Import | Export | Description |
---|---|---|---|
INSBOU004 | Successor of DICO (SALES005). | ||
BMECat 2005 V4.0 | Successor of BMEcat 2005 V5.0. | ||
PAB 2 | Until may ’25 |
Exchange format (ASCII) developped and managed by ETIM Nederland. |
|
AttachmentIndex | Exchange format for attachments. | ||
Koppeltabel | Exchange format (ASCII) to make references between products and trade items. | ||
ICC Condition message | Exchange format to communicate discounts or net prices on trade items. |
Based on the national character, history and compatibility, the ‘ANSI’/’Latin-1’ (officially: ISO/IEC 8859-1) drawing set ISO/IEC 8859-1) set. The Latin-1 drawing set supports West European languages (so not Hebrew, Chinese etc.) Exports from the 2BA database are coded as standard according to the Latin-1 encoding (GABI, PAB1 and PAB 2).
More information: