Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-OPENED] ROOT RECORD IN DATA BASE IS NOT UNIQUE using Parent Child Hierarchy

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CASE-OPENED] ROOT RECORD IN DATA BASE IS NOT UNIQUE using Parent Child Hierarchy
 Login/Join
 
Member
posted
Hi,
I need some help on creating reports using parent-child hierarchy in report painter.
D_Product Table Structure:
PRODUCT_ROWID PRODUCT_KEY PRODUCT_NAME PARENT_KEY
1 TOTAL SKU Consolidated Products
2 TOTAL_BRANDED Consolidated Branded Products TOTAL SKU
3 TOTAL_COMPO Consolidated Component TOTAL SKU
4 TOTAL_OTHER Other non-SKU Items TOTAL SKU
Note: The parent_key for TOTAL_SKU product is blank

MODEL:
Created dimensions with “parent-child hierarchy” for D_PRODUCT connects to a fact table (F_ORDER) using (D_PRODUCT.PRODUCT_ROWID= F_ORDER.PRODUCT_ROWID)
Unique ID : D_PRODUCT.PRODUCT_KEY
Caption : D_PRODUCT.PRODUCT_NAME
Parent Of : D_PRODUCT.PARENT_KEY

REPORT PAINTER::
Added the "product_key" in to the report from object inspector in report painter and where it is set as "Hierarchy" and included one measure "Sold_Qty" and set it as "SUM" and same measure "Sold_Qty” column is added, where set it as "FROLL"
When I execute the report, it displays the error code
“(FOC32440) ROOT RECORD IN DATA BASE IS NOT UNIQUE
BYPASSING TO END OF COMMAND”
Kindly help me on this issue.

This message has been edited. Last edited by: <Kathryn Henning>,


WebFOCUS 8.0.07
Windows, HTML
 
Posts: 12 | Registered: March 26, 2014Report This Post
Virtuoso
posted Hide Post
Are these relational tables, or are they FOCUS files?

If relational, check the generated synonyms of the two underlying tables, to see whether the declared primary key (indicated by KEYS=n in the access file, and the first n FIELD declarations in the master file) matches your understanding of the primary-key structure of each table.
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Member
posted Hide Post
Gross,

These tables are relational.

I am getting the same error,after primary keys are defined for product_row_id & product_key in the D_PRODUCT table and for Product_rowid in F_ORDER fact table.


WebFOCUS 8.0.07
Windows, HTML
 
Posts: 12 | Registered: March 26, 2014Report This Post
Member
posted Hide Post
Any luck on this?


WebFOCUS 8.0.07
Windows, HTML
 
Posts: 12 | Registered: March 26, 2014Report This Post
<Kathryn Henning>
posted
Hi Smanicka,

There isn't much information in our knowledge base regarding this error. Please open a case on InfoResponse Online so that we can work with you on this issue.

Thanks and regards,

Kathryn
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-OPENED] ROOT RECORD IN DATA BASE IS NOT UNIQUE using Parent Child Hierarchy

Copyright © 1996-2020 Information Builders