EPM Module
1.Planning
2.Narrative Reporting
3.Financial Close and Consolidation
4.Enterprise Data Management
EDM Training:
- Waklrhtough of the EDM Interface (Home page, user preferences, Views, Requests, etc)
- EDM application types and synchronization of metadata to the applications
- Using Requests to make changes to the metadata
- Governance of the COA using request and approval workflows
- Using Pipeline to automate the synchronization
- Nofitifications
- Security
Customer point of view:
- A solution configured specifically with customer metadata
- Single Sign-on
- An application with access to customer users
- Application types that are not in scope
Challenges we can solve with EDM
- We need help from IT to determine why we cannot compare between Budget and Actuals
- I can't define what this means for the organization, as it means something different access groups
- This hierarchy does not fulfil my reporting needs
- 'What If' we reorganize the departments/employees?
- I don't know who requested or approved this change in the Chart of Accounts
- I can't compare number across geographies
- Which team/system is reporting the correct numbers?
Business Benefits:
Transformational Changes
We need to map and track changes through the transformation.
- EDM (Load, Compare, Map, Validate, Publish)
- Chart of Accounts -> EDM ->Final, Migrated Chart of Accounts
- Other Chart of Accounts -> EDM ->Final, Migrated Chart of Accounts
- EDM -> Data Maps
- Chart of Accounts -> DataMaps ->Final, Migrated Chart of Accounts
- Other Chart of Accounts -> DataMaps ->Final, Migrated Chart of Accounts
Benefits
- Multi-user collaboration
- Change Visualization
- Completed audit trails
- Embedded governance
- Continuous compares
- Leverage Hierarchies
Ongoing Routine Changes
- Change Request: I need a new set of accounts to track transactions for a new product
- Change Request Validated _> EDMC->Immediate feedback from governance process
- EDMC-> Consolidation, Planning, Reporting, Supply Chain, HCM, Fusion GL, PSFT
- For both Analytical systems and Transactional Systems
Benefits:
- Enterprise Data Aligned
- Trust in numbers
- Decentralized Input
- Centralized Management
- Reduced Errors
- Secure & Audited Process
Overview
EDM is system that manages and governs structural changes across the enterprise to give you a consistent view across Oracle and non-Oracle applications within a hybrid, multi-cloud environment.
ENHANCED COLLABORATION
Centralizes data management, enabling teams to share and collaborate on data changes effectively.
ENTERPRISE DATA CONSISTENCY & ACCURACY
Centralized and systematic approach to managing, governing and ensuring the accuracy and consistency of enterprise data (e.g., Account, Entity, Company, ETC.) across the organization
IMPROVED DATA GOVERNANCE
Facilitates better data stewardship, compliance and adherence to regulatory requirements
OPERATIONAL EFFICIENCY
Automates data management processes, reducing manual effort and minimizing errors visa subscriptions and converters
STREAMLINED DATA INTEGRATION
Simplifies integration with other enterprise systems, reducing complexity and time.
Metadata Synchronization Process
EDM
Account Maintenance View
GL Viewpoint->GL
Planning Viewpoint->Planning
FCCS Viewpoint->FCCS
Application Foundation
Application Types
Register application types for commonly-used external applications, ensuring conformity with minimal configuration, such as the Planning application type. It also provides a Universal application type for customizable configurations that are not out-of-the-box.
E-Business Suite General Ledger
FCCS
FreeForm
Planning Modules
Univeral
Enterprise Profitability and Cost Management
Financials Cloud General Ledger
Planning
Tax Reporting
Users
Enterprise Data Management Cloud Service - Application Adaptors
- Packaged Cloud App Integration with an open interface
- Two types of application adapters are available: CUSTOM and OUT OF THE BOX.
- Out of the box application adapters are intended to delivers packaged integration and predefined functionality.
- Custom adapter is intended to integrate with any application, on-premises or in the cloud, Oracle or non-Oracle.
Application Type Out of the Box Custom
Oracle Fusion GL Yes
Oracle Planning & Budgeting Yes
Oracle FCCS Yes
Universal Application Yes
Data Management
Views
Views gives you a collection of lists and/or hierarchies for a particular context or activity, such as Company maintenance.
Views consist of one or more viewpoints where you can update data.
Entity Maintenance
Requests
All changes to data are made by using requests. Requests can be user-generated or system-generated by using subscriptions, and they can occur across hierarchies within a single application or across applications depending on how you structure the view in which the request is made.
Validations
Validations in Oracle EDM involve applying rules and checks to ensure data quality, consistency, and compliance within managed data elements or hierarchies.
Predefined Validations:
Created automatically when you register an application, and they enforce the requirements for the external system based on the application type.
Example of Predefined Validations (for GL Account dimension)
- Duplicate (Shared Nodes)
- Maximum Depth Check
- Maximum Length Node Name Text/Numeric
- Minimum /Maximum Node Name
Custom Validations
User-defined rules created by using custom business logic to enforce specific business requirements and data quality standards that are not covered by predefined validations. These validations are tailored to the unique needs of the organization.
Subscriptions
Subscriptions enable you to share data between viewpoints by subscribing a target viewpoint to a source viewpoint.
When an update is made to the source viewpoint, a request is automatically generated to make the same change in the target viewpoint.
General Ledger View (Source)
Chart of Accounts Viewpoint
Source Request
Target
Request#1 -> Subscription #1 (Financial Close view (target #1), FM Chart of Accounts Viewpoint)
Request Assignee #1
Target
Request#2 -> Subscription #2 (Planning view (target #2), Planning Chart of Accounts Viewpoint)
Request Assignee #2
Target
Request#3 -> Subscription #3 (Enterprise Planning view (target #3), Enterprise Planning Chart of Accounts Viewpoint)
Request Assignee #3
Audit
Audits enable you to view both transactional changes to data and metadata changes over time.
Application Foundation
Dimensions
Dimensions are fundamental data structures that represent categories or grouping of data. They are used to organized and manage data hierarchies and relationships within the application.
Properties
Properties are attributes assigned to dimension members that provide additional context and metadata, such as descriptions, start/end dates, or custom fields. They help in defining and managing the characteristics and behaviors of data elements within the application.
Examples of Predefined GL Properties
Property Level
Account Type Node
Allow Budgeting Node
Allow Posting Node
Enabled Node
End Date Node
Financial Category Node
Reconcile Node
Start Date Node
Summary Node
Third Party Control Account Node
Tree Label Relationship
Examples of Predefined Planning Properties
Property Level
Connection:
Application connections enable you to directly import and export data to external applications through seamless integration with other Oracle modules
Governance
Key Features & Functionalites
Security
Application Setup:
Hierarchy Management
- Organize and maintain data hierarchies in one platform
- Manage multiple tree versions
Data Chain:
Node Type->Hierarchy Set-> Node Set-> View Point
Data object: Node Types
Description: The nodes belong to the following node types: The employee nodes are contained by the Employees node type.
The department nodes are contained by the Departments node type.
Example: Employees: Emily, Olivia, Bob, Mary, Robert, Sam, Jack, Gabriel
Departments: Finance, Marketing, Analytics
Data object: Hierarchy Set:
Description: Defines the parent-child relationships as follows: Departments nodes can have child Employees nodes.
Employees nodes cannot have child nodes. The hierarchy set also defines the child Employees nodes of the Department nodes.
Example: Employees by Departments
Analytics: Jack, Emily, Mary
Marketing: Sam, Robert, Olivia
Finance: Bob, Gabriel
Data object: Node Set:
Description: Includes the Analytics and Finance Departments' hierarchies. The hierarchy set's Marketing hierarchy is excluded.
Example: Analytics and Finance Employees
Analytics: Jack, Emily, Mary
Finance: Bob, Gabriel
Data object: View Point
Description: Displays the nodes specified in the node set
Example:
Example: Analytics and Finance Employees
Analytics: Jack, Emily, Mary
Finance: Bob, Gabriel
