Skip to the content.

AR Transactions and Lines 11i – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Receivables · all Receivables reports

Overview

Detail AR transaction report with line level details and special columns for service contracts (OKS) and lease contracts (OKL) data

Show Sales Credits lists each line once per salesperson credit, with the revenue and non-revenue split. Transaction and line amounts are shown on the first row of a transaction or line only, so they can be summed.

Revenue As Of Date adds the accounting rule and the deferred revenue position of each line: Revenue Recognized is the sum of the revenue distributions with a GL date up to that date, and Unearned Balance is the line amount less that, for lines with an accounting rule or with revenue deferred by Revenue Management.

Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.

Report Parameters

Operating Unit, Invoice Number, Transaction Number, Customer Name like, Account Number, Salesperson, Sales Order, Category, Class, Period, Inv. Date From, Inv. Date To, Status, Overdue for more than x Days, Transaction Type, Transaction Class, Print Date from, Print Date to, Show Sales Credits, Revenue As Of Date, Deferred Revenue Only

Oracle EBS Tables Used

ra_customer_trx_all, ar_cons_inv_trx_all, ar_cons_inv_all, ra_customer_trx_lines_all, mtl_system_items_b_kfv, ra_cust_trx_line_gl_dist_all, okc_k_lines_b, okc_k_items, hr_all_organization_units_vl, ar_payment_schedules_all, oe_sys_parameters_all, ra_batch_sources_all, ra_cust_trx_types_all, ra_terms_tl, hz_cust_accounts, hz_parties, hz_cust_site_uses_all, ra_territories_kfv, hz_cust_acct_sites_all, hz_party_sites, ar_receipt_methods, ap_bank_accounts_all, ap_bank_branches, mtl_units_of_measure_tl, jtf_rs_salesreps, jtf_rs_resource_extns_vl, oe_order_lines_all, oe_order_headers_all, oks_bill_txn_lines, oks_bill_cont_lines, oks_bill_sub_lines, oks_bill_sub_line_dtls, cs_counter_values, oks_k_lines_b, cs_counters, cs_counter_groups, mtl_system_items_vl, okc_rules_b, okl_cnsld_ar_strms_b, okc_rule_groups_b, okl_strm_type_b, okl_strm_elements, gl_code_combinations_kfv, okc_line_styles_b, csi_item_instances, okc_k_headers_b, okc_k_lines_tl

Report Categories

Enginatics

GL Account Distribution Analysis, GL Account Analysis, GL Account Analysis (Drilldown) (with inventory and WIP)

Running This SQL Without Blitz Report

The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.

Download & Import Options

Resource Link
Excel Example Output Example
Blitz Report™ XML Import AR_Transactions_and_Lines_11i.xml
SQL Source AR Transactions and Lines 11i.sql
Full Report on Enginatics www.enginatics.com/reports/ar-transactions-and-lines-11i/

Case Study & Technical Analysis: AR Transactions and Lines

1. Executive Summary

Business Problem

Accounts Receivable (AR) departments need detailed visibility into customer transactions to manage collections, resolve disputes, and analyze revenue. Standard reports often lack the flexibility to show data at different levels of granularity (Header, Line, Distribution) or to include industry-specific details like Service Contracts (OKS) or Lease Management (OKL). Common challenges include:

Solution Overview

The AR Transactions and Lines report is a versatile, multi-level reporting tool that serves as the “Swiss Army Knife” for AR analysis. It allows users to run the report at the Header level (for aging and balances), Line level (for product and revenue analysis), or Distribution level (for accounting reconciliation). It enriches standard AR data with critical context from Order Management, Service Contracts, and Payments.

Key Benefits

2. Technical Analysis

Core Tables and Views

The report queries the core AR transaction tables and links to several peripheral modules:

SQL Logic and Data Flow

The SQL uses a modular approach with lexical parameters (&line_columns, &distribution_columns) to dynamically adjust the query based on the user’s selected “Display Level”.

Integration Points

3. Functional Capabilities

Reporting Dimensions

Key Parameters

4. Implementation Considerations

Performance

Best Practices


© Enginatics GmbH