WBS Codes are not defined

Question

I work for a company that uses Estimating and I recently helped them upgrade to 19.12. I don't work in Estimating but help them with their IT needs. All of the sudden when they create a new estimate they're receiving the message: 
 the following database Wbs codes are not defined in the the 'estimate name' estimate. 
 Job Cost 
 These Wbs codes will not be included on estimate items during takeoff. 
 When I look in there DATA tab and WBS I can see the Job Cost code for both the Estimate and Database and they match. 
 This is only showing up with new estimates. Can someone please help point me in the right direction for a solution? Thanks

Hamidk · Accepted Answer

The "Estimate Information" is nothing to do with the Database that you have picked, so don't worry about the "Estimate Information" . 
 After this, call out few items into the estimate. Then close the sage. 
 I would say if you open it again... you must not see this warning...unless the estimate has lost the connection to the database which right now you know how to re-connect it. 
 All you must be care and be care full all your old estimates. I explain before how you can check and see in a new specific tap

twse · Answer

You say they're " both the Estimate and Database and they match". Are they the same # on the WBS table ie are they both WBS #6 or whatever the # is? Are they both the same size and same type and same unit of measure?

Hamidk · Answer

1) About the WBS 
 1-1)When you go to the below 
 
 Check what is the pre-existing WBS in the estimate that just opened. 
 1-2) Then at the same time go and check what the alive WBS define in the database that you are working on (below) 
 
 If you have a pre-existing WBS in your database that never defined (the same) in the current estimate you get the note. remember there are 40 WBS can be define in the estimate (or database) 
 2) For job Cost Codes - Goto project information and find the below

You must connect the "job Cost System name" to your accounting file

Hamidk · Answer

No worries, I am expecting you are getting the below message : 
 
 This means I open an old estimate that never ever generated with your current selected database. 
 Once Sage Estimate generates an item then won&rsquo;t recall and update the item again from the database. 
 That&rsquo;s why your old estimate won&rsquo;t talk and update as per your database! 
 For example, create a new blank estimate from sketch with your database (put few items) and close and re-open it again. You won&rsquo;t get any warning message like that. 
 
 &ldquo;When I Edit Values on there are more values in the Database code than the Estimate&rdquo; Hey, for sure there should be more values in the database than the estimate. This is not a problem. 
 The point is the existing generated items in the estimate need to be re-tagged to your current WBS1

Okay to solve your current issues, first make new Tab with &ldquo;Sequences&rdquo; and &ldquo;Group Hierarchy&rdquo; with the &ldquo;Job Cost (tagged in your system as WBS Code 1)&rdquo; and see what you get. Anything classified as &ldquo;*unassigned&rdquo; means needs to re-tagged. Hoping not getting a lot!:( 
 I would make the correction like this &hellip;. Select entire row (like excel), right click and use the &ldquo;move&rdquo; and follow the below screen shot to find the correct WBS 1 in your current database:

As far as I can see there is misinterpretation between what you and I about using WBS (as cost codes in WBS part, which is okay for cost organizing etc !) with what Sage Estimate use Cost Phase Codes to communicate with Sage Accounting Departments. Apparently your company is not using this sounds to me, so you shouldn&rsquo;t be worry.

Sage Construction & Real Estate

WBS Codes are not defined

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING