# Fix Wrong Row Counts When Joining Across OTBI Subject Areas > Source: https://netray.co/erp-help/fusion-otbi-subject-area-join-issues > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Most subject areas in Oracle Fusion OTBI are self-contained and only support reliable analysis within their own folders; dragging a folder from a second subject area into the same analysis without a genuine shared join key silently produces duplicated or missing rows because OTBI has no way to correctly relate the two fact grains. Fix it by staying inside one subject area where possible, or by explicitly using a subject area that Oracle designed to cross domains, rather than combining arbitrary folders yourself. ## Kind how-to ## System oracle-fusion ## Erp Oracle Fusion Cloud ERP ## Module Oracle Transactional Business Intelligence / Subject Areas ## Query OTBI analysis returns no rows or duplicated rows across subject areas ## Alternate Queries - how to join two OTBI subject areas correctly - OTBI analysis wrong row counts multiple subject areas - combining folders from different OTBI subject areas - OTBI duplicate rows when adding a second folder ## Applies To Oracle Fusion Cloud ERP, SCM, and HCM, all OTBI subject areas, all monthly updates ## Steps ### Diagnose and fix an OTBI multi-subject-area row count problem **Items:** Confirm which subject area each folder you dragged into the analysis belongs to - the criteria pane groups folders by subject area, so check whether you have combined folders from two different top-level subject areas. If row counts look inflated, check whether you combined a header-level folder (one row per order) with a lines-level folder (one row per line) without a shared grain, which multiplies header attributes across every line. If row counts look too low or zero, check whether the two folders share no real join key at all - OTBI is silently returning an empty or filtered result rather than erroring. Search for a purpose-built cross-domain subject area (for example, one explicitly named to cover Order Management and Receivables together) before trying to manually relate two single-domain subject areas. If no cross-domain subject area exists for your combination, split the requirement into two separate analyses at matching grains and combine them in a dashboard, or in Excel/BI Publisher, rather than forcing an unsupported OTBI join. For a genuinely custom cross-subject-area requirement, evaluate a BI Publisher data model (custom SQL or multiple data sets) instead of trying to reshape OTBI folders to fit. Validate any fix against a known total (an existing report or a manual count for a small data set) before trusting the corrected analysis. ## Sections ### Why OTBI Cannot Freely Join Across Subject Areas **Body:** Each OTBI subject area is a curated semantic layer built around one or a small number of related fact grains, with folders and columns Oracle has already joined correctly within that subject area. When you drag in a folder from an unrelated subject area, OTBI has no metadata describing how the two fact grains relate, so it either falls back to a cross join that duplicates rows, or filters down to nothing because no matching dimension exists. ### Header Versus Line Grain, The Most Common Trap **Body:** A very common version of this problem happens even inside a single subject area: combining a header-level measure, such as order total, with a line-level folder produces one row per line, and the header total appears to repeat and overstate when summed naively. Check the grain of every folder you add - Oracle typically names or documents which folders are header level and which are line or detail level - before summing any measure. ### When Oracle Provides A Cross-Domain Subject Area **Body:** For some common cross-functional questions, Oracle ships a subject area explicitly designed to combine domains correctly, such as one that already joins procurement and payables data at a sensible grain. Always check whether a purpose-built subject area exists for your combination before assuming you need to force two unrelated ones together. ### When To Stop Fighting OTBI And Use BI Publisher **Body:** If the requirement genuinely needs data from domains with no supported subject area relationship - say, HCM headcount alongside SCM inventory value - a BI Publisher data model with multiple data sets, or a custom SQL query against the appropriate views, gives you explicit control over the join instead of relying on OTBI's implicit relationships, which were never designed for that combination. ## Pitfalls - Combining header and line-level folders in the same OTBI analysis and summing a header measure without checking for duplication. - Dragging in a second, unrelated subject area's folder because it happens to have a similarly named column, assuming that implies a valid join. - Trusting a row count that looks plausible without validating it against a known total - silent duplication or filtering both look like normal results at a glance. - Rebuilding the same broken combination in a dashboard prompt instead of fixing the underlying analysis, which just moves the wrong numbers downstream. - Not checking whether Oracle already ships a cross-domain subject area for the exact combination before manually forcing two single-domain ones together. ## Ai Angle ERPray grounded on your Fusion OTBI metadata can flag, before you run the analysis, that two folders you have combined come from unrelated subject areas or different grains, and suggest whether a purpose-built cross-domain subject area or a BI Publisher data model actually fits the question - catching the silent duplication or empty-result problem before it reaches a report someone relies on. ## Faq ### How can I tell which subject area a folder belongs to? **Answer:** In the OTBI analysis criteria pane, folders are grouped under the subject area name shown at the top of the Subject Areas panel when you select it. If you have added a second subject area to the same analysis, you will see a second top-level grouping - that is your signal the combination may not be supported. ### Does OTBI ever warn me when a join is unsupported? **Answer:** No. OTBI does not raise an error for an unsupported cross-subject-area combination; it just returns whatever the implicit relationship (or lack of one) produces, which can look like a plausible but wrong row count. Always validate against a known total. ### Is there a list of which subject areas can be combined? **Answer:** Oracle does not publish a general compatibility matrix; the safest approach is to check the subject area descriptions and look for a purpose-built subject area that already spans the domains you need, or ask through Oracle Support or the reporting guide for that specific combination. ### Can a dashboard prompt fix a bad multi-subject-area join? **Answer:** No. A dashboard prompt filters the same underlying analysis; if the analysis itself is joining two unrelated subject areas incorrectly, filtering it narrows the wrong result set rather than fixing the join. ## Search terms OTBI subject area join issue, OTBI duplicate rows fix, OTBI wrong row count analysis, combining OTBI subject areas, OTBI header line grain, Oracle Fusion OTBI cross domain reporting, OTBI analysis returns no rows, Fusion OTBI subject area folders --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json