Results for “ar_posting_report_interim”

24 results




Overview
Explore in AI Chat

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

Overview

AR_POSTING_REPORT_INTERIM is a temporary staging table in the Oracle Receivables (AR) schema, owned by AR and holding a VALID status in the Oracle E-Business Suite 12.1.1 and 12.2.2 data dictionary. Its documented purpose is to serve as the working store used by the Posting Execution report, the concurrent process that drives the transfer of receivables accounting entries from the subledger into the General Ledger interface. Rather than querying large transactional tables directly, the Posting Execution program populates this interim table with aggregated posting totals, then reads it back to render the report output and reconcile amounts by posting control, currency, journal category, and accounting cycle.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is link. AR_POSTING_REPORT_INTERIM is best understood as an associative structure that ties posting runs (AR_POSTING_CONTROL), currencies (FND_CURRENCIES), and ledgers (GL_SETS_OF_BOOKS_11I) together with their summarized debit and credit measures. It is not a master or reference entity; its rows are transient and are typically regenerated on each execution of the posting process.

Key Information Stored

The physical schema documented in ETRM 12.2.2 contains 13 columns. The most significant are:

  • POSTING_CONTROL_ID — Identifier of the posting control record governing the run; also the leading column of the primary key and a foreign key to AR_POSTING_CONTROL.
  • CURRENCY_CODE — The currency in which the summarized amounts are expressed; foreign key to FND_CURRENCIES.
  • USER_JE_CATEGORY_NAME — The user-defined journal entry category (for example, invoice, debit memo, receipt, adjustment) under which the posting activity is grouped.
  • CYCLE_NUMBER — The accounting cycle within the posting run, distinguishing successive batch iterations of the same control.
  • SET_OF_BOOKS_ID — The ledger (set of books) to which the entries are destined; foreign key to GL_SETS_OF_BOOKS_11I.
  • ENTERED_DR / ENTERED_CR — Entered debit and credit amounts in the transaction (entered) currency.
  • ACCOUNTED_DR / ACCOUNTED_CR — Accounted debit and credit amounts converted to the ledger currency.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard Oracle EBS audit columns recording who created or last modified each row and when.

The surrogate primary key is AR_POSTING_REPORT_INTERIM_PK, defined across POSTING_CONTROL_ID, CURRENCY_CODE, USER_JE_CATEGORY_NAME, and CYCLE_NUMBER. The unique index AR_POSTING_REPORT_INTERIM_U1 mirrors that same four-column combination, confirming it as the documented business-key candidate that guarantees one summary row per posting control, currency, journal category, and cycle.

Common Use Cases and Queries

The primary use case is diagnostic: reviewing the Posting Execution report output after a posting run to confirm that entered and accounted balances reconcile by ledger, currency, and journal category. Typical queries aggregate the debit and credit measures for a given posting control:

  • Reconciliation by control and ledger: SELECT set_of_books_id, currency_code, SUM(accounted_dr), SUM(accounted_cr) FROM ar_posting_report_interim WHERE posting_control_id = :p_control GROUP BY set_of_books_id, currency_code;
  • Category-level analysis: grouping on USER_JE_CATEGORY_NAME to isolate invoice versus receipt activity.
  • Audit of who generated the interim rows, using CREATED_BY and CREATION_DATE.
  • Cycle drill-down using CYCLE_NUMBER to observe progressive batch behavior within one posting control.

Because the table is transient, reporting should target a specific POSTING_CONTROL_ID rather than assuming persistent historical content.

Related Objects

  • AR_POSTING_CONTROL — Parent of the POSTING_CONTROL_ID foreign key; defines each posting run.
  • GL_SETS_OF_BOOKS_11I — Referenced via SET_OF_BOOKS_ID; supplies ledger context (chart of accounts, currency, period).
  • FND_CURRENCIES — Referenced via CURRENCY_CODE; provides currency names, precision, and formatting.
  • AR_POSTING_REPORT_INTERIM_PK / _U1 — The primary key constraint and unique index enforcing the business key.
  • Posting Execution report concurrent program — The consumer that populates and reads this interim table.
  • GL_INTERFACE — Downstream destination to which finalized receivables accounting entries are ultimately passed.

Used together, these objects support the end-to-end subledger posting and reconciliation workflow in Oracle Receivables.