Results for “bom_eam_shutdown_type”

50+ results




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

Overview

APPS.BOM_STANDARD_OPERATIONS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that presents standard manufacturing operations as defined in Oracle Bills of Material and Oracle Work in Process. A standard operation represents a reusable shop-floor step—identified by an operation code and sequence—that can be attached to routings, assemblies, and work orders. The view flattens the core BOM_STANDARD_OPERATIONS record and enriches it with department details, production line information, and decoded lookup values.

The view is significant because it exposes several denormalized and derived columns that are not directly present on the base table. It joins to the MFG_LOOKUPS view to resolve the SHUTDOWN_TYPE code into a user-facing meaning via the BOM_EAM_SHUTDOWN_TYPE lookup type, and it supplies derived flags—COUNT_POINT_FLAG, AUTOCHARGE_FLAG, and CHECK_SKILL—that simplify operational reporting. Within ETRM and other technical repositories, it is catalogued as an APPS-owned view referenced by external reporting, integration, and extension logic rather than by seeded concurrent programs.

Underlying Base Objects

The view is defined over four documented objects:

  • BOM_STANDARD_OPERATIONS (SYNONYM) — the primary table holding the operation header: sequence, operation code, department, yield, shutdown type, and descriptive flexfield attributes.
  • BOM_DEPARTMENTS (SYNONYM) — joined on DEPARTMENT_ID to supply the department code, description, and location.
  • WIP_LINES (SYNONYM) — outer-joined on LINE_ID to return the production line code where an operation is line-specific.
  • MFG_LOOKUPS (VIEW) — outer-joined on LOOKUP_TYPE = 'BOM_EAM_SHUTDOWN_TYPE' and LOOKUP_CODE = TO_NUMBER(SHUTDOWN_TYPE) to translate the shutdown type into its meaning.

The join to BOM_DEPARTMENTS is mandatory (no outer join), so every row returned requires a valid department. The joins to WIP_LINES and MFG_LOOKUPS are outer joins, meaning operations without an assigned line or a recognized shutdown type are still returned, with those columns null.

Key Columns

Common Use Cases and Queries

Because the view resolves the BOM_EAM_SHUTDOWN_TYPE lookup, it is commonly used to report on EAM shutdown operations and count-point/autocharge configurations. Typical scenarios include querying operations by organization, department, or production line, and extracting flexfield attributes for integration.

Operations for a specific organization:

  • SELECT standard_operation_id, operation_code, department_code, sequence_num FROM apps.bom_standard_operations_v WHERE organization_id = :org_id ORDER BY operation_code;

EAM shutdown operations with decoded meaning:

  • SELECT operation_code, department_code, shutdown_type, shutdown_type_value FROM apps.bom_standard_operations_v WHERE organization_id = :org_id AND shutdown_type IS NOT NULL;

Count-point and autocharge analysis:

  • SELECT operation_code, count_point_flag, autocharge_flag, check_skill FROM apps.bom_standard_operations_v WHERE organization_id = :org_id;

Line-specific operations:

  • SELECT line_code, operation_code, department_code FROM apps.bom_standard_operations_v WHERE organization_id = :org_id AND line_code IS NOT NULL ORDER BY line_code, sequence_num;

For data extraction, the STANDARD_OPERATION_ID should be used as the stable join key to base tables, while the view's decoded columns eliminate the need for separate lookup joins in downstream reports.