Not every attribute is representative of a primary key, obviously. Especially when you have delta T (current) records. No sane database design is going to have all attributes in a single table. This is 40 year old design methodology. The right way to have a primary key (item) and single source of truth is to leverage relations, often through views with INSERT/UPDATE triggers. Not being able to register a view as editable is a bad design decision that has nothing to do with whether the views are *actually* "editable."
There is so, so much custom coding and ETL work that needs to be done to get around that frustrating limitation.