Results for “aep_code”

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

Overview

OKL_TRX_TYPES_UV is a seeded, read-only view in the APPS schema belonging to the Oracle Leasing and Finance Management (OKL) module. It presents a denormalized, language-aware representation of transaction type definitions used throughout the leasing application. The view combines the base table OKL_TRX_TYPES_B (which stores language-independent attributes such as transaction type identifiers, accounting event codes, and class codes) with the translation table OKL_TRX_TYPES_TL (which stores the user-facing NAME and DESCRIPTION in the session language). By joining these objects and resolving several coded values into their lookup meanings, the view provides a single reporting source that eliminates the need for consumers to perform their own joins or lookup translations.

Within the Oracle EBS 12.1.1 and 12.2.2 environments, this view is the standard reference for reporting and integration requirements that need to enumerate or describe the transaction types that drive lease accounting and contract processing. Because it presents translated names and decoded descriptions in one row per transaction type, it is well suited to concurrent program reports, Oracle Discoverer or OBIEE extracts, and inbound/outbound interface logic that must resolve a transaction type identifier into something meaningful to end users.

Underlying Base Objects

The view is defined over two documented base objects: OKL_TRX_TYPES_B (referenced through a synonym) and OKL_TRX_TYPES_TL (also referenced through a synonym). The join condition is an equijoin on the ID column, restricted so that the translation row matches the session language via the predicate TRYT.LANGUAGE = USERENV('LANG'). This means the view returns exactly one row per transaction type, with the localized text for the running user's language.

The view also references the package OKL_ACCOUNTING_UTIL, which is documented as a referenced base object. The package function GET_LOOKUP_MEANING is invoked three times within the view's SELECT list to translate coded columns into descriptive text: AEP_CODE into AEP_CODE_DESC (lookup type OKL_ACCOUNTING_EVENT_TYPE), TRY_TYPE into TRY_TYPE_DESC (lookup type OKL_TRANSACTION_TYPE_CATEGORY), and TRX_TYPE_CLASS into TRX_TYPE_CLASS_DESC (lookup type OKL_TRANSACTION_TYPE_CLASS). Since this function call is embedded in the view definition, the localized descriptions are computed at query time and reflect current lookup configuration.

Key Columns

• ID and OBJECT_VERSION_NUMBER – Surrogate primary key of the transaction type and the optimistic locking version, sourced from OKL_TRX_TYPES_B.
• TRY_ID, TRY_ID_FOR – Core identifiers used to relate a transaction type to the originating or related transaction. The columns TRY_ID_NAME and TRY_ID_FOR_NAME are exposed as TO_CHAR(NULL) placeholders in the view definition, meaning the view does not resolve these identifiers to names.
• TRY_TYPE / TRY_TYPE_DESC – Transaction type category code and its decoded lookup meaning (lookup OKL_TRANSACTION_TYPE_CATEGORY).
• AEP_CODE / AEP_CODE_DESC – Accounting event type code and its decoded meaning (lookup OKL_ACCOUNTING_EVENT_TYPE).
• TRX_TYPE_CLASS / TRX_TYPE_CLASS_DESC – Transaction type class code and decoded meaning (lookup OKL_TRANSACTION_TYPE_CLASS).
• NAME, DESCRIPTION – Localized transaction type name and description from OKL_TRX_TYPES_TL.
• SFWT_FLAG, ILC_ID, CONTRACT_HEADER_LINE_FLAG, TRANSACTION_HEADER_LINE_DETAIL – Flags and identifiers controlling whether the transaction type applies at contract, header, line, or detail level.
• ORG_ID – Multi-org operating unit identifier, enabling operating-unit-specific filtering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.

Common Use Cases and Queries

A frequent use case is resolving a stored transaction type identifier to a readable name for reporting. A user searching for the TRY_ID_FOR attribute is typically seeking a lookup or validation source that maps the relationship between transaction types. The following query lists all transaction types with their decoded classes:

SELECT try_id
     , name
     , try_type_desc
     , trx_type_class_desc
     , aep_code_desc
  FROM apps.okl_trx_types_uv
 ORDER BY name;

For multi-org scenarios, restrict results to a single operating unit, since ORG_ID is exposed directly:

SELECT try_id, name, try_id_for, trx_type_class_desc
  FROM apps.okl_trx_types_uv
 WHERE org_id = :p_org_id;

Integration and validation logic can join the view to lease transaction tables on the TRY_ID column to obtain the localized NAME and DESCRIPTION without performing additional lookup resolution. Because the view already decodes the key classification columns, it is the recommended access path for any point that requires transaction type descriptions rather than raw codes.