Hi Robert,
Aldon LM(i) will not create an object in the ITG or QUA environments that is based on an object in a different library. In order to protect against this, Aldon LM(i) creates "phantom" copies of any requisite objects in the library in which the basing object is being created. It determines what phantoms are necessary by examining the copy of the basing object in the "from" environment. If this is a PROMOTE operation, then it uses the copy in the next lower environment (Developer or Integration). If this is a CREATE in place then it looks at the existing object in that environment. If it is a Create non-resident, then it looks in the next higher environment (QA or production). If the "authoritative" copy of the object is created incorrectly, or is missing, then Aldon LM(i) will not be able to correctly determine what phantoms to create.
Are Table_One, Table_Two and Table_Three registered in LMi? Which environment are they in? If they are not registered in LMi, you may want to load them into the same release of the SQL view.
Again, this Forum is for information only. For ease of tech support, please open a case in Rocket Community after signing in to https://www.rocketsoftware.com/support.
Best regards,
Jack