As promised, here is yet another detailed analysis for AIM’s.

Big -5 Implemenation consulting companies uses AIM (Application Implementation Methodology) to manage all of its Oracle Application projects. AIM can also be used for other different software implementations and does not limited to only Oracle Applications. However, the methodology was/is purposely built for Oracle Applications and the detailed deliverables produced are designed with the Oracle Application products in mind, as these are initially used for oracle consulting guys, and with time these are adopted methodology in Oracle application across the industry.

The following Oracle Applications Areas are covered by AIM:

• Oracle Financials
• Oracle Distribution
• Oracle Human Resources
• Oracle Manufacturing
• Oracle Projects
• Oracle Process Manufacturing
• Business Intelligence

AIM incorporates two things. First, it is a methodology showing what tasks are required, what order they should be completed in, and what resources are required . Secondly,it provides deliverable templates for all the tasks that require them. Hence the hybrid of methodology with a deliverable template tool makes AIM a powerful product.

One biggest disadvantage of AIM methodology is that is very complicated. Complicated in the sense it has ample number of deliverables which are more than 225 in number. In other word , the project time frame can be makes direct impact on this methodology , i mean to say if you tried to use them all you would be spending atleast 9-12 months implementing a 3 month project. AIM is supposed to be used by experienced project managers that pick and choose the tasks they require for each project.Most of Consulting company have fine tuned and took tailored approach for AIM’s methodology, based of there standard implementation practice.

AIM defines business needs at the beginning of the project and maintains their visibility throughout the implementation. It defines internal, external, and time sensitive business events and maps each event to the responding business and system processes. Using this method, the client gains an accurate understanding of the business requirements that need to be focused on during the course of the implementation.

AIM Structure Framework

AIM is a framework of related elements. It involves phases, processes, tasks and dependencies:

• A task is a unit of work, which results in a single deliverable. That deliverable may take many different forms like reports, schedules, code, or test results for example.
• A process is a closely related group of dependent tasks, which meets a major objective. A process is usually based on a common discipline.
• A phase is a chronological grouping of tasks. It enables a flexible way to organize tasks, schedule major deliverables, and deliver projects.

Processes and phases are explained in more detail below.

Processes

A process in AIM represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs. A task can belong to only one process. Project team members are usually assigned to a process according to their specialization and background. A brief description of the AIM processes are given below:

1. Business Requirements Definition: Business Requirements Definition defines the business needs that must be met by the implementation project. You document business processes by identifying business events and describing the steps that respond to these events.

2. Business Requirements Mapping: Business Requirements Mapping compares the business requirements to standard application software functionality and identifies gaps that must be addressed to fully meet business needs. As gaps between requirements and functionality emerge, they are resolved by documenting workarounds, alternative solutions, application extensions, or by changing the underlying business process.

3. Application and Technical Architecture: During the Application and Technical Architecture you design an information systems architecture that reflects your business vision. Using the business and information systems requirements, this process facilitates development of a plan for deploying and configuring the hardware required for a successful implementation.

4. Module Design and Build: Module Design and Build produces custom software solutions to gaps in functionality identified during Business Requirements Mapping. Custom software solutions include program modules that must be designed, built, and tested before they can be incorporated into the system.

5. Data Conversion : Data Conversion defines the tasks and deliverables required to convert legacy data to the Oracle Applications tables. The first step of this process explicitly defines the business objects that are required for conversion and the legacy source systems that store these objects. The converted data may be needed for system testing, training, and acceptance testing as well as for production.

6. Documentation :Documentation begins with materials created early in the project. Using detailed documents from the project, the writing staff develops user and technical material that are tailored to the implementation.

7. Business System Testing: Business System Testing focuses on linking test requirements back to business requirements and securing project resources needed for testing. It supports utilizing common test information including data profiles to promote testing co-ordination and to minimize duplication of test preparation and execution effort.

8. Performance Testing:Performance Testing enables you to define, build, and execute a performance test. Use the results to make decisions on whether the performance is acceptable for the business and to help propose tactical or strategic changes to address the performance quality shortfall. Performance Testing is closely related to Application and Technical Architecture; they are interdependent.

9. User Training:Training prepares both users and administrators to assume on the tasks of running the new application system. It includes development of materials and methods as well as administration. Instructors and courseware developers orient their material toward roles and jobs, and not toward application modules.

10.Production Migration : Production Migration moves the company, system, and people to the new enterprise system. Following production cutover, it monitors and refines the production system and plans for the future. The Production Migration process encompasses transition to production readiness, production cutover, and post-production support

