Thursday, February 18, 2010

Profile Options - AOL

There are four possible levels at which system administrators can view and update a profile option value: site, application, responsibility, and user.

  • FND: Enable Cancel Query [ Yes (default) / No ] - Option to cancel the form query if taking long time
  • Concurrent: Active Request Limit - Limits the number of requests that may be run simultaneously by each user or for every user at a site. If you do not specify a limit, no limit is imposed. Users cannot see or update this profile option. This profile option is visible and updatable at all four levels.

Wednesday, February 17, 2010

Multiple Reporting Currencies

Multiple Reporting Currencies (MRC) is an Oracle General Ledger feature that allows you to report in your functional currency and in one or more foreign currencies. You do this by defining one or more reporting sets of books, in addition to your primary set of books. You can set up multiple reporting SOBs and associate them with a primary SOB.

Your primary functional currency is the currency you use to record transactions and maintain your accounting data; the currency in which you transact most of your business and the one you use for legal reporting.

A reporting functional currency is a currency other than your primary functional currency for which you need to report accounting data.

If you only need to report balances in a currency other than your primary functional currency, the General Ledger Translation feature is probably sufficient.

You need MRC when:

  1. You operate in a country whose unstable currency makes it unsuitable for managing your business. As a result, you need to manage your business in a more stable currency and still be able to report your transactions and account balances in the unstable local currency.
  2. Your company is multinational, and you need to report financial information in a common functional currency other than that of the transaction or your primary functional currency.
  3. You operate in a country that is part of the European Monetary Union (EMU), and you want to concurrently report in Euro in preparation for the pan-European currency.

Monday, February 15, 2010

Tables Info - Cost Management

CST_ITEM_COSTS
  • Inventory_Item_ID
  • Cost_Type_ID
  • Organization_ID
  • Item_Cost
CST_ITEM_COST_DETAILS
  • Inventory_Item_ID
  • Cost_Type_ID
  • Cost_Element_ID
  • Organization_ID
  • Item_Cost

Thursday, February 11, 2010

Period End Close - General

Periods represent non-overlapping consecutive date ranges. Every Financials customer needs to successfully close the accounting books each period.
General Steps
Here are some guidelines, from a general perspective, how you can perform the close process for every subledger:
a) Complete transactions
b) Create accounting
c) Reconcile transactions
d) Post to General Ledger
e) Reconcile accounting
f) Close period

Step b), Create Accounting, is a new step in Release 12, as it is an SLA feature. The accounting can be created immediately online, or can be run as a process in the background e.g. as a batch job at a time that matches your business needs.
The important thing to note, is that the accounting is not the distribution on the transaction. The final accounting by SLA could result in different accounting entries being generated based on the accounting rules you have configured. Therefore, you need to ensure that all your accounting for your transactions is created before you post to General Ledger, in order to update the balances correctly.

In Release 11i, when you close your periods in each of the subledgers, Oracle General Ledger will automatically create the balancing lines for journals posted to General Ledger. This changes in Release 12 as subledger accounting creates the balancing lines at the time you account for the subledger transactions.

The subledger accounting journal represents your REAL accounting and the balancing lines are created as part of these subledger accounting journals. When you close a period in Release 12, you’re actually closing subledger accounting. The journals can then be posted to the general ledger to update the GL balances.

Period End Close Dependencies

Performance Tuning

Database Metrics and Alerts:

Metrics and Statistics

Histograms

Database Alerts - DBA_THRESHOLDS gives you the threshold settings defined for the instance

Baselines:

Real-time Operation Monitoring:

Wednesday, February 10, 2010

Oracle Documentations

TSD / TDD Guidelines

  • Mapped to its FSD / BRD.
  • Data Flow Diagram
  • Process Flow Diagram
  • ER Diagram linking all the tables involved.
  • Use Cases
  • Assumptions / Dependencies / Open Issues needs to be updated regularly.

Saturday, February 6, 2010

Oracle Finance

Chart of Accounts:
Chart of Accounts (COA) determines how your accounting information is collected, categorized, and stored for reporting purposes. In Oracle Financials, all accounts are identified by a unique Accounting key Flexfield combination, which is your COA structure. The Accounting Flexfield (AFF) consists of multiple segments, such as those for company, cost center, and account. One full AFF is called a combination.You assign each account the qualifier of asset, liability, owner's equity, revenue, or expense.

Subledger Accounting:
Sub Ledger Accounting (SLA) introduced in Release 12, provides a common repository of all your accounting information.

Just as Oracle General Ledger stores balances and journals, Subledger Accounting stores subledger balances and subledger journals for all of your subledgers that require accounting.

In Release 11i the transactions and distributions represented the accounting. In Release 12 however, distributions on transactions in subledgers are considered to be the default accounting and should therefore not be used for reconciliation purposes. The reason is that subledger accounting enables you to change the accounting for transactions so it is different from the default accounting. Therefore, the subledger accounting becomes the single source of truth for accounting reconciliations.

Things to Ponder:


  1. Using more GL account KFF Segments doesn't affect the performance as the application uses the CCID (Code Combination ID) and not run the processes via the concatenated segments. However more the segments the more GL manual entries.