Results for “uom_code”

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

Overview

The OKC_TIMEUNIT_V view belongs to the Contracts Core (OKC) product within Oracle E-Business Suite and is deployed in the APPS schema. It is a reporting and integration view that presents the valid time units used in contract authoring, particularly the units of measure associated with time-based pricing and time-code logic. In the Oracle Contracts architecture, time units (for example, Days, Weeks, Months, Years) are referenced when contract terms express duration, billing periods, or periodic rates. Rather than requiring developers and report authors to join the underlying code-unit definition table to the units-of-measure repository and the FND lookup definitions, OKC_TIMEUNIT_V encapsulates those joins and exposes a single, denormalized result set. This makes it the preferred access point for custom reports, concurrent programs, and interface extracts that require a readable time-unit list. The view is valid and available in both the 12.1.1 and 12.2.2 codelines; the documented ETRM metadata for 12.2.2 confirms its APPS ownership and its dependency on the base objects described below.

Underlying Base Objects

The view is defined over three primary data sources, combined in a single SQL statement. The driving table is OKC_TIME_CODE_UNITS_B, referenced through a synonym, which stores the association between a time code and a unit of measure together with the quantity and an active flag. It is joined to OKX_UNITS_OF_MEASURE_V, the units-of-measure view that supplies the UOM code, the translated unit-of-measure name, the description, and the disable date. A third join links TCU.TCE_CODE to FND_LOOKUPS with the constraint that LOOKUP_TYPE equals 'OKC_TIME'; this supplies the FNDL.MEANING value exposed as TIMEUNIT. Note that the view text includes a commented-out predicate on UOM.DISABLE_DATE, indicating that inactive units of measure are not filtered out by default; consumers must apply their own date or active-flag filters. The documented dependencies also list FND_GLOBAL (PACKAGE), which is commonly referenced by such views for session and multi-org context, although it does not contribute columns to the final projection.

Key Columns

• UOM_CODE — The units-of-measure code from the base time-code-units table, serving as the join key to the UOM repository.
• UNIT_OF_MEASURE — The translated name of the unit of measure from OKX_UNITS_OF_MEASURE_V.
• DESCRIPTION — The descriptive text of the unit of measure.
• TCE_CODE — The time code that links to the FND lookup of type OKC_TIME.
• TIMEUNIT — The lookup meaning (FNDL.MEANING), giving the user-facing label for the time unit.
• QUANTITY — The numeric quantity associated with the time code unit, expressing how many base units the code represents.
• INACTIVE_DATE — The disable date of the unit of measure, sourced from UOM.DISABLE_DATE; null indicates an enabled unit.
• ACTIVE_FLAG — The active flag from the base table, indicating whether the time-code unit association is currently usable.

Common Use Cases and Queries

Typical usage includes validating time units during contract interfaces, populating LOV-style queries in custom forms, and generating extracts for downstream billing engines. A common pattern restricts the result to active entries and enabled units of measure:

• SELECT uom_code, unit_of_measure, timeunit, quantity FROM okc_timeunit_v WHERE active_flag = 'Y' AND (inactive_date IS NULL OR inactive_date > SYSDATE);
• SELECT timeunit, unit_of_measure FROM okc_timeunit_v WHERE tce_code = :tce_code;
• SELECT uom_code, description FROM okc_timeunit_v ORDER BY timeunit;

Because the view does not itself filter inactive units, reports requiring only currently effective time units should always include the INACTIVE_DATE and ACTIVE_FLAG predicates shown above.