Solution ID: prim85294
Error: "SQL ERROR: Invalid object name….", when trying to open any cost code detail view
Status: Reviewed
Version(s): 11.0, 11.1, 12.0, 12.1, 13.0

Fact: Database: Microsoft SQL Server
Problem: Error: “SQL ERROR: Invalid object name….”, when trying to open any cost code detail view
Problem:

One of the following errors is thrown, when trying to open any cost code detail view:


SQL ERROR: Invalid object name ‘bid_complete_basic’


SQL ERROR: Invalid object name ‘bid_completion_view’


SQL ERROR: Invalid object name ‘estimate_costing_detail_view’


SQL ERROR: Invalid object name ‘procure_combined_awarded_estimate_view’


SQL ERROR: Invalid object name ‘procure_combined_estimate_view’


SQL ERROR: Invalid object name ‘Procure_General_Item_Awarded_Estimate_View’


SQL ERROR: Invalid object name ‘Procure_General_Item_Estimate_View’


SQL ERROR: Invalid object name ‘procure_item_view’


SQL ERROR: Invalid object name ‘Procure_Scope_Item_Awarded_Estimate_View’


SQL ERROR: Invalid object name ‘Procure_Scope_Item_Estimate_View’


SQL ERROR: Invalid object name ‘GET_BID_TOTAL’


SQL ERROR: Invalid object name ‘GET_COMPLETE_GENERAL_BIDS’


SQL ERROR: Invalid object name ‘GET_COMPLETE_SCOPE_BIDS’


SQL ERROR: Invalid object name ‘GET_SCOPE_BID_TOTALS’
Problem: Unable to open any cost code
Change: The Contract Management MS SQL databases were either migrated from Sybase or created brand new.
Cause: The problem database is missing various views, functions, and possibly other objects.

The missing objects were most likely never created, because the Contract Management database utility was not able to change the database compatibility level to 2000 (80).

Contract Management databases on Microsoft SQL are required to be at the 2000 (80) compatibility level in order for Contract Management to function correctly.
Fix:
  1. Ensure that the MS SQL server instance sa user account has the proper permissions to execute the following stored procedure: sp_dbcmptlevel

    The sa user account needs these permissions, because Contract Management uses that account to create the databases.

  2. Once the proper permissions have been granted, delete the corrupt databases and re-run the database migration or creation.

If re-running the database migration or creation is not possible, contact Oracle Primavera Support for help resolving the issue.