AR: Use Subledger Period Close Exceptions Report to be better prepared for month end closing.

The Subledger Period Close Exceptions Report lists all accounting events and journal entries that fail period close validation. This report helps in resolving exceptions quickly so that exceptions are not left to slow down the period-end close. It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or non-transferred journal entries.
You can also generate the Subledger Period Close Exceptions Report through a concurrent request as follows:

Receivables Responsibility:
Nav: Control -> Requests -> Run
Execute the Subledger Period Close Exceptions Report

General Information on the report:

Note: 793598.1 How to Use the Subledger Period Close Exceptions Report for Period Close Activity?

Known issues with the report:

Note: 736361.1 Subledger Period Close Exception Report Shows Unprocessed Cash And Misc Receipts, However They Are Processed

Note: 1207013.1 Subledger Period Close Exception Report (XLAPEXRPT) Shows Incomplete Adjustments

Note: 1074631.1 Unable to close periods due to Receipts and Invoices in Final status in Subledger Period Close Exception Report Output.


My subledger period closed exception report contains two entries as invalid i.e FA addition and another is depreciation.
This happened when addition of fixed assets done from legacy system to oracle fixed assets where the asset's current cost and accumulated depreciation are same.

Posted by KIRTHIVASAN on March 09, 2013 at 04:09 AM EST #

Hi Kirthivasan,
Thanks for your comment. But I'm not sure if your comment is just that, only a comment, or whether you have a problem or question about how to resolve the two exceptions. If you've got a question on this then probably the best place to get an answer is the Receivables MOS Community:

Posted by LuciaC on March 11, 2013 at 01:36 AM EDT #


Just want to ask what is the difference of Subledger exception report generated in sl level and that of report submitted by the closing admin..Because when we run the sler in ap module there are 5 unprocessed trx but when the closing admin run the report it captured 10trx.

Posted by guest on October 08, 2014 at 03:53 AM EDT #

Thanks for your comment and for coming to our blog! The best place to ask this sort of question is in the My Oracle Support Community. The new URL is:
The experts there will be happy to help.

Posted by LuciaC on October 21, 2014 at 12:29 AM EDT #


My subledger period close exception report goes into error, everytime when I try to close the GL period. The issue is the period closes successfully but the report runs into error and shows some xml error. Is it a known issue?


Posted by guest on November 18, 2014 at 02:39 AM EST #

Hi Prabhu,

There are many reasons why this could happen, it really depends on what the exact error is. Since the period closes successfully, one possible cause could be that the timeout to generate the report is set too low, that is fixed by increasing the value set for profile option Concurrent:OPP Response Timeout. That is a common fix.


Posted by LuciaC - Oracle on November 20, 2014 at 03:39 AM EST #

Post a Comment:
  • HTML Syntax: NOT allowed

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected



« April 2015