Search Results okc_time_code_units_v

Overview

The view APPS.OKS_TIME_CODE_UNITS_V is a lightweight database object within the Service Contracts (OKS) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to define object metadata for use by the JTF (Java Technology Framework) layer, which supports the self-service and interaction-center user interfaces. Rather than exposing business data directly, the view delivers a denormalized projection—comprising an identifier, a placeholder, and a null name field—that JTF consumes to populate object metadata registries. The view is owned by the APPS schema and holds a VALID status, indicating it is a compiled, functioning database object present in a standard installation.

Underlying Base Objects

The view is defined over a single documented base object: OKC_TIME_CODE_UNITS_V, itself a view in the Contracts (OKC) schema. The ETRM metadata lists only this one referenced object, and the view text confirms a direct, one-to-one dependency with no joins, aggregations, or filters applied at this layer. This construction means OKS_TIME_CODE_UNITS_V acts as a thin wrapper or adaptation layer: it renames and reshapes the column output of OKC_TIME_CODE_UNITS_V to match the naming convention expected by the JTF metadata framework. Because the underlying object is itself a view, the true physical source tables reside further down the dependency chain within the Contracts schema, and any change to those base tables propagates through OKC_TIME_CODE_UNITS_V to this OKS-level view.

Key Columns

The view exposes three columns, all aliased to conform to JTF metadata requirements:

• ID1 — mapped from the source column UOM_CODE (Unit of Measure Code). This carries the code identifying each time-related unit of measure, serving as the primary identifier consumed by JTF.
• ID2 — populated with the literal '#', a constant placeholder value rather than a data-bearing column. The use of a fixed literal is consistent with JTF metadata definitions where a stable secondary key is required but no meaningful value exists.
• NAME — returned as NULL, indicating no descriptive name is supplied at this layer. Consumers requiring a display name must obtain it from the underlying Contracts object or an associated lookup.

Note that the ETRM column listing names only NAME. The view text, however, documents all three projected columns (ID1, ID2, NAME), which is the authoritative definition for query purposes.

Common Use Cases and Queries

This view is most relevant to EBS developers and administrators working with JTF metadata registration, service contract time units, and interaction-center configuration rather than to end-user reporting. Typical scenarios include troubleshooting JTF object metadata, validating that time code units are available to a JTF-enabled page, and reconciling the OKS-facing projection against the OKC source view. A basic query follows:

• SELECT ID1, ID2, NAME FROM APPS.OKS_TIME_CODE_UNITS_V; — retrieves the complete projection for all time code units.
• SELECT ID1 FROM APPS.OKS_TIME_CODE_UNITS_V WHERE ID1 = :uom_code; — verifies that a specific unit of measure is exposed to JTF.
• SELECT v.ID1, c.* FROM APPS.OKS_TIME_CODE_UNITS_V v, APPS.OKC_TIME_CODE_UNITS_V c WHERE v.ID1 = c.UOM_CODE; — joins back to the underlying Contracts view to recover descriptive attributes that this view omits.

Because NAME is always null and ID2 is a constant, queries should rely on the base OKC object whenever human-readable labels are required. The view should be treated strictly as a metadata bridge, not as a reporting source.