Results for “okl_ag_source_maps_v”

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

Overview

OKL_AG_SOURCE_MAPS_V is a reporting view within the Oracle Leasing and Finance Management (OKL) module of Oracle E-Business Suite. It exposes the configuration records that define source maps for the Account Generator (AG) used by leasing contracts. In Oracle EBS, the Account Generator derives accounting flexfield combinations dynamically from source data during transaction processing, and a source map determines how the Account Generator reads a value from a given source object or table and maps it into a generated accounting segment. This view presents those mapping definitions in a form suitable for inquiry, reporting, and integration.

The view is documented in ETRM 12.2.2 and is identified as not implemented in the reference database, meaning the definition is delivered but the corresponding database object was not created in the environment from which the metadata was extracted. Because it is a view rather than a base table, no DML should be performed against it; consumers use it strictly for read access.

Underlying Base Objects

The documented definition of OKL_AG_SOURCE_MAPS_V is a straightforward projection over a single base table, OKL_AG_SOURCE_MAPS. No additional base objects are documented. The SELECT list aliases the base table as ALSB and returns every column required to describe a source map record, including its primary key, line type association, versioning attributes, audit columns, and multi-organization identifier.

The view adds a row-level security predicate. The WHERE clause compares the entity NVL(ORG_ID, ...) against a value derived from USERENV('CLIENT_INFO'), decoding the first ten characters of the client information string to a number and defaulting to -99 where the value is blank or unavailable. This restricts the rows returned to those matching the organization context established by the connecting session, consistent with the multi-org access model used across EBS transaction tables.

Key Columns

• ROW_ID — the ROWID of the underlying row in OKL_AG_SOURCE_MAPS, providing a physical locator for the record.
• ID — the primary key identifying the source map definition.
• AE_LINE_TYPE — the Account Generator line type to which the source map applies, linking the mapping to the transaction line context that drives account generation.
• OBJECT_VERSION_NUMBER — the optimistic locking version used by the EBS framework to detect concurrent updates.
• SOURCE — the source object or table from which the Account Generator retrieves the value.
• PRIMARY_KEY_COLUMN — the column on the source used to identify the relevant source row.
• SELECT_COLUMN — the specific column on the source from which the generated segment value is selected. This is the attribute commonly referenced when searching for "select_column" in relation to source map configuration.
• ORG_ID — the operating unit or organization owning the record, used by the view's security predicate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row.

Common Use Cases and Queries

This view is primarily used to audit and troubleshoot Account Generator behavior for leasing transactions. Administrators query it to confirm which source column supplies a given segment for a line type, and to compare the configured SELECT_COLUMN and PRIMARY_KEY_COLUMN against the actual source data.

• Retrieve all source maps for a line type:
  SELECT id, ae_line_type, source, select_column FROM okl_ag_source_maps_v WHERE ae_line_type = :line_type;
• Find which source maps reference a particular column:
  SELECT id, ae_line_type, source FROM okl_ag_source_maps_v WHERE select_column = :column_name;
• Audit recent configuration changes:
  SELECT id, ae_line_type, last_updated_by, last_update_date FROM okl_ag_source_maps_v ORDER BY last_update_date DESC;

Because the view enforces organization security through USERENV('CLIENT_INFO'), queries must be executed from a session with the correct operating unit context to return the expected rows; failure to do so can result in an empty result set even when records exist in the base table.