Oracle E-Business Suite R12 Financial Modules

When a transaction (invoice) is completed in Oracle Receivables, the system inserts or updates records in AR_PAYMENT_SCHEDULES_ALL to track the payment schedule and outstanding balance.

In Oracle Receivables, valid receipt statuses include CLEARED, CONFIRMED, REMITTED, and REVERSED. RECONCILED is a status managed in Cash Management, not a direct receipt status in AR.

In Oracle Receivables, standard application rule sets include Line First - Tax After, Prorate All, and Line and Tax Prorate. 'Line & Freight Prorate' is not a standard default application rule set.

In Oracle Payables, the standard payment batch lifecycle requires formatting the payment files (FORMAT) after the payment batch has been successfully built, before confirming the payments.

In Oracle Payables, standard payment methods include Check, Wire, Clearing, and Electronic. 'Automatic' is a payment method type or process, but not a valid lookup value for a specific payment method.

In Oracle General Ledger Mass Allocation formulas, the offset account (option O) receives the balancing entry. The formula allocates amounts from account A, and option O automatically receives the offsetting debit/credit to keep the entry balanced.

In Oracle General Ledger Financial Statement Generator (FSG), valid components include Row Sets, Column Sets, and Display Sets. Order Set is not a valid FSG component.

In Oracle Assets, a mass addition line becomes eligible for preparation once the accounting is created and transferred to the General Ledger. Posting the accounting in GL is not a prerequisite for preparing mass additions in FA.

In Oracle Cash Management, the AutoReconciliation process uses Bank Transaction Codes to determine how to reconcile transactions and automatically create miscellaneous receipts or payments based on the transaction setup.

The Subledger Accounting (SLA) feature introduced in Oracle EBS R12 did NOT make the Global Accounting Engine (GAE) obsolete. While SLA provides enhanced accounting functionality, GAE continues to exist and serve specific purposes. The two features coexist rather than SLA completely replacing GAE.

The Reporting Currencies feature in R12 Ledger and the MRC (Multiple Reporting Currencies) feature from earlier versions serve different purposes. R12 Reporting Currencies creates separate ledgers for each reporting currency, while MRC managed multiple reporting currencies within a single ledger. The new feature offers a different approach, not a direct replacement.

When a Ledger is created in Oracle General Ledger R12, the system automatically generates a default Data Access Set for that ledger, granting full read and write privileges.

In Oracle EBS R12, setting up E-Business Tax is mandatory before you can successfully enter and process tax-related journals in the General Ledger module.

Data Access Sets control data access security and define what data users can view across multiple ledgers. They do not provide a single consolidated window for importing journals from multiple ledgers - journal import is still performed through the standard Journal Import interface for each ledger separately.

Oracle EBS R12 FSG (Financial Statement Generator) does support publishing reports in XML format. This is a standard feature that allows financial statements to be exported in XML for integration with other systems or for downstream processing.

In Oracle E-Business Suite R12 General Ledger, when you end-date a code combination, the system does not automatically redirect transactions to an alternate account; you must manage this through other rules or manual adjustments.

While the Accounting Setup Manager in R12 is indeed used to set up Ledgers, Legal Entities, Operating Units, Chart of Accounts, and Value Sets, it is not a 'single setup window.' These tasks are performed through multiple windows, steps, and wizards within the Accounting Setup Manager framework, not one unified interface.

The Mass Allocation feature was NOT made obsolete in Oracle EBS R12. This feature continues to be available and supported in R12 for creating allocation journals to distribute costs and revenues across multiple dimensions. Mass Allocation remains a valid and actively used feature.