Results for “okl_transaction_type_category”

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

Overview

OKL_TRX_TYPES_UV is an APPS-owned view within the Oracle E-Business Suite Enterprise Trading and Transportation Management (ETRM) or Oracle Lease and Finance Management (OKL) module. It presents a denormalized, translation-aware denormalized snapshot of the transaction type setup used across lease and financial contracts. The view joins the base tables OKL_TRX_TYPES_B (which stores language-independent attributes and foreign keys) with OKL_TRX_TYPES_TL (which stores the translatable name and description). Its primary reporting purpose is to expose not only the raw transactional setup codes (TRY_TYPE, TRX_TYPE_CLASS, AEP_CODE) but also their human-readable lookup meanings, which are resolved at runtime through the package function OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING. For users searching on "okl_transaction_type_category", the view is directly relevant because the TRY_TYPE column is passed to GET_LOOKUP_MEANING using the lookup type OKL_TRANSACTION_TYPE_CATEGORY, and the resulting description is surfaced as TRY_TYPE_DESC. This makes OKL_TRX_TYPES_UV a convenient integration and reporting object for consumers who require both the category code and its decoded meaning without performing multiple joins themselves.

Underlying Base Objects

The view is defined over two synonyms: OKL_TRX_TYPES_B and OKL_TRX_TYPES_TL. OKL_TRX_TYPES_B is the base (non-translatable) table holding the definitive configuration of each transaction type, including the AEP code, ILC identifier, TRY_TYPE category, TRX_TYPE_CLASS, ORG_ID, and standard WHO audit columns. OKL_TRX_TYPES_TL is the translation table, supplying SFWT_FLAG, NAME, DESCRIPTION, CONTRACT_HEADER_LINE_FLAG, and TRANSACTION_HEADER_LINE_DETAIL for a given language. The view joins them on TRYB.ID = TRYT.ID with the restriction TRYT.LANGUAGE = USERENV('LANG'), ensuring that only the translation matching the session language is returned. The third referenced object, OKL_ACCOUNTING_UTIL, is a PL/SQL package whose function GET_LOOKUP_MEANING is invoked three times to decode AEP_CODE, TRY_TYPE, and TRX_TYPE_CLASS into their descriptive lookup meanings.

Key Columns

• ID, OBJECT_VERSION_NUMBER – Primary identifier and optimistic locking version from OKL_TRX_TYPES_B.
• TRY_TYPE / TRY_TYPE_DESC – The transaction type category code and its decoded meaning, derived via the OKL_TRANSACTION_TYPE_CATEGORY lookup. This pair is the object of the user's search term.
• TRX_TYPE_CLASS / TRX_TYPE_CLASS_DESC – The transaction classification code and its decoded description using the OKL_TRANSACTION_TYPE_CLASS lookup.
• AEP_CODE / AEP_CODE_DESC – The accounting event parameter code and its decoded meaning from OKL_ACCOUNTING_EVENT_TYPE.
• ILC_ID, TRY_ID, TRY_ID_FOR, TRY_ID_FOR_NAME – Internal lease contract and derived transaction type identifiers; the NAME columns are populated as NULL placeholders in this view text.
• NAME, DESCRIPTION – Language-specific transaction type name and description from OKL_TRX_TYPES_TL.
• SFWT_FLAG, CONTRACT_HEADER_LINE_FLAG, TRANSACTION_HEADER_LINE_DETAIL – Configuration flags controlling behavior at contract header, line, and detail levels.
• ORG_ID and WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) – Multi-org security and standard audit tracking.

Common Use Cases and Queries

Typical uses include reporting on configured transaction types by category, validating category assignments during lease setup, and feeding downstream integrations that require decoded category descriptions. A representative query filtering on the transaction type category is:

• SELECT TRY_TYPE, TRY_TYPE_DESC, NAME, TRX_TYPE_CLASS FROM APPS.OKL_TRX_TYPES_UV WHERE TRY_TYPE = :category AND ORG_ID = :org_id;
• SELECT ID, TRY_TYPE_DESC, AEP_CODE_DESC, TRX_TYPE_CLASS_DESC FROM APPS.OKL_TRX_TYPES_UV ORDER BY TRY_TYPE, NAME;
• SELECT COUNT(*) FROM APPS.OKL_TRX_TYPES_UV WHERE SFWT_FLAG = 'Y' AND CONTRACT_HEADER_LINE_FLAG = 'Y';

Because the lookup descriptions are computed through OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING, users should ensure the relevant lookup types (OKL_TRANSACTION_TYPE_CATEGORY, OKL_TRANSACTION_TYPE_CLASS, OKL_ACCOUNTING_EVENT_TYPE) are populated, otherwise the _DESC columns may return NULL. The view honors the session language, so multi-language environments will see descriptions consistent with the user's USERENV('LANG') setting.