Introduction
Data extraction plays an important role in Oracle Fusion Cloud implementations. Whether the requirement involves enterprise reporting, downstream analytics, data integration, or external applications, organizations need a reliable way to retrieve business information without disrupting transactional operations.
Traditionally, Oracle Fusion Cloud customers have used tools such as BI Cloud Connector (BICC) and BI Publisher to address different extraction requirements.
Oracle is now introducing a different architecture for application data extraction, built around a dedicated read-only data store in Oracle Autonomous Data Warehouse (ADW).
The change is significant because extraction workloads no longer need to run directly against the transactional application instance. Instead, they operate against a replicated data store that is synchronized with Fusion Cloud application data in near real time.
Along with this architectural improvement, Oracle provides a Redwood-based interface for defining, scheduling, and monitoring extracts.
This article explores how the framework works, its key capabilities, implementation requirements, and the considerations that matter when planning new or existing Oracle Fusion Cloud data integrations.
1. Understanding the New Data Extraction Architecture
The central idea behind the new framework is to separate data extraction workloads from the transactional environment.
Oracle Fusion Cloud applications continuously support operational activities such as creating transactions, maintaining business records, running validations, and processing financial information.
Data extraction adds another workload to the environment, particularly when organizations need large volumes of information for external reporting or integration.
The new framework addresses this by automatically replicating application data into a dedicated, read-only Autonomous Data Warehouse data store.
Extraction requests are processed against this replicated environment rather than directly against the transactional application instance.
The architecture can be understood as follows:
Fusion Cloud Transactional Data → Near Real-Time Replication → Read-Only Autonomous Data Warehouse → Business Views → Data Extraction
This separation helps reduce the effect of extraction activity on core application performance.
It also provides a foundation for more reliable extraction processing.
Why the Architecture Matters
The most important improvement is not simply a redesigned extraction page.
It is the change in where the extraction workload runs.
By moving extraction activity to a replicated read-only environment, Oracle can support reporting and integration requirements while reducing the impact on operational processing.
For organizations with significant extraction requirements, this architectural separation is particularly relevant.
However, near real-time replication should not be interpreted as instantaneous synchronization. Extracted information reflects the data available in the replicated store when the extraction is performed.
2. Business Views Simplify Data Access
Another important part of the framework is the introduction of predefined business views.
Technical extraction solutions often require an understanding of the underlying application data model, including the relationships between tables, views, and business entities.
The new framework provides a more functional approach by exposing predefined business objects and their attributes.
Users can select the business information required for extraction without needing to work directly with the full complexity of the underlying database structures.
This makes the extraction definition process more accessible to teams working across functional and technical responsibilities.
Business-Oriented Extraction Design
The business view approach provides a logical layer between the application data model and the extraction definition.
Users can select one or more available business views, choose the required attributes, and define applicable filters.
This is useful when building extracts for reporting platforms, integration solutions, or downstream analytical applications.
The framework is intended to simplify access to supported business information rather than expose every underlying database object.
That distinction is important when evaluating whether a particular extraction requirement can be implemented using the new functionality.
3. Defining Extracts Through the Redwood Interface
Oracle provides a Redwood-based user experience for configuring and monitoring data extracts.
The navigation is:
Tools → Data Extraction
The interface allows users to define extraction requirements using available business objects.
The main configuration activities include selecting business views, choosing attributes, and applying filters.
Selecting Business Objects
Users can include one or more supported business views in an extraction definition.
This provides flexibility when the required information is represented across different available business objects.
Selecting Attributes and Filters
After identifying the business objects, users can select the attributes required in the output and define filter criteria.
This allows the extraction to focus on relevant business information instead of retrieving unnecessary data.
From a solution design perspective, selecting only the required attributes and applying appropriate filters remains a useful practice.
It helps keep the extraction definition aligned with the downstream business requirement.
4. Full and Incremental Extraction Support
The new framework supports both full and incremental extracts.
These options address different integration and reporting needs.
| Extraction Type | Purpose |
|---|---|
| Full Extract | Retrieves the applicable dataset based on the extraction definition |
| Incremental Extract | Retrieves the applicable incremental data according to the framework's supported extraction behavior |
Full Extracts
A full extract is useful when the consuming system requires a complete dataset based on the selected business objects and filters.
This may be relevant during initial data loads or when a downstream solution needs a refreshed dataset.
Incremental Extracts
Incremental extraction is useful for recurring data movement where the consuming application needs changes rather than repeatedly retrieving the entire dataset.
This can reduce unnecessary data transfer and support more efficient integration designs.
The exact incremental behavior should be validated against the supported business objects and Oracle's framework documentation before finalizing an integration architecture.
The availability of both extraction types gives implementation teams flexibility when designing data movement requirements.
5. On-Demand and Scheduled Extraction
The framework supports two execution approaches:
On-demand execution allows users to initiate an extract when the information is required.
Scheduled execution supports recurring extraction requirements without requiring a user to manually initiate every run.
These capabilities are relevant for both operational reporting and downstream integration processes.
An organization may require extracts at defined intervals to support a reporting platform or an external application.
Scheduled execution allows the extraction to be incorporated into a recurring data delivery process.
On-demand execution remains useful for ad hoc requirements or controlled validation activities.
The appropriate execution approach depends on the business requirement, expected data availability, and the downstream processing schedule.
6. Monitoring Extraction Status
Defining and scheduling extracts is only part of the extraction lifecycle.
Implementation teams also need visibility into execution results.
The new Data Extraction workspace supports monitoring and reviewing extract statuses.
This provides a centralized way to follow extraction activity and determine whether the relevant runs have completed.
From an operational perspective, monitoring is important because downstream systems often depend on the availability of extracted files.
A failed or incomplete extract may affect subsequent reporting or integration activities.
The ability to review execution status within the extraction interface helps support routine monitoring and troubleshooting.
7. Why Read-Only Replication Is Important
The introduction of a dedicated replicated data store changes the relationship between transactional processing and data extraction.
There are three particularly important aspects.
Reduced Impact on Transactional Processing
Extraction requests are processed against the read-only replicated data store rather than directly against the transactional instance.
This reduces the need for extraction workloads to compete with operational processing on the source environment.
Improved Extraction Reliability
A dedicated environment for extraction provides a more suitable foundation for handling extraction workloads.
This can be particularly beneficial for organizations that regularly move application data into external systems.
Near Real-Time Data Availability
The replicated environment is synchronized with Fusion Cloud application data in near real time.
This helps support reporting and integration requirements that need relatively current information.
However, implementation teams should distinguish near real-time replication from real-time transactional access.
Where strict data freshness requirements exist, replication timing and extraction execution behavior should be considered during solution design.
8. Enabling the Data Extraction Framework
The feature requires configuration before users can access the new extraction experience.
Step 1: Enable the Feature Through Opt In
Navigate to the Opt In user interface under the Financials offering.
Enable the feature:
Redwood: Extract Application Data from a Read-Only Data Store Using a Redwood Page
Ensure that the parent feature in the hierarchy is also enabled.
Although the feature is enabled through an offering, it can be used to extract data from any available product family, regardless of which offering was used for enablement.
This is important for implementations spanning multiple Oracle Fusion Cloud modules.
Step 2: Configure the Required Profile Option
Set the following profile option to Yes:
ORA_ASE_SAS_INTEGRATION_ENABLED
Profile option name:
Enable Security Console External Application Integration
If the profile option is already set to Yes, no change is required.
Step 3: Assign the Required Security Duties
Users must be assigned the appropriate duties to access the Data Extraction functionality.
The required duties are described in the security section below.
Custom roles involved in the configuration must have Permission Groups enabled.
Step 4: Provide Extract File Access
To allow users to view and download extracted files, assign the following role:
OBIA_EXTRACTTRANSFORMLOAD_RWD
Role name:
Upload and download data from on-premise system to cloud system
This role is required in addition to the duties that provide access to the extraction functionality.
Environment Readiness
Oracle advises customers with environment readiness or enablement questions to have their help desk contact Oracle Support.
This is worth considering before enabling the functionality in an environment where readiness has not been confirmed.
9. Security Roles and Access Requirements
Security configuration is an important part of implementing the new Data Extraction framework.
Oracle identifies three duties required for access.
| Duty | Role Code |
|---|---|
| Data Extraction Tasks Management Duty | ORA_RCS_EXTRACT_SPECIALIST_DUTY |
| Data Extraction Services Management Duty | ORA_DR_RCS_EXECUTE_EXTRACT |
| Data Extraction Services Integration Access Duty | ORA_DR_RCS_EXTRACT_INTEGRATION |
These duties must be incorporated into the applicable user job roles.
Custom roles must have Permission Groups enabled.
In addition, users who need to view or download extract files require:
OBIA_EXTRACTTRANSFORMLOAD_RWD
From an implementation perspective, it is useful to distinguish between access to define and execute extracts and access to retrieve the resulting files.
Both areas should be included in security validation.
A user may have access to the Data Extraction workspace but still require the appropriate file access role to complete the intended workflow.
10. Moving from BICC to the New Framework
One of the most significant considerations is Oracle's direction for future data extraction development.
Oracle recommends the new framework for all new extraction use cases.
The framework is also expected to eventually replace data extraction using BICC and BI Publisher.
This makes it important for organizations to evaluate the new approach when designing future integrations.
However, migrating an existing extraction solution requires more than recreating the same selection criteria in a different interface.
Business Object Mapping
BICC business objects do not necessarily have a direct one-to-one equivalent in the new framework.
Existing extraction designs must therefore be reviewed to identify the corresponding business objects and attributes.
Some extraction definitions may require redesign.
Oracle provides specific guidance for this activity in its Map BICC Data to Business Object Data documentation.
Existing Integrations
For existing BICC-based integrations, organizations should evaluate the supported business objects, attribute availability, filters, and incremental extraction behavior before planning a migration.
The new framework represents Oracle's recommended direction, but that does not mean every existing extract can be moved without changes.
A structured assessment is important to avoid assumptions about functional equivalence.
New Integration Requirements
For new extraction use cases, the new framework should be considered as the preferred starting point, subject to feature availability and supported data requirements.
This aligns with Oracle's published direction and can help reduce future dependency on extraction approaches that are expected to be replaced.
11. Current Limitations and Design Considerations
The new extraction framework offers important improvements, but there are limitations that implementation teams should understand.
Descriptive Flexfields Are Not Currently Included
Extensible attributes, including Descriptive Flexfields (DFFs), are not currently included in the predefined business views.
This is an important consideration for Oracle Fusion Cloud implementations that rely heavily on custom attributes.
Before selecting the framework for an extraction requirement, consultants should confirm that the necessary business information is available through the supported views.
Requirements involving DFF attributes may not currently be fully supported through this approach.
English Language Support
The current extraction experience supports English only.
Organizations operating in multilingual environments should consider this limitation when planning user access and operational processes.
No Guaranteed One-to-One BICC Mapping
Existing BICC extraction definitions cannot be assumed to map directly to the new business object model.
Business object and attribute mapping should be reviewed as part of any migration assessment.
Near Real-Time Does Not Mean Immediate
The replicated data store is synchronized in near real time.
For integrations requiring strict synchronization with the latest transactional changes, the expected data freshness should be validated.
Feature Readiness
Environment readiness should be confirmed before implementation.
Oracle Support can assist with readiness-related questions through the organization's help desk.
12. What This Means for Oracle Fusion Cloud Consultants
For functional and technical consultants, the new Data Extraction framework introduces several considerations beyond the extraction interface itself.
Extraction Architecture Becomes a Design Decision
The availability of a replicated read-only data store creates a different option for moving data out of Fusion Cloud.
Consultants should evaluate this architecture when defining integration and reporting solutions.
Business Object Understanding Remains Important
Although the framework simplifies access through predefined business views, consultants still need to understand the business information required by downstream applications.
Selecting the correct objects, attributes, and filters remains essential.
Existing Extraction Designs Need Assessment
Organizations with established BICC integrations should review their current extraction inventory and identify potential migration considerations.
This includes understanding which data elements are available through the new business views.
Security Must Be Validated End to End
Access to the extraction workspace and access to the resulting files are separate considerations.
Both should be validated during configuration and testing.
Functional Coverage Determines Suitability
The absence of extensible attributes from predefined business views may affect some extraction requirements.
Consultants should assess supported data coverage before committing to a particular integration design.
13. Business Benefits of the New Framework
The new Data Extraction functionality provides several advantages for organizations using Oracle Fusion Cloud Applications.
| Business Benefit | Functional Significance |
|---|---|
| Reduced transactional impact | Extraction workloads run against replicated read-only data |
| Improved extraction performance | Dedicated extraction architecture supports more efficient processing |
| Improved reliability | Extraction activity is separated from core transactional workloads |
| Simplified data access | Predefined business views reduce underlying data model complexity |
| Flexible execution | Supports full, incremental, on-demand, and scheduled extracts |
| Better operational visibility | Redwood interface supports extract definition and status monitoring |
| Near real-time data availability | Replicated data supports reporting and integration needs requiring relatively current information |
The broader value is the combination of architectural separation and simplified extraction management.
Together, these capabilities provide a foundation for building data-driven solutions that complement Oracle Fusion Cloud Applications.
Final Thoughts
Oracle's new Data Extraction framework represents an important change in how Fusion Cloud application data can be made available to external systems.
The move to a dedicated, read-only Autonomous Data Warehouse data store separates extraction workloads from transactional processing and introduces a more business-oriented approach through predefined views.
The Redwood interface further simplifies the experience by bringing extract definition, scheduling, and monitoring into a common workspace.
For organizations using BICC or BI Publisher for extraction, Oracle's stated direction makes the new framework an important capability to evaluate.
However, migration planning should account for differences in business object mapping, current attribute coverage, and specific integration requirements.
From a consultant's perspective, the most important consideration is understanding both the architectural benefit and the functional boundaries of the new approach.
The framework is not simply another extraction tool. It represents a shift toward accessing replicated application data through a dedicated extraction layer, with the objective of improving performance, reliability, and usability.
As organizations continue expanding their reporting, analytics, and integration capabilities, this approach provides a new foundation for extracting business data from Oracle Fusion Cloud Applications.



Top comments (0)