Results for “rec_offset_flag”

50+ results




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

Overview

RA_CUST_TRX_LINE_GL_DIST_ALL is the core Oracle Receivables (AR) accounting distribution table. It stores the accounting records generated for revenue, unearned (deferred) revenue, unbilled receivables, receivables, tax, freight, and other distribution lines associated with a customer transaction line. Every time Receivables creates a transaction or applies revenue recognition, it writes one or more rows here to define the debit and credit account combinations, the accounting amounts, the GL date, and the posting status. In Oracle EBS 12.1.1 and 12.2.2, this table resides in the AR schema, is a partitioned-style "ALL" table (with the corresponding multi-org org_id column), and is central to Revenue Recognition, Subledger Accounting transfer, and General Ledger posting. Because the table records the linkage between transaction lines, salesreps, accounting flexfields, and posting runs, it is best understood as a transactional link table in the Data Vault sense: it connects transaction line events to General Ledger account combinations and posting control records rather than storing a standalone descriptive entity.

Key Information Stored

Additional documented columns such as REQUEST_ID, PROGRAM_ID, ORG_ID, LATEST_REC_FLAG, EVENT_ID, and the MRC_ columns support concurrent program auditing, multi-organization security, correction of prior distributions, and Multi-Reporting-Currency balances.

Common Use Cases and Queries

Typical use cases include revenue recognition reconciliation, deferred revenue reporting, subledger-to-GL tie-out, and troubleshooting unposted or unbalanced transactions. A common query pattern joins the distribution to the transaction line and header:

  • Revenue by account: select ACCOUNT_CLASS, SUM(AMOUNT) from RA_CUST_TRX_LINE_GL_DIST_ALL group by ACCOUNT_CLASS.
  • Unposted distributions: select from RA_CUST_TRX_LINE_GL_DIST_ALL where GL_POSTED_DATE is null and POSTING_CONTROL_ID is null.
  • Drill-down to accounts: join CODE_COMBINATION_ID to GL_CODE_COMBINATIONS and CONCATENATED_SEGMENTS for reporting.
  • Ledger comparison: filter on SET_OF_BOOKS_ID and CUSTOMER_TRX_ID to reconcile an invoice's distributions.

Reports such as the Revenue Recognition report, Unposted Transactions report, and Subledger Accounting reconciliation extract largely from this table.

Related Objects

  • RA_CUSTOMER_TRX_ALL — header transaction; join via CUSTOMER_TRX_ID.
  • RA_CUSTOMER_TRX_LINES_ALL — transaction lines; join via CUSTOMER_TRX_LINE_ID.
  • GL_CODE_COMBINATIONS — accounting flexfield definitions; join via CODE_COMBINATION_ID.
  • GL_SETS_OF_BOOKS_11I — ledger/set of books; join via SET_OF_BOOKS_ID.
  • RA_CUST_TRX_LINE_SALESREPS_ALL — salesperson credits; join via CUST_TRX_LINE_SALESREP_ID.
  • AR_POSTING_CONTROL — posting run control; join via POSTING_CONTROL_ID.
  • AR_REVENUE_ADJUSTMENTS_ALL — revenue adjustments; join via REVENUE_ADJUSTMENT_ID.

Record creation and posting are generally driven by the AutoAccounting and Revenue Recognition programs rather than direct inserts, so DBA/developer activity should focus on querying and reconciling this table.