Search Results okr_clsf_types




Overview

OKR_CLSF_TYPES is a configuration table in the Oracle EBS Contracts for Rights (OKR) module, a product line associated with intellectual property and rights management that has been marked obsolete in the EBS 12.1.1 and 12.2.2 releases. The table stores classification types for a property type, functioning as a cross-reference or lookup object that relates a property type to one or more valid classification types. In practical terms, it defines which classifications are permissible for a given intellectual property or property type, acting as the bridge between the property-type catalog and the classification catalog.

The ETRM metadata indicates the object is not implemented in this database, which is consistent with the OKR product's obsolete status. The documentation is therefore primarily of historical and referential interest, useful for understanding legacy schema designs and for migration or archival analysis.

From a data-modeling perspective, the mined heuristic Data Vault classification is satellite-leaning. This suggests that the table behaves less like an independent business hub and more like a dependent, attribute-bearing structure whose identity is derived from its parent entities. Its composite primary key, OKR_IP_CLSF_TYPES_PK, reinforces this view by combining two foreign-key referencing columns rather than relying on a single generated surrogate key.

Key Information Stored

The table's structure centers on a small set of columns that together define the association between property types and classification types.

  • IP_TYPE — Part of the composite primary key (OKR_IP_CLSF_TYPES_PK). Identifies the property type to which a classification applies. This column is also a foreign key to OKR_PROP_TYPES_B.IP_TYPE.
  • CLSF_TYPE — The second component of the composite primary key. Identifies the classification type associated with the given property type.

The documented metadata does not identify a separate surrogate primary key for this object; the primary key is the composite of IP_TYPE and CLSF_TYPE. Both columns are therefore business-key candidates by definition, and together they form the natural unique identifier for each row. No additional descriptive or attribute columns are documented in the provided excerpt, so the table should be treated as a minimal junction or reference structure whose primary purpose is enforcing valid property-type/classification combinations. Where implementations extend such tables, audit columns or enabled flags are common, but none are confirmed in the source metadata and should not be assumed.

Common Use Cases and Queries

Because OKR_CLSF_TYPES governs which classifications are valid for a property type, the most common query pattern is a filtered lookup constrained by property type. A representative pattern would join the classification types for a specific property type, for example selecting CLSF_TYPE from OKR_CLSF_TYPES where IP_TYPE equals a supplied value. Reporting queries frequently join outward to OKR_PROP_TYPES_B to resolve the property-type name and inward from OKR_CLASSIFICATIONS to reconcile actual classification assignments against the permitted set.

Validation and data-quality scenarios use the table to detect orphaned or invalid classifications, comparing rows in OKR_CLASSIFICATIONS against the allowed pairs defined in OKR_CLSF_TYPES. Migration or archival efforts use it to reconstruct the legacy reference data that governed rights classification before the OKR module was retired. In all cases, since the table is not implemented in supported databases, these queries apply primarily to legacy environments, historical extracts, or documentation-driven reconstruction rather than to live EBS 12.1.1 or 12.2.2 instances.

Related Objects

The FK metadata identifies the two most significant related objects, and the transitive relationship through the classification table extends the dependency chain.

  • OKR_PROP_TYPES_B — Referenced by OKR_CLSF_TYPES.IP_TYPE; supplies the property-type definition that each classification row qualifies.
  • OKR_CLASSIFICATIONS — References OKR_CLSF_TYPES and links outward on both IP_TYPE and CLSF_TYPE, meaning classification records must resolve to a permitted property-type/classification pair.

These dependencies confirm that OKR_CLSF_TYPES sits between the property-type catalog and the classification catalog, serving as the validation backbone for rights classification. Any analysis of classification data in the legacy OKR schema should account for this three-table chain, since OKR_CLASSIFICATIONS cannot be fully interpreted without the permitted combinations defined in OKR_CLSF_TYPES and the property types defined in OKR_PROP_TYPES_B. No associated views, APIs, or concurrent programs are documented in the available metadata.