The Process can easily understood by this diagram against Phases discussed below.

Phases

An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a common goal. During a project phase, your project team will be executing tasks from several processes. A brief description of the AIM processes are given below:

1. Definition: This consist of review the organization’s business objectives, evaluate the feasibility of meeting those objectives under time, resource, and budget constraints. Moreover this can be best consider as SOW(statement of work) preparation phase.

2. Operations Analysis:During Operations Analysis, the project team develops Business Requirements Scenarios based on deliverables from Definition that are used to assess the level of fit between the business requirements and standard application functionality. Gaps are identified and corresponding solutions developed. The analysis results in a proposal for conducting business operations under the envisioned application technical architecture. Solutions for gaps evolve into detailed designs during Solution Design.

3. Solution Design:The purpose of Solution Design is to develop the detailed designs for the optimal solutions to meet the future business requirements. During this phase, project team members create detailed narratives of process solutions developed during Operations Analysis. Supporting business requirements may require building application extensions to standard features; several alternative solutions may have been defined during Operations Analysis. The project team carefully scrutinizes these solutions and chooses the most cost effective alternatives.

4. Build:The coding and testing of all customizations and other custom software including enhancements, data conversions, and interfaces is done during Build. Policy and procedure changes relating to business process modifications are developed. Business system testing is performed to validate that the developed solutions meet business requirements. If customizations, extensions, or conversions are not required, Build is still important because it includes the business system test, which is commonly conducted as a formal conference room pilot. The business system test validates the solutions and is performed in an environment that closely resembles production.

5. Transition: During Transition, the project team deploys the finished solution into the organization. All the elements of the implementation must come together to transition successfully to actual production. The project team trains the end users while the technical team configures the production environment and converts data. Transition ends with the cutover to production, when end users start performing their job duties using the new system.

6.Production: Production begins immediately with the production cutover. It marks the last phase of the implementation, and the beginning of the system support cycle. Included in this final phase is a series of refinements and performance measurement steps. The inhoues MIS/IT Department personnel work quickly to stabilize the system and begin regular maintenance. They will provide the ongoing support to the organization for the remaining life of the system. During Production, you compare actual results to project objectives.

For more Information about AIM’s ..here is the link for you..

Overview
Auto Lockbox is a service that commercial banks offer corporate customers to enable them to outsource their accounts receivable payment processing. Auto Lockbox eliminates manual data entry by automatically processing receipts that are sent directly to your bank. You can also use Auto Lockbox for historical data conversion. For example, you can use Auto Lockbox to transfer receipts from your previous accounting system into Receivables. Auto Lockbox ensures that the receipts are accurate and valid before transferring them into Receivables.

Benefit of auto lockbox

• Eliminates manual data entry
• Streamlines the application of receipt to outstanding transactions
• Effectively manages cash flow by reducing turnover for converting checks into cash

When can I use lockbox

• apply receipt to outstanding invoice
• import historical receipt data
• auto lockbox report , such as the post quick cash Execution Report, are a good tool to reconcile auto lockbox receipt with the bank transmission

What is inside the lockbox process

This consist of 3 steps process, viz

1. Import: During this step, Lockbox reads and formats the data from your bank file into interface table AR_PAYMENTS_INTERFACE_ALL using a SQL *Loader script.

2. Validation: The validation program checks data in this interface table for compatibility with Receivables. Once validated, the data is transferred into QuickCash tables (AR_INTERIM_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RCPT_LINES_ALL) . At this point, you can optionally query your receipts in the QuickCash window and change how they will be applied before submitting the final step, Post QuickCash.

3. Post QuickCash: This step applies the receipts and updates your customer’s balances.

Process Flow
Here is schematic data flow and process flow of lockbox process

Set Up
These are the Normal Set Required for Auto lockbox. This is part of AR Set up:

• Define Banks
  • Define Remittance Bank with Account use Internal where checks from customer are deposited.
• Define Receipt Class
  • Define a Receipt class to determine the required processing steps for receipts to which you assign payment methods with this class.
• Define Payment Methods
  • Define a payment method with all receipt accounts.
• Define Receipt Source
  • Define Receipt Batch Source and attach receipt class, payment method and remittance bank account information to the Receipt Source.
• Define Lockbox
  • Define Lockboxes to use the Receivables Autolockbox program.
