MTL_CATEGORY_SETS_B
Schema: INVcontrolCategory set definitions — validation rules, control level (master-org vs org-level), the multiple-assignments flag, and the default category new items inherit
The category set NAME is not on this table at all — it lives only on the translation companion (MTL_CATEGORY_SETS_TL, not yet cataloged), so any query showing set names is language-filtered.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
7 fields · 1 key
7 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CATEGORY_SET_ID | Surrogate key of the category set | NUMBER | Primary-key field |
| 2 | STRUCTURE_ID | The flexfield structure the set's categories use | NUMBER | |
| 3 | VALIDATE_FLAG | Whether assignments are validated against the set's category list | VARCHAR2 | |
| 4 | MULT_ITEM_CAT_ASSIGN_FLAG | Whether one item may carry multiple categories in this set — the flag behind category-rollup double counting | VARCHAR2 | |
| 5 | CONTROL_LEVEL | Whether assignments are controlled at the master org or per org | NUMBER | |
| 6 | DEFAULT_CATEGORY_ID | The category new items inherit in this set | NUMBER | |
| 7 | HIERARCHY_ENABLED | Whether the set supports category hierarchies | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading MTL_CATEGORY_SETS_B on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <CATEGORY_SET_ID>, <watermark>
-- ============================================================
-- Table : MTL_CATEGORY_SETS_B — Category set definitions — validation rules, control level (master-org vs org-level), the multiple-assignments flag, and the default category new items inherit
-- Purpose: Column-selected read of MTL_CATEGORY_SETS_B — auto-generated from field metadata
-- Grain : One row per CATEGORY_SET_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.CATEGORY_SET_ID AS "Surrogate key of the category set",
t.STRUCTURE_ID AS "The flexfield structure the set's categories use",
t.VALIDATE_FLAG AS "Whether assignments are validated against the set's category list",
t.MULT_ITEM_CAT_ASSIGN_FLAG AS "Whether one item may carry multiple categories in this set — the flag behind category-rollup double counting",
t.CONTROL_LEVEL AS "Whether assignments are controlled at the master org or per org",
t.DEFAULT_CATEGORY_ID AS "The category new items inherit in this set",
t.HIERARCHY_ENABLED AS "Whether the set supports category hierarchies"
FROM <catalog>.<schema>.MTL_CATEGORY_SETS_B t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.CATEGORY_SET_ID = <CATEGORY_SET_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.CATEGORY_SET_ID;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON MTL_ITEM_CATEGORIES.CATEGORY_SET_ID = MTL_CATEGORY_SETS_B.CATEGORY_SET_IDON MTL_CATEGORY_SETS_B.DEFAULT_CATEGORY_ID = MTL_CATEGORIES_B.CATEGORY_ID
More Item & Product Master tables
- MTL_CROSS_REFERENCES_BItem cross-references — maps items to external identifiers (GTINs, superseded part numbers, customer and supplier part numbers) by cross-reference type, either per organization or org-independent
- MTL_ITEM_CATEGORIESThe item-to-category assignment — one row per item, organization, category set, and category; the bridge every category rollup crosses
- MTL_ITEM_REVISIONS_BItem revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change notice that introduced it
- MTL_SYSTEM_ITEMS_BThe item master — one row per item per inventory organization, carrying identity (the SEGMENTn flexfield the user-visible item number concatenates from), status, unit of measure, and the control flags for every functional area; every balance, transaction, and order line joins back to it on INVENTORY_ITEM_ID + ORGANIZATION_ID
- MTL_SYSTEM_ITEMS_TLThe item master's translation companion — item description and long description in every installed language, one row per item per organization per language
- MTL_UNITS_OF_MEASURE_TLThe unit-of-measure master — both the 3-char UOM code and the 25-char unit name, the UOM class, and the base-unit flag, one row per unit per language