3830596 - Custom MDF object missing in Story data source due to duplicate logical table name in FoundationObjects

• A custom MDF object does not appear in the Story Report data source picker under Foundation Objects.
• Repository Object Status for the custom MDF object shows Not Available.
• No CALC_VIEW creation traces are recorded for the object.
• Error message observed: "Logical table name should be unique within a sub domain schema. Violation [Objectname]. This validation is case insenstive"
• Secondary messages can include "Error checking permission details" and "No permission to view entity".

• Data Modelling - Module & Entity Data Issues

1. Create a new Story report.
2. Add a new data source.
3. Expand Foundation Objects in the available data list.
4. Observe that the custom MDF object is not available for selection; in Report Object Configuration Entity the Repository Object Status shows Not Available.

Duplicate logical table name within the FoundationObjects sub-domain (case-insensitive), for example two MDF objects or associations using the same logical table name such as payRange_geozone. This causes schema generation to stop and prevents calc view creation for all objects in the sub-domain.

In corporate data model check if violated object association eg: to geoZone from PayRange is defined twice

Please correct this and maintain unique association from PayRange to Geozone and it will fix the issue

• Refer to: Custom MDF object is not reportable in Story
• Refer to: Configuring Custom MDF objects for reportability using Story reports

custom mdf not visible, story report, data source picker, foundationobjects, repository object status not available, logical table name duplicate, payRange_geozone, checksumgenerator, calc_view not generated, unique within sub domain schema, duplicate association, report object configuration entity, metadata refresh, mdf reportability, story data model , KBA , LOD-SF-ANA-SAC-DAM , Data Modelling - Module & Entity Data Issues , Problem