Installing a Scoped Application is creating tables with different sys_id values at each install of the application and so sys_ids for tables are not consistent across instances [sys_db_object, sys_dictionary]Issue When installing a Scoped Application, the tables that are created during the install can have different sys_id values.CauseHaving different [sys_db_object] sys_ids, on its own, is not an indicator of a problem and so this is expected behaviour of the ServiceNow Platform.Related LinksAs [sys_db_object] sys_ids have never been guaranteed to be the same from one instance to another, the ServiceNow Platform attempts to adjust for this via coalesce strategies, when applying future update sets. [sys_db_object] has a coalesce strategy on the name value, so we will rename updates for tables that do have different sys_ids between source and target instances. By updating the existing record with the same name through the coalesce strategy, it will prevent duplicate table names. If you want to preserve the Scoped Application table sys_ids, after the installation of the Scoped Application on PROD, we recommend to clone the PROD instance to all other instances, where you want to preserve the table sys_ids. Please contact ServiceNow Customer Support, if further guidance is required.