Results for “billing_method”

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

Overview

The EAM_BILL_BY_REQUIREMENTS_V view in the APPS schema is a forms-support object within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. As documented in the ETRM metadata, its stated purpose is to simplify forms coding by consolidating the data required to render the "Bill by Requirements" block on the work order billing form. Rather than issuing multiple base-table joins from the form's underlying block, Oracle developers exposed a single view that flattens the required material and resource requirement rows together with their associated billing quantities.

Because the view presents a derived, denormalized projection of work order requirements, billed quantities, and UOM information, it is equally useful as a reporting source for EAM billing analysis. It answers the operational question: for a given work order, organization, and operation, which item or resource requirements have been applied, what quantity has already been billed, and what quantity remains billable under the currently active billing method.

Underlying Base Objects

The view is defined over a combination of WIP/EAM and inventory master objects. The documented referenced base objects are:

• WIP_REQUIREMENT_OPERATIONS (WRO) — the primary driver, supplying work order material requirement rows keyed by WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, and INVENTORY_ITEM_ID.
• EAM_WORK_ORDER_BILLS (EWOB) — the billing transaction table, outer-joined to requirements and filtered so that only rows with BILLING_METHOD = 1 are aggregated.
• MTL_SYSTEM_ITEMS_KFV (MSI) — the key flexfield item view, supplying CONCATENATED_SEGMENTS, PRIMARY_UOM_CODE, and INVOICE_ENABLED_FLAG.
• WIP_EAM_PARAMETERS (WEP) — the EAM parameter table, contributing the INVOICE_BILLABLE_ITEMS_ONLY and MATERIAL_BILLABLE_FLAG attributes used to decide whether an item is billable.
• WIP_OPERATION_RESOURCES and BOM_RESOURCES — referenced in the second half of the UNION, which presents resource requirement lines alongside material lines.
• MTL_SYSTEM_ITEMS — the base item master, referenced by the KFV view and join logic.

The definition is a UNION of two branches: a material branch (TYPE = 1) built from WIP_REQUIREMENT_OPERATIONS and MTL_SYSTEM_ITEMS_KFV, and a resource branch drawing from BOM_RESOURCES/WIP_OPERATION_RESOURCES. All billing joins are outer joins, so requirements with no billing activity still appear with a billed quantity of zero.

Key Columns

• WIP_ENTITY_ID — the work order identifier; the primary grouping key.
• ORGANIZATION_ID — the inventory organization owning the work order.
• OP_SEQ_NUM — the operation sequence number (aliased from OPERATION_SEQ_NUM).
• ITEM_RESOURCE_ID / ITEM_RESOURCE_NAME — the inventory item ID or resource ID, and its concatenated display name (item segments or RESOURCE_CODE).
• TYPE — discriminator between material (1) and resource line types.
• UOM — the primary unit of measure of the item or resource.
• APPLIED_QUANTITY — the quantity issued or applied to the requirement (QUANTITY_ISSUED).
• BILLED_QUANTITY — the sum of EAM_WORK_ORDER_BILLS.BILLED_QUANTITY for billing method 1, defaulted to 0 via NVL.
• BILL_QUANTITY — the remaining billable amount, computed as APPLIED_QUANTITY minus BILLED_QUANTITY.
• BILL_INVENTORY_ITEM_ID — populated only when the item is invoice-enabled and EAM parameters permit billable items; otherwise NULL.
• BILL_UOM — the UOM applicable to billing (mapped from PRIMARY_UOM_CODE).
• BILLING_METHOD — carried from EAM_WORK_ORDER_BILLS; the filter restricts this branch to method 1.

Common Use Cases and Queries

The most frequent use is interrogating outstanding billable quantities for a work order:

• Open billing analysis — SELECT WIP_ENTITY_ID, ITEM_RESOURCE_NAME, APPLIED_QUANTITY, BILLED_QUANTITY, BILL_QUANTITY FROM EAM_BILL_BY_REQUIREMENTS_V WHERE BILL_QUANTITY > 0 ORDER BY WIP_ENTITY_ID, OP_SEQ_NUM. This isolates requirements with a remaining billable balance.
• Billing method verification — filtering on BILLING_METHOD confirms which requirement lines are governed by the active method, helping reconcile discrepancies between the form and the bills table.
• Billable item eligibility — querying WHERE BILL_INVENTORY_ITEM_ID IS NOT NULL returns only items that pass the INVOICE_ENABLED_FLAG and INVOICE_BILLABLE_ITEMS_ONLY/MATERIAL_BILLABLE_FLAG checks in the view logic.
• Work order billing reconciliation — joining WIP_ENTITY_ID and ORGANIZATION_ID to WIP_DISCRETE_JOBS or EAM_WORK_ORDERS_V to produce a full work order billing status report.

Because the view resolves UOM, item naming, and billing eligibility in a single statement, it remains the preferred data source for both the EAM billing form and downstream reporting queries in release 12.1.1 and 12.2.2.