Search Results oks_time_measures_pub




Overview
Explore in AI Chat

Overview

The APPS.OKS_TIME_MEASURES_PUB package body is a public (PUB classified) PL/SQL API within the Oracle E-Business Suite Service Contracts (OKS) module. Its principal business function is to compute time-based service quantities and durations required to support service contract pricing, billing, and coverage calculations. Service contracts frequently require derived values such as the number of full billing periods covered, the duration of a partial period, the applicable unit of measure, or the quantity of service deliverable within a specified number of days. Rather than embedding this arithmetic logic throughout the application, Oracle centralizes it in this package so that pricing engines, contract authoring flows, and billing processes can invoke a consistent, validated calculation.

The package exposes a published API surface, indicating that it is intended for supported invocation by other EBS modules and by customer extensions. It also serves as an internal utility layer consumed by numerous sibling packages in the Service Contracts schema, as evidenced by its dependency and reverse-dependency footprint.

Key Procedures and Functions

The ETRM metadata documents eleven public procedures and functions. Recurring naming patterns indicate two functional clusters: period/duration calculation and quantity/UOM calculation.

  • GET_TARGET_QTY, GET_TARGET_QTY_CAL, and GET_TARGET_QTY_SERVICE — Return the target service quantity under different calculation bases: a general calculation, a calendar-based calculation, and one oriented toward the service being delivered. These drive quantity defaults for service lines.
  • GET_PARTIAL_PERIOD_DURATION and GET_FULL_PERIODS — Compute the duration of a portion of a period and the count of complete periods spanned by a date range, supporting proration of contract value.
  • GET_CON_FACTOR — Derives a conversion factor, used to normalize quantities across differing measurement bases.
  • GET_QTY_FOR_DAYS — Converts a number of days into a corresponding service quantity.
  • GET_QUANTITY — General-purpose quantity retrieval for service measure calculations.
  • GET_UOM_CODE and GET_DURATION_UOM — Resolve the unit of measure for a quantity and for a duration respectively.
  • GET_MONTHS_BETWEEN — Calculates the number of months spanning two dates, the foundational period metric used by the period functions above.

All routines are declared in the package specification and implemented in this body; the metadata does not prescribe parameter signatures, so callers should consult the specification in the EBS database for exact arguments.

Tables Accessed

The package reads reference and setup data through two documented APPS synonyms:

  • MTL_UNITS_OF_MEASURE_TL — the Inventory unit-of-measure translation table, consulted to resolve UOM codes and their language-specific descriptions returned by GET_UOM_CODE and GET_DURATION_UOM.
  • OKC_TIME_CODE_UNITS_B — the base table defining time code units used by the Contracts Core time framework, supplying the conversion relationships between time units on which duration and period calculations depend.

No transactional tables are documented as being written by this package; it behaves as a calculative/read-only utility, deriving results from setup and date inputs.

Usage Notes

Because the package is classified PUB and is referenced by seventeen other database objects, it is invoked broadly across the Service Contracts module rather than through a single interface. Typical callers include service contract authoring forms and their underlying APIs, pricing and billing routines that must prorate or annualize service charges, and concurrent programs that generate or renew contract lines. The dependency list confirms integration with libraries such as FND_API (standard EBS API error/return handling), OKC_API, OKC_TIME_UTIL_PUB, and OKS_BILL_UTIL_PUB, indicating that this package participates in coordinated contract lifecycle and billing logic.

Customizations and extensions should call the public routines rather than duplicating the period and quantity arithmetic, ensuring consistent behavior with the seeded pricing engine. Because no database object references this package directly (only packages do), it is a leaf-level utility in the dependency graph, making it safe to invoke from custom code without triggering unintended cascading behavior. Developers should verify the package specification for exact parameter modes and return types, and should validate inputs against the same UOM and time code setup data the package itself depends on.