R12.2.4 Receivables: Create Accounting errors due to imbalanced CM application distributions

Although MOS document "Create Accounting Completed With Error (319) Unbalanced Distributions of CM Application" from article ID 2116697.1 does not give you an exact issue or resolution, it may help you to build some proactive alerting around an imbalance in credit and debit entries in AR_DISTRIBUTIONS_ALL.

R12.2.3: New profile option to run Create Accounting in detail

Upgrading to R12 brought a lot of changes from 11.5.10.2 across every module and Receivables with the transition from needing to run the "General Ledger Transfer" report to running the "Create Accounting" report.  With R12.2.3 enough people have requested a new feature so the Create Accounting can mimic the General Ledger Transfer a bit which My Oracle Support article "How to run create accounting in detail level with no merge in R12" goes into detail in document ID 1992895.1 about the patch required and the profile option which needs to be enabled to take advantage of this development.

R12: Create Accounting in error due to older files

File this one away for reference if you are upgrading to R12, or if you are applying some patches, and your Create Accounting program starts giving you ORA-00001 errors.  My Oracle Support note "Create Accounting Program Ending In Error:An internal error has occurred in the program xla_je_validation_pkg.populate_segment_values. ORA-00001: unique constraint (XLA.XLA_AE_SEGMENT_VALUES_U1) violated." from document ID 1902705.1 is directly on point with the files, versions, and patch which will resolve this.

If this helps you, please let me know so I can look for more of these types of articles in the future!

R12: Create Accounting and scaling options

Coming fresh off the presses, yesterday we had a problem with our Create Accounting program where it gave us the following error:

****Warning!!! Due to high volume of data, got out of memory exception...***
****Please retry with scalable option or modify the Data template to run in scalable mode...***

Obviously this is not something we wanted (or expected) to see so we compared the run parameters to what was run before, and it did not appear to be anything out of the ordinary so off to My Oracle Support I went.  I found note 1470317.1 titled "PAXACCPB PRC: Create Accounting Completes With Error: Due to high volume of data, got out of memory exception...Please retry with scalable option or modify the Data template to run in scalable mode" which had steps for resolving our issue but the interesting part of this was we had already followed the note EXCEPT for a critical part of it where we made the scalable flag default to N instead of Y.  Once we made that change, after regression testing in QA first, the business re-ran the report for the same org that had the same volume of data, and the report completed successfully this time!