EBS Vs Fusion Org Structure
Oracle E-Business Suite Application and Oracle Fusion Applications have a few key functional differences, such as Middleware concepts, Fusion Enterprise Structure and org structure that is detailed below. Oracle Fusion Applications have been designed to ensure your enterprise meet legal and management objectives
Fusion Enterprise Structure:
1. Enterprise
2. Division
3. Primary Ledger
4. Legal Entity
5. Business Unit
6. Inventory Org
Global Enterprise Model: Only one Enterprise (Business Group) is allowed in Oracle Fusion Application instance
· Divisions are introduced in the Business structure, which will be reporting to the Enterprise. These are logical segregation of the business/verticals, it’s an optional element in the model
· New enhancements in the Legal Entity (LE) and Primary Ledger are the heart of the structure — they own the whole liabilities and Assets of an organization
· Operating unit is replaced with BU (Business Unit) and which is more powerful in Oracle Fusion
· MOAC is replaced with Shared Service Center, one BU works on multiple Legal Entity
· Inventory orgs report to BU, LE and Ledger in Oracle Fusion
· Under the Enterprise, we can maintain LDG (Legislative Data Groups), which is similar or equal to BG in EBS.
Technical Differences :
IDM/OIM (Identity Manager/Oracle Identity Manager): Used for managing users’ information such as user privileges, access and more.
• APM (Authorization Policy Manager): In Fusion Applications, Menus (EBS) are replaced with the roles. APM is used to manage these roles.
• BPM (Business Process Management): AME in EBS is replaced with the BPM. This is used to manage the workflow and approval related information. We can also define approval rules in BPM based on the business requirement.
• UCM (Universal Content Management): Used for data imports and exports into Fusion i.e. Data Conversions of any legacy data should be first loaded into the UCM followed into the Fusion tables.
• FBDI (File Based Data Import): This is the template used for loading the data into UCM.
• SOA (Service Oriented Architecture): This is integration with various third-party systems — it consists of connectors, web-services, etc.
• BPEL (Business Process Execution Language) Focuses on customizing the workflow processes and more.
Oracle E-Business Suite Application and Oracle Fusion Applications have a few key functional differences, such as Middleware concepts, Fusion Enterprise Structure and org structure that is detailed below. Oracle Fusion Applications have been designed to ensure your enterprise meet legal and management objectives
Fusion Enterprise Structure:
1. Enterprise
2. Division
3. Primary Ledger
4. Legal Entity
5. Business Unit
6. Inventory Org
Global Enterprise Model: Only one Enterprise (Business Group) is allowed in Oracle Fusion Application instance
· Divisions are introduced in the Business structure, which will be reporting to the Enterprise. These are logical segregation of the business/verticals, it’s an optional element in the model
· New enhancements in the Legal Entity (LE) and Primary Ledger are the heart of the structure — they own the whole liabilities and Assets of an organization
· Operating unit is replaced with BU (Business Unit) and which is more powerful in Oracle Fusion
· MOAC is replaced with Shared Service Center, one BU works on multiple Legal Entity
· Inventory orgs report to BU, LE and Ledger in Oracle Fusion
· Under the Enterprise, we can maintain LDG (Legislative Data Groups), which is similar or equal to BG in EBS.
Technical Differences :
IDM/OIM (Identity Manager/Oracle Identity Manager): Used for managing users’ information such as user privileges, access and more.
• APM (Authorization Policy Manager): In Fusion Applications, Menus (EBS) are replaced with the roles. APM is used to manage these roles.
• BPM (Business Process Management): AME in EBS is replaced with the BPM. This is used to manage the workflow and approval related information. We can also define approval rules in BPM based on the business requirement.
• UCM (Universal Content Management): Used for data imports and exports into Fusion i.e. Data Conversions of any legacy data should be first loaded into the UCM followed into the Fusion tables.
• FBDI (File Based Data Import): This is the template used for loading the data into UCM.
• SOA (Service Oriented Architecture): This is integration with various third-party systems — it consists of connectors, web-services, etc.
• BPEL (Business Process Execution Language) Focuses on customizing the workflow processes and more.
