This is in continuation to my last post API's availability. Here are the some keynotes on the API's availability in GL.
Oracle Applications provides four methods for adding budgeting transactions, Application Desktop Integrator (ADI) Budget Wizard, manual entry through the application forms, journal import and budget import.
- ADI: ADI is a spreadsheet-based application that allows the user to format data inside a Microsoft Excel spreadsheet and then upload into Oracle Applications. ADI uses Budget Wizards and Budget Templates to simplify the data entry. In addition, ADI is delivered as standard functionality, as opposed to a custom interface that would require additional development, maintenance and upgrade consideration.
- Manual Entry and Updating: Manual entry requires the user to have access to the Oracle Application's General Ledger module and specifically the enter budget amounts forms for your accounts to replace any existing budget balances. You can enter budget amounts for each account in the budget organization one-by-one, or you can use worksheet mode to enter budgets for several accounts at once. Budget rules enable you to distribute budget amounts for all periods.
- Budget Interface: Budget interface provides a mechanism for transferring large numbers of budget data from a third-party budget source system to your General Ledger application Budget Interface table. Once you load your budget information into the Budget Interface table, you can run Budget Upload to post your budget data into your General Ledger application. Budget Upload uses the Budget Interface table GL_BUDGET_INTERFACE to upload budget information. The Budget Interface table is organized in such a manner that provides a column for each budget period in your current open fiscal year in addition to account and other relevant information on a single budget line.
- GL Interface: GL Interface is another option for uploading large numbers of budget data from a third-party budget source. With this option the source must provide a file that mimics the layout found in the GL_INTERFACE table. The process for uploading a budget through the journal import process is similar to that found using budget interface functionality. The most significant difference is found in the format of the budget record. Here the record is formatted in such a way that each budget line provides an amount for a single budget period within the open fiscal year. Consequently, assuming a fiscal year has twelve periods, a full fiscal year budget for one account would require twelve individual lines to be processed to produce a budget across the full year.
- Manual Entry and Updating: Manual entry requires the user to have access to the Oracle Application's General Ledger module. After accessing enter journals form the user is presented with a choice of either entering a new journal or searching an existing journal for update. On a new journal the user can choose to overwrite default information found in header by selecting choices from the drop-down list, in some cells the data is free form and others the default information cannot be changed. The bottom area of the form also known as the journal line detail is used to enter amount, account information and journal line description.
- ADI: Journal Wizard is functionality provided with ADI that allows you to create journal entries using Excel, then upload them into Oracle GL. With ADI the Wizard generates the journal entry template to match the systems configuration. Therefore, in certain cases where the volume is not excessively large this method may be used to format and upload journal entries to Oracle GL. In addition, ADI is delivered as standard functionality, as opposed to a custom interface that would require additional development, maintenance and upgrade consideration.
- GL Interface: Use journal import to load large numbers of journal transactions from third-party systems such as payroll, accounts payable and accounts receivables systems. When using the journal import functionality standard and statistical type journals can be processed. In cases where migration from an older system to Oracle GL is taking place, GL Interface can be used to facilitate the process.
Loading Daily Rates
When using General Ledger's Multiple Reporting Currencies feature, your daily rates are used to convert your primary set of books' journals to the appropriate reporting currencies when the journals are copied to your reporting sets of books. Your daily rates must be defined before you post journals in your primary set of books. To load daily currency rate information two options are available, manual entry using the Daily Rates form or direct loading through the GL_DAILY_RATES_INTERFACE table.
You should take a note, normally one currency exchange rate is used for all set of books throughout the organization therefore preventing out-of-balance issues especially in the case of intercompany transactions.
- Manual Currency Rate Input: This option is used primarily when data volumes are small and updates occur on a monthly intervals. In most cases the data is extracted from the internet or another source and someone is required to calculate a month average then enter the values into the system, using the daily rates form in the Oracle GL application.
- Automatic Currency Rate Loading: Depending on the frequency and number of currencies used throughout the business, the volume may become too much to handle through a manual entry process. Additionally, choosing this option makes daily updates more practical and accurate. Several services provide daily currency rate information that can be transferred to Oracle GL. Once the file is received the data is upload into the GL_DAILY_RATES_INTERFACE and subsequently a trigger moves the data into a production table.
The GL_DAILY_RATES_INTERFACE is the interface table used to create, update, and delete daily conversion rates. This table should be used to load rates into the GL_DAILY_RATES table.
Generating Intercompany Transactions
The Global Intercompany System (GIS) provides a central location for subsidiaries to enter intercompany transactions, those occurring between set of books. Furthermore, the process is built in such a manner that an entry requires approval from the sender and receiver prior to the transaction posting. With this process transaction amounts, dates, and currencies are confirmed by both subsidiaries and subsequently producing more accurate results.
The process provides three mechanisms for entering transactions, manual, automatic transaction line generation and import transactions through the GIS open interface table GL_IEA_INTERFACE. The main factor for choosing which option to use is mainly based on data volume and integration with external systems.
- Manual Intercompany Transaction Input: Use the Enter Intercompany Transactions window to enter, update, approve, reject or mark transactions for deletion. This process is convenient for quick entry and correction of entries that may have been interfaced in larger batches.
- Automatic Transaction Line Generation: Using predefined AutoAccounting rules establishing chart of account relationships between GIS senders and receivers, GIS can automatically generate code combinations and amounts for any code combination of the following: sender clearing, receiver distribution, and receiver clearing transaction lines.
- Intercompany Transaction Import: GIS provides the Open Interface to handle high volumes of intercompany transactions and integration with external systems. The AutoAccounting rules are applicable to transactions entering GIS through the open interface......