• Define Transmission Format
  • Define the Transmission Format which Auto Lockbox uses when importing data into Receivables.
• Define AutoCash Rule Set
  • autocash rule sets determine how a quickcash receipt is applied to open debit items.
  • enter a sequence for automatiocally applying receipts
  • select one or more autocash rules for receipt application from the list of autocash Rule options
  • Define AutoCash Rule Sets to determine the sequence of rules that Post
  • QuickCash uses to update Customer’s account balances.
• Control file
  • Create a control file which is used by SQL * Loader to import the data into interface table and it is placed in the directory $AR_TOP/bin
• Data file
  • data are kept into directory $AR_TOP/bin

Lets start with simple question.

What is a methodology..

“A methodology is a set of guidelines or principles that can be tailored and applied to a specific situation.”

In a project environment, these guidelines might be a list of things to do. A methodology could also be a specific approach, templates, forms, and even checklists used over the project life cycle.

Therefore that was the driving factor for bringing AIM’s as methodology which was initially used by Oracle consulting , which is now most acceptable methodology for oracle application roll out.

So then what oracle application methodology in short AIM’s based out of…

• Multi-track methodology
• Technology Modernization
• Business Process Reengineering
• Oracle Application/System Development
• Organizational Change
• Project Management

When it was first launched
Any Guess… The first version of AIM was initially released for use by Oracle Consulting staff in October 1994.

• Tasks, steps and deliverables for project life cycle
• Templates for many deliverables

AIM 2.0, a refined version of the method, was released in July 1997.

Oracle introduced AIM Advantage 3.0 in September 1999.

What is current version in market?
Oracle has launched AIM’s 3.1 version, which is also called as AIM’s Advantage, which is now a consider as web-deployed tool kit for planning, executing and controlling Oracle Applications implementation projects.

What is new in AIM’s?
In newer version couple of new enhancement has been made, they are
· Support for business process change using the new Business Process Architecture process
· Integration with Oracle products like Oracle Business Models and Oracle Tutor

Is any cost for holding AIM’s tool?
Yes, as reported on Oracle site it cost you USD $2195 for per Named User(.. this may be changed..check with Oracle site)

What other methods and tools are integrated with AIM 3.1?
AIM 3.1 is closely integrated with Oracle’s Project Management Method (PJM). AIM and PJM tasks are both reflected in the AIM Work Breakdown
Structure (WBS).

• Oracle Business Models (OBM)
• Solution Value Assessment (SVA)
• Oracle Support Assessment (OSA)
• Learning Needs Assessment (LNA)
• Enterprise Data Management System (EDMS)
• Oracle Tutor

How I get the AIM’s software?
AIM’s download is only limited to OPN (Oracle Partner Network)

What is software requirement for AIM’s 3.1
1. Windows 2000, XP, NT
2. Adobe Acrobat Reader 6.0 or later
3. Microsoft Office 2000 or later
4. Microsoft IE 6.0 or later, or Netscape 7.0 or later

What is covered in AIM’s

1. Technology Modernization
   This can be understood as the IT track contains tasks and steps relating to the creation and maintenance of procedures governing the hardware, systems software, toolsets, and databases.
2. Oracle Application/System Development
   The Oracle Application/System Development track contains the tasks and steps relating to the development of custom or tool code to support interfaces, conversions, extensions, reports, and integration testing exercises. This track overlaps the process reengineering track with the iterative design and setup of the application modules.
3. Business Process Reengineering
   The BPR track contains tasks and steps relating to process reengineering and application configuration. Prototyping is used to facilitate the design of “To Be” processes.
4. Organizational Change
   The Organizational Change track contains the tasks and steps relating to culture and change readiness assessment, organizational and job analysis, facilities analysis and preparation, user procedures and performance based training.
5. Project Management
   This track contains the tasks and steps relating to the development and management of work products on an Oracle Applications engagement. Its focus is to ensure that projects are estimated correctly, managed successfully, and properly integrated

Will come back with yet another additional information for AIM’s, keep watching this space…Good Weekend guys ..

So, the big news for this fortnight is ..on 16th June Oracle celebrated his 30th Birthday.

The 30 year journey from “Systems Development Laboratories(SDL)” to “Oracle” has been recalled by Rich on this great day.So, Guys, its perfect time to take a quick look on all goodies the oracle have in last 30 years.

1.Oracle 30 Years History

2.A power point by Rich Niemiec, How Oracle Came to Rule the Database World.

3.Oracle Application Evalution History

