Search Results je_exchange_rate

Overview

APPS.AR_POSTED_TRANSACTIONS_V is a supplementary Oracle E-Business Suite view owned by the APPS schema. Within the Receivables (AR) module it serves primarily to simplify Oracle Forms coding, and its design reflects that intent. The view correlates posted subledger transaction activity with the corresponding General Ledger journal entries, presenting a consolidated, side-by-side picture of each transaction and the accounting it produced. Because it is explicitly classified as a Forms-support view, Oracle does not recommend that customers query or alter data using it directly; its definition may change dramatically in subsequent minor or major releases. This warning is significant for reporting and integration architects operating on EBS 12.1.1 or 12.2.2, who should treat the object as an internal, non-contractual interface. Its continued presence in 12.2.2 confirms that the Forms-driven posting and review flows within Receivables still depend on it, even as Oracle continues to encourage the use of documented public APIs and the Receivables open interface for integration work.

Underlying Base Objects

Documented ETRM metadata for 12.2.2 shows the view is defined over a broad set of Receivables, General Ledger, and Trading Community Architecture objects. The Receivables transaction side draws on RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, and RA_CUST_TRX_LINE_GL_DIST_ALL. Application, adjustment, receipt, and miscellaneous cash activity are covered by AR_RECEIVABLE_APPLICATIONS_ALL, AR_ADJUSTMENTS_ALL, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, and AR_MISC_CASH_DISTRIBUTIONS_ALL. The accounting side joins the GL posting tables GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, and GL_IMPORT_REFERENCES. Party and site information is resolved through HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_SITE_USES_ALL, while document sequencing and lookup values come from FND_DOCUMENT_SEQUENCES and the GL_LOOKUPS view. Notably, the query text embedded in the view source references the underlying view APPS.AR_POSTED as the driving FROM clause, with the ETRM column listing exposing the flattened projection of that internal structure.

Key Columns

The view exposes two mirrored column families. The JE_* columns describe the General Ledger journal entry: JE_STATUS, JE_EFFECTIVE_DATE, JE_PERIOD_NAME, JE_BATCH_NAME, JE_HEADER_NAME, JE_LINE_NUM, JE_DESCRIPTION, JE_DOC_SEQUENCE_VALUE, JE_DOC_SEQUENCE_NAME, JE_EXCHANGE_RATE, JE_CURRENCY_CODE, and the entered and accounted debit/credit amounts. The TRX_* columns describe the Receivables transaction: TRX_NUMBER, TRX_LINE_NUMBER, TRX_DATE, TRX_GL_DATE, TRX_VEND_CUST_NAME, TRX_VEND_CUST_SITE, document sequence attributes, TRX_TRANSACTION, TRX_ASSO_TRANSACTION, and the corresponding entered and accounted amounts. Two rate columns are central to reconciliation: JE_EXCHANGE_RATE carries the rate applied to the journal line, while TRX_EXCHANGE_RATE carries the rate recorded on the subledger transaction. Comparison of the two — together with JE_CURRENCY_CODE, entered amounts, and accounted amounts — allows the analyst to detect rate mismatches, rounding differences, and revaluation effects that interfere with subledger-to-GL ties. Keys PK_1, SET_OF_BOOKS_ID, and CCID anchor each row to a ledger and accounting flexfield combination.

Common Use Cases and Queries

Typical use cases include subledger-to-GL reconciliation, investigation of out-of-balance posting batches, and comparison of transaction versus journal exchange rates across multi-currency Receivables activity. A representative query follows.

• Retrieve posted transactions and their journal lines for a period:
  SELECT trx_number, trx_date, trx_currency_code, trx_exchange_rate, je_exchange_rate, je_currency_code, je_accounted_dr, je_accounted_cr FROM apps.ar_posted_transactions_v WHERE je_period_name = :period AND set_of_books_id = :sob;
• Identify rate variance between subledger and GL:
  SELECT trx_number, trx_exchange_rate, je_exchange_rate FROM apps.ar_posted_transactions_v WHERE NVL(trx_exchange_rate,0) <> NVL(je_exchange_rate,0);
• Trace a specific transaction to its journal entry:
  SELECT trx_number, je_header_name, je_line_num, je_description FROM apps.ar_posted_transactions_v WHERE trx_number = :trx;

Because the object is a Forms-support view, production reporting should preferably be redirected to documented base tables or to supported AR and GL reporting extracts. Where the view must be used, queries should be constrained by ledger and accounting period to limit the volume and to reduce the risk of performance degradation.