Integrate OAS with EBS for both authentication and authorization of users leveraging EBS RBAC roles.

Jorge Marañón-Oracle

(On Behalf of the customer on SR 3-41645779051)

1. Reason current product functionality is insufficient:
   Oracle Analytics Server has deprecated the native integration with Oracle E-Business Suite (EBS) for authentication and authorization using EBS
   Role-Based Access Control (RBAC). This creates a significant gap in enterprise security architecture, as organizations can no longer leverage
   their existing EBS security model to control data access in OAS reporting environments.
2. Detailed description of the Enhancement Request:
   Objective:
   Restore EBS RBAC integration capability in Oracle Analytics Server to support enterprise reporting requirements for DoD customers.
   Background:
   Three mission-critical DoD partners require OAS as their primary Enterprise Reporting solution for EBS systems. The previous OBIEE solution
   successfully supported EBS RBAC integration through ICX cookie authentication, enabling seamless user authorization that respected existing
   EBS security policies. This capability is essential for maintaining data governance and security compliance in government environments.
3. How the product can be changed to achieve the desired result:
   Implement a method in OAS for integrating with EBS R12.2 to allow OAS to inherit EBS RBAC. This method must ensure that EBS RBAC is respected when OAS users query the EBS database via ad hoc queries, via Subject Areas defined in the repository, and any other way OAS can be used to query the EBS database. OBIEE delivered this integration with EBS RBAC (i.e., authorization) via the ICX cookie integration.
4. Reasons to consider the Enhancement Request:
   Market Demand: Significant DoD customer base requires this functionality for EBS modernization
   Competitive Advantage: Positions OAS as viable replacement for OBIEE in government sector
   Customer Retention: Prevents migration to alternative BI platforms
   Revenue Impact: Enables expansion into high-value government contracts
5. Business impact if the Enhancement is not considered:
   If Enhancement is NOT Implemented:
   Financial: Loss of DoD market segment and associated revenue
   Operational: Customers forced to develop costly custom integration solutions
   Strategic: Reduced OAS adoption rates in government/enterprise sectors
   Competitive: Customers may choose alternative BI platforms with EBS integration
   Timeline: Each customer implementation delayed 6-12 months for custom development
   If Enhancement IS Implemented:
   Accelerated OAS adoption across DoD customer base
   Reduced implementation costs and time-to-value for customers
   Enhanced product competitiveness in enterprise market
6. Enhancement is affecting an implementation milestone:
   We need to be able to upgrade to a supported version of OAS before OBIEE goes out of sup-port. This should be accomplished before the end of 2026.
7. Description of the business flow that is affected by this Enhancement :
   ERPCS need to build a custom solution to integrate OAS with EBS for both authentication and authorization of users leveraging EBS RBAC roles.
8. Can you easily recover from, bypass or work around the problem:
   Primary Workaround: Continue using legacy OBIEE platform
   Limitations: End-of-life product with limited support and no new features
   Risk: Security vulnerabilities and compliance issues with unsupported software
   Alternative Workaround: Custom integration development
   Cost: additional money for development effort
   Timeline: Extends OAS implementation with custom code development effort
   Risk: Custom code maintenance burden and potential security gaps
9. Does your system or application continue normally after the problem occurs?
   The absence of this feature does not cause system failures but creates significant operational and security challenges that impact the viability of
   OAS as an enterprise reporting solution for EBS environments.
10. Are the standard features of the system or application still available; is the loss of ser-vice minor?
    Priority Level: High - Mission Critical
    Rationale:
    Affects core security and compliance requirements; Blocks adoption by strategic government customers.
    No viable alternative exists within Oracle's current product portfolio; Impacts multiple high-value customer relationships
    Recommended Timeline: availability for DoD customers before the end of 2026.