4. Oracle Celebrates 30 Years of Innovation by By David A. Kelly

More over, you have to wait for July-Aug edition of Oracle , that has featuring “Oracle Celebrates Thirty Years of Innovation”..so keep watching

Happy Beleted Birthday Oracle !!

This is in continuation to API’s availability,Here are the API’s availability in AP.

Credit Card Transaction Processing

• Manual Credit Card Entry: A form is available for entry through the Oracle Payables application.
• Credit Card Transaction Interface Table: This process loads transaction data from the credit card issuer (American Express, Diner’s Club, MasterCard and Visa) into Oracles AP module. Oracle Payable then uses this data to confirm transactions with employees. Once the transactions have been approved the credit card transaction lines are imported into Payables Open Interface using the Credit Card Invoice Interface Summary program. The credit card transactions are then available for final import to Oracle Payables where the transactions become invoices.

Creating Invoices
In Oracle Payables four methods are available for entering an invoice into the system.

• Manual Invoice Entry: Two methods for manual invoice entry exist. Using Oracle Payables system Invoice Workbench which includes the Invoice Batches window and Distribution window users can enter complex invoices, and invoices requiring online validation. In addition this functionality is useful in processing invoices that require special attention such as immediate payment.
• The second method of manual invoice entry, Invoice Gateway, is used when entering high volumes of invoices. Generally these invoices do not require online validation or defaulting of accounting information. After entering invoices using the gateway, the invoice import must be run, at that time validation and defaulting is performed. This method of entry can be used in lieu of invoice interfaces. Although, using the gateway can accomplish similar results to that found with an interface process, manual entry is no substitute.
• Automatic Invoice Creation: Oracle Payables provides functionality to produce periodically recurring invoices. This functionality may be used to substitute manual invoice entry or the payables open interface. In the case of recurring invoices that would normally come from an external system choosing to setup a recurring invoice formula may be an alternative.
• Using Payables Open Interface: Choose this method for processing large volumes of invoices that originate in external system. Additionally, this process is useful in handling employee expense reports generated through self-service applications, expense reports entered by the Payables Department, invoices for employee credit card expenses, Oracle Projects billing and time and expenses, and EDI invoices transferred from the Oracle EDI gateway.

Purchase Order Matching

Oracle Payables can be implemented without Oracle Purchasing, to allow this several purchasing tables are installed initially which must be populated using custom interfaces. Only two-way matching is available when data is loaded using the interface method. Two-way approval verifies that purchase order and invoice information match within your tolerances as follows: Quantity billed on the purchase order shipment is less than or equal to Quantity ordered on the purchase order shipment. Invoice price on the purchase order shipment is less than or equal to Purchase order price on the purchase order shipment.
Receipts can only be matched in an install that also includes Oracle Purchasing.
The only method for interfacing data into the purchasing tables described in this section is through a customized interface from an external source. Note: Interfacing this information is not supported by Oracle.

• Loading PO_HEADERS: Each record in this table represents a purchase order, which is an order for goods or services from a single supplier. Each purchase order may have multiple lines (PO_LINES). In addition, each blanket purchase order may have multiple blanket releases (PO_RELEASES), which release an amount from the blanket.
• Loading PO_LINES: Each record in this table represents a purchase order line, which identifies the items and unit price for the goods ordered on a purchase order. Each purchase order line may have multiple shipments (PO_LINE_LOCATIONS).
• Loading PO_LINE_LOCATIONS: Each record in this table represents a purchase order line, which identifies the items and unit price for the goods ordered on a purchase order. Each purchase order line may have multiple shipments (PO_LINE_LOCATIONS).
• Loading PO_DISTRIBUTIONS/PO_DISTRIBUTIONS_AP_V: Each record in this table/view represents a purchase order distribution, which identifies the account charged for the items on a purchase order shipment.
• Loading PO_RELEASES: Each record in this table represents a blanket release for a purchase order. A blanket release may create multiple shipments.
• Loading AP_INVOICES/AP_INVOICE_DISTRIBUTIONS: Each purchase order shipment can be matched to multiple invoices(AP_INVOICES), and a single invoice may be matched to multiple purchase order shipments. When you match an invoice to a purchase order shipment, Payables creates an invoice distribution AP_INVOICE_DISTRIBUTIONS) from each purchase order distribution on the shipment. When you match an invoice to a single purchase order distribution, Payables creates a single invoice distribution from the purchase order distribution.

Vendor Interface

