Once a Client purchase the Licenses of Oracle E-Business Suite, they will be delivered a Standard Application Package. In the Standard Application Package (Production Instance), they need to configure their Business Requirements as per the Standard Business Procedures and their business practices. As a summary Implementation is a process of configuring the application where their business needs is working and their accounting structure is deriving the necessary accounting entries and system is generating the Reporting as per the daily business needs, statutory requirements and MIS reporting is generated in the Oracle E-Business Suite system

Vanilla Implementation Approach

  Vanilla Implementation is Configure the Standard Application as per the Standard Business Process without customizing any of the components. The clients are very much flexible on utilization of the software features and go accordingly as per the standards available in the E-Business Suite. So that they will be benefits on Cost, Implementation time frame is reduced, Maximum utilization of application features and minimum training needs. It’s a good approach for the customers to start up there ERP practice with this implementation on the initial period, so that by using the application for a period of time course of 6 Months to 1 Year for better understanding the Oracle Application functionalities and features. Later if required if any of the process needs to changed from the standard procedure they can plan for the Customize Components where ever is required. In vanilla Implementation we can also do a little bit of customization as a Cosmetic Changes.

  Process Customization Approach

 After a deep study of the business process and their requirements, if the client wants to change Minor or Major application standard features, then they can do a Customization in the E-Business Suite. Basically if there business approach needs some more additional functionalities and more reporting needs which is not delivered In the standard application as per the client required formats, then the application will be modified, Customized and extended.
Each Company has its own Implementation strategy and process on how to Start and End up with a successful implementation which is derived from the AIM standards. As per my Understanding the Implementation is divided into Different Phases.

  Customer Activity

•   Procurement of E-Business Suite Licenses from Oracle or Oracle Partners
•   Get the Customer Support Identification Number (CSI) Number
•   Identify the Implementation Partners or Team

•    Identify Business Process Definition of Procure to Pay and Order to Cash Process
•   Indentify the Organization Structure of the Customer and which Operating Units comes under Oracle E-Business Suite Practice

•   One Organization operates in One Country
•   One Organization Operates in Multiple Country
•   Multiple Organization operates in One Country
•   Multiple Organization operates in Multiple Country

As an Implementation process, where they required E-Business Suite Practice, so that plan and provide the Oracle Multi Organization Standards

 Phase II - Project Manager / Delivery Manager / Senior Functional Team / Customer Managers

•  Business Requirement Definition – Discuss and get Sign-Off from the Customer on what is expected from Oracle E-Business Suite as Deliverables. It good if all the aspects are discussed in detail to under the customer needs

•   Requirement Gathering on Business Process Model
•   Requirement Gathering on Financials Reporting
•   Requirement Gathering on Day to Day Task and Daily Reporting
•   ;Requirement Gathering on Auditing and Statutory Taxation Reporting
•   Requirement Gathering on Management Information System (MIS) Reporting
•   Fix a Time Line for the Deliverables and the Team who needs to Sing-off and Freeze the Requirements
•   Data Conversion - Data Migration (If any data’s needs to be imported to Oracle E-Business suite from Legacy System)

  Phase III – Implementation Team / Functional Consultants / Associate Consultants / Technical Team

•    Configure the CRP1 Instance mapping the applications as per the requirements
•    Identify the GAP between Application and Business Model
•    If any GAP is Analyzed Plan for the Customization Components (if Any GAP)

  Phase IV – Technical Team and DBA Team

•    Build and Customization the Application for Indentified GAP between Application and Business
•    Data Interface and Data Conversion – Legacy System Data’s
•    Patching and Cloning - Clone the CRP1 and CRP2 Instance to a GOLD and UAT Instance
•    Plan for the Required Hardware and Software Supports
•    Prepare a Plan for Cloning / Back Up / Security Issues / Connectivity Issues
•    Prepare for Delivery to the Customers
•    Performance Testing by Implementation Team

  Phase V - Implementation Team and Customer Team

•   User Acceptance Testing - Business Users Test the application as per the Business Needs are configured as per the requirements sign-off Document
•   Minor Change Requests - Modify the Setup Configuration in the UAT and GOLD as per the Business Team flexibility in case of any Minor Modification
•   Deliverables - Sign Off from the Clients on the Business Process Models
•   User Training as Per the Roles and Responsibility
•   Perform Scheduled Programs, configure Workflows and Alerts on the Exceptional Data's to the Business Team
•   Documentation to be Delivered to the Clients
•   Deliverables of the Financials Reporting for Daily Basis
•   Deliverables of the Taxation Reporting, Reconciliation Process and Statutory Reporting
•   Deliverables of the Month End Closure Reporting and Yearly Closure Procedures
•   UPK - Learning Management System Online Availability with Required Process Documentation
•   Indentify the Module Features to maximum utilization of the Application
•   Configure the Production Sever with the Required setups and Data’s - Production Migration - GO-Live