How are SAP fields like MATNR mapped?

A built-in dictionary maps common SAP, Salesforce, and Oracle fields to canonical names, so MATNR becomes materialNumber. Fields not in the dictionary are converted to camelCase with a type inferred from the field name and flagged as heuristic.

Can I use the generated schema directly in production?

Treat it as a design accelerator, not a finished contract. Confirm each mapping against source-system metadata and your canonical governance, especially rows marked heuristic in the mapping evidence.

Are my source fields sent to a server?

No. The mapping and schema generation run entirely in your browser and nothing is uploaded.

What do SAP fields such as MAKTX and MEINS become?

With SAP as the source system, the built-in dictionary maps MATNR to materialNumber, MAKTX to materialDescription, and MEINS to baseUnitOfMeasure. The mapping evidence table lists each source field with its canonical field, type, and confidence, so you can see which mappings came from the dictionary and which were inferred.

Canonical schema generator

A canonical schema defines a business entity once, with stable field names and types, so consumers do not depend on each source system's own field names.

Map SAP, Salesforce or Oracle source fields to canonical names and generate a draft JSON or YAML schema with mapping evidence. Runs in your browser.

Browser-sideNo accountCopy, download, or print

Last reviewed 30 Oct 2026

Your inputs are saved as a draft in this browser only. Nothing is uploaded.

Jump to result

Result

Source systemSAP

Canonical entityProduct360

Fields mapped6 / 6

Heuristic mappings0

Suggested mappings to accelerate design; confirm each against source-system metadata and your canonical governance before use. Heuristic mappings are derived from field names, not a data dictionary.

Mapping evidence

Source field	Canonical field	Type	Confidence
MATNR	materialNumber	string	mapped
MAKTX	materialDescription	string	mapped
MEINS	baseUnitOfMeasure	string	mapped
MATKL	materialGroup	string	mapped
MTART	materialType	string	mapped
WERKS	plant	string	mapped

JSON Schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Product360",
  "type": "object",
  "x-sourceSystem": "SAP",
  "properties": {
    "materialNumber": {
      "type": "string",
      "x-sourceField": "MATNR"
    },
    "materialDescription": {
      "type": "string",
      "x-sourceField": "MAKTX"
    },
    "baseUnitOfMeasure": {
      "type": "string",
      "x-sourceField": "MEINS"
    },
    "materialGroup": {
      "type": "string",
      "x-sourceField": "MATKL"
    },
    "materialType": {
      "type": "string",
      "x-sourceField": "MTART"
    },
    "plant": {
      "type": "string",
      "x-sourceField": "WERKS"
    }
  }
}

YAML:

$schema: "https://json-schema.org/draft/2020-12/schema"
title: Product360
type: object
x-sourceSystem: SAP
properties:
  materialNumber:
    type: string
    x-sourceField: MATNR
  materialDescription:
    type: string
    x-sourceField: MAKTX
  baseUnitOfMeasure:
    type: string
    x-sourceField: MEINS
  materialGroup:
    type: string
    x-sourceField: MATKL
  materialType:
    type: string
    x-sourceField: MTART
  plant:
    type: string
    x-sourceField: WERKS

JSON Schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Product360",
  "type": "object",
  "x-sourceSystem": "SAP",
  "properties": {
    "materialNumber": {
      "type": "string",
      "x-sourceField": "MATNR"
    },
    "materialDescription": {
      "type": "string",
      "x-sourceField": "MAKTX"
    },
    "baseUnitOfMeasure": {
      "type": "string",
      "x-sourceField": "MEINS"
    },
    "materialGroup": {
      "type": "string",
      "x-sourceField": "MATKL"
    },
    "materialType": {
      "type": "string",
      "x-sourceField": "MTART"
    },
    "plant": {
      "type": "string",
      "x-sourceField": "WERKS"
    }
  }
}

YAML:

$schema: "https://json-schema.org/draft/2020-12/schema"
title: Product360
type: object
x-sourceSystem: SAP
properties:
  materialNumber:
    type: string
    x-sourceField: MATNR
  materialDescription:
    type: string
    x-sourceField: MAKTX
  baseUnitOfMeasure:
    type: string
    x-sourceField: MEINS
  materialGroup:
    type: string
    x-sourceField: MATKL
  materialType:
    type: string
    x-sourceField: MTART
  plant:
    type: string
    x-sourceField: WERKS

How to use it

Choose the source system: SAP ERP, Salesforce, Oracle, or a generic system.
Pick the canonical entity, such as Product360 or Customer360, and the output format: JSON, YAML, or both.
Paste your source fields, one per line, such as MATNR or customer_id.
Review the mapping evidence table, then copy or download the generated schema.

Questions

How are SAP fields like MATNR mapped?: A built-in dictionary maps common SAP, Salesforce, and Oracle fields to canonical names, so MATNR becomes materialNumber. Fields not in the dictionary are converted to camelCase with a type inferred from the field name and flagged as heuristic.
Can I use the generated schema directly in production?: Treat it as a design accelerator, not a finished contract. Confirm each mapping against source-system metadata and your canonical governance, especially rows marked heuristic in the mapping evidence.
Are my source fields sent to a server?: No. The mapping and schema generation run entirely in your browser and nothing is uploaded.
What do SAP fields such as MAKTX and MEINS become?: With SAP as the source system, the built-in dictionary maps MATNR to materialNumber, MAKTX to materialDescription, and MEINS to baseUnitOfMeasure. The mapping evidence table lists each source field with its canonical field, type, and confidence, so you can see which mappings came from the dictionary and which were inferred.