Existing and new vendors must be loaded into the Oracle Payables application to support payables activities. Two methods may be used to enter vendors into Oracle Applications, manual entry and direct loading using a customized loader program.

• Manual Vendor Loading: Use the Enter Vendor window. Using this functionality vendor header information as well as vendor site information can be entered.
• Vendor Interface: When interfacing vendors into Oracle Applications two tables must be loaded the PO_VENDORS and PO_VENDOR_SITES_ALL. The vendor table contains all header information and the site table contains information about each the vendor locations such as “ship to” and “bill to”. Using this method makes sense when the volume of new vendors is large. Note: Interfacing this information is not supported by Oracle.
• Those who are in 11.5.10 they will find yet another method ie by interface.
  You have to Load data into the staging tables first ie.AP_SUPPLIERS_INT – Supplier Information
  AP_SUPPLIER_SITES_INT – Supplier Sites Information ,AP_SUP_SITE_CONTACT_INT – supplier Contact details This uses Vendor ID, Vendor Site Code to relate the contacts to specific vendor. Once data get loaded three interface program should be kicked out which is as
  • Supplier Open Interface Import.
  • Supplier Sites Open Interface Import
  • Supplier Site Contacts Open Interface Import

This is in continuation to API’s availability,Here are the API’s availability in AR.

Invoices

• Manual Entry and Updating: Manual entry or update of invoices requires the user to have access to the Oracle Application’s Accounts Receivable module and specifically the Enter Invoices form. You can enter and update invoices for valid customers. AR uses AutoAccounting to create the revenue accounting combination based on the invoice line information.
• AutoInvoice Interface: AutoInvoice interface provides a mechanism for transferring large volumes of invoices, credit memos, debit memos, and on-account credits from third-party and legacy systems into Receivables. Information is loaded into the RA_INTERFACE_LINES_ALL (which stores information about each interface line imported) and RA_INTERFACE_SALESCREDITS_ALL (containing the sales credit information) tables then imported into the Oracle Applications by the AutoInvoice Import process.You can also refer my old post for autoinvoice details.

Receipts

• Manual Entry and Updating: Manual entry or update of receipts requires the user to have access to the Oracle Application’s Accounts Receivable module and specifically the Enter Receipts form. You can enter and update receipts for open and future accounting periods.
• AutoLockbox Interface: AutoLockbox interface provides a mechanism for transferring large volumes of payments from bank files or third party systems into Receivables. Information is loaded into the AR_PAYMENTS_INTERFACE_ALL table then imported into the Oracle Applications by the AutoLockbox Import process.
  The AR_PAYMENTS_INTERFACE_ALL table stores imported lockbox information that has not been validated. AutoLockbox creates one row in this table for each record in a transmission. When the validation step of AutoLockbox is run, Oracle Receivables transfers the information from the AR_PAYMENTS_INTERFACE_ALL tables to the AR_INTERIM_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RCPT_LINES_ALL tables.

Customers

• Manual Entry and Updating: Manual entry or update of customers requires the user to have access to the Oracle Application’s Accounts Receivable module and specifically the Enter Customers form. You can enter and update customers, multiple customer addresses (sites), and multiple contact(s) for each address.
• Customer Interface: The customer interface provides a mechanism for transferring large volumes of customers from third party and legacy systems into Receivables. Information is loaded into the RA_CUSTOMER_INTERFACE, RA_CONTACT_PHONES_INTERFACE, RA_CUSTOMER_PROFILES_INTERFACE, RA_CUSTOMER_BANKS_INTERFACE, and RA_CUST_PAY_METHOD_INTERFACE tables then imported into the Oracle Applications by the Customer Import process.
• TCA API’s: The customer information can also be loaded into application by TCA API’s.

Sales Tax Rates

• Manual Entry and Updating: Manual entry or update of sales tax data requires the user to have access to the Oracle Application’s Accounts Receivable module and specifically the Tax Locations and Rates form. You can enter and update location and rate information through this form.
• Sales Tax Rate Interface: The Sales Tax Rate Interface lets you load sales tax records into your Oracle Receivables application from your sales tax feeder system. Information is loaded into the AR_TAX_INTERFACE table then imported into the Oracle Applications by the Sales Tax Rate Interface process.
  The AR_TAX_INTERFACE table is used to import location, postal code and sales tax rate information into Oracle Receivables. Rows are inserted in this table and then the Sales Tax Interface Program is run to create records in AR_LOCATION_VALUES and AR_LOCATION_RATES. Each row can define a new location and assign to it multiple postal code and effectively date ranges, and each range may have an optional sales tax rate.

