12th January 2010, 01:02 pm by Nagamohan UpparaOne of many cool features in SLA is creating manual journal entries. Many times wehave a need to pass manual entries to reverse the entries happened a source transactionbecause the account is wrong or date is wrong or even the value is wrong. All sub ledgersgive you a way to reverse the transaction and hence reverse the associated accountingentry. But sometimes you may run out of time and luck and resort to manual entries inGL. Once we are GL to enter manual entries for transactions that pertain to sub ledger,we lose an opportunity to reconcile as we do not have primary references for which wehave created this accounting entry for. If we have any reports that are based on SLAtables the reconciliation becomes harder as we cannot link anything that happened in theGL with the SLA. After all, the purpose of SLA is to eliminate this risk of reconciliationwith GL.Also, I guess, Oracle Support uses this route (manual journal entries) to fix any entriesthat were corrupted in the original transaction.While entering these manual entries we can capture original transaction attributes usingsupporting references feature where you can capture attributes like asset_id if it is Assetsrelated entry, transaction_id if it is related to Inventory, invoice_Id for AP andcustomer_trx_id or cash_receipt_id if it is AR invoice or cash respectively, These givemeaning to the manual journal entries.