Results for “backfush_flag”

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

Overview

BOM_STANDARD_OPERATIONS_ALL_V is an Oracle Applications (APPS) view owned by the APPS schema and registered as VALID within the Bills of Material (BOM) product family. It exposes "standard operations — all records," providing a consolidated read interface over the standard operations defined for an organization. In the Oracle EBS 12.1.1 and 12.2.2 technical stack, this view serves as the reporting and integration access point for the operation master data that drives routing and manufacturing execution.

The view is documented in the ETRM metadata as a simple projection rather than a join-based construct. Its definition selects a defined column list from BOM_STANDARD_OPERATIONS, aliased as BSO. Because the definition contains no UNION ALL, no ORG_ID filter, and no multi-organization rewrite, the "_ALL" suffix reflects that the view surfaces every organization's rows rather than applying a session-based operating-unit restriction. Consumers must therefore supply their own ORGANIZATION_ID predicate when querying a specific organization. The view is read-oriented; it exposes the column list required for inquiry and downstream reporting without adding transformation logic.

Underlying Base Objects

The ETRM documentation identifies a single referenced base object: BOM_STANDARD_OPERATIONS, exposed to the APPS schema as a SYNONYM. The view text confirms that BOM_STANDARD_OPERATIONS_ALL_V is defined directly over this table with the alias BSO, and that every column in the view originates from that single source. Column names are passed through unchanged.

Because the view depends on one table, it introduces no additional join cost or cardinality risk. Row counts in the view match the base table exactly, and the view inherits the base table's indexes and constraints for query planning purposes. It is important to note the documented synonym relationship: the APPS synonym resolves to the underlying BOM base table, so the view remains a thin abstraction layer. No other BOM tables, such as department or resource tables, are referenced in the documented view text.

Key Columns

• STANDARD_OPERATION_ID — Primary identifier for the standard operation record.
• OPERATION_CODE and OPERATION_DESCRIPTION — The user-facing code and descriptive text of the operation.
• ORGANIZATION_ID — The organization to which the operation belongs; essential for filtering, since the view is not organization-restricted.
• DEPARTMENT_ID — Department associated with the operation.
• OPERATION_TYPE and SEQUENCE_NUM — Classification and ordering attributes.
• OPTION_DEPENDENT_FLAG — The column retrieved in the user's search. It indicates whether the standard operation is option-dependent, meaning it is included or excluded based on the configuration options selected on an assembled item. This flag is critical when reporting on configured or assemble-to-order routings, since option-dependent operations are not unconditionally applied.
• BACKFLUSH_FLAG (listed as BACKFUSH_FLAG in the column listing) — Indicates whether components are backflushed at this operation.
• MINIMUM_TRANSFER_QUANTITY and COUNT_POINT_TYPE — Shop-floor transfer and count-point behavior.
• DEFAULT_SUBINVENTORY and DEFAULT_LOCATOR_ID — Default material sourcing locations.
• CRITICAL_TO_QUALITY and VALUE_ADDED — Quality and value-add indicators used in cost and quality analysis.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — Descriptive flexfield columns for client-specific extensions.
• LINE_ID, plus the standard WHO and concurrent program columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), which support auditing and change tracking.

Common Use Cases and Queries

Typical uses include validating routing setup, extraction of operation master data into data warehouses, and reports that identify option-dependent or backflush operations. The following query lists option-dependent operations for a given organization:

• SELECT organization_id, operation_code, operation_description, department_id, option_dependent_flag FROM apps.bom_standard_operations_all_v WHERE organization_id = :org_id AND option_dependent_flag = 'Y';
• SELECT operation_code, department_id, backflush_flag, minimum_transfer_quantity FROM apps.bom_standard_operations_all_v WHERE organization_id = :org_id ORDER BY operation_code;
• SELECT attribute_category, attribute1, attribute2, operation_code FROM apps.bom_standard_operations_all_v WHERE organization_id = :org_id AND attribute_category = :cat;

Because the view is unconstrained by organization, all queries should include an ORGANIZATION_ID predicate to avoid cross-organization data leakage in reports. The OPTION_DEPENDENT_FLAG column specifically supports configuration-driven routing analysis.