Tax Vendor Extension

Oracle provides a Tax Vendor Extension to integrate external tax calculation programs with the Oracle Application’s Accounts Receivable module. This extension allows you to provide for complex tax calculation requirements while retaining the full power of Receivables to create and store other tax data. The tax extension is called whenever a tax rate is calculated by the Receivables Tax Engine.

This is in continuation to my last post API’s availability. Here are the some keynotes on the API’s availability in GL.

Budget Upload
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.

Importing Journals

• 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….[]..

The setting up of approval hierarchy for PO requires few mandatory setup , which start with employee /Buyer information.These are the following steps required.

• Define the employee and his/her superiors
• Define the positions for the employee and the superiors

N –> Setup –> Personnel –> Positions

• assign the employee and the superiors to a position

N –>Setup –> Personnel –> Jobs

• define an approval group which allows him/her to approve PO’s up to the approval limit. Same for the superiors.

N –> Setup –> Personnel –> Position Hierarchy

• Make sure the document type (e.g. PO) allows ‘Owner can Approve’ (checkbox)
• Assign the approval groups to the correct positions
• Create a position hierarchy for every org according to your wishes
• Assign the hierarchies to the document type
• Run the concurrent request ‘Fill Employee Hierarchy’

and , finally the above can be understood in the data diagram as below.

For new babies in oracleapps world, hope this would be great helps.

Configuration
The configuration means you are changing Oracle Applications processing using profiles options flex fields and folder definitions to cater your requirement.
Typical example is like enabling or disabling flex field.Changing profile options.

Personalization
This is changing the Oracle Applications Forms and framework user interfaces .

Extension
Changing the Oracle Applications Forms and Framework logic
These are typically a program that is in addition to an exiting standard program but that does not change core code or objects.

Bolt Ons
Software packages integrated with ERP used to support specific capabilities of the COTS software

Customizations
It is basically Custom coding or modification over existing application to make more control over functionality. The more complex nature of business may cause a heavy customization. Coding includes Oracle Workflow, Oracle Alert, Financials/Sales Analyzer, Oracle Reports, Oracle Discoverer, Oracle Forms, and PL/SQL. You should also take a note customizations may also include data conversions.

Interface
A boundary across which two independent systems meet and act upon or communicate with each other. You can find details here.

Legacy System
An existing computer system or application program which continues to be used generally due to cost or feasibility considerations.

RICE Objects
This is typically more pronounced during the implementation of product, it consist of:

• Reports-A formatted and organized presentation of data.
• Interfaces-A boundary across which two independent systems meet and act on or communicate with each other.
• Conversions-A process that transfers or copies data from an existing system to load production systems at implementation.
• Extensions (or enhancements)-A program that is in addition to an exiting standard program but that does not change core code or objects.

Adding Modules
This is typically understood, the client would be extending more businesses in ERP by enabling some new module. For instance, if a customer begins with Financials and Purchasing and decides to add Order Management down the road, the implementation of Order Management within existing Suite and instance is called as Adding module or module enabling. This would be again follow a typical subset of implementation cycle.

Globalizations
Globalizations are standard product features being part of the fresh installation or released via a Maintenance Pack, and they are available to all customers.

Localizations

This is something called fulfilling local need for federal and state reporting requirement. Most of the countries in the world have specific unique local business needs and legal requirements. Oracle Applications is being used in more than 140 countries, and in order to attend some of those local business and legal requirements, Oracle has added to 11i a new set of functionality and parameters called Localizations.
If you are working in Mideast and south Asia or South America (Brazil), there is always a huge tons of Localizations stuff would in your existing application. To know more about the localization refer Metalink 122491.1 and find out what country requires localization and what for……

These are the few steps which is required to make a host based Concurrent Program.

The first steps would be , you have to create a script and save as .prog extension and put into your application top bin folder.
If your custom application is XX then the scripts should goes to $XX_TOP/bin
For example, call the script CUSTOM.prog and place it under

Step 2
Now,you have understood , the execution of unix program is bit different in oracle application. The only things you have to notice is you need to pass 4 mandatory parameter to execute host program.
The other way around is ,you can use fndcpesr and link with your host program.It means the fndcpesr will take care of your 4 mandatory parameter.

You have to simply create a soft link with $XX_TOP/bin folder.

   ln -s $FND_TOP/bin/fndcpesr