Search Results billed_uom_code

Overview

APPS.EAM_WORK_ORDER_BILL_DETAILS_V is a database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered as part of the Enterprise Asset Management (EAM) product family and is documented in ETRM as "an internal view used to simplify forms coding." Its purpose is therefore not primarily end-user reporting, but rather to consolidate the join logic required to display work order billing information on EAM maintenance and billing forms. Because the view encapsulates multi-table joins across work order billing, work-in-process entities, project accounting, trading community, and receivables, it provides a stable, denormalized projection that forms developers can query without embedding complex join conditions in form-level code.

Underlying Base Objects

The view text selects from EAM_WORK_ORDER_BILLS (aliased EWOB) as the driving table, which stores the billing lines generated for EAM work orders. It is joined to WIP_ENTITIES (WE) on WIP_ENTITY_ID and ORGANIZATION_ID to retrieve the work order name; to PA_PROJECTS_ALL (PPA) and PA_TASKS (PT) on PROJECT_ID and TASK_ID using outer joins to obtain project and task descriptions; to HZ_CUST_ACCOUNTS (HCA) and HZ_PARTIES (HP) to resolve customer name; and to RA_CUSTOMER_TRX_ALL (RCTA) and RA_CUSTOMER_TRX_LINES_ALL (RCTLA) to retrieve the associated receivables invoice number, date, and line number. The joins to receivables are keyed on the interface attributes INTERFACE_LINE_ATTRIBUTE3, INTERFACE_LINE_ATTRIBUTE4, and the context value 'WORK ORDER BILLING', which is the mechanism EAM uses to correlate a work order billing record with its AR invoice line. All base objects are referenced through APPS synonyms, consistent with standard EBS 12.1.1 and 12.2.2 architecture.

Key Columns

• WORK_REQUEST_ID — the identifier of the associated work request, exposed from EAM_WORK_ORDER_BILLS. This is the column users typically search for when tracing a billing line back to its originating work request.
• WIP_ENTITY_ID / WIP_ENTITY_NAME — the work order identifier and its display name.
• ORGANIZATION_ID — the inventory organization owning the work order.
• CUSTOMER_ID / CUSTOMER_NAME — the bill-to customer account and party name.
• INVENTORY_ITEM_ID / RESOURCE_ID — the item or resource being billed.
• BILLED_INVENTORY_ITEM_ID, BILLED_QUANTITY, BILLED_UOM_CODE, BILLING_BASIS — the billed entity, quantity, unit of measure, and the basis used to compute the charge.
• COST_OR_LISTPRICE, COSTPLUS_PERCENTAGE, COST_TYPE_ID, PRICE_LIST_HEADER_ID, BILLED_AMOUNT — pricing attributes and the resulting billed amount.
• PROJECT_ID / PROJECT_NAME, TASK_ID / TASK_NAME — project accounting context for the billing line.
• TRX_NUMBER, LINE_NUMBER, INVOICE_DATE, REF_INVOICE_TRX_NUMBER, REF_INVOICE_LINE_NUMBER — the AR invoice reference and its date, resolved through RCTA and RCTLA.
• CURRENCY_CODE, CONVERSION_RATE, CONVERSION_TYPE_CODE, CONVERSION_RATE_DATE — currency and conversion details applied to the billing amount.
• BILLED_DATE — aliased from CREATION_DATE of the billing record.

Common Use Cases and Queries

The principal use case is tracing EAM work order billing lines to their receivables invoices, and from a work request to the amounts billed. A typical query by work request is:

SELECT wip_entity_name,
       work_request_id,
       customer_name,
       billed_quantity,
       billed_amount,
       trx_number,
       line_number,
       invoice_date
FROM   apps.eam_work_order_bill_details_v
WHERE  work_request_id = :work_request_id
AND    organization_id = :org_id;

A second scenario reconciles billing amounts for a given invoice number by joining on TRX_NUMBER, and a third aggregates billed amounts by project and task for cost recovery reporting. Because the view is documented as internal and intended for forms coding, Oracle does not guarantee its columns across patches or upgrades; custom reports should ideally be built against the underlying base tables, using this view as a functional reference for the correct join logic.