We migrate your OBIEE Logical SQL reports to OAC, handle every syntax breaking change, rebuild presentation variables, and stay on call for 30 days after go-live. Fixed price by report volume.
Get a Migration Quote →OAC is not a drop-in replacement for OBIEE. The subject areas look the same — the Logical SQL syntax doesn't always behave the same.
| Area | OBIEE (Classic) | OAC Behavior | Status |
|---|---|---|---|
| Presentation variables | @{varName}{default} | Same syntax — but prompt binding behavior differs in Workbooks vs Dashboards | ⚠ Verify |
| FILTER() function | FILTER("Measure" USING condition) | Supported — but correlated measure references break if subject area changed | ⚠ Test each |
| EVALUATE() / EVALUATE_AGGR() | Passes DB-native SQL to physical layer | Restricted in OAC SaaS — many calls blocked by Oracle security policy | ✗ Often breaks |
| Row limits on dashboards | Configurable up to millions of rows | OAC SaaS caps certain exports — raises errors on existing large downloads | ⚠ Audit exports |
| RPD / Semantic Model | Binary .rpd file, Admin Tool | XML-based Semantic Model — direct migration tool available but requires validation | ⚠ Plan for it |
| Subject areas | Standard HCM subject areas | Same subject areas available — no changes needed for OTBI-based reports | ✓ Compatible |
| BIP integration | BIP linked to OBIEE data models | BIP still works in OAC but connection config changes | ⚠ Reconfigure |
SELECT "Workforce - Worker Assignment" ."Worker Name", EVALUATE('REGEXP_SUBSTR(%1, %2)', "Worker"."Email Address", '@(.+)') AS "Domain" FROM "Workforce - Worker Assignment"
SELECT "Workforce - Worker Assignment" ."Worker Name", SUBSTRING( "Worker"."Email Address" FROM POSITION('@' IN "Worker"."Email Address") + 1 ) AS "Domain" FROM "Workforce - Worker Assignment"
We scan your full OBIEE catalog, classify every report by migration risk, and deliver the assessment. You decide what to migrate, retire, or defer. No code changes yet.
We start with your most complex reports — EVALUATE() calls, custom SQL, cross-subject-area joins. These are the ones that take longest and hold up UAT if left to the end.
Migrate MEDIUM and LOW risk reports (usually batch-processed). Parallel UAT begins on Week 2 output. Side-by-side comparison report ready for your team's signoff.
We're on call for go-live day. Post-go-live, any report issues in the 30-day window are handled with same-day turnaround. After that, you own the environment with our full runbook.
No hourly billing. Scope is agreed upfront. If we find more reports in scope during inventory, we discuss before adding to the engagement — no surprise invoices.
We work in your OAC environment. You provision a user account for us with Catalog permissions and we run validation against your actual target environment — not a sandbox that might behave differently.
The Phase 1 inventory and risk assessment is available as a standalone $1,500 engagement. You get the full catalog inventory and migration risk report. Most clients find it validates the migration decision (or clarifies what would need to be retired vs. migrated).
Yes. The majority of engagements are either OBIEE 11g → OAC or OBIEE 12c → OAC. The Logical SQL dialect differences are well-understood at both versions. RPD migration is more involved for 11g environments — factor that into scoping.
OTBI reports built in Oracle HCM Cloud using standard subject areas are mostly compatible without changes — the subject areas port cleanly. The migration work is primarily on custom OBIEE reports, BIP integrations, and any reports using EVALUATE() or custom SQL.
Not required, but strongly recommended. Data quality issues that exist in your OBIEE environment will carry forward into OAC. Running the HCM Data Health Check before migration ensures you're migrating clean data — not compounding existing issues. We bundle both at a discount.
Send us your OBIEE version, report count estimate, and target go-live. We'll come back with a scope and quote within one business day.
Get Migration Quote →