Search Results autocharge_flag




Overview
Explore in AI Chat

Overview

APPS.ENG_REVISED_OPERATIONS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes engineering revised operations — that is, the operation sequences belonging to engineering change order (ECO) revisions of items before those revisions are released into production routing. The view consolidates data from the engineering module (ENG_REVISED_ITEMS, ENG_REVISED_OPERATIONS) with reference data sourced from the Bills of Material module (BOM_STANDARD_OPERATIONS, BOM_DEPARTMENTS, BOM_OPERATIONAL_ROUTINGS). Its primary role is to present a denormalized, human-readable projection of revised operations, resolving foreign keys such as department, standard operation, and routing into their business-meaningful codes while still exposing the underlying surrogate identifiers.

The view constitutes the engineering-side counterpart of operational routing queries, and is frequently used by reports, concurrent programs, and integrations that must inspect routing structures attached to pending revisions rather than to released routings.

Underlying Base Objects

The view is defined over the following documented base objects, referenced through public synonyms owned by APPS:

  • ENG_REVISED_OPERATIONS (aliased A) — the driving table supplying operation sequence records, effectivity and disable dates, flags, attributes, and the WHO audit columns.
  • ENG_REVISED_ITEMS (aliased ERI) — joined on REVISED_ITEM_SEQUENCE_ID to tie each operation back to its revised item.
  • BOM_OPERATIONAL_ROUTINGS (aliased BOR) — joined on ROUTING_SEQUENCE_ID to resolve the parent routing header.
  • BOM_STANDARD_OPERATIONS (aliased BSO) — joined to derive STANDARD_OPERATION_CODE.
  • BOM_DEPARTMENTS (aliased BD) — joined to derive DEPARTMENT_CODE and LOCATION_ID.
  • BOM_OPERATION_SEQUENCES — documented as a referenced object supporting the routing/operation model shared with the engineering tables.

A critical filter in the view definition is A.IMPLEMENTATION_DATE IS NOT NULL, so only operations that have been implemented (that is, revisions with a recorded implementation date) are returned.

Key Columns

The view projects the full column set of ENG_REVISED_OPERATIONS plus several derived and resolved values:

Common Use Cases and Queries

Typical scenarios include engineering change reports, revision comparison extracts, routing validation prior to release, and interfaces that must move revised operations into production routings. Because AUTOCHARGE_FLAG is a derived decode rather than a stored column, queries filtering on autocharge behavior must target this view rather than the base table.

A representative query listing revised operations with their autocharge status:

  • SELECT operation_sequence_id, operation_seq_num, standard_operation_code, department_code, autocharge_flag, count_point_flag FROM apps.eng_revised_operations_v WHERE autocharge_flag = 2;

Joining the view back to ENG_REVISED_ITEMS for a specific revision, or to BOM_OPERATIONAL_ROUTINGS for routing context, is also common. Because the view enforces the IMPLEMENTATION_DATE IS NOT NULL predicate, it cannot be used to inspect unimplemented revisions; callers requiring those rows must query ENG_REVISED_OPERATIONS directly.