AR Sales Journal By Customer – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Imported from BI Publisher Description: Sales Journal By Customer Application: Receivables Source: Sales Journal By Customer (XML) Short Name: RAXGLA_XML DB package: AR_RAXGLA_XMLP_PKG

Report Parameters

Reporting Level, Reporting Context, Report By Line, Company Segment Low, Company Segment High, GL Date From, GL Date To, Entered Currency, GL Account Type, Posting Status, Customer Name Low, Customer Name High, Customer Number Low, Customer Number High, Transaction Date From, Transaction Date To, Transaction Type Low, Transaction Type High, Transaction Number Low, Transaction Number High, Exclude Rounding equals zero

Oracle EBS Tables Used

gl_sets_of_books, hr_all_organization_units_vl, hz_cust_accounts_all, hz_parties, ra_customer_trx_all, ra_customer_trx_lines_all, ar_xla_ctlgd_lines_v

Report Categories

Enginatics, Nidec changes

AR Open Items Revaluation, AR Transactions and Lines, CST COGS Revenue Matching, AR Aging, GL Account Distribution Analysis

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output AR Sales Journal By Customer - Default 06-Nov-2023 041650.xlsx
Blitz Report™ XML Import AR_Sales_Journal_By_Customer.xml
Full SQL on Enginatics www.enginatics.com/reports/ar-sales-journal-by-customer/

AR Sales Journal By Customer - Case Study & Technical Analysis

Executive Summary

The AR Sales Journal By Customer is a fundamental accounting report that bridges the gap between operational sales activity and financial reporting. It provides a detailed listing of all sales transactions—Invoices, Credit Memos, and Debit Memos—grouped by customer. This report is indispensable for reconciling the Receivables subledger to the General Ledger (GL) and for analyzing revenue generation by client.

Business Challenge

Accurate revenue recognition is the cornerstone of financial integrity.

Solution

The AR Sales Journal By Customer report addresses these needs by:

Technical Architecture

The report relies on the integration between Oracle Receivables and the Subledger Accounting (SLA) engine.

Key Tables & Joins

Logic

  1. Selection: Retrieves transactions based on the “GL Date” range to align with the accounting period.
  2. Grouping: Aggregates data by Customer, then by Transaction Type (Invoice, Credit Memo).
  3. Filtering: Applies filters for “Posting Status” to separate posted from unposted items.
  4. Detailing: If “Report By Line” is enabled, it lists every individual line item; otherwise, it may summarize at the transaction level.

Parameters

FAQ

Q: Does this report show cash receipts? A: No. This is a Sales journal, focusing on the revenue generation side (Invoices, Credit Memos). Cash receipts are typically reported in the “AR Receipt Register” or “AR Cash Journal.”

Q: Why is the GL Account missing for some lines? A: If the transaction has not been accounted (AutoAccounting hasn’t run or failed), the distribution lines might not exist or be complete. Check the “Posting Status.”

Q: What is the difference between “Transaction Date” and “GL Date”? A: The Transaction Date is when the sale occurred. The GL Date is when it is recognized in the books. They can differ (e.g., a Jan 31st invoice booked in Feb). This report typically filters by GL Date for accounting purposes.

© 2026 Enginatics