Skip to content
EBS Reference

MTL_CATEGORY_SETS_B

Schema: INVcontrol

Category set definitions — validation rules, control level (master-org vs org-level), the multiple-assignments flag, and the default category new items inherit

Notes

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field.

Fields

7 fields · 1 key

7 fields.

Table fields: position, field name, description, data type, and flags. 7 fields.
#FieldDescriptionTypeFlags
1CATEGORY_SET_IDSurrogate key of the category setNUMBER
Primary-key field
2STRUCTURE_IDThe flexfield structure the set's categories useNUMBER
3VALIDATE_FLAGWhether assignments are validated against the set's category listVARCHAR2
4MULT_ITEM_CAT_ASSIGN_FLAGWhether one item may carry multiple categories in this set — the flag behind category-rollup double countingVARCHAR2
5CONTROL_LEVELWhether assignments are controlled at the master org or per orgNUMBER
6DEFAULT_CATEGORY_IDThe category new items inherit in this setNUMBER
7HIERARCHY_ENABLEDWhether the set supports category hierarchiesVARCHAR2

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.

Query parameters

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

  • MTL_ITEM_CATEGORIESMTL_CATEGORY_SETS_Bforeign key · N:1
    ON MTL_ITEM_CATEGORIES.CATEGORY_SET_ID = MTL_CATEGORY_SETS_B.CATEGORY_SET_ID
  • MTL_CATEGORY_SETS_BMTL_CATEGORIES_Bforeign key · N:1
    ON MTL_CATEGORY_SETS_B.DEFAULT_CATEGORY_ID = MTL_CATEGORIES_B.CATEGORY_ID

Browse more Item & Product Master tables

More Item & Product Master tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.