IMPLEMENTATION & SUPPORT PROCESS
Implementation types
Types of Implementation: 1. Fresh Implementation 2. Rollout projects 3. Up gradation Projects 4. Supporting Projects 5. Enhancement Project (Adding Modules)
IMPLEMENTATION & SUPPORT PROCESS
Implementation steps 1. Project Management Plan 2. Kick off Meeting 3. As Is Analysis 4. As Is Document 5. To be document 6. Mapping 7. Gap Analysis 8. Configuration/ Setup 9. Testing of Configuration 10. 11. 12. 13. 14. 15. 16. 17. CRP Conference Room Pilot UAT User Acceptance Test Production Configuration Data Migration End User Training Go Live Parallel Run Post implementation Support
2
IMPLEMENTATION & SUPPORT PROCESS
Implementation steps
1. Project Management Plan: In this phase, Project Manager will create document called PMP Document with the details of project time frame, required project. This document will be shared with client side steering committee members to get sign off that document. Manager will be shared this document with team members. resources and the total cost of the
2. Kick off Meeting: In this phase introduction will be happen between the implementation team and the steering committee members and super users of client side.
IMPLEMENTATION & SUPPORT PROCESS
3. As Is Analysis: In this phase implementation team will study and analyze the current process of the client business. 4. As Is Document: This will be created with the current process analysis. 5. To Be Document: In this document we will capture all the information how would be the future process of client on Oracle Apps. This document will be reviewed by steering committee of client and get signed off. 6. Mapping: Process of verify the customer requirement with Oracle Standard functionality is called Mapping.
IMPLEMENTATION & SUPPORT PROCESS
Implementation steps 7. Gap: If any requirement is not available in the Oracle Standard functionality is called Gap. To fix the gap we have to do the following Gap Analysis to find out the best solution. i) ii) iii) iv) Customization Form Personalization Work Around Re engineering.
Customization: Developing new forms or Reports in Oracle Apps Form Personalization: Without writing any programs and coding we can modify some forms. Work around: Some process may not be required to do by customer, but he has to follow the process to complete the activity. For example: Zero payments and Petty cash. Re engineering: Changing the current process followed by customer to fit with oracle.
IMPLEMENTATION & SUPPORT PROCESS
Implementation steps
8. Configuration & Setup: In this stage we will configure the setup for client systems. We have 3 types of instances: 1. Test instances (CRP Instance) Only for testing 2. Development Instance (Dev Instance) To develop custom components 3. Production Instance (Prod Instance) Real time instance.
9. Testing of Configuration: We will verify the accuracy of the configuration before showing to client. 10. CRP: Conference room pilot: We will show the configuration to client and will get
signoff. In general there are 2 CRPs is enough to get sign off. 11. UAT: User Acceptance Test: In this phase test instance will be provided to key
users of client to test the application.
6
IMPLEMENTATION & SUPPORT PROCESS
Implementation steps
12.
Production Configuration: Once UAT signed off we will configure the production instance. Through cloning test instance will be copied to Dev instance for the purpose of technical people usage.
13.
Data Migration: Data moving from Legacy System to Production instance is called Data Migration or data Conversion. Functional Consultant responsibility in data migration: - Template preparation for Suppliers, Customers, Purchase Invoice, Sales invoices, Assets, Bank accounts, Payment terms. - Templates will be filled up by client and implementation team will validate the completed templates. - These templates with data will be shared to technical consultants.
IMPLEMENTATION & SUPPORT PROCESS
- Technical people will be developing some staging tables by using some tools like SQL Loader. They will be writing some custom programs to store the data in directories. They will be writing the programs in such a way that, system will pick up the data from the staging tables. - If you run the program then data will flow into Oracle Apps. - Before that Functional consultant has to set up the pre requisites like Customer and Supplier Accounts. - To upload the assets data we use Web ADI process. For this we do not need to create staging tables for data storing. Validation also not required. - There will be cut off date for data migration. - Information which we migrate: Supplier header, Supplier site, Supplier contact information. Customer header, Open transactions.
14. 15.
End user training: Training to end users Go live: After migrating data into production instance, customer start using the
Oracle apps, this activity is called as Go Live. This instance is called Prod instance.
IMPLEMENTATION & SUPPORT PROCESS
Implementation steps 16. Parallel Run: Customer will enter the data in the both the applications in Legacy and Oracle Apps. This process is required until the Oracle instance get stabilized.
17.
Post implementation Support : Once the implementation completed, after go live, customer may request to provide support for some time.
IMPLEMENTATION & SUPPORT PROCESS
AIM METHODOLOGY
This is an application implementation methodology developed by Oracle Corporation. We use this methodology for Oracle Apps projects implementation. Sequence of order of task to complete implementation is called AIM Methodology.
This will be conducted in 6 phases. 1. Definition 2. Operational Analysis 3. Solution Design 4. Build 5. Transition 6. Production.
10
IMPLEMENTATION & SUPPORT PROCESS
AIM METHODOLOGY
AIM Methodology Stage 1. Definition
Implementation Step Project Management plan Kick of Meeting As Is Process To be process
Document Name PMP BP 040 BP 080 RD 020
2. Operation Analysis
Mapping Gap Gap Analysis BR 030 MD 050 (FDD) BR 100 TE 040
3. Solution Design 4. Build Configuration / Setup Testing CRP
11
IMPLEMENTATION & SUPPORT PROCESS
5. Transition UAT Production Configuration Data Migration User Training 6. Production Go Live Parallel Run Post implementation Support BR 100 & BR110 CV
BP = Business Process BR = Business Requirement MD = Module Design RD = Requirement Definition FDD = Functional Design Document TE = Test scripts CV = Conversion Documents
12
IMPLEMENTATION & SUPPORT PROCESS
Documents AIM Methodology
BP 040 = Current Business Process BP080 = Future Business process RD020 = Requirement Definition = BP040 +BP080 MD050 = Functional specification document BR100 = Application setup document TE040 = Test Scripts BR110 = Profile Options
13
IMPLEMENTATION & SUPPORT PROCESS
SUPPORTING
Steps in resolving an issue: 1. Understand the issue 2. Find the setup is correct 3. Is there any problem with user creation 4. Get help from Meta link (Oracle portal) 5. Google.
Issue Status: 1. New 2. WIP 3. Waiting for user response 4. Pending for additional information 5. Reject 6. Closed
14
IMPLEMENTATION & SUPPORT PROCESS
7. SUPPORTING
Details required raising SR / TAR: 1. Application 2. Application version 3. Database version 4. Issue description 5. Issue title 6. Platforms 7. Customer identification number 8. Contact information 9. Manager 10. Siviority
Tools used to raise service requests: 1. Remedy 2. Clarify 3. Lotus
15
IMPLEMENTATION & SUPPORT PROCESS
HOW TO RISE TO SERVICE REQUEST IN METALINK
Web site link: https://support.oracle.com Tabs in the window: Dash Board Knowledge Service requests
Go to Service Requests tab, there are 6 steps in SR logging 1. General Information 2. Product and Problem 3. Related Knowledge 4. Upload files 5. Problem Details 6. Review then submit SR
16
IMPLEMENTATION & SUPPORT PROCESS
I. GENERAL INFORMATION: Enter problem summary Enter Problem description Explain the steps you followed Enter the error message number if any Choose Support Identification number Fill using: Manual Entry
Go to Contact information: Enter SR contact name Choose contact method: update to SR / Email / Telephone number
Request Tracking: Request Language: English Say Next
17
IMPLEMENTATION & SUPPORT PROCESS
II. PRODUCT AND PROBLEMS:
Product: Product version: Product language: Platform: Platform version: Security level:
Oracle Payables 12.1.1 English Linux Oracle Linux 5 1/2/3/4
Data base version: 11.2.02 (11g)
Security levels: 1 2 3 4 Very big serious issue Production environment cannot run Big issue Server loss, operations can continue in restricted manner Minor issue Operations can run with work around General issue Does not impact operations
18
IMPLEMENTATION & SUPPORT PROCESS
If you choose security level 1, System will ask for the following questions: Does this issue occur in a customized application? Yes / No If your answer is Yes: Oracle wont give support If your answer is No we have to provide the below information: - Manager Name and Telephone number - Service request user name, phone number, Email and secondary contact
Choose problem category and Sub category from list of values
Say Next
19
IMPLEMENTATION & SUPPORT PROCESS
III. RELATED KNOWLEDGE:
In this step, system will suggest some suitable solutions to the above problem, if you found solution for the request you can stop the request, otherwise you can continue to raise service request
IV. UPLOAD FILES:
You can upload screen shots and any other supporting files. Click on Browse and then attach files. Click on Upload You can see message Upload completed Say Next
20
IMPLEMENTATION & SUPPORT PROCESS
V. PROBLEM DETAILS:
In this step we have to re produce all the details about the problem.
Answer all the below questions:
1. Instance name: 2. Type of system:
System ID or Server ID Test or Development No work around is
3. Describe any recent changes: No up gradation and patch application has been done 4. Describe any work around you are using to avoid this problem: possible. 5. Describe how this problem impact your business: We are unable to process payments to vendors
21
IMPLEMENTATION & SUPPORT PROCESS
6. If connection required to your system: Site name: http:conference.oracle.com Enter conference ID & Conference key Say Join Conference Tool bar will be open with computer monitor icon Place the cursor on monitor icon and share the desk top 7. Please upload screen shots: You can paste screen shots here Oracle people can log in to our system
through OWC (Oracle web Conference Session).
Say Next
22
IMPLEMENTATION & SUPPORT PROCESS
VI. REVIEW AND SUBMIT SR:
In this step you can view all the information you entered in the previous steps Review the information You can go back to previous screens and make changes
Say Submit SR number will be generated
Go to Service request tab to see the SR number
23
IMPLEMENTATION & SUPPORT PROCESS
SOME SUPPORTING ISSUES AND SOLUTIONS
S.NO 1 2 payment
ISSUE User not able to create accounting for Payment Batch System is not selecting any invoice
REASON / SOLUTION User not created accounting for invoice Invoice recorded with one payment method, for payment different payment method selected Settlement days entered in the payables options, we have to remove that There was bug in application, we have raised SR, oracle given patch, we have applied patch with the help of technical people BUG
3 4
User unable apply prepayment MRC while posting transferring data transactions not going to reporting SOB
We have created Budget journal, when inquiry not able to find balances
24
IMPLEMENTATION & SUPPORT PROCESS
6 Create accounting program in R 12 Receivables is ending with error We run the Validate application accounting definition program then it works fine
Implementation Work around:
Petty Cash: Create employee as petty cash supplier Create one bank account to Supplier Transfer funds from our internal bank account to Supplier bank account At the time of payment to employee, make payment from supplier bank
25
