Results for “cost_or_listprice”

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

Overview

EAM.EAM_WORK_ORDER_BILLS is the Enterprise Asset Management table that stores work order billing information in Oracle E-Business Suite 12.1.1 and 12.2.2. It records how completed or in-progress maintenance work orders are priced and invoiced to customers, capturing the commercial dimensions of an EAM work order alongside the cost and labor detail held elsewhere in the EAM and Work in Process schemas. Each row represents a billing line tied to a work order, an operation, and a billable item, enabling organizations that perform maintenance as a chargeable service to generate receivables from their asset management activity.

From a dimensional modeling perspective, the mined foreign-key structure suggests this table behaves as a satellite-leaning entity: it hangs off core transactional hubs such as WIP_EAM_WORK_REQUESTS and reference entities such as MTL_SYSTEM_ITEMS_B and CST_COST_TYPES, carrying descriptive billing attributes rather than acting as an independent hub or a pure many-to-many link. This classification is a heuristic modeling suggestion, not a declared Oracle construct.

Key Information Stored

The table contains 39 documented columns. The most operationally significant are:

• ORGANIZATION_ID — the inventory organization under which the work order and billing occur; a mandatory partitioning key and part of the composite foreign key to MTL_SYSTEM_ITEMS_B.
• WIP_ENTITY_ID and OPERATION_SEQ_NUM — link the billing line to the specific work order and routing operation being charged.
• WORK_REQUEST_ID — foreign key to WIP_EAM_WORK_REQUESTS, anchoring the row to the originating maintenance request.
• BILLED_INVENTORY_ITEM_ID, BILLED_UOM_CODE, and BILLED_QUANTITY — the item, unit of measure, and quantity being billed.
• INVENTORY_ITEM_ID and RESOURCE_ID — the maintained item and resource consumed to perform the work.
• COST_TYPE_ID and COST_OR_LISTPRICE — foreign key to CST_COST_TYPES plus the decision flag selecting cost versus list price as the billing basis.
• COSTPLUS_PERCENTAGE and BILLING_BASIS — markup percentage and the rule governing how the amount is derived.
• BILLED_AMOUNT and OVERRIDE_BILL_AMOUNT — the computed charge and any manual override.
• CURRENCY_CODE, CONVERSION_RATE, CONVERSION_TYPE_CODE, and CONVERSION_RATE_DATE — the currency and conversion context for the amount.
• CUSTOMER_ID and BILL_TO_ADDRESS_ID — the party being invoiced and the destination address.
• INVOICE_TRX_NUMBER and INVOICE_LINE_NUMBER — the resulting receivable transaction reference.
• PROJECT_ID, TASK_ID, and PA_EVENT_ID — project accounting linkage for capitalized or project-charged work.

Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) follow standard EBS conventions. No surrogate primary key is documented in the supplied metadata; the unique business key is most likely the composite of ORGANIZATION_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, and BILLED_INVENTORY_ITEM_ID.

Common Use Cases and Queries

Typical reporting includes billable work order value by customer, cost-versus-list-price analysis, and reconciliation of EAM billing lines to receivable invoices.

• Summarizing charges: SELECT  CUSTOMER_ID, SUM(BILLED_AMOUNT) FROM EAM_WORK_ORDER_BILLS GROUP BY CUSTOMER_ID;
• Joining to work requests to attribute billing: SELECT b.WIP_ENTITY_ID, b.BILLED_AMOUNT, r.* FROM EAM_WORK_ORDER_BILLS b, WIP_EAM_WORK_REQUESTS r WHERE b.WORK_REQUEST_ID = r.WORK_REQUEST_ID;
• Verifying billing basis: filter on BILLING_BASIS and COST_OR_LISTPRICE to explain variances between modeled cost and invoiced amount.
• Multicurrency analysis using CURRENCY_CODE and CONVERSION_RATE for translated reporting.

Related Objects

• WIP_EAM_WORK_REQUESTS — joined via WORK_REQUEST_ID; the parent work request driving the maintenance activity.
• MTL_SYSTEM_ITEMS_B — joined via BILLED_INVENTORY_ITEM_ID and ORGANIZATION_ID; source of billable item definitions.
• CST_COST_TYPES — joined via COST_TYPE_ID; defines the cost basis used in pricing.
• WIP entities (e.g., WIP_DISCRETE_JOBS / WIP_ENTITIES) — keyed by WIP_ENTITY_ID for operation context.
• Receivables (AR) invoice tables — referenced through INVOICE_TRX_NUMBER and INVOICE_LINE_NUMBER.
• Project Accounting objects (PA events, projects, tasks) — linked via PROJECT_ID, TASK_ID, and PA_EVENT_ID.
• FND / audit views — standard EBS audit joins on LAST_UPDATED_BY and LAST_UPDATE_DATE.