Journeys

Journey

All journeys

Customer part number mapped to internal PN

An inbound customer feed uses its own CPN scheme — mapped once, resolved everywhere after.

Integrator Line lead
Slug
cpn-mapping
Steps
3
Steps live
3 / 3

Steps

  1. Mapping editor Step 1

    CON-04 field transforms normalize the feed — the CPN field still needs an internal PN mapping

    S3 · Integration Studio
  2. CPN mappings Step 2

    CPN↔PN mapping UI: FlexZala CPN bound to the internal PN, ambiguous matches flagged

    S2 · Produce
  3. Work orders Step 3

    Work-order BOM lines resolve the customer CPN to the internal PN automatically

    S2 · Produce