2. • Existing Third party reporting applications are
often complicated because of integrations and
type of data.
• Multiple Tools / layers for reporting.
• Data is often duplicated at different stages.
• Existing FSG, Oracle EBS reports and
Discoverer(resides in ERP database) are different
ways of Oracle EBS reporting but only good for a
quick transactional reporting.
Current State of Integrations or
3rd party EBS reporting
3. THINGS TO CONSIDER FOR A REPORTING SOLUTION
• Period closing and Reconciliation reports
• Future Reporting Handoff or Application switch
• Post Period Closing Reports for Analytics
• Master data and transaction data extract design
from Source system
• Ease of Aggregation and Drill down in reporting
tool.
4. DESIGN / ARCHITECTURE
Physical layer
Business Area
Logical Layer
Presentation Later Dash boad /
Reporting
Finance
AP AR GL CM
MasterData
Customers Suppliers GL Objects Employees
HR
HR files
Invoices
Credit memos
Payments
Suppliers
Supplier Sites
Customers
Transactions
Property
manager
Projects
Purchase
orders
Adjustments
Asset
transactions
Customer Sites
Costcenters
Companies
Accounts
Locations
Banks
Users
Lookups
Tax codes
Receipts
Above diagram is just an overview, detailed extract and fields has to be
documented.
5. SOLUTION
• Multiple Data Extraction programs from EBS based on Business Area -> Categories and Master
Data.
• Similar process for all modules in EBS.
• Programs can be called from a Business Event for master data changes.
• One Historical Run in the beginning.
• Scheduled runs will be delta extracts, since file sizes will be small and frequent runs can be
initiated.