Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

layout default
title CAC Receiving Account Detail | Oracle EBS SQL Report
description Report to get the receiving accounting distributions, in detail, by item, purchase order, purchase order line, release, project number, transaction date…
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Enginatics, Nidec changes, R12 only, CAC, Receiving, Account, Detail, po_releases_all, mtl_units_of_measure_vl, org_acct_periods
permalink /CAC%20Receiving%20Account%20Detail/

CAC Receiving Account Detail – Oracle EBS SQL Report

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

Overview

Report to get the receiving accounting distributions, in detail, by item, purchase order, purchase order line, release, project number, transaction date, creation date, created by and transaction identifier. With the Show SLA Accounting parameter you can choose to use the Release 12 Subledger Accounting (Create Accounting) account setups by selecting Yes. And if you have not modified your SLA accounting rules, select No to allow this report to run a bit faster. With Show WIP Outside Processing parameter to display or not display WIP outside processing information (WIP job and OSP resource code) and Show Project Information to display or not display the project, project name and task. And if you accrue expense receipts at time of receipt, for expense destinations when there is no item number, this report will get the expense category information and put it into the columns for the first category.

(Note: this report has not been tested with encumbrance entries.)

Parameters:

Transaction Date From: enter the starting transaction date (mandatory). Transaction Date To: enter the ending transaction date (mandatory). Show SLA Accounting: enter Yes to use the Subledger Accounting rules for your accounting information. If you choose No the report uses the pre-Create Accounting entries. Show Projects: display the project, project name and task. Enter Yes or No, use to limit the reported columns (mandatory). Show WIP Outside Processing: display the WIP job and outside processing resource. Enter Yes or No, use to limit the reported columns (mandatory). Category Set 1: any item category you wish, typically the Cost or Product Line category set (optional). Category Set 2: any item category you wish, typically the Inventory category set (optional). Transaction Type: enter the transaction type to report (optional). Minimum Absolute Amount: enter the minimum debit or credit to report (optional). To see all accounting entries, enter zero (0) and leave the other parameters blank. Supplier Name: enter the specific supplier you wish to report (optional). PO Number: enter the specific purchase order number you wish to report (optional). Destination Code: enter the purchase order destination type you wish to report (optional). You can choose Inventory, Expense or Shop Floor (WIP outside processing). Item Number: enter the specific item number(s) you wish to report (optional). Organization Code: enter the specific inventory organization(s) you wish to report (optional). Operating Unit: enter the specific operating unit(s) you wish to report (optional). Ledger: enter the specific ledger(s) you wish to report (optional).

/* +=============================================================================+ -- | Copyright 2010 - 2022 Douglas Volz Consulting, Inc. -- | Permission to use this code is granted provided the original author is -- | acknowledged. No warranties, express or otherwise is included in this -- | permission.

-- +=============================================================================+
--
--
--
--
--
--
--
--
--
--
--
-- +=============================================================================+*/

Report Parameters

Transaction Date From, Transaction Date To, Show SLA Accounting, Show Project Information, Show WIP Outside Processing, Category Set 1, Category Set 2, Category Set 3, Transaction Type, Minimum Absolute Amount, Supplier Name, PO Number, Destination Code, Item Number, Organization Code, Operating Unit, Ledger

Oracle EBS Tables Used

po_releases_all, mtl_units_of_measure_vl, org_acct_periods, gl_code_combinations, fnd_lookup_values, hr_organization_information, hr_all_organization_units_vl, gl_ledgers, po_lookup_codes, fnd_user, &project_tables, gl_access_set_norm_assign, gl_ledger_set_norm_assign_v, mo_glob_org_access_tmp, dual

Report Categories

Enginatics, Nidec changes, R12 only

Related Reports

CAC Receiving Expense Value (Period-End), CAC Receiving Value (Period-End), CAC Manufacturing Variance, CAC WIP Resource Efficiency, CAC Invoice Price Variance, GL Account Analysis, CAC Receiving Account Summary, 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 CAC Receiving Account Detail 03-Sep-2022 132129.xlsx
Blitz Report™ XML Import CAC_Receiving_Account_Detail.xml
Full SQL on Enginatics www.enginatics.com/reports/cac-receiving-account-detail/

Case Study & Technical Analysis: CAC Receiving Account Detail

Executive Summary

The CAC Receiving Account Detail report is a forensic accounting tool for the Receiving module. It lists the specific accounting entries (Debits and Credits) generated by receiving transactions. This is critical for reconciling the "Receiving Inspection" (Asset) and "PO Accrual" (Liability) accounts.

Business Challenge

  • Reconciliation: The General Ledger shows a balance in "Receiving Inspection" that doesn't match the subledger. Which transaction caused the drift?
  • Accrual Auditing: Verifying that the liability was booked correctly for a specific high-value receipt.
  • SLA Visibility: In R12, Subledger Accounting (SLA) rules can transform accounts. Users need to see the final account used, not just the default from the PO.

Solution

This report bridges the gap between Operations and Finance.

  • Granularity: One row per accounting line (Debit or Credit).
  • Context: Links the journal line back to the PO Number, Receipt Number, Item, and Project.
  • SLA Integration: Can optionally pull data from xla_ae_lines to show the final transformation rules applied.

Technical Architecture

  • Tables: rcv_receiving_sub_ledger (Pre-SLA), xla_ae_lines (Post-SLA), rcv_transactions.
  • Logic: The "Show SLA Accounting" parameter toggles between the raw subledger table and the XLA engine tables.

Parameters

  • Show SLA Accounting: (Mandatory) "Yes" for accurate GL matching, "No" for faster operational checks.
  • Transaction Date From/To: (Mandatory) Accounting period.
  • Minimum Absolute Amount: (Optional) Filter out small rounding differences.

Performance

  • Variable: Running with "Show SLA Accounting = Yes" is slower because it joins to the massive XLA tables.

FAQ

Q: Why are there two entries for one receipt? A: A standard receipt generates a Debit to Receiving Inspection and a Credit to the Accrual Account. Q: Does this show "Deliver" transactions? A: Yes, it shows the full flow: Receive (Dr Insp / Cr Accrual) -> Deliver (Dr Inv / Cr Insp).


Useful Links

© 2026 Enginatics