Results for “lk_type”

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

Overview

APPS.AR_ADJUSTMENTS_V is a reporting and integration view in the Oracle E-Business Suite Receivables module, exposed under the APPS schema. It presents adjustment transactions — credits, write-offs, chargebacks, and other receivable corrections — in a denormalized, human-readable form that joins the base adjustment record to customer, transaction, payment schedule, reason code, and user information. Because adjustments directly affect customer balances and the aging of receivables, the view is central to reconciliation, collections analysis, and general ledger tie-out reporting.

The view is defined in both EBS 12.1.1 and 12.2.2 with the same underlying logic and column list, so reports and integrations built against it remain portable across the two releases. In 12.2.2 the definition also carries the standard multi-organization ORG_ID column, which is required for correct operating-unit filtering under the 12.2 legal-entity and operating-unit model. The view is read-only by convention; it is not intended as a DML interface, and posting or reversal of adjustments should be performed through the Receivables forms or the public APIs.

Underlying Base Objects

The ETRM metadata records the following referenced objects for the APPS-owned view:

• AR_ADJUSTMENTS (synonym) — the driving base table containing the adjustment header rows, amounts, dates, and foreign keys.
• RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL (synonyms) — invoice, debit memo, credit memo, and chargeback headers and lines to which adjustments are applied.
• AR_PAYMENT_SCHEDULES_ALL (synonym) — installment and balance information used to determine the schedule being adjusted.
• AR_RECEIVABLES_TRX_ALL (synonym) — receivables activity definitions that categorize the accounting effect of the adjustment.
• RA_CUST_TRX_TYPES_ALL and RA_BATCH_SOURCES_ALL (synonyms) — transaction type and batch source context.
• AR_LOOKUPS (view) — value sets supplying the meaning of lookup-coded columns.
• HZ_CUST_ACCOUNTS and HZ_PARTIES (synonyms) — customer account and party name information.
• FND_USER (synonym) — the creator or approver of the adjustment.
• FND_ATTACHMENT_UTIL_PKG (package) — attachment function used to surface supporting documentation.

The join logic follows the Receivables data model: AR_ADJUSTMENTS is the anchor, with outer joins to the transaction, schedule, activity, customer, and lookup tables so that adjustments are returned even when optional descriptive attributes are absent.

Key Columns

• ADJUSTMENT_ID, ADJUSTMENT_NUMBER — primary key and user-facing document number.
• ADJUSTMENT_TYPE — classifies the adjustment, for example write-off, credit, or chargeback.
• AMOUNT, ACCTD_AMOUNT — entered and accounted amounts of the adjustment.
• APPLY_DATE, GL_DATE, GL_POSTED_DATE — accounting and application dates used for period and aging analysis.
• CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, PAYMENT_SCHEDULE_ID — the invoice, line, and installment being adjusted.
• CODE_COMBINATION_ID, DISTRIBUTION_SET_ID, POSTABLE — accounting distribution and posting readiness indicators.
• REASON_CODE — reason for the adjustment; resolved through AR_LOOKUPS.
• CHARGEBACK_CUSTOMER_TRX_ID, FREIGHT_ADJUSTED, LINE_ADJUSTED, RECEIVABLES_CHARGES_ADJUSTED — flags and references describing the nature of the adjustment.
• APPROVED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE — audit and approval tracking, joined to FND_USER.
• ORG_ID — operating unit, required for multi-org filtering in 12.2.2.

Common Use Cases and Queries

Typical uses include reporting adjustment activity by reason code, reconciling adjustments to the general ledger, and feeding downstream collection or credit-management systems. The user search term "lk_type" reflects a frequent requirement to resolve lookup-coded values such as adjustment type or reason code. A representative query follows:

SELECT a.adjustment_number,
       a.adjustment_type,
       l.meaning            AS reason_meaning,
       a.amount,
       a.acctd_amount,
       a.apply_date,
       ct.trx_number,
       a.org_id
FROM   apps.ar_adjustments_v a,
       apps.ar_lookups l,
       apps.ra_customer_trx_all ct
WHERE  a.reason_code = l.lookup_code
AND    l.lookup_type  = 'ADJUSTMENT_REASON'
AND    a.customer_trx_id = ct.customer_trx_id
AND    a.apply_date >= :p_from_date
AND    a.org_id = :p_org_id;

In practice, reports should always filter on ORG_ID and a date range over APPLY_DATE or GL_DATE to bound the result set, and join to AR_LOOKUPS on both LOOKUP_TYPE and LOOKUP_CODE for correct lookup resolution.