Results for “okc_time”

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

Overview

APPS.OKC_TIMEUNIT_V is a reporting view in the Oracle E-Business Suite Contracts (OKC) schema that exposes the relationship between contract time units and the standard units of measure defined in Oracle's common unit-of-measure framework. In the ETRM (Enterprise Contract and Transaction Management) data model, contracts frequently express durations, periods, and quantities in terms that must be normalized against a canonical unit-of-measure and a lookup-driven time code. This view joins the time-code-to-unit mapping held in OKC_TIME_CODE_UNITS_B to the descriptive text stored against units of measure, and further resolves the time unit's meaning through the FND_LOOKUPS lookup type OKC_TIME. The result is a human-readable, denormalized rowset suitable for reporting, concurrent program output, and integration extracts.

The view is owned by APPS and is therefore a public, read-only object available to any session with the standard APPS grants. It is version-neutral across EBS 12.1.1 and 12.2.2; the documented metadata (ETRM 12.2.2) shows no structural divergence from the 12.1.1 form, meaning queries written against it remain portable between the two releases.

Underlying Base Objects

The view is defined over three referenced objects:

• OKC_TIME_CODE_UNITS_B (accessed via synonym) — the driving table supplying uom_code, tce_code, quantity, and active_flag. The "_B" suffix indicates it is the base (non-translated) table of the time code units entity.
• OKX_UNITS_OF_MEASURE_V (view) — supplies unit_of_measure_tl, description, and disable_date, providing the translatable and descriptive attributes of each unit of measure.
• FND_LOOKUPS (view) — supplies the lookup meaning for lookup_type = 'OKC_TIME', which yields the TimeUnit display value in the SELECT list.

FND_GLOBAL (package) is also documented as a referenced base object, reflecting the environment context typically invoked by views in the APPS layer. The joins are equijoins on tcu.tce_code = fndl.lookup_code and uom.uom_code = tcu.uom_code. The trailing filter on disable_date is present in the source but commented out, so expired units of measure are not excluded by the view itself.

Key Columns

• UOM_CODE — the unit-of-measure code from OKC_TIME_CODE_UNITS_B; the join key to the unit-of-measure view.
• UNIT_OF_MEASURE — the translatable name of the unit of measure (unit_of_measure_tl).
• DESCRIPTION — the longer description of the unit of measure.
• TCE_CODE — the time code entity value that links to the OKC_TIME lookup.
• TIMEUNIT — the lookup meaning resolved from FND_LOOKUPS for lookup_type OKC_TIME, providing the business-friendly time unit label.
• QUANTITY — the numeric quantity associated with the time-code/unit combination.
• INACTIVE_DATE — sourced from the unit of measure's disable_date; NULL for active units.
• ACTIVE_FLAG — the active indicator carried from the base table.

Common Use Cases and Queries

Typical uses include populating time-unit selection lists in contract authoring, reconciling contract term quantities against standard units, and feeding downstream extracts that require a readable time unit. A simple verification query:

SELECT uom_code, unit_of_measure, tce_code, timeunit, quantity, active_flag FROM apps.okc_timeunit_v;

To retrieve only active mappings with an explicit expiration guard:

SELECT uom_code, timeunit, quantity FROM apps.okc_timeunit_v WHERE active_flag = 'Y' AND NVL(inactive_date, TRUNC(SYSDATE)) >= TRUNC(SYSDATE);

Joining to contract line or term tables on uom_code allows reporting of contract durations in their resolved time unit, while joining on tce_code provides the lookup meaning for grouping and aggregation.