Introduction

Fusion as the word suggests stand for Culmination / Mix / Combination.

In context of Oracle, Fusion is referred as Fusion Applications.

So Why Fusion Applications?

Before that let’s understand What is Fusion Applications?

Fusion Application is a new Oracle Product to cater to ERP Needs.

But we already have so many ERP Applications. Some of the most popularly used being EBS (E-Business Suite), PeopleSoft, JDEdwards to name a few. So why a new ERP application to cater to business needs. The answer is:

Fusion Applications is an attempt (and for that matter a very popular and widely accepted one) by Oracle. It takes the best features from EBS and PeopleSoft and does makes life simpler for Business Users and (Both Functional and Technical) Implementation Consultants. Let’s try to get into more details of the same. We would categorize this discussion into two broad categories namely:

1. Business Reasons (Details about why should Business adopt Fusion)

2. Functional Reasons (Details about why should Functional Consultant adopt Fusion)

3. Technical Reasons (Details about why should Technical Consultant adopt Fusion)

Business Reasons

1. Easy to use

2. Better Look and Feel

3. Better Functionality

4. Better User Experience

Functional Reasons

1. Configuration is simpler (Most configurations from ‘Setup and Maintenance’)

Most of the setups start with Manage% ( screenshot below)

2. Configuration is based on Train Stop Models (First Step guides you to second step and so on)

3. Allows What IF Scenarios (Manage Enterprise Structures, Allows Multiple Combination but Loads just one)

Below Screenshots gives details of creating Enterprise Structures (and then to view to Technical Summary Report). This would not get loaded but would be used for comparative analysis. Screenshots displaying what-if scenarios (ESC Setup Example).

Example of WHAT IF SCENARIO (Using Enterprise Structure Configurator)

Step 1: Manage Enterprise

Step 2: Manage Divisons

Step 3: Manage Legal Entities

Step 4: Create Business Units

Step 5: Manage business units

Step 6: Manage Reference Data Sets

STEP 7: Manage Business Unit Set Assignment

Step 8: Manage Location Reference Set

Interview Results

Management Reporting Structure

Technical Summary Report

Click on Download Technical Summary Report to Get PDF Report

Report Screenshots

We can configure multiple such Enterprise Values and compare before loading one. So we can have WHAT IF scenarios. This feature is not supported in older Legacy Systems (EBS / PPLSOFT).

Technical Reasons

Broad Responsibilities of any Technical Resource on any ERP Implementations are:

1. Inbound Integration (HDL from Release 10 makes life simpler, data-load on button click)

2. Reporting via (BIP / OTBI)

3. Outbound Integration (HCM Extracts)

All the above three are very easy to implement in Fusion HCM.

So, It is for all the above stated reasons we should have Fusion Applications. Happy Adoption……. Cheers……

Ashish Harbhajanka

Add comment