Results for “cz_populators”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CZ_POPULATORS is a Configurator (CZ) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores product-structure Populators. A Populator defines the rules and query logic by which the Configurator engine derives, filters, and presents valid options, items, and properties for a configurable model node. It is a core metadata object in the runtime configuration model, and it drives how the Configurator resolves user selections against approved item types, item masters, and property constraints.

The table is owned by the CZ schema. In the documented 12.2.2 physical schema it contains 32 columns. Its primary key is CZ_POPULATORS_PK on POPULATOR_ID, with the unique index also documented across POPULATOR_ID and ZD_EDITION_NAME, reflecting EBS 12.2.2 editioning support. Heuristically, the FK topology classifies CZ_POPULATORS as satellite-leaning: it hangs off parent anchors (CZ_PS_NODES, CZ_FILTER_SETS) and carries descriptive, rule-oriented attributes rather than acting as a pure association link.

Key Information Stored

The surrogate primary key is POPULATOR_ID. Business-key candidates are captured by the unique index on POPULATOR_ID and ZD_EDITION_NAME (the edition-scoped identity used by 12.2 online patching). Other significant columns include:

• NAME and DESCRIPTION — user-facing identity of the Populator.
• OWNED_BY_NODE_ID — FK to CZ_PS_NODES; identifies the product-structure node that owns this Populator.
• FILTER_SET_ID — FK to CZ_FILTER_SETS; the filter set applied when the Populator evaluates candidates.
• RESULT_TYPE — defines the kind of result the Populator returns (item, item type, property, etc.).
• FEATURE_TYPE, VIEW_NAME, QUERY_SYNTAX — the feature/query definition used to resolve candidates.
• HAS_LEVEL, HAS_DESCRIPTION, HAS_PROPERTY, HAS_ITEM_TYPE, HAS_ITEM — flags controlling which result attributes are populated.
• PERSISTENT_POPULATOR_ID — links the runtime Populator to its persistent definition.
• XFR_GROUP, SRC_APPLICATION_ID, SEED_DATA_FLAG, SEEDED_FLAG — provenance and cross-application transfer metadata.
• DELETED_FLAG, EFF_FROM, EFF_TO, EFF_MASK, SECURITY_MASK — lifecycle, effective-dating, and visibility controls.
• LAST_GENERATION_DATE, CHECKOUT_USER, ZD_EDITION_NAME, and the standard WHO columns.

Common Use Cases and Queries

Typical scenarios include diagnosing why a model node presents an incorrect option set, auditing seeded versus user-defined Populators, and reporting which Populators back a given model. A representative join resolves a Populator to its owning node and filter set:

• SELECT p.POPULATOR_ID, p.NAME, n.NODE_ID, f.FILTER_SET_ID FROM CZ.POPULATORS p JOIN CZ.CZ_PS_NODES n ON p.OWNED_BY_NODE_ID = n.NODE_ID JOIN CZ.CZ_FILTER_SETS f ON p.FILTER_SET_ID = f.FILTER_SET_ID WHERE p.DELETED_FLAG = 'N';
• Inventory of seeded Populators: SELECT POPULATOR_ID, NAME, SEED_DATA_FLAG, SEEDED_FLAG FROM CZ.CZ_POPULATORS WHERE SEEDED_FLAG = 'Y';
• Reverse lookup of Populators referenced by node mappings: SELECT * FROM CZ.CZ_POPULATORS p, CZ.CZ_POPULATOR_MAPS m WHERE p.POPULATOR_ID = m.POPULATOR_ID;

EFF_FROM/EFF_TO and EFF_MASK support as-of reporting, while ZD_EDITION_NAME is used to isolate the applicable edition during patching cycles.

Related Objects

• CZ_PS_NODES — parent anchor via OWNED_BY_NODE_ID; CZ_PS_NODES.FROM_POPULATOR_ID also references CZ_POPULATORS.
• CZ_FILTER_SETS — referenced through FILTER_SET_ID.
• CZ_POPULATOR_MAPS — child table referencing CZ_POPULATORS.POPULATOR_ID.
• CZ_POPULATOR_MAPS and the CZ_PS_NODES structure together form the product-structure graph the Configurator engine traverses at runtime.