Welcome to the Business Views Problems web-site, David!
And allow me to cite Sr. JDE Specialist Saad Mian's tips and techniques related to the issue you/we have.
1 BSVW introduce a middle layer between the application and the database.
2 They do not use aggregate functions, sub-elects or value-based joins.
3 They may use misleading column names in case of multiple joins.
4 They cannot be created over non-OneWorld files and
5 Non-OneWorld software cannot use BSVW to query data.
But how do we approach YOUR problem? When you can't make it, fake it! That is:
1 Create a DATABASE View, say FV55xxx (as a union of F4201 & F42019)
2 Create a OneWorld file (FV55xxx) using the DATABASE View's specs (columns, data types ...).
3 Do not generate the file on the Enterprise Server! Just check the specs out, on the Deployment Server
4 Create the (working) Business View W55xxx over FV55xxx joined with your OTHER table.
5 Generate W55xxx, and use it in any OW Appplication or UBE
Thank you Saad!
LIVE: B732.1 SP12.2, Oracle 806
SANDBOX: Xe SP15, Oracle 8i
RS/6000, Citrix