Results for “adj_type_code”

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

Overview

AR_ADJUSTMENTS_REP_ITF is an interface (staging) table owned by the AR schema in Oracle E-Business Suite Receivables. Its documented purpose is to serve as the RXi interface table for the Adjustments Register report. In the Oracle EBS reporting architecture, RXi (Report eXchange interface) tables act as a transient landing area for extracted transactional data; a report program or concurrent process populates the interface table, and the report layout reads from it to produce formatted output. This table is therefore not a primary transactional store but a reporting-support object that captures adjustment-related data drawn from the Receivables transaction and adjustment tables.

The table contains 37 documented columns in the 12.2.2 ETRM schema. Based on the mined foreign key structure, the heuristic Data Vault classification is satellite-leaning. As a modeling suggestion, this reflects the table's descriptive, attribute-rich nature: it carries contextual details about adjustments and their associated customers rather than acting as a pure hub or link. The single documented foreign key to HZ_CUST_ACCOUNTS (via CUSTOMER_ID) indicates that the customer identity is referenced from outside rather than resolved within this table.

Key Information Stored

The table's columns cluster into identification, currency, adjustment classification, and accounting attributes. The most significant include:

• REQUEST_ID — ties the interface rows to the concurrent request that populated them, enabling report run traceability and purge by request.
• CUSTOMER_ID — the foreign key to HZ_CUST_ACCOUNTS, the primary linkage to the customer master.
• CUSTOMER_NAME and CUSTOMER_NUMBER — denormalized customer identification for report display.
• TRX_NUMBER, TRX_DATE, and DUE_DATE — transaction context for the adjustment.
• ADJ_NUMBER, ADJ_NAME, ADJ_TYPE, ADJ_CLASS, ADJ_TYPE_CODE, and ADJ_TYPE_MEANING — the adjustment's identity and classification.
• ADJ_AMOUNT and ACCTD_ADJ_AMOUNT — the entered and accounted adjustment amounts.
• ADJ_CURRENCY_CODE and FUNCTIONAL_CURRENCY_CODE — currency context for the amounts.
• GL_DATE and POSTABLE — accounting date and posting eligibility of the adjustment.
• ACCOUNT_CODE_COMBINATION_ID and the DEBIT_* columns (DEBIT_ACCOUNT, DEBIT_ACCOUNT_DESC, DEBIT_BALANCING, DEBIT_NATACCT with their descriptions) — the accounting distribution used by the adjustment.
• ORGANIZATION_NAME, DOC_SEQUENCE_NAME, DOC_SEQUENCE_VALUE, and D_OR_I — organizational, document sequencing, and debit/credit indicator attributes.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

The metadata does not document a declared surrogate primary key or unique index for this table. In practice, interface tables such as this are typically keyed by REQUEST_ID combined with a row-identity column, but no such constraint is confirmed in the ETRM record.

Common Use Cases and Queries

The primary use is diagnostic and reporting. Administrators query the table to verify what the Adjustments Register report extracted for a given run, to reconcile reported adjustment totals against the base tables, or to troubleshoot why a customer or adjustment is missing from the report output.

SELECT CUSTOMER_NAME, TRX_NUMBER, ADJ_NUMBER,
       ADJ_TYPE_MEANING, ADJ_AMOUNT, ACCTD_ADJ_AMOUNT,
       GL_DATE, POSTABLE
FROM   AR.AR_ADJUSTMENTS_REP_ITF
WHERE  REQUEST_ID = :request_id
ORDER  BY CUSTOMER_NAME, TRX_NUMBER;

Other uses include aggregating accounted adjustment amounts by GL period and currency, filtering by POSTABLE to isolate postable versus non-postable adjustments, and joining CUSTOMER_ID to HZ_CUST_ACCOUNTS to resolve account details. Because the table is a staging area, queries should generally be scoped by REQUEST_ID, and rows should be treated as transient and purged between runs.

Related Objects

• HZ_CUST_ACCOUNTS — referenced via AR_ADJUSTMENTS_REP_ITF.CUSTOMER_ID; joins customer identity to the staging rows.
• AR_ADJUSTMENTS — the base adjustment transaction table that supplies report content.
• AR_PAYMENT_SCHEDULES — links transactions to their adjustment activity.
• RA_CUSTOMER_TRX_ALL — the transaction header for TRX_NUMBER and TRX_DATE context.
• GL_CODE_COMBINATIONS — resolves ACCOUNT_CODE_COMBINATION_ID and the DEBIT_* accounting descriptions.
• FND_CONCURRENT_REQUESTS — relates REQUEST_ID to the concurrent program run.
• AR_ADJUSTMENTS_REP — the associated report program that consumes this interface table.

Together these objects form the extraction, reporting, and accounting-resolution path supporting the Adjustments Register.