Results for “counter_net_reading”

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

Overview

The APPS.MTL_FETCH_AGREEMENT_LINES view is an EBS reporting construct that joins Oracle Service Contracts (OKC) agreement structures to 3PL billing counter configuration and counter readings. Its purpose is to expose, for each usage-based service agreement line, the associated client, service item, billing UOM, service period, and the latest counter reading recorded for the counter tied to that contract line. The view is central to the 3PL (third-party logistics) billing flow, where charges are computed from meter-style counter values rather than fixed quantities.

In the EBS 12.1.1 and 12.2.2 releases, the view appears in the ETRM object catalog under owner APPS. It surfaces a column named counter_net_reading, which is why a search on that term resolves to this view. The view relies on the server-side package INV_3PL_BILLING_COUNTER_PVT to resolve the "top" counter for a given contract and line, meaning it is not a simple flat projection; it embeds procedural logic at query time.

Underlying Base Objects

The documented referenced objects are CSI_COUNTER_READINGS, HZ_CUST_ACCOUNTS, HZ_PARTIES, INV_3PL_BILLING_COUNTER_PVT, MTL_CLIENT_PARAMETERS, MTL_SYSTEM_ITEMS_B_KFV, OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, and OKC_K_LINES_B.

• OKC_K_HEADERS_ALL_B / OKC_K_LINES_B / OKC_K_ITEMS supply the contract header, contract line, and item-level agreement data. Items are restricted to JTOT_OBJECT1_CODE = 'OKX_USAGE', identifying usage lines.
• MTL_SYSTEM_ITEMS_B_KFV provides the service item and its concatenated segments, resolved against OKC_K_ITEMS.OBJECT1_ID1 (inventory item) and OBJECT1_ID2 (organization).
• MTL_CLIENT_PARAMETERS links the contract line's customer account to a client id, code, and number.
• HZ_CUST_ACCOUNTS and HZ_PARTIES resolve the customer account to a party name for display.
• CSI_COUNTER_READINGS stores the actual counter values; the view selects the most recent reading by matching the maximum COUNTER_VALUE_ID for the resolved counter.
• INV_3PL_BILLING_COUNTER_PVT.get_top_counter_details is invoked to derive the effective counter for the contract/line combination, both for the reading join and for the reading subquery.

Key Columns

• contract_number, contract_id, authoring_org_id — contract identity and owning organization.
• service_agreement_line_id — the OKC line id (OKC_K_ITEMS.CLE_ID), keyed to the agreement line.
• client_id, client_code, client_number, client_name — the 3PL client associated with the agreement line.
• service_item, service_item_org_id, inventory_item_id, billing_uom — the billed item and its unit of measure.
• service_line_start_date, service_line_end_date — the effective period of the service line.
• counter_item_id — the counter instance resolved via the billing counter package.
• counter_net_reading — the net reading value from CSI_COUNTER_READINGS; the central measure used for usage billing.
• last_computation_date and counter_reading — timestamp and raw reading of the latest counter record.

Common Use Cases and Queries

Typical uses include validating usage-based billing inputs, reconciling counter readings against invoiced quantities, and building client-facing usage reports. Because the view already resolves the latest reading, it is convenient for point-in-time reporting.

SELECT contract_number,
       client_name,
       service_item,
       billing_uom,
       counter_net_reading,
       last_computation_date
  FROM apps.mtl_fetch_agreement_lines
 WHERE service_line_start_date >= :p_from_date;

Analysts may also filter by client_id to isolate a single 3PL client, or join back to CSI_COUNTER_READINGS when historical readings—not just the latest—are required. Performance depends on the counter package calls, so restricting by contract or client is advisable.