Results for “operation_category_code”

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

Overview

AHL_OPERATIONS_B is the base table in the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module that stores the master definition of Standard and Non Standard Operations. In Oracle EBS 12.1.1 and 12.2.2, an operation represents a discrete unit of maintenance work performed within a work order, route, or repair execution flow, and this table serves as the authoritative definition record for that work content. Standard operations are reusable templates referencing defined labor, material, and resource requirements, while non standard operations are created for one-off or ad hoc work. The table is owned by the AHL schema and is validated in the ETRM metadata for release 12.2.2 with a documented physical schema of 70 columns.

The heuristic Data Vault classification mined from the foreign key structure identifies AHL_OPERATIONS_B as a hub. This is a modeling suggestion rather than a physical implementation characteristic: the table carries a single-column surrogate primary key (OPERATION_ID) that is referenced by many dependent tables, which is the defining signature of a hub entity in a Data Vault model. The numerous outbound dependencies — labor, materials, resources, phases, and route and work order operations — behave as link and satellite structures surrounding that hub.

Key Information Stored

The surrogate primary key is OPERATION_ID, enforced by the constraint AHL_OPERATIONS_B_PK. Business key candidates are documented through unique indexes: AHL_OPERATIONS_B_U1 on OPERATION_ID and AHL_OPERATIONS_B_U2 on the fifteen SEGMENT columns (SEGMENT1 through SEGMENT15) combined with REVISION_NUMBER, indicating that the operation number is composed of a multi-segment flexfield structure. Operationally, OPERATION_NUMBER holds the user-facing operation identifier.

• OPERATION_ID — surrogate primary key and the join column for nearly all dependent tables.
• REVISION_NUMBER / REVISION_STATUS_CODE — revision control for engineering change management of the operation definition.
• STANDARD_OPERATION_FLAG / SUMMARY_FLAG / ENABLED_FLAG — flags distinguishing standard versus non standard operations, summary (rollup) records, and enabled status.
• SEGMENT1–SEGMENT15 — the multi-segment key making up the operation number, also used as the second unique business key.
• OPERATION_CATEGORY_CODE / OPERATION_TYPE_CODE / PRODUCT_TYPE_CODE — classification of the operation by category, type, and product applicability.
• WORK_CENTER_CODE / ZONE_CODE / SUB_ZONE_CODE — physical and organizational placement of the work.
• PROCESS_CODE / OPERATOR_CODE / OPERATOR_PARTY_ID — the process performed and the assigned operator or party.
• OPRPRIM_SKILL_TYPE_CODE / SKILL_COMPETENCE_ID — skill and competence requirements for execution.
• TIME_SPAN / ACTIVE_START_DATE / ACTIVE_END_DATE / START_DATE_ACTIVE / END_DATE_ACTIVE — duration and effective dating of the operation.
• QA_PLAN_ID / QA_INSPECTION_TYPE — foreign key to QA_PLANS defining the quality plan and inspection type.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS controlling multi-tenant or organizational data access.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield storage for client-specific extensions.
• ENIGMA_OP_ID / ENIGMA_SOURCE / ENIGMA_DOC_ID / MODEL_CODE — integration columns linking the operation to external ENIGMA-authored technical documentation and model identification.
• Standard who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) support audit and optimistic locking.

Common Use Cases and Queries

The most frequent requirement is to retrieve the complete operation definition, typically joining the base table to its translation table to obtain the language-specific description. A representative pattern selects the header, segments, category, and time span from AHL_OPERATIONS_B and joins AHL_OPERATIONS_TL on OPERATION_ID to obtain the operation name in the session language.

Reporting scenarios include listing all enabled standard operations for a given work center, enumerating operations by category and product type, and identifying operations whose effective dates have lapsed. Because the second unique index comprises the segment columns plus REVISION_NUMBER, lookups that resolve an operation by its displayed number must include the appropriate segments and the active revision.

Maintenance and diagnostic queries commonly join to AHL_ROUTE_OPERATIONS to determine which routes consume an operation, or to AHL_WORKORDER_OPERATIONS to trace where an operation has been applied on live work orders. Quality-focused analysis joins to QA_PLANS via QA_PLAN_ID to confirm that operations requiring inspection are correctly associated with a QA plan. Multi-organization environments must always filter or join through SECURITY_GROUP_ID against FND_SECURITY_GROUPS to respect data access boundaries.

Related Objects

The following objects have documented foreign key relationships with AHL_OPERATIONS_B and represent its most significant dependencies.

• AHL_OPERATIONS_TL — translation table joined on OPERATION_ID; supplies language-specific names and descriptions for the operation.
• AHL_OPERATIONS_H_B — history table joined on OPERATION_ID; retains prior revisions of the operation definition.
• AHL_ROUTE_OPERATIONS and AHL_ROUTE_OPERATIONS_H — join on OPERATION_ID; associate operations with routes and their history.
• AHL_OPERATION_PHASES and AHL_OPERATION_PHASES_H — join on OPERATION_ID; hold sequential phases that subdivide the operation.
• AHL_WORKORDER_OPERATIONS — joins on OPERATION_ID; records operations instantiated against work orders.
• AHL_RT_OPER_LABOR and AHL_RT_OPER_LABOR_H — join on OBJECT_ID; define labor requirements for the operation.
• AHL_RT_OPER_MATERIALS and AHL_RT_OPER_MATERIALS_H — join on OBJECT_ID; define material requirements.
• AHL_RT_OPER_RESOURCES — joins on OBJECT_ID; defines resource requirements.
• QA_PLANS — referenced by AHL_OPERATIONS_B.QA_PLAN_ID; defines the quality plan applied to the operation.
• FND_SECURITY_GROUPS — referenced by AHL_OPERATIONS_B.SECURITY_GROUP_ID; governs data access.