Search Results dept_class_code

Overview

APPS.CST_XLA_DEPARTMENT_REF_V is an Oracle E-Business Suite internal reference view owned by the APPS schema and registered under the FND Design Data application short name BOM. Its status is VALID in both 12.1.1 and 12.2.2 environments. The view exposes department reference data — department identifiers, codes, descriptions, class codes, maintenance cost categories, location identifiers, and the full descriptive flexfield (DFF) attribute set — in a single, denormalized projection. Its name indicates that it is intended to support the Cost Management (CST) and Subledger Accounting (XLA) architecture, specifically by supplying department-level reference information that can be joined to accounting and cost events.

The object carries an explicit Oracle Internal Use Only warning: Oracle does not support direct access to the underlying applications data except through standard Oracle Applications programs. This designation is typical of XLA support views that map transactional facts to accounting definitions. The view is therefore best understood as a reporting and diagnostics aid — useful to technical consultants who need to reconcile departmental attributes referenced by SLA and cost processing — rather than a supported public interface.

Underlying Base Objects

The documented base object for this view is BOM_DEPARTMENTS, accessed through its synonym. BOM_DEPARTMENTS is the master table for department definitions in Oracle Bills of Material and related manufacturing modules. The view is a column-for-column projection of that table, optionally restricted depending on the deployed XLA/costing logic. The columns follow the standard BOM_DEPARTMENTS column naming convention: DEPT_ID is the primary key, and each descriptive attribute retains the DEPT_ prefix used by the base table.

Because the view resolves to a synonym over BOM_DEPARTMENTS, it inherits the base table's indexes and constraints. Queries filtered on DEPT_ID or DEPT_CODE will benefit from the primary key and unique index on the base table, while the view layer itself adds negligible cost. There is no aggregation, DISTINCT, or inline function in the documented projection, so the view does not constrain the optimizer's ability to push predicates down to BOM_DEPARTMENTS.

Key Columns

• DEPT_ID (NUMBER) — Unique department identifier; the primary key and the join key to both departmental reference tables and to XLA/cost transaction tables that store a department identifier.
• DEPT_CODE (VARCHAR2 10) — Short alphanumeric department code used in user-facing screens and reports.
• DEPT_DESCRIPTION (VARCHAR2 240) — Long description of the department.
• DEPT_CLASS_CODE (VARCHAR2 10) — Classification code used to group departments for reporting or processing logic.
• DEPT_MAINT_COST_CAT (VARCHAR2 30) — Maintenance cost category. This is the column most directly associated with the search term "dept_maint_cost_cat" and is the primary reason a user would query this view; it appears in the projection specifically to map a department to its maintenance cost category.
• DEPT_LOCATION_ID (NUMBER) — Identifier of the location associated with the department.
• DEPT_ATTRIBUTE_CATEGORY (VARCHAR2 30) — The DFF structure defining column, which determines which of the flexibility segments are meaningful.
• DEPT_ATTRIBUTE1 through DEPT_ATTRIBUTE15 (VARCHAR2 150 each) — Descriptive flexfield segments available for client-specific extensions.

Common Use Cases and Queries

The most common use case is validating the maintenance cost category assigned to a department, particularly when investigating how costs are being classified during XLA event processing. A second use case is joining the view to departmental DFF data for operational reporting without touching the base table directly. A third is a lightweight lookup of department code and description for a reporting query where only the reference attributes are needed.

Sample query to retrieve maintenance cost categories for all departments:

SELECT dept_id,
       dept_code,
       dept_description,
       dept_maint_cost_cat
  FROM apps.cst_xla_department_ref_v
 ORDER BY dept_code;

Sample query to resolve a specific department's attributes and DFF segments:

SELECT dept_id,
       dept_code,
       dept_description,
       dept_class_code,
       dept_maint_cost_cat,
       dept_attribute_category,
       dept_attribute1,
       dept_attribute2
  FROM apps.cst_xla_department_ref_v
 WHERE dept_code = :p_dept_code;

Sample query joining departments to a cost fact table on DEPT_ID to explain a classification:

SELECT v.dept_code,
       v.dept_maint_cost_cat,
       f.cost_element_id
  FROM apps.cst_xla_department_ref_v v,
       apps.cst_cost_element_costs f
 WHERE v.dept_id = f.dept_id
   AND f.period_id = :p_period_id;

Because the object is marked internal use only, any query should be confined to diagnostic and reconciliation purposes, and production reporting should wherever possible be redirected to an Oracle-supported interface.