Search Results dept_code

Overview

The CST_XLA_DEPARTMENT_REF_V view is a public APPS-schema database view in Oracle E-Business Suite, owned by the Applications schema and holding VALID status across releases 12.1.1 and 12.2.2. It belongs to the BOM (Bills of Material) product family and functions as a reference view that exposes department master data in a form suitable for consumption by the Cost Management and Subledger Accounting (XLA) architecture, as indicated by the CST_ and XLA_ prefixes in its name. Rather than storing data itself, the view projects a curated column list — including aliased department identifiers, class codes, maintenance cost categories, and descriptive flexfield attributes — so that downstream costing, accounting, and reporting components can resolve department references without querying the base table directly.

The view is read-only and inherits the security profile of its invoking user or concurrent program. Because it resides in APPS, it appears in the standard object inventory at both 12.1.1 and 12.2.2, and the documented metadata for 12.2.2 lists BOM_DEPARTMENTS (SYNONYM) as its single referenced base object.

Underlying Base Objects

The view is defined over the BOM_DEPARTMENTS base table, referenced through a synonym in the APPS schema. The view text performs a direct, unfiltered projection of the columns required by costing and accounting processes. The view aliases the base columns to an XLA-oriented naming convention, preserving the physical data but abstracting the underlying table structure. Because there is no join, aggregation, or WHERE clause in the view definition, it behaves as a lightweight passthrough layer; performance characteristics therefore track the indexes and statistics of BOM_DEPARTMENTS.

Key Columns

• DEPT_ID — Surrogates BOM_DEPARTMENTS.DEPARTMENT_ID; the primary department identifier used in foreign-key relationships.
• DEPT_CODE — Exposes DEPARTMENT_CODE, the short user-facing code. This is the column most frequently targeted by users searching on "dept_code".
• DEPT_DESCRIPTION — Department name/description text.
• DEPT_CLASS_CODE — Classifies the department for cost rollup and accounting purposes.
• DEPT_MAINT_COST_CAT — Maps to MAINT_COST_CATEGORY, directing maintenance cost assignment.
• DEPT_LOCATION_ID — Reference to the department's location.
• DEPT_ATTRIBUTE_CATEGORY and DEPT_ATTRIBUTE1 through DEPT_ATTRIBUTE15 — The descriptive flexfield segments carried through for context-sensitive reporting and integrations.

Common Use Cases and Queries

This view is typically used to resolve a department code to its internal ID, enrich costing and WIP transactions with department descriptions, and supply XLA accounting definitions. A simple lookup by department code takes the following form:

• SELECT dept_id, dept_code, dept_description FROM cst_xla_department_ref_v WHERE dept_code = :dept_code;
• SELECT dept_code, dept_class_code, dept_maint_cost_cat FROM cst_xla_department_ref_v ORDER BY dept_code;
• SELECT d.dept_code, d.dept_description FROM cst_xla_department_ref_v d, bom_departments b WHERE d.dept_id = b.department_id;

Because the view carries no built-in organization or operating-unit filter, queries intended for multi-org environments should join to the appropriate organization-secured base objects. Retrieval of attribute columns supports flexfield-driven reporting without exposing the raw base table to end users.