Results for “adjustment_reason_code”

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

Overview

The APPS.OKL_TRX_AR_ADJSTS_V view is a reporting and integration object within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. Its documented purpose is to expose OKL write-off transactions that generate corresponding Receivables adjustments. Because write-offs in Lease and Finance Management frequently require a downstream accounting impact in Oracle Receivables, this view provides a consolidated, query-friendly projection of those adjustment records — combining the transactional base attributes with their language-dependent descriptive text.

The view is defined with STATUS VALID and is owned by the APPS schema, which means it is intended to be consumed by concurrent programs, Oracle Reports, OA Framework pages, and external integrations that need read-only access to lease write-off adjustment data without navigating the normalized _B/_TL table pair directly. Note that write-offs represented here are typically stored as negative amounts, since they reduce the receivable balance rather than increasing it.

Underlying Base Objects

The view is defined over two synonyms that resolve to the underlying OKL base tables:

• OKL_TRX_AR_ADJSTS_B — the base (transaction) table holding the non-translatable attributes of each write-off adjustment record.
• OKL_TRX_AR_ADJSTS_TL — the translation table holding language-dependent descriptive columns.

The join is performed on ID (ADJB.ID = ADJT.ID) with the additional predicate ADJT.LANGUAGE = USERENV('LANG'), so each row returns the translation matching the session language. The view is a straight equi-join with no aggregation, meaning one base row generally yields one view row. The ROWID of the base table is exposed as ROW_ID, and the OBJECT_VERSION_NUMBER column supports optimistic locking semantics for any consuming form.

Key Columns

• ID / ROW_ID — primary identifier and row locator for the underlying adjustment record.
• ADJUSTMENT_REASON_CODE — the reason code classifying the write-off adjustment; this is frequently the primary filter used by reporting queries and is the column most often searched by users.
• SFWT_FLAG — sourced from the translation table (ADJT), indicating the short-term/soft write-off classification.
• TRX_STATUS_CODE — the lifecycle status of the adjustment transaction (for example, whether it has been applied, cancelled, or is pending).
• CCW_ID / TCN_ID / TRY_ID — foreign keys linking the adjustment to the originating contract, transaction, and related OKL entities.
• APPLY_DATE / GL_DATE / TRANSACTION_DATE — the applied date, the accounting date used for general ledger posting, and the transaction date respectively.
• COMMENTS — free-text description from the translation table.
• ORG_ID — the operating unit, enforcing Multi-Org security for the record.
• ATTRIBUTE1 … ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF (Descriptive Flexfield) columns, allowing client-specific extensions.
• Audit columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.

Because the view uses USERENV('LANG'), a session must have a valid language setting (for example, US) or no rows are returned from the translation side.

Common Use Cases and Queries

Typical uses include reconciling write-offs to AR adjustments, reporting adjustments by reason code, and feeding downstream accounting or audit extracts. A representative query filtering on the reason code is:

• SELECT id, adjustment_reason_code, trx_status_code, apply_date, gl_date, org_id, tcn_id, try_id, comments FROM apps.okl_trx_ar_adjsts_v WHERE adjustment_reason_code = :reason_code AND org_id = :org_id ORDER BY gl_date;
• SELECT adjustment_reason_code, COUNT(*) FROM apps.okl_trx_ar_adjsts_v GROUP BY adjustment_reason_code ORDER BY 2 DESC;
• SELECT v.id, v.gl_date, v.tcn_id, v.attribute1 FROM apps.okl_trx_ar_adjsts_v v WHERE v.trx_status_code = 'APPROVED' AND v.gl_date BETWEEN :from_date AND :to_date;

In all cases, callers should bind ORG_ID for Multi-Org compliance and account for the language-dependent join when building integrations.