Results for “default_locator_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM_STANDARD_OPERATIONS_VAL_V is an APPS-owned database view in the Oracle E-Business Suite Bills of Material (BOM) module. It exposes the set of valid standard operations — that is, standard operations whose associated department has not been disabled as of the current system date. In Oracle EBS 12.1.1 and 12.2.2, standard operations represent reusable shop-floor routing steps (such as drilling, assembly, or inspection) that are performed within a manufacturing department. This view serves as a filtered, denormalized projection that joins the standard operation definition with its owning department, ensuring that only operations attached to active departments are returned to reports, concurrent programs, and integration interfaces.

The view's role is primarily read-only reporting and validation. Because it applies a date-based filter on the department's disable date, business users querying routings, work definitions, or cost rollups through this view never see operations belonging to decommissioned departments, which preserves the integrity of production planning and shop-floor dispatch data.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• BOM_STANDARD_OPERATIONS — aliased as BSO, the primary table holding the standard operation record, including its department reference, operation code, count point type, transfer quantity, and descriptive flexfield attributes.
• BOM_DEPARTMENTS — aliased as BD, the department master, supplying the department code, description, and location.

The join condition is BD.DEPARTMENT_ID = BSO.DEPARTMENT_ID, and the validity filter is expressed as TRUNC(NVL(BD.DISABLE_DATE, SYSDATE+1)) > TRUNC(SYSDATE). This means a department with a NULL disable date is treated as active indefinitely, while a department whose disable date is today or earlier is excluded. The view also returns BSO.ROWID as ROW_ID, providing a stable row identifier for updatable-block constructs in Oracle Forms.

Key Columns

The columns most relevant to functional and technical use are:

• STANDARD_OPERATION_ID — primary key of the standard operation.
• OPERATION_CODE — the short code identifying the operation.
• ORGANIZATION_ID — the manufacturing organization to which the operation belongs.
• DEPARTMENT_ID / DEPARTMENT_CODE — the department reference; DEPARTMENT_CODE originates from BOM_DEPARTMENTS.
• DEPARTMENT_DESCRIPTION — the descriptive name of the department, sourced as BD.DESCRIPTION. This is the column most frequently requested by users searching for "department_description," since it allows routing and operation reports to display a human-readable department name alongside the operation.
• LOCATION_ID, MINIMUM_TRANSFER_QUANTITY, COUNT_POINT_TYPE, BACKFLUSH_FLAG, DEFAULT_SUBINVENTORY, DEFAULT_LOCATOR_ID, CRITICAL_TO_QUALITY, and VALUE_ADDED — operational attributes governing material movement, backflushing, and quality/valuation classification.
• OPTION_DEPENDENT_FLAG and the descriptive flexfield columns ATTRIBUTE_CATEGORY through ATTRIBUTE15 — user-defined extensibility.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for audit and concurrent manager traceability.

Common Use Cases and Queries

Typical scenarios include routing-step reporting, department workload analysis, and validation lookups in custom integrations. A simple listing of active standard operations with their department names is the most common query:

• SELECT operation_code, department_code, department_description FROM bom_standard_operations_val_v WHERE organization_id = :org_id ORDER BY department_code, operation_code;
• Department workload:
  SELECT department_description, COUNT(*) FROM bom_standard_operations_val_v WHERE organization_id = :org_id GROUP BY department_description;
• Backflush analysis:
  SELECT operation_code, department_description FROM bom_standard_operations_val_v WHERE backflush_flag = 1;
• LOV/validation lookups keyed on department_description for custom Forms or OAF pages.

Because the view applies a SYSDATE-based predicate on the department disable date, results may vary over time without any underlying data change, a behavior worth noting when results are cached in downstream systems.