QANATIX
Data Ingestion

XML Catalogs

Ingest BMEcat catalogs and SAP IDoc XML.

XML Catalogs

QANATIX parses enterprise XML formats natively — BMEcat product catalogs and SAP IDoc master data.

BMEcat

Upload BMEcat XML catalogs (standard format for B2B product data exchange in Europe):

curl -X POST https://api.qanatix.com/api/v1/ingest/manufacturing/product/upload \
  -H "Authorization: Bearer sk_live_abc123..." \
  -F "file=@catalog.xml"

QANATIX parses ARTICLE elements and maps fields to vertical_data:

  • SUPPLIER_AIDpart_number
  • DESCRIPTION_SHORTname
  • ARTICLE_PRICEprice
  • All other fields preserved in vertical_data

SAP IDoc

QANATIX auto-detects SAP IDoc XML and parses it with type-specific extractors.

curl -X POST https://api.qanatix.com/api/v1/ingest/manufacturing/material/upload \
  -H "Authorization: Bearer sk_live_abc123..." \
  -F "file=@matmas_export.xml"

Supported IDoc types

IDoc TypeDescriptionEntity mapping
MATMASMaterial mastername = MAKTX, material_number = MATNR, material_type = MTART
DEBMASCustomer mastername = NAME1, customer_number = KUNNR, country = LAND1
CREMASVendor mastername = NAME1, vendor_number = LIFNR

Unknown IDoc types

IDoc types not in the list above are parsed generically — all segments and fields are preserved in vertical_data.segments. Nothing is lost.

{
  "name": "ZCUSTOM IDoc 0000000003",
  "vertical_data": {
    "idoc_type": "ZCUSTOM",
    "doc_number": "0000000003",
    "segments": {
      "Z1DATA": [{"FIELD1": "Value1", "FIELD2": "Value2"}]
    }
  }
}

Auto-detection

QANATIX detects IDoc XML automatically by looking for <IDOC> and <EDI_DC40> elements. You don't need to specify the format — just upload the file.

On this page