Results for “grid_id”

50+ results




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

Overview

CZ_GRID_COLS is a Configurator (CZ) module table in Oracle E-Business Suite, owned by the CZ schema and valid in both 12.1.1 and 12.2.2. Its documented role is to specify a column within an explicit compatibility grid. In the Configurator data model, an explicit compatibility grid defines, cell by cell, which combinations of option values are permitted or forbidden. CZ_GRID_DEFS establishes the grid itself, and CZ_GRID_COLS defines the vertical axes — the individual columns — that, together with rows, form the matrix of compatibility outcomes. Each row in this table therefore represents one configurable dimension of a single grid.

Because the table carries a surrogate key (GRID_COL_ID) plus effective-dating and audit columns (EFF_FROM, EFF_TO, CREATION_DATE, LAST_UPDATE_DATE, DELETED_FLAG), a Data Vault classification heuristic places it as hub-leaning: it behaves as a durable business entity (a grid column) with dependent descriptive and temporal attributes, rather than as a pure intersection or link. In practice it is best modeled as a hub with an attached satellite for its effective-dated and audit attributes.

Key Information Stored

The table contains 15 documented columns. The most significant are:

  • GRID_COL_ID — surrogate primary key, enforced by CZ_GRID_COLS_PK. Uniquely identifies each column definition.
  • GRID_ID — foreign key to CZ_GRID_DEFS; identifies the parent grid to which this column belongs. This is the principal business-scoping attribute.
  • PREV_GRID_COL_ID — self-referencing foreign key (to CZ_GRID_COLS) that orders or chains columns within a grid, supporting column sequencing or supersession.
  • DATA_TYPE — the data type of the column, governing how cell values in CZ_GRID_CELLS are interpreted.
  • EFF_FROM / EFF_TO — effective date range for the column definition, enabling date-tracked changes to grid structure.
  • DELETED_FLAG — soft-delete indicator, so historical structure can be retained while logically removing a column.
  • SECURITY_MASK / EFF_MASK — masking attributes applied at the column level.
  • CHECKOUT_USER — identifies the user who has checked out the column for modification, reflecting Configurator's checkout/versioning model.
  • CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

GRID_COL_ID is the only documented unique surrogate key; no separate unique business-key index is documented, so GRID_ID plus column position/name (if present in the underlying physical definition) would be the closest business-key candidate.

Common Use Cases and Queries

Typical usage centers on reporting and diagnosing compatibility grids. A common query lists all columns of a given grid with their types and effective dates:

  • SELECT GRID_COL_ID, GRID_ID, DATA_TYPE, EFF_FROM, EFF_TO FROM CZ.CZ_GRID_COLS WHERE GRID_ID = :grid_id AND DELETED_FLAG = 'N';
  • Join to CZ_GRID_CELLS to reconstruct permitted value combinations: SELECT c.GRID_COL_ID, c.CELL_ID FROM CZ_GRID_CELLS c JOIN CZ_GRID_COLS g ON g.GRID_COL_ID = c.GRID_COL_ID WHERE g.GRID_ID = :grid_id;
  • Resolve ordering/supersession chains via the self-join on PREV_GRID_COL_ID to determine column sequence.
  • Audit active vs. perished definitions using EFF_FROM/EFF_TO windows filtered to a transaction date.

Legacy data migration and Configurator setup validation also rely on this table to verify that every grid column has authored cells and expression nodes.

Related Objects

  • CZ_GRID_DEFS — parent grid definition; joined via CZ_GRID_COLS.GRID_ID = CZ_GRID_DEFS.GRID_ID.
  • CZ_GRID_COLS (self) — column sequencing via CZ_GRID_COLS.PREV_GRID_COL_ID = CZ_GRID_COLS.GRID_COL_ID.
  • CZ_GRID_CELLS — cell values referencing GRID_COL_ID; the primary dependent table.
  • CZ_COMBO_FEATURES — references GRID_COL_ID, linking columns to feature combinations.
  • CZ_EXPRESSION_NODES — references GRID_COL_ID, tying grid columns into Configurator expression/rule logic.

Together these objects form the structural and value-level backbone of explicit compatibility in Oracle Configurator.