From EBS Forms to Oracle Redwood: The Evolution of Oracle ERP User Experience
From EBS Forms to Oracle Redwood: The Evolution of Oracle ERP User Experience
From Oracle Forms and OAF to Fusion Cloud, Visual Builder and Redwood — explore how Oracle enterprise application experiences are evolving toward modern, role-based and intelligent user experiences.
Introduction
For many years, Oracle ERP users interacted with enterprise applications through technologies such as Oracle Forms and Oracle Application Framework (OAF). These technologies provided powerful capabilities for implementing complex enterprise processes and business rules.
But enterprise users have changed.
Modern users expect applications to be intuitive, responsive, role-oriented and increasingly intelligent.
Is Oracle Redwood simply a new user interface, or does it represent a fundamental change in how we design and extend enterprise applications?
The answer is much closer to the second.
Redwood represents a broader evolution of Oracle's application experience, bringing together modern UX principles, personalization, extensibility, contextual experiences and intelligent capabilities.
The Evolution of Oracle ERP User Experience
Let's look at the journey from traditional Oracle EBS interfaces to the modern Redwood experience.
1. Oracle Forms
The foundation of Oracle E-Business Suite. Highly powerful, transaction-oriented and deeply integrated with Oracle Database.
2. Oracle Application Framework (OAF)
Web-based enterprise applications brought browser-based interaction, personalization and web application development into the EBS ecosystem.
3. Oracle Fusion Cloud Applications
Oracle's cloud application architecture introduced a new model for ERP, HCM, SCM and other enterprise applications.
4. Visual Builder and Extensibility
Modern extension technologies enabled developers to build experiences around Oracle Cloud applications without relying on traditional core application customization.
5. Oracle Redwood
A modern experience focused on consistency, usability, role-based interaction, personalization and intelligent workflows.
Oracle ERP UX Evolution at a Glance
EBS
Web UI
Cloud
Extensions
Modern UX
What Makes Redwood Different?
Role-Based
The experience can focus on what is relevant to a specific business role instead of exposing unnecessary functionality.
Responsive
Modern enterprise experiences need to work naturally across different screen sizes and devices.
Extensible
Modern Oracle Cloud applications provide supported mechanisms for extending functionality without heavily modifying the core application.
Intelligent
AI and automation can increasingly become part of the application experience rather than separate tools.
Contextual
Users can increasingly receive information and actions based on the context of their current business process.
Consistent
A common design language helps provide a consistent experience across Oracle applications.
Oracle Forms vs Redwood
| Area | Traditional Forms | Redwood Experience |
|---|---|---|
| User Experience | Transaction / form oriented | Modern task and role oriented |
| Navigation | Menu driven | Context and task driven |
| Customization | Forms Personalization / custom forms | Supported cloud extensibility mechanisms |
| Mobile Experience | Limited | Responsive modern experience |
| Intelligence | Usually custom-built | Increasingly embedded into the experience |
| Architecture | Database-centric | Cloud application and service oriented |
What Does Redwood Mean for Oracle Technical Consultants?
This is where the transition becomes particularly interesting for developers who have spent years working with Oracle EBS.
Traditional EBS Skill Set
- Oracle Forms
- OAF
- PL/SQL
- Concurrent Programs
- Oracle Workflow
- Forms Personalization
- Database APIs
- Interface Tables
Modern Oracle Skill Set
- Oracle Fusion Cloud
- REST APIs
- Visual Builder
- Oracle Integration
- Oracle APEX
- Cloud Security
- Extensibility
- AI and Automation
The New Technical Consultant
The role is evolving from simply implementing technical changes to designing the correct architecture for the business requirement.
Redwood and Oracle Cloud Extensibility
One of the biggest architectural changes for EBS developers moving to Oracle Cloud is the way customization and extensibility are approached.
Redwood + Oracle APEX
Oracle APEX can play an interesting role alongside Fusion applications. Instead of trying to force every custom requirement into the core ERP, APEX can be used to build focused applications, dashboards and workflows.
Redwood + Generative AI
Perhaps the most exciting direction is the combination of modern enterprise UX and artificial intelligence.
Traditional enterprise interaction often looks like this:
An intelligent experience aims to reduce those steps:
Example
Imagine a procurement user receiving an intelligent notification:
The user does not need to manually search multiple screens. The system brings the relevant business context to the user.
A Future Intelligent ERP Experience
What Should Oracle Technical Consultants Learn?
- Fusion architecture
- ERP business processes
- Security model
- Cloud application concepts
- REST APIs
- Visual Builder
- JavaScript fundamentals
- Oracle APEX
- Oracle Integration
- REST and SOAP
- Authentication
- Error handling and monitoring
- Generative AI
- RAG
- AI agents
- Enterprise AI architecture
Think Architecture First
A modern Oracle technical consultant should increasingly approach requirements through architecture rather than immediately writing code.
Business Requirement
|
v
Can Fusion Configuration Solve It?
|
Yes
|
v
Configuration
|
No
|
v
Is Supported Extension Available?
|
Yes
|
v
Visual Builder / APIs / Extension
|
No
|
v
APEX / Integration / External Service
|
v
AI / Automation Opportunity?
What Happens to Oracle Forms Developers?
The transition to Redwood does not mean that years of Oracle Forms and EBS experience suddenly become irrelevant.
In fact, understanding enterprise business processes, Oracle Database, PL/SQL, transaction processing and ERP architecture remains extremely valuable.
Business Knowledge
Deep understanding of ERP processes remains a major advantage.
Technical Foundation
PL/SQL, APIs, integrations and database knowledge continue to matter.
New Skills
Add Cloud, APIs, APEX, extensibility, UX and AI to the existing foundation.
Key Takeaways
- Redwood is more than a visual redesign.
- Oracle ERP experiences are moving toward role-based and contextual interactions.
- Traditional EBS expertise remains highly valuable.
- Technical consultants need to understand supported cloud extensibility.
- APEX can complement enterprise cloud applications for custom solutions.
- AI can transform enterprise applications from transactional systems into intelligent assistants.
- The future consultant needs both ERP domain expertise and modern cloud skills.
Conclusion
Oracle ERP has travelled a remarkable journey—from Oracle Forms and OAF to Fusion Cloud and now the Redwood experience.
But this isn't simply a journey from one UI technology to another. It represents a broader evolution in the way enterprise applications are designed, extended and consumed.
Forms → Web → Cloud → Responsive UX → Role-Based Experience → Intelligent Experience → AI-Assisted Enterprise
For Oracle technical consultants, this creates a tremendous opportunity. The people who understand both the traditional Oracle ERP foundation and modern cloud technologies can play a critical role in this transition.
The future consultant understands the business process, cloud architecture, API layer, user experience and intelligence layer that connect everything together.
What's Next?
The next step in this journey is to explore how Redwood can be extended using APIs, Visual Builder, Oracle APEX and AI.
Part 2: Oracle Redwood for Technical Consultants — Extensibility, APIs, APEX and Architecture
Comments
Post a Comment