List of various functional articles covering topics like Oracle General Ledger, Oracle Receivables, Oracle Payables etc
User Rating: 4 / 5
What do I mean when I say Transaction Write-Offs?
If a customer’s transaction is outstanding for a longest period and we have no clue as to if the customer is going to pay or not, we cannot trace the customer and now we want to write-off that transaction. This is also called as Bad Debts.
How to enter bad debts in Oracle Receivables?
As per Oracle Receivable’s standard functionality: There is no such term in Receivables as Bad Debts. Receivables suggests that we “adjust” the particular transaction. is type of write off that will address our Bad Debt scenario.
These are setup and transactions steps for creating and entering Bad Debt Adjustments
Here are the details for Setups:
User Rating: 0 / 5
R12 Payment Manager (New Module)
Monitor the progress of the recent pay run processes
Highlight any payment processes that require attention and automatically prompt to take appropriate actions
Shortcuts and tabs for initiating, reviewing and adjusting proposed funds disbursements.
b. Oracle will automatically generate the Scheduled Payment Selection Report
Which is the equivalent to the Preliminary Payment Register in 11i
Multi-Org Access Control’ (MOAC)
Multi-Org or multiple organization access (MOAC) is basically the ability to access multiple operating units from a single application responsibility. In Release 11i, when one had to enter or process data for multiple operating units, one had to login to different responsibilities because each responsibility could only access one operating unit. If one was managing Payables for Sweden, Norway and Finland one needed to define three different responsibilities. In Release 12, one would create a Security Profile and assign as many operating units as you required. One can tie that security profile to a single responsibility using a profile option called “MO: Security Profile”.
Benefits of MOAC_
- Used when Multi-Org is NOT enabled
- On upgrade, assigned operating unit of 11i responsibility
- Assign security profile name at User or Responsibility level
R12 General Ledger new feature
• Simultaneous Data Access to Multiple Legal Entities and Ledgers
• Simultaneous Opening and Closing of Periods for Multiple Ledgers
• Cross-Ledger and Foreign Currency Allocations
• Simultaneous Currency Translation of Multiple Ledgers
• Financial Reporting Across Ledgers
• Automatic Journal Copy
• Streamline Automatic Posting
• Streamline AutoReversal Criteria Setup
• Streamline Consolidation Mappings
• Replacement for Disabled Accounts
• Data Security across Legal Entities and Ledgers
• Management Reporting Security
• Prevent Reversal of Journals with Frozen Sources
• Prevent Reversal of Unposted Journals
• Control Accounts
• Definition and Setup Security
• Auditability for Journal Line Reconciliation
• Entered Currency Reporting and Analysis
• Foreign Currency Recurring Journals
• Intercompany Balancing Support for Encumbrances
• Integration with Subledger Accounting
• Intercompany feature enhanced: This is now part of Oracle Advanced Intercompany System product.
• Account Analysis and Drilldown is a new web-based interface that allows to easily review and analyze general ledger financial data.
• GL Standard Reports Integration With XML Publisher
• New Terms: Ledger replaces Set of Books. A group of Ledger is called Ledger set, in a Ledger Sets, user can simultaneously-
Sub Ledger Accounting Flow Chartà
Accounting Setup Manager in R12- There is a single page for setups-
R12 Account Payables new feature
User Rating: 5 / 5
In large implementations with large transaction base in GL, it is very common to get java.lang.OutOfMemoryError" errors in the Output Post Processor log of the Subledger Accounting program Account Analysis Report. This report produces the output in BI Publisher.
To resolve this, you need to implement the steps below
1. Navigate to XML Publisher Administrator responsibility
2. Click Administration->Configuration
User Rating: 5 / 5
This article contains step by step implementation guide with examples for EBiz Tax in R12.
IMPORTANT - To view this article, you must have access to http://docs.google.com
It will take upto a minute for this document to load.
User Rating: 5 / 5
often the GL Super Users create manual journals either directly from
the screens or using the Web ADI to upload the journals straight into
General Ledger. However account codes used in these manual journals are
secured via value set security and the cross validation rules. But this
level of security is not enough. For the sake of an example, the GL
Users must not be allowed to tamper with the amount of expenditure a
company has made on Office Furniture for their offices. Let us say that
all the GL Account segment value Office Furniture related expenses are
A feature named Third Party account is a feature of R12 which helps keep the Subledger like Payables or Receivables in sync with General Ledger.
The control account functionality of 11i is now called Third Party account in R12. Some accounts should only be entered via the Subledger, and not be allowed for manual journal creation in GL. Hence for those entries, we can enable the qualifier to flag those as Third Party account.
In the value set definition screen, query the segment value as shown in image below. In this case, the Account Segment value is 5115. Against the segment qualifier, in Third Party Control Account, select value = Supplier, because in this example we will control the charges to this account segment via Payables whilst ensuring that Supplier details are specified. In other words, this configuration will ensure that you cannot put a charge against office supplier into GL unless you have specified the Supplier from whom the goods were purchased.