Import Formats & Mapping Systems

PXM separates mapping configurations into three primary mapping systems: Flat Mapping, Hierarchy Mapping, and Fixed Predefined Formats.

---

Flat Mapping (CSV / Excel)

Used for files structured as tabular lists of records (such as standard spreadsheets or tabular databases). Each column in the source file is mapped to a specific property on the target PXM entity.

CSV/Excel File ---> Flat Mapping ---> Java Objects (JSON Preview) ---> PXM Command File ---> DB Ingestion

Transformation Rules

You can apply simple transform chains to format and normalize incoming column data on-the-fly:

• Case Conversion: Automatically switch input to uppercase or lowercase.
  • Example: Catalog ID -> transform "upper case" -> product.catalogId
• String Appending: Append suffixes or prefixes.
  • Example: Status ID -> transform "append '00'" -> product.statusId

Overwrite Parameters

Overwrite parameters provide fine-grained control to conditionally alter fields during import. They are stored as an OverwriteFieldEntry array in the JobParameters of the Import Channel.

Standard supported override fields:

Field Name	Type	Description	Example Value
supplierId	String	Overwrite the target Supplier	"demoSupplier"
catalogId	String	Overwrite the target Catalog	"MasterCatalog"
contractId	String	Overwrite the target Contract	"standard-pricelist-DE"

Two execution modes are supported:

• Overwrite Always: The parameter in the import file is always replaced with the override value, regardless of whether it is already populated in the file.
• Overwrite If Empty: The parameter is overridden only if the field is missing or empty in the import file.

---

Hierarchy Mapping (XML / JSON)

Used for complex, nested hierarchical datasets. You map elements using standard FreeMarker templating inside a visual schema workspace.

XML/JSON File ---> FreeMarker Template ---> Target Command JSON ---> DB Ingestion

The Hierarchy Mapping Editor

The mapping workspace consists of four key sections:

1. Source Schema: A tree representation based on your XSD or JSON schema. Clicking fields injects their path expressions into the mapping template.
2. Target Schema: Displays the structural design of the PXM internal models (Product, Prices, Attribute Sections).
3. Mapping Template Editor: A workspace where you write FreeMarker templating scripts to translate source paths into the target PXM JSON structure.
4. Result / Preview: Runs the template on a sample payload to provide immediate feedback, alerting you to errors before launching the import job.

Simple Mapping Template Example:

{
  "productId": "${SourceSchema.product.id}",
  "catalogId": "${SourceSchema.catalogNumber}",
  "supplierId": "${SourceSchema.supplier.id}",
  "statusId": 100,
  "attributeValues": [
    <#list SourceSchema.product.description as desc>
      {
        "attribute": "Description",
        "language": "${desc.Language}",
        "values": [
          "${desc.value}"
        ]
      }<#sep>,</#sep>
    </#list>
  ]
}

---

Predefined Standard Mapping Formats

PXM includes specialized fixed parsers for key industry-standard formats:

1. ECLASS

A cross-industry standard for the classification and description of products and services.

• Import File Requirements: A .zip archive containing the standard ECLASS CSV files for Groups, ValueLists, ValueListItems, and Attributes.

• System Labels: For ECLASS version 12, the import classification must be labeled as ECLASS12 (or format ECLASS<version>).

• Defaults: The default import settings assume ECLASS12 as the classification and de-DE as the language. You can override these defaults in the Import Channel configuration if you are importing other variants (e.g., ECLASS10 in en-US).

• Database Setup: You must execute standard SQL scripts located at ./pxm/import/ECLASS within your workarea to insert standard unit of measure entries and descriptions before starting.

  [!IMPORTANT] After running SQL insertions, you must reload the system cache: Navigate to Settings → Data Storages → Click Reload Cache.

2. ETIM

A global classification standard for technical products in electrical, HVAC, and plumbing sectors.

• Import File Requirements: A .zip archive containing standard ETIM CSV files for Groups, ValueLists, ValueListItems, and Attributes.
• System Labels: For ETIM version 9, ensure your classification is labeled as ETIM9 (or format ETIM<version>).
• Defaults: The system default is ETIM9 using language de-DE. Alternate ETIM classifications and target languages can be specified as overrides in your channel setup.
• Database Setup: Execute the provided ETIM SQL helper scripts located at ./pxm/import/ETIM on your workarea to populate the Unit of Measures.

3. TecDoc

The leading data standard for the automotive aftermarket spare parts industry.

• Import File Requirements: A .zip archive containing .dat files conforming to the TecDoc version 2.7 standard.
• Required Files: The archive must contain the following core files:
  • TEC_DOC_27_AXLE
  • TEC_DOC_27_BASIC
  • TEC_DOC_27_CAR
  • TEC_DOC_27_CV
  • TEC_DOC_27_CV_PRODUCER_ID
  • TEC_DOC_27_DRIVING_CAB
  • TEC_DOC_27_ENGINE
  • TEC_DOC_27_GENERIC_ARTICLE
  • TEC_DOC_27_TRANSMISSION
• Validation: Ensure files are correctly formatted and named. If errors occur, inspect file encoding and make sure all nine core tables are present in the archive.