Results for “activity_source”

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

Overview

APPS.EAM_BILL_BY_ACTIVITIES_V is a reporting view in the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Its documented purpose is to simplify Oracle Forms coding by consolidating work order billing information required by the "Bill by Activities" block within the EAM work order execution form. Rather than joining multiple work management, inventory, and lookup tables directly in form logic, the view exposes a single denormalized result set that the form—and any external consumer—can query with minimal effort.

The view is defined over work order billing records and aggregates billed quantities per work order activity. Because it resides in the APPS schema and is deployed in both 12.1.1 and 12.2.2 environments, it is available to any custom concurrent program, BI Publisher report, or SQL-based integration connecting to EBS. Note that the view is read-only by nature; it presents derived data and is not intended to back DML operations.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

• EAM_WORK_ORDER_BILLS (synonym) — the primary transactional table holding billed quantities per work order and organization.
• WIP_DISCRETE_JOBS (synonym) — the EAM work order header carrying activity attributes such as the primary item, activity type, activity cause, and activity source.
• WIP_EAM_PARAMETERS (synonym) — EAM work management parameters, supplying the INVOICE_BILLABLE_ITEMS_ONLY setting.
• MTL_SYSTEM_ITEMS (synonym) — the item master, providing description, primary UOM, and the invoice-enabled flag for the activity item.
• MFG_LOOKUPS (view) — the shared lookup view, joined three times against lookup types MTL_EAM_ACTIVITY_TYPE, MTL_EAM_ACTIVITY_CAUSE, and MTL_EAM_ACTIVITY_SOURCE.

The join between WIP_DISCRETE_JOBS and EAM_WORK_ORDER_BILLS is an outer join restricted to billing method 2, meaning one row is returned per work order activity even when no billing lines exist. The remaining joins to parameters, items, and lookups are likewise outer joins keyed on organization and lookup code, ensuring translation of coded values without dropping activity rows.

Key Columns

• WIP_ENTITY_ID and ORGANIZATION_ID — identify the work order and the inventory organization, forming the natural key of the result set together with ACTIVITY_ID.
• ACTIVITY_ID — the primary item of the work order, representing the activity performed.
• BILLED_QUANTITY — the summed BILLED_QUANTITY from EAM_WORK_ORDER_BILLS, defaulted to 0 when no billing rows exist.
• BILL_QUANTITY — computed as 1 minus BILLED_QUANTITY, indicating the remaining quantity still eligible for billing.
• BILL_INVENTORY_ITEM_ID and BILL_UOM — the item to be billed and its unit of measure, controlled by the invoice-enabled flag and the INVOICE_BILLABLE_ITEMS_ONLY parameter.
• ACTIVITY_DESCRIPTION, ACTIVITY_TYPE, ACTIVITY_SOURCE, and ACTIVITY_CAUSE — descriptive attributes resolved from MTL_SYSTEM_ITEMS and the MFG_LOOKUPS meanings. The ACTIVITY_CAUSE column, mapped to lookup type MTL_EAM_ACTIVITY_CAUSE, is the attribute most commonly searched by users diagnosing billing eligibility.

Common Use Cases and Queries

Typical scenarios include reviewing billing status per activity, reconciling unbilled activities, and driving invoice generation from EAM work orders. The following query retrieves billing status for a given work order:

• SELECT wip_entity_id, organization_id, activity_id, activity_cause, activity_type, billed_quantity, bill_quantity, bill_uom FROM apps.eam_bill_by_activities_v WHERE wip_entity_id = :p_wip_entity_id;
• SELECT activity_cause, SUM(bill_quantity) FROM apps.eam_bill_by_activities_v WHERE organization_id = :p_org GROUP BY activity_cause;
• SELECT * FROM apps.eam_bill_by_activities_v WHERE NVL(billed_quantity, 0) = 0 AND bill_inventory_item_id IS NOT NULL;

Queries should always filter by organization where practical, since the view spans all organizations. Because aggregation is performed inside the view, no additional GROUP BY is required unless further summarization is intended.