Answer
Check whether the generated SQL shows the IAL view name incorrectly double-prefixed — for example something like select * from &AO.bell1app.ronv_test instead of the correct form, which should simply be the fully-qualified view name under the actual IAL owner schema (e.g. select * from BELL1INFO.RONV_TEST). The &AO. token already resolves to the Application Owner, so having both the &AO. token AND a literal, separately-typed owner-name prefix in front of the view name produces invalid SQL. This specific double-prefix pattern has been a confirmed platform defect in some releases (fixed in one major version but not consistently ported to others) — if you see this exact malformed pattern in the generated query, it's worth reporting to IFS support as this known issue rather than assuming a mistake in your own IAL configuration.