Results for “inv_3pl_billing_counter_pvt”

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

Overview

INV_3PL_BILLING_COUNTER_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It supports third-party logistics (3PL) billing counter functionality within Oracle Inventory. The package manages counter readings associated with contractual arrangements between a warehouse operator and a customer, allowing consumption or activity volumes captured through CSI counters to be recorded and reconciled against billing agreements held in Oracle Contracts.

The package is declared with AUTHID CURRENT_USER, meaning its database objects execute with the privileges of the invoking user rather than the defining user, which is typical for private helper packages in the 3PL billing flow. It carries an API classification of PVT, indicating it is not intended as a public integration interface but rather as an internal building block invoked by other EBS components.

Its documented scope is deliberately narrow: two program units covering one insert/update operation and one lookup function. This reflects its role as a supporting utility for higher-level 3PL billing programs and form logic rather than a standalone processing engine.

Key Procedures and Functions

• inv_insert_readings_using_api — A procedure that inserts or processes a counter reading for a given counter. It accepts identifiers for the counter, the count date, the new reading value, the net reading value, and an associated transaction identifier. This procedure encapsulates the logic required to create counter reading records consistent with the Inventory counter data model, presumably delegating to standard counter APIs and applying validation before persistence.
• get_top_counter_details — A function returning a NUMBER. It accepts a contract identifier and a contract line/entity identifier and returns a counter reference value. Its purpose is to resolve the applicable or "top" counter for a given contractual context, enabling callers to determine which counter governs billing calculations for that agreement line. The single numeric return is consistent with returning a counter identifier or association reference used in subsequent processing.

Tables Accessed

The package interacts with the CSI (Installed Base) and OKC (Contracts) table families through APPS synonyms:

• CSI_COUNTERS_B and CSI_COUNTER_ASSOCIATIONS — define counters and their associations to items or instances, which are queried by get_top_counter_details to resolve the correct counter for a contract context.
• CSI_COUNTER_READINGS — stores the actual meter or counter readings written by inv_insert_readings_using_api.
• CSI_ITEM_INSTANCES and CSI_TRANSACTIONS_S — provide instance and transaction context linking readings to installed base entities.
• CS_CSI_COUNTER_GROUPS — groups counters, supporting organization or hierarchy-based resolution of the applicable counter.
• OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, and OKC_K_LINES_B — supply contract header, item, and line data used to map a contract and line to the relevant counter.
• DUAL — used for simple scalar evaluations and default returns.

Usage Notes

Because the package is classified as PVT and is referenced by three other packages, it is invoked internally by higher-level 3PL billing and counter management modules rather than by end users directly. Typical invocation paths include concurrent programs that import or recalculate counter readings for billing periods, and form-based transactions where a user records a meter reading against a contract. Custom extensions should treat this package as a dependent utility: the supported integration approach is to call the public 3PL billing APIs that in turn invoke this private package, thereby preserving the integrity of counter association and contract linkage logic.

Developers tracing the behavior of get_top_counter_details should note that its resolution logic is bound to the CSI counter association and OKC contract structures listed above; changes to contract or counter configuration can therefore change which counter is returned for a given contract and line combination.