Search Results count_point_flag

Overview

ENG_REVISED_OPERATIONS_V is an APPS-owned view in the Oracle E-Business Suite Engineering (ENG) module that presents pending and implemented revised operations. It exposes the operation-level detail of engineering change order (ECO) revisions to manufacturing routings, allowing revised operation sequences to be queried before and after they are implemented into production routings. In Oracle EBS 12.1.1 and 12.2.2, the view serves as a reporting and integration surface for ECO-driven routing changes, complementing the base revision tables ENG_REVISED_ITEMS and ENG_REVISED_OPERATIONS.

The view is particularly relevant to users searching for standard_operation_code, because it exposes the BOM_STANDARD_OPERATIONS.OPERATION_CODE column under the alias STANDARD_OPERATION_CODE. This provides the human-readable standard operation code associated with a revised operation, rather than requiring a join to the standard operations table.

Underlying Base Objects

The documented view metadata lists the following referenced base objects, each accessed through APPS synonyms:

• ENG_REVISED_OPERATIONS — the primary driver table (aliased A) holding the revised operation rows.
• ENG_REVISED_ITEMS — the revised item header (aliased ERI), joined on REVISED_ITEM_SEQUENCE_ID.
• BOM_STANDARD_OPERATIONS (aliased BSO) — supplies OPERATION_CODE as STANDARD_OPERATION_CODE.
• BOM_DEPARTMENTS (aliased BD) — supplies DEPARTMENT_CODE and LOCATION_ID.
• BOM_OPERATIONAL_ROUTINGS (aliased BOR) — routing header context for the revised routing.
• BOM_OPERATION_SEQUENCES — referenced in the documented metadata as a base object supporting operation sequence lookups.

The joins link each revised operation to its owning revised item and to the standard operation, department, and routing definitions that give the revision its manufacturing context.

Key Columns

• STANDARD_OPERATION_CODE (from BSO.OPERATION_CODE) — the standard operation identifier, the column most commonly searched for.
• OPERATION_SEQUENCE_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQ_NUM — sequence identifiers and display number for the operation within the routing.
• STANDARD_OPERATION_ID, DEPARTMENT_ID, DEPARTMENT_CODE, LOCATION_ID — foreign keys and descriptive codes for the standard operation and department.
• OPERATION_DESCRIPTION — text description of the revised operation.
• EFFECTIVITY_DATE, DISABLE_DATE, IMPLEMENTATION_DATE — date controls governing when the revised operation takes effect.
• COUNT_POINT_TYPE and derived COUNT_POINT_FLAG / AUTOCHARGE_FLAG — DECODE expressions translating count point types into reporting flags.
• BACKFLUSH_FLAG, OPTION_DEPENDENT_FLAG, OPERATION_TYPE, REFERENCE_FLAG — operational behavior indicators, with NVL defaults where nulls are expected.
• YIELD, CUMULATIVE_YIELD, REVERSE_CUMULATIVE_YIELD, LABOR/MACHINE/TOTAL_TIME_CALC and _USER, NET_PLANNING_PERCENT — yield and time calculation values for the operation.
• CHANGE_NOTICE, IMPLEMENTATION_DATE, CANCELLATION_DATE, CANCEL_COMMENTS — ECO change control attributes.
• ROW_ID (A.ROWID) — the row identifier supporting updateable or row-targeted processing.
• ATTRIBUTE1 through ATTRIBUTE15 and WHO columns — descriptive flexfield segments and audit trail fields.

Common Use Cases and Queries

The view is typically used to report pending versus implemented ECO operation changes, to validate routing revisions prior to implementation, and to extract standard operation codes for interfaces. A representative query filtering on the standard operation code is:

SELECT operation_seq_num, standard_operation_code, department_code, operation_description, effectivity_date, implementation_date
FROM apps.eng_revised_operations_v
WHERE standard_operation_code = :standard_operation_code
AND effectivity_date >= :start_date;

Additional scenarios include listing all revised operations for a given revised item, auditing backflush or count point settings, and comparing calculated versus user-entered operation times. Because the view exposes ROW_ID and the attribute columns, it can also support controlled updates and flexfield-driven reporting in ECO workflows.