My Oracle Support Banner

"A supertype-subtype relationship cannot be established between two subtype entities that belong to same or different supertype group" Error in Erwin Data Modeler When Creating New FSI_D_ Table in OFSAA (Doc ID 2830439.1)

Last updated on DECEMBER 29, 2021

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)

Goal

User tried to create a new custom FSI_D_ instrument table, by adding child relations as FSI_D_CASA table, but found properties are not the same. Type property in FSI_D_CASA relation is "Subtype", whereas in new FSI_D_ is "Identifying". After uploading data model, columns in parent tables were not created in new FSI_D_ table.

User tried to add super-type relationships between custom instrument table and super-type entities, however he only managed to add one such relationship. When adding the second one, below popup message was received:

  A supertype-subtype relationship cannot be established between two subtype entities that belong to same or different supertype group

 

User referred steps in "How to Add Custom Instrument Tables" document, which is available at: https://docs.oracle.com/cd/E26650_01/homepage.htm , and even the more detailed steps available in chapter 9 "Create Subtype and Supertype Relationship" from OFSAAI 8.1 Data Model Extension Guidelines , which provides information on how to create the Subtype and Supertype relationship between two entities.

Since some issues may come from super-type tables being created incorrectly, user also tried copying from a seeded data model (see below steps), but to no avail.

1). Copy seeded FSI_D_ table and rename / update and super type tables.
2). Check for differences between custom table and seeded table.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.