Results for “item_resource_name”

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

Overview

EAM_CAPT_BILL_BY_REQ_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Enterprise Asset Management (EAM) module. Its documented status is VALID in both release 12.1.1 and 12.2.2. The view exists to present, in a single unified result set, the materials, direct items, and resources associated with an EAM work order. As stated in the object description, it is fundamentally a union of the bill-by-requirements view (EAM_BILL_BY_REQUIREMENTS_V) with the direct items view, with the important restriction that only a subset of direct item records is retrieved.

The view serves as a reporting and integration surface for capturing work order billing data. Rather than joining the underlying work order, requirement, resource, and billing tables manually, consumers can select from this view to obtain applied quantities, billed quantities, and derived bill quantities in a consistent structure. Because it exposes a TYPE discriminator, it allows both item-based and resource-based lines to be reported together without the caller needing to reconcile two separate sources. It is typically consumed by EAM billing and capture programs, custom reports, and interface extracts that need to know how much of a given requirement remains to be billed.

Underlying Base Objects

The documented base objects referenced by the view are BOM_RESOURCES, EAM_DIRECT_ITEM_RECS_V, EAM_WORK_ORDER_BILLS, FND_GLOBAL, MTL_SYSTEM_ITEMS_KFV, WIP_EAM_PARAMETERS, WIP_OPERATION_RESOURCES, and WIP_REQUIREMENT_OPERATIONS.

• WIP_REQUIREMENT_OPERATIONS — supplies the material requirement lines per work order and operation sequence, including inventory item and issued quantity.
• WIP_OPERATION_RESOURCES — supplies the resource lines applied to work order operations, including applied resource units.
• EAM_WORK_ORDER_BILLS — holds the billed quantities and billing method used to compute what has already been billed and what remains.
• MTL_SYSTEM_ITEMS_KFV — provides the concatenated item segment name and primary unit of measure for item lines.
• BOM_RESOURCES — provides the resource code used to name resource lines.
• EAM_DIRECT_ITEM_RECS_V — the direct items source referenced by the description; only selected records are included.
• WIP_EAM_PARAMETERS — the EAM parameter table joined by organization.
• FND_GLOBAL — the standard EBS package used for session context such as organization and user identifiers.

The view is defined in two branches combined by UNION. The first branch joins requirement operations to MTL_SYSTEM_ITEMS_KFV and to EAM_WORK_ORDER_BILLS (restricted to BILLING_METHOD = 3) via outer joins, aggregating BILLED_QUANTITY and assigning TYPE = 1 for materials. The second branch joins operation resources to BOM_RESOURCES and the same billing table, assigning TYPE = 2 for resources and returning NULL for the bill inventory item and bill UOM columns. Grouped aggregates ensure one row per work order, organization, operation sequence, and item or resource.

Key Columns

• WIP_ENTITY_ID — the work order identifier; the primary grouping key across both branches.
• ORGANIZATION_ID — the inventory organization in which the work order resides.
• OP_SEQ_NUM — the operation sequence number to which the line belongs.
• ITEM_RESOURCE_ID — the inventory item ID for material lines, or the resource ID for resource lines.
• ITEM_RESOURCE_NAME — the concatenated item segment name, or the resource code, depending on line type.
• TYPE — discriminator: 1 indicates a material/direct item line, 2 indicates a resource line.
• UOM — the unit of measure for the applied quantity.
• APPLIED_QUANTITY — quantity issued for materials, or applied resource units for resources.
• BILLED_QUANTITY — the summed billed quantity from EAM_WORK_ORDER_BILLS, coalesced to zero when no billing exists.
• BILL_INVENTORY_ITEM_ID and BILL_UOM — populated for material lines and NULL for resource lines.
• BILL_QUANTITY — the residual to be billed, computed as APPLIED_QUANTITY minus BILLED_QUANTITY.
• BILLING_METHOD — the billing method carried from the work order bills record.

Common Use Cases and Queries

Typical scenarios include reviewing outstanding billable quantities for a work order, reconciling applied versus billed materials and resources, and feeding downstream cost capture or interface processes. The following query lists all outstanding material lines for a specific work order:

SELECT wip_entity_id, organization_id, op_seq_num, item_resource_name, uom, applied_quantity, billed_quantity, bill_quantity
FROM apps.eam_capt_bill_by_req_v
WHERE wip_entity_id = :p_wip_entity_id
AND type = 1
AND bill_quantity > 0
ORDER BY op_seq_num, item_resource_name;

To obtain a consolidated view of both materials and resources with a readable line type, the TYPE column can be decoded:

SELECT wip_entity_id, op_seq_num,
DECODE(type, 1, 'MATERIAL', 2, 'RESOURCE') line_type,
item_resource_name, applied_quantity, billed_quantity, bill_quantity
FROM apps.eam_capt_bill_by_req_v
WHERE organization_id = :p_org_id;

Because the view aggregates billed quantities, it is also convenient for organization-level summaries of unbilled balances grouped by item or resource. All queries should be executed with the appropriate EBS responsibility and organization context, since the view relies on standard EAM and WIP data and on session context supplied through FND_GLOBAL.