We have a few products that create different schemas in the company database.

Some of those tables are detected, but also error out when using the customer combiner.

It appears like the tool detects any column CUSTNMBR and possibly Customer_ID.

This blog outlines the issue much better:

https://timwappat.info/post/2015/09/03/Customer-combiner-and-table-not-found-errors

Ideally the Customer Combiner would ignore and/or handle different schemas more appropriately.,