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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
7 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CATEGORY_SET_ID | Surrogate key of the category set | NUMBER | Key |
| 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_Bon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- 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;4 parameters not filled: <catalog>, <schema>, <CATEGORY_SET_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. 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