Results for “ahl_operations_b_kfv”

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

Overview

APPS.AHL_OPERATIONS_B_KFV is a key flexfield (KFV) view automatically generated by the Oracle E-Business Suite Flexfields infrastructure for the AHL – Complex Maintenance Repair and Overhaul product. It resides in the APPS schema with a documented status of VALID and is classified by ETRM as a "Key flexfield automatically generated KFV view." Its purpose is to expose the descriptive flexfield-style key flexfield segments defined on the AHL_OPERATIONS_B entity in a denormalized, reporting-friendly layout.

The view is not a maintained business object; it is a thin projection over the base operations table. It reproduces the identifying and control columns of AHL_OPERATIONS_B alongside SEGMENT1 through SEGMENT15 and two derived concatenated columns. Because it preserves every attribute column, it can be used in place of the base table for read-only reporting while presenting the flexfield segments as discrete, individually addressable fields. In Oracle EBS 12.1.1 and 12.2.2, such KFV views are the supported surface for discoverer reports, BI Publisher data templates, and inbound/outbound interface programs that must resolve an operation by its flexfield combination rather than by OPERATION_ID alone.

Underlying Base Objects

The view text is defined over a single documented base object, AHL_OPERATIONS_B, referenced through a SYNONYM in the APPS schema. The SELECT list maps directly to columns of that table, with one important exception: the literal string 'X' is supplied twice, in the positions occupied by CONCATENATED_SEGMENTS and PADDED_CONCATENATED_SEGMENTS in the documented column list. The view therefore does not derive the concatenated value from the segment columns at runtime; it returns a constant placeholder for those two columns.

Consequently, the view can be treated as a one-to-one row image of AHL_OPERATIONS_B. No joins, unions, or aggregations are introduced, so row counts and OPERATION_ID cardinality match the base table exactly. Any DML against operations must still be performed against the base table or its transactional companions; the KFV view is strictly a query object.

Key Columns

• OPERATION_ID — Primary identifier of the operation record; the join key to routing and work-order structures.
• ROW_ID — Row identifier exposed by the view, used by Oracle Forms and by tools that require a ROWID-based handle.
• OPERATION_TYPE_CODE — The column the user searched for. It classifies the operation, distinguishing standard and non-standard operation types and driving downstream validation and processing logic.
• PROCESS_CODE, QA_INSPECTION_TYPE — Supplementary classification and quality-inspection attributes of the operation.
• STANDARD_OPERATION_FLAG, SUMMARY_FLAG, ENABLED_FLAG — Status and structure indicators controlling whether the operation is a reusable standard, a summary parent, or currently active.
• REVISION_NUMBER, REVISION_STATUS_CODE — Revision control attributes for the operation definition.
• START_DATE_ACTIVE, END_DATE_ACTIVE — Effective dating window for the operation.
• SEGMENT1 … SEGMENT15 — The key flexfield segments, exposed individually for filtering and reporting.
• CONCATENATED_SEGMENTS, PADDED_CONCATENATED_SEGMENTS — Documented in the column list; populated with the literal 'X' by the view definition.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 … ATTRIBUTE15 — Descriptive flexfield context and attribute values.

Common Use Cases and Queries

The most frequent requirement is locating operations by type. Because OPERATION_TYPE_CODE is exposed directly, reporting can filter on it without reference to lookup internals:

• SELECT operation_id, operation_type_code, process_code, revision_number, enabled_flag FROM apps.ahl_operations_b_kfv WHERE operation_type_code = :p_type_code AND enabled_flag = 'Y';
• Filter by effective dates to return only operations valid on a given day: WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE).
• Resolve a flexfield combination to its operation: SELECT operation_id, segment1, segment2, segment3 FROM apps.ahl_operations_b_kfv WHERE segment1 = :p_seg1 AND segment2 = :p_seg2.
• Join to work-order and routing tables on OPERATION_ID to enrich maintenance reporting, joining on operation_id against AHL_WORKORDERS or routing structures as configured.

One caution applies to all such queries: CONCATENATED_SEGMENTS and PADDED_CONCATENATED_SEGMENTS return the constant 'X' and must not be used for display or matching. Where a true concatenated key is required, it should be assembled from the individual SEGMENT columns or obtained from the base table using the flexfield API.