{"id":724,"date":"2019-11-26T13:26:54","date_gmt":"2019-11-26T13:26:54","guid":{"rendered":"http:\/\/www.2ba.nl\/2019\/11\/26\/sales005-2\/"},"modified":"2026-03-19T12:07:14","modified_gmt":"2026-03-19T12:07:14","slug":"sales005","status":"publish","type":"post","link":"https:\/\/2ba.wimwillems.nl\/en\/documentation\/file-exchange\/file-formats\/sales005\/","title":{"rendered":"DICO (SALES005)"},"content":{"rendered":"\n

DICO<\/h1>\n\n\n
\n
\"DICO\"<\/figure>\n<\/div>\n\n\n

The DICO Standaard (formerly SALES Standaard) is the messaging standard for communication between chain parties in the construction and installation industries. This documentation is a supplement to the original format description of the Ketenstandaard Bouw en Techniek.<\/p>\n\n\n\n

DICO SALES005 is the successor to INSBOU004.<\/p>\n\n\n\n

Mapping<\/h3>\n\n\n\n

2BA ensures that the data pool complies with the Dutch standards of Ketenstandaard Bouw en Techniek and GS1. The supporting exchange formats are allocated to the internal fields of the data model. Some internal fields may vary in length or type as described in the guideline of the exchange formats.<\/p>\n\n\n\n

Mapping DICO SALES005<\/h5>\n\n\n

<\/i> Product message<\/a>
<\/i> Trade Item message<\/a>
<\/i> Item relationship message<\/a>
<\/i> ETIM version<\/a>
\n<\/i> Attachment type<\/a>
\n<\/i> Attachments attributes<\/a>
\n<\/i> Product certificats<\/a>
<\/i> Product status code<\/a>
<\/i> Trade item status code<\/a>
\n<\/i> Packaging codes<\/a>
\n<\/i> Delivery time<\/a>
<\/i> Type of item relationship<\/a>

\n<\/i> Refurbished, used trade items (DataUDEv2)<\/a>
\n<\/i> Rental trade items (DataUDEv2)<\/a><\/p>\n\n\n

Ketenstandaard Bouw en Techniek (Chain Standard Construction and Engineering)<\/h5>\n\n\n\n

For the full documentation of the DICO standard, we refer you to the Ketenstandaard Bouw en Techniek<\/a>. They issue XSD diagrams, the list of functional features and support for all DICO messages. You need to be a member of Ketenstandaard or your organisation needs to have a 2BA-ETIM combination contract with 2BA.<\/p>\n\n\n\n

Valid data sets<\/h5>\n\n\n\n

DICO messages must be validated without errors according to the accompanying scheme. Ketenstandaard Bouw en Techniek offers a validate tool<\/a> (login required) for this purpose within the website.<\/p>\n\n\n\n

\n\n\n\n

Item message header<\/h3>\n\n\n\n

Example header of the DICO item message:<\/p>\n\n\n\n

\n<PriceCatalogue xmlns:xs="http:\/\/www.w3.org\/2001\/XMLSchema" xmlns="http:\/\/www.ketenstandaard.nl\/artikelbericht\/SALES\/005" xmlns:exs="http:\/\/www.ketenstandaard.nl\/SALES\/Extensies" xmlns:xsi="http:\/\/www.w3.org\/2001\/XMLSchema-instance" xsi:schemaLocation="http:\/\/www.ketenstandaard.nl\/artikelbericht\/SALES\/005 Artikelbericht_SALES005.xsd">\n    <PriceCatalogueNumber>cataogusnummer10<\/PriceCatalogueNumber>\n    <MessageDate>2019-11-11<\/MessageDate>\n    <PriceChangeIndicator>false<\/PriceChangeIndicator>\n    <Currency>EUR<\/Currency>\n    <MutationCode>4<\/MutationCode>\n     <Datapool>\n            <GLN>8714252005929<\/GLN>\n    <\/Datapool>\n    <Manufacturer>\n        <GLN>8714252005929<\/GLN>\n    <\/Manufacturer>\n    <Grouping>\n        <Supplier>\n            <GLN>8714252005929<\/GLN>\n        <\/Supplier>\n<\/pre><\/div>\n
\n\n\n<\/p>\n\n\n<\/p>\n
Important notes:<\/h5>\n
\n\n\n<\/p>\n\n\n<\/p>\n
    \n\n
    <\/p>\n
  1. Buyer<\/b> not required.<\/li>\n
    \n\n<\/p>\n
    \n\n<\/p>\n
  2. Data Pool<\/b> GLN from 2BA or InstallData.<\/li>\n
    \n\n<\/p>\n
    \n\n<\/p>\n
  3. Manufacturer<\/b> not required.<\/li>\n
    \n\n<\/p>\n
    \n\n<\/p>\n
  4. Grouping<\/i>, required. This element can be repeated if item records of varying GLNs have to be delivered.<\/li>\n
    \n\n<\/p>\n
    \n\n<\/p>\n
  5. The NAW information is not necessary here.<\/li>\n
    \n\n<\/p>\n
    \n\n<\/p>\n
  6. Attachments and certificates at header level will not be imported.<\/li>\n
    \n\n<\/p><\/ol>\n
    \n\n\n<\/p>\n\n\n<\/p>\n
    \n\n\n<\/p>\n\n\n<\/p>\n
    Product message header<\/h3>\n
    \n\n\n<\/p>\n\n\n<\/p>\n
    Example header of the DICO product message:<\/p>\n
    \n\n\n<\/p>\n\n\n<\/p>\n
    \n<ProductData xmlns:xs="http:\/\/www.w3.org\/2001\/XMLSchema"\n             xmlns="http:\/\/www.ketenstandaard.nl\/productgegevens\/SALES\/005.1"\n             xmlns:exs="http:\/\/www.ketenstandaard.nl\/SALES\/Extensies"\n             xmlns:xsi="http:\/\/www.w3.org\/2001\/XMLSchema-instance"\n             xsi:schemaLocation="http:\/\/www.ketenstandaard.nl\/productgegevens\/SALES\/005.1 Productgegevens_SALES005.xsd"><\n    <MessageNumber>P45789<\/MessageNumber>\n    <MutationCode>9<\/MutationCode>\n    <MessageDate>2019-01-05<\/MessageDate>\n    <ETIMVersion>\n         <VersionNumber>DYNAMIC<\/VersionNumber>\n         <IssueDate>2018-10-11<\/IssueDate>\n    <\/ETIMVersion>\n    <Supplier>\n       <GLN>8714252005929<\/GLN>\n    <\/Supplier>\n    <Datapool>\n        <GLN>8714252005929<\/GLN>\n    <\/Datapool>\n    <Manufacturer>\n        <GLN>8714252005929<\/GLN>\n    <\/Manufacturer>\n<\/pre><\/div>\n\n\n\n\n\n<\/p>\n
    Important notes:<\/h5>\n
    \n\n\n<\/p>\n\n\n<\/p>\n
      \n\n
      <\/p>\n
    1. Buyer<\/strong> not required.<\/li>\n
      \n\n<\/p>\n
      \n\n<\/p>\n
    2. Supplier GLN<\/strong> for the supplied batch.<\/li>\n
      \n\n<\/p>\n
      \n\n<\/p>\n
    3. Data Pool GLN<\/strong> from 2BA or InstallData.<\/li>\n
      \n\n<\/p>\n
      \n\n<\/p>\n
    4. Manufacturer<\/strong> not necessary, the GLN at record level will be used.<\/li>\n
      \n\n<\/p>\n
      \n\n<\/p>\n
    5. The address information is not necessary here.<\/li>\n
      \n\n<\/p>\n
      \n\n<\/p>\n
    6. Attachments and certificates at header level will not be imported.<\/li>\n
      \n\n<\/p><\/ol>\n
      \n\n\n<\/p>\n\n\n
      \n\n\n\n<\/p>\n
      Type of dataset<\/h3>\n
      \n\n\n<\/p>\n\n\n<\/p>\n
      2BA supports DICO complete or update and mutation files. A complete dataset should contain all active products. The fact is that a new, complete file overwrites all records in the database<\/span>! Use MutationCode<\/strong> to define the dataset as a complete or mutation file.<\/p>\n
      \n\n\n<\/p>\n\n\n<\/p>\n
      Existing product records not present in the complete file will be given status code 130 – ‘lapsed product’. Existing trade data not present in the complete file will be deleted.<\/p>\n
      \n\n\n<\/p>\n\n\n<\/p>\n
        \n\n
        <\/p>\n
      1. Mutation code9: complete file.<\/li>\n
        \n\n<\/p>\n
        \n\n<\/p>\n
      2. Mutation code4: mutation file.<\/li>\n
        \n\n<\/p><\/ol>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
        We recommend working with complete datasets. By working with complete datasets, the published data remains most similar to your source data. If you have such a large range with a large number of attachments and regular changes, we recommend mutation files and periodically publishing a complete file.<\/p>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
        \n\n\n




        \n\n\n<\/p>\n
        ETIM Classification<\/h3>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
        Country specific features<\/h5>\n
        \n\n\n\n<\/p>\n
        \nWith the introduction of ETIM version 8 it is possible to communicate country-specific features. This functionality is supported from DICO SALES005.1.<\/p>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
        ETIM version listing<\/h5>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
        According to the SALES005 product message documentation, a value of up to 35 characters can be specified for the ETIM version. The data model supports up to 10 characters for the ETIM version. See the mapping of the ETIM version versus data model here<\/a>.<\/p>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
        Reason no value<\/h5>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
        According to the ETIM guideline, if a value cannot be allocated, the data supplier has the option of using a minus sign. 2BA does not recognise values with a minus sign. Instead, use one of the following reasons:<\/p>\n
        \n\n\n<\/p>\n\n\n<\/p>\n
          \n\n
          <\/p>\n
        1. NA; Not applicable (this feature is not applicable in the context of a product in this class).<\/li>\n
          \n\n<\/p>\n
          \n\n<\/p>\n
        2. MV; Missing value (an alphanumerical feature is relevant, but there is no correct value in this ETIM version).<\/li>\n
          \n\n<\/p>\n
          \n\n<\/p>\n
        3. UN; Unknown (the data supplier can specify no value at present; but it is possible in principle).<\/li>\n
          \n\n<\/p><\/ol>\n
          \n\n\n<\/p>\n\n\n<\/p>\n
          \n\n\n<\/p>\n\n\n<\/p>\n
          Status code<\/h3>\n
          \n\n\n<\/p>\n\n\n<\/p>\n
          There is also a mutation code at line level in the model. This value cannot<\/u> be delivered with the DICO standard. There is however a mutation code at file level (for both the item and the product message). A status code has also been defined at line level. The combination of the two codes is interpreted as follows:<\/p>\n
          \n\n\n<\/p>\n\n\n<\/p>\n
          Type of dataset: mutation (4):<\/span><\/p>\n
          \n\n\n<\/p>\n\n\n<\/p>\n
            \n\n
            <\/p>\n
          1. Read all product records with mutation code: 3 (modify).<\/li>\n
            \n\n<\/p>\n
            \n\n<\/p>\n
          2. Item records with status code 125, 94E to mutation code: 3 (modify).<\/li>\n
            \n\n<\/p>\n
            \n\n<\/p>\n
          3. tem records with status code 130 to mutation code: 2 (delete).<\/li>\n
            \n\n<\/p><\/ol>\n
            \n\n\n<\/p>\n\n\n<\/p>\n
            Type of dataset: complete (9):<\/p>\n
            \n\n\n<\/p>\n\n\n<\/p>\n
              \n\n
              <\/p>\n
            1. Read all items with mutation code (model): 1 (add\/new).<\/li>\n
              \n\n<\/p>\n
              \n\n<\/p>\n
            2. Read all products with mutation code (model) 1: (add\/new).<\/li>\n
              \n\n<\/p><\/ol>\n
              \n\n\n<\/p>\n\n\n<\/p>\n
              \n\n\n



              \n\n\n<\/p>\n
              Logistics Information<\/h3>\n
              \n\n\n<\/p>\n\n\n<\/p>\n
              The item message refers you to the EANCOM 7065<\/a> list for packaging codes. This list is not<\/span> included in the XSD diagram. Since the list contains many double forms, irrelevant to the sector, it was decided to use a selection from the list.<\/p>\n
              \n\n\n<\/p>\n\n\n<\/p>\n
              If a code is missing and there is no alternative available, you can request 2BA to add this code. Such a request will also be submitted to ETIM International for the exchange format BMEcat 2005 ETIM Guidelines.<\/p>\n
              \n\n\n<\/p>\n\n\n
              <\/i> Mapping Packaging codes<\/a>
              <\/p>\n\n\n<\/p>\n\n\n<\/p>\n
              Important notes:<\/h5>\n
              \n\n\n<\/p>\n\n\n<\/p>\n
                \n\n
              1. If the number of packaging parts is greater than one, the packaging dimensions submitted will apply for all packaging parts.<\/li>\n\n <\/ol>\n\n\n\n
                \n\n




                \n\n\n
                Price details<\/h3>\n\n\n
                For each item it can be defined how the item can be ordered, on which unit the price is based, which discount group the item falls into and how the item can be used.<\/p>\n\n
                DICO (SALES005) supports up to 100 prices per item. Future prices can be added to the catalogue message where the start date of the price  is in the future. When multiple prices are available per item, an export will include this element multiple times in the catalogue message.<\/p>\n
                \nYou cannot remove previously specified future prices from the data pool. If you want to correct a future price, you can submit a new future price with the same effective date as that of the \u201cincorrect\u201d price. The old future price is then overwritten.<\/p>\n\n
                Important note:<\/h5>\n\n\n