Loading

Passport Category Mappings

A Passport Category Mapping explains how Actualog records supply the requirements of a Passport Profile. It connects a category and its approved effective template to a particular profile edition. It is a reusable definition, rather than a passport for one product.

For example, a mapping can obtain nominal capacity from an approved Product Release, the manufacturing period from the selected Production Batch, and the serial number from the selected Product Instance. Each resulting value retains its source information.

Categories remain the source taxonomy

Actualog's product categories and inherited attributes remain the basis for product classification and templates. A passport mapping does not create a parallel product taxonomy. Attributes and declarations determine applicable profile outcomes; a category name alone may be insufficient.

The mapping must match the subject's category and approved template. A family mapping can be explicitly inherited into descendants. A leaf mapping can override an inherited binding only when the override is declared. Competing inherited bindings produce an issue rather than an arbitrary choice.

What a field binding contains

Each binding selects a destination requirement, a source scope and a named field or attribute. It also specifies expected units and a supported transformation or lookup. Source scopes include approved product information, batch parameters, instance information, evidence, observations and other supported records.

Model characteristics come from the approved release. Batch facts come from that batch. Individual observations describe that instance. Choosing the newest unrelated value is not a substitute for selecting the correct source scope.

Who maintains mappings and where

Application administrators maintain category mappings in Profiles and mappings. Company users select a compatible approved mapping when preparing a passport at the profile's exact Model, Batch or Item level. Supporting batch or instance bindings are used only when the requirement and selected subject make them applicable.

  1. Open the mappings list and search by name or category.
  2. Create a category mapping edition for the intended profile.
  3. Select the category and approved effective template by name.
  4. Add typed field bindings and any explicit inherited overrides.
  5. Save and inspect Coverage, template impact and sample preview before activation.

An activated edition is immutable. Create a new category mapping edition for a correction or changed template contract.

Blockers and maintenance

Missing required bindings, incompatible units, unavailable attributes, conflicting inheritance and ambiguous applicability must be corrected before publication. The profile must also be active. A new product template or unit definition can require a successor mapping; it must not rewrite historical publications.

Review field lineage in the sample preview. If several sources appear to satisfy one requirement, determine the intended authoritative subject and evidence rules instead of weakening validation. Passport mappings and external channel mappings are maintained independently because their destinations and approvals differ.

Related topics: Passport Profiles, Creating Digital Product Passports, Channel Requirement Profiles.