Oracle Implementation Methodalagy

Application Implementation Method is a provan approach, which specifies all the activities which are required to implement oracle applications successfully.

The scope of the AIM is enterprise wide.

There are eleven processes of implementation.

1. Business Process Architecture[BP]

This phase explains
Existing business practices
Catalog change practices
Leading practices
Future practices

2. Business Requirement Definition[RD]

This phase explains about the
Base line questionnaire and
The gathering of information.


3. Business Requirement Mapping[BR]

In this phase we can match all the requirements of business with the standard functionality of the oracle applications.

If all the requirements match with oracle standard (with out customization) functionality then, it is called as vanilla implementation).

4. Application and Technical Architecture [TA]

Explains the infrastructure requirements to implement oracle applications.
For example:
desktops
software
hardware

people...etc

5. Build and Module Design[MD]

In this phase concentrate on developing the new functionality which is required by the client.
This is called customization.
In this phase explains how to design a forms, database and reports...

6. Data Conversion:[CV]

Is the process of converting or transferring the data from legacy system to oracle applications? This is called as data migration.
Ex: transferring the closing balances of the previous year as an opening balances to next year.

7. Documentation:[DO]
I
n this phase we have to prepare module wise user guides and implementation manuals which helps in the implementation.

8. Business System Testing:[TE]

A process of validating the setup’s and the functionality by a tester to certify its status is allied business system testing. It is done by a functional consultant.

9. Performance Testing:[PT]

Performance testing means evaluation of transaction saving time, transaction retrieval times. It is done by a technical team.

10; Adoption and Learning.[AP]

This phase explains about the removal of the legacy system of the client. The entire user should be trained with new oracle applications. In this phase we have to prepare user manuals.

11. Production Migration[PM]

A process of decommissioning of legacy system and the usage of new oracle application system begins in this phase.

Form personalization

Introduction to Form personalization

Form personalization is a declarative feature that alters the look and behavior of the oracle forms with out changing base code. This concept was introduced in the release 11.5.10. All E-Business suit forms can be personalized

By using form personalization you can:1. Display your own terminology.
2. Stream lines the screen interaction.
3. Implement security policies.
4. Add your own validation and error messages.

There are some limitations:
1. You can only change what oracle forms allows to be changed at run time.
2. You can only respond to limited trigger events only.
3. Your changes may be overridden by oracle base code.

Procure To Pay Cycle Process

1. Create a Standard Purchase order.

2. Give Shipments

3. Give Distributions

4. Approve PO

5. See the status of the PO In The header level: It is approved.

6. Go to the ReceivingàReceipts

7. Give the sub inv and stock locator where you want store the goods. And Save.

8. View the request status and refresh If not Completed.

9. Run the Program Pay on receipt auto invoice.(Which Generate Invoice Automatically)

10. View the Status of the program and refresh if not completed.

11. Go to Payables: InvoiceàEntry àInvoice
Query with the Invoice Num ERS%

12. Validate the Invoice .After Validate Enable the creating Accounting check box.

13.See The Account 

14. Enable the check box Pay in full. And Pres ok.

15. Select the Bank and Go to Actions 

16. Enable the check box Create Accounting and press ok.

17. See the Account Created.


18. Now see the invoice status validated, accounted and amount paid.



19. Go to Cash Management: Bank Statementsà Manual clearing. àClear Transactions
Find the Bank Account.


20. Enable the Transaction and press Clear Transaction Button.


21. Go to Payables: PaymentàEntryàPayment
Query with Payment Date


22. Go to actions, enable Create Accounting and press ok.


23. See the Account created.

24. Run: Payables Transfer to General Ledger.


25.View the Request status and refers if not completed.


26.Got to GL:JournalàImportàRun



27.View the request status and refers if not completed.


28. Go to JournalsàEnter .Find with Source as Payables.


29.Now We can Post the journals.

Journal source and categories

Journal source and categories is used to differentiate journal entries and to enhance your audit trail.

Journal entry source indicates where your journal entries originate

Journal categories help you differentiate entries by purchase or type.
Examples for Sources:
Assets
Purchasing
Payables
Manual
Budget …...Etc.
Examples For Categories:
Accruals
Adjustment
Receipts
Revaluation
Payments..Etc..

Oracle applications provided required source and categories with default. But you can define with your sauce and categories by using the following navigation:
GL:Setup->Journal->Source
Setup->journal-.Categories

With Journal Source you can:

Define inter company and suspense accounts for specific sources.
Run auto post program for specific source
Import journals by source
Freeze journals imported from sub ledgers to prevent users from making changes.
If you have journal approval enabled for your set of books, you can use journal source to enforce management approval of journal before they are posted.

With Journal Categories you can:

Define inter company and suspense accounts for specific category.
Use document sequence to sequentially number journals by categories.