Results for “cost_basis_code”

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

Overview

AHL_WO_OPERATIONS_TXNS is a transactional table in the AHL (Complex Maintenance Repair and Overhaul) product family of Oracle E-Business Suite, documented as valid in both 12.1.1 and 12.2.2. It stores production work order operation information, capturing the resource, material, and scheduling detail associated with work order operations executed within an MRO or shop floor context. The table sits at the intersection of production scheduling, resource management, and cost accumulation, functioning as the operational transaction layer behind work order execution in AHL.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as a link. This is consistent with its structure: the table is dominated by foreign key relationships that associate work order operations with resources, materials, and bills of material resources. It is a connective, event-oriented table rather than a standalone reference entity.

Key Information Stored

The table documents 53 columns. The primary key is enforced by AHL_WO_OPERATIONS_TXNS_PK1 on the column WO_OPERATION_TXN_ID, a surrogate identifier. A unique index, AHL_WO_OPERATIONS_TXNS_U1, exists on the same column, making it the documented business-key candidate. The most significant columns for consumption and integration are:

• WO_OPERATION_TXN_ID — surrogate primary key, the identifier most commonly referenced as wo_operation_txn_id.
• WORKORDER_OPERATION_ID — foreign key to AHL_WORKORDER_OPERATIONS; ties the transaction to a specific work order operation.
• OPERATION_RESOURCE_ID — foreign key to AHL_OPERATION_RESOURCES.
• SCHEDULE_MATERIAL_ID — foreign key to AHL_SCHEDULE_MATERIALS.
• BOM_RESOURCE_ID — foreign key to BOM_RESOURCES.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing row-level access control.
• TRANSACTION_TYPE_CODE, LOAD_TYPE_CODE, OPERATION_TYPE_CODE — classification codes for the operation transaction.
• TOTAL_REQUIRED, REQUIRED_QUANTITY, QUANTITY_PER_ASSEMBLY, SCHEDULED_QUANTITY, ASSIGNED_UNITS, APPLIED_RESOURCE_UNITS — quantity and unit measures driving resource consumption.
• APPLIED_RESOURCE_VALUE, COST_BASIS_CODE, STANDARD_RATE_FLAG_CODE, AUTOCHARGE_TYPE_CODE — cost and charging characteristics.
• RES_SCHED_START_DATE, RES_SCHED_END_DATE, OP_SCHEDULED_START_DATE, OP_SCHEDULED_END_DATE, OP_ACTUAL_START_DATE, OP_ACTUAL_END_DATE — resource and operation scheduling versus actual dates.
• INVENTORY_ITEM_ID, SUPPLY_LOCATOR_ID, SUPPLY_SUBINVENTORY, DATE_REQUIRED — material supply and inventory context.
• OBJECT_VERSION_NUMBER and the standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — concurrency and audit tracking.
• ATTRIBUTE1 through ATTRIBUTE15 plus ATTRIBUTE_CATEGORY — the descriptive flexfield extension area.

Common Use Cases and Queries

The table is most commonly queried to report operation-level resource transactions for a work order, to reconcile applied resource units and values for costing, or to compare scheduled versus actual operation dates for shop floor performance. A typical pattern joins the transaction to its parent operation and resource:

• List all transactions for a work order operation: SELECT * FROM AHL_WO_OPERATIONS_TXNS WHERE WORKORDER_OPERATION_ID = :op_id;
• Resource consumption by operation: join AHL_WO_OPERATIONS_TXNS to AHL_OPERATION_RESOURCES on OPERATION_RESOURCE_ID to resolve resource names against applied units.
• Cost roll-ups: aggregate APPLIED_RESOURCE_VALUE grouped by COST_BASIS_CODE across a date range using OP_ACTUAL_START_DATE.
• Material supply analysis: join to AHL_SCHEDULE_MATERIALS and filter on SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID, or DATE_REQUIRED.
• Row-level security filtering by SECURITY_GROUP_ID in custom reports.

Because the table carries both scheduling and actual dates, variance reporting on operation start and end times is a frequent reporting requirement.

Related Objects

The documented foreign keys identify the primary dependent and referenced objects:

• AHL_WORKORDER_OPERATIONS — referenced via WORKORDER_OPERATION_ID; the parent operation record.
• AHL_OPERATION_RESOURCES — referenced via OPERATION_RESOURCE_ID.
• AHL_SCHEDULE_MATERIALS — referenced via SCHEDULE_MATERIAL_ID.
• BOM_RESOURCES — referenced via BOM_RESOURCE_ID, linking to Oracle Bills of Material resource definitions.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, used for access control.

In practice, the table is also consumed alongside the AHL Work Order APIs and the AHL work order operation DML paths that insert and update operation transactions during production execution. These relationships make AHL_WO_OPERATIONS_TXNS a central link between work order operations, resources, materials, and security groups in the AHL schema.