Results for “okl_cost_adjustments_v”

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

Overview

OKL_COST_ADJUSTMENTS_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. Its documented purpose is to present a denormalized, language-aware projection of the two principal cost adjustment entities: the base table OKL_COST_ADJUSTMENTS_B and its translation table OKL_COST_ADJUSTMENTS_TL. In Oracle EBS Release 12.1.1 and 12.2.2, the OKL module stores cost adjustment definitions that influence how lease and finance contracts derive and subsidize costs, and this view serves as the primary read interface for that data.

Because the view joins the translation table using USERENV('LANG'), it automatically returns descriptive text in the session's language, making it suitable for both concurrent program reporting and integration extracts that must respect localization. Oracle does not typically expose the _B and _TL tables directly to end users; this view is the sanctioned access layer, ensuring that callers receive the correct language row alongside all operational attributes.

Underlying Base Objects

The view is defined over two synonyms registered in the ETRM metadata: OKL_COST_ADJUSTMENTS_B and OKL_COST_ADJUSTMENTS_TL. The join condition in the view text is CDJ.ID = CDJT.ID AND CDJT.LANGUAGE = USERENV('LANG'), so the base row supplies all operational, audit, and attribute columns, while the translation row supplies SHORT_DESCRIPTION, DESCRIPTION, and COMMENTS. Both underlying objects exist only as synonyms in the documented metadata, meaning the physical tables are owned elsewhere but are accessible to APPS code and query tools.

Key Columns

• ROW_ID – Maps to CDJ.ROWID; useful for identifying the physical base row, though not a stable business key.
• ID – Primary surrogate key linking the base and translation rows.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the OKL framework during updates.
• PROCESSING_TYPE – The user's search term; identifies how the cost adjustment is processed by the leasing engine.
• ADJUSTMENT_SOURCE_TYPE / ADJUSTMENT_SOURCE_ID – Classify and reference the originating adjustment source.
• PARENT_OBJECT_CODE / PARENT_OBJECT_ID – Point to the owning business object, enabling polymorphic association.
• BASIS, VALUE, PERCENT_BASIS_VALUE, DEFAULT_SUBSIDY_AMOUNT – Quantitative attributes driving the adjustment amount.
• STREAM_TYPE_ID, SUPPLIER_ID – Foreign references to stream type and supplier definitions.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield (DFF) columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS who-columns.
• SHORT_DESCRIPTION, DESCRIPTION, COMMENTS – Translated descriptive text from the _TL table.

Common Use Cases and Queries

The view is commonly queried for reporting on cost adjustment configuration, for integration extracts into downstream pricing or contract systems, and for validating processing types configured in a given environment. A typical query that focuses on the user's search term is:

• SELECT id, processing_type, basis, value, short_description FROM apps.okl_cost_adjustments_v WHERE processing_type = :p_type;
• SELECT id, parent_object_code, parent_object_id, processing_type FROM apps.okl_cost_adjustments_v WHERE parent_object_id = :p_parent_id;
• SELECT id, adjustment_source_type, adjustment_source_id, default_subsidy_amount FROM apps.okl_cost_adjustments_v ORDER BY creation_date DESC;

Because the view filters on USERENV('LANG'), callers must ensure their session language has translation rows; otherwise the description columns return null. Performance is generally acceptable on the ID join, and the view should be preferred over direct _B/_TL access to preserve language semantics and encapsulation.