BOM

 

sdifiore's picture

Hi,

Talking about Postbooks 3.3.0.

I’m trying to build a Bill of materials for an item
I have all raw components to build it in the items list, listed as “purchased”
Whenever I try to add then assembly (Product → Bill of Material → New), select the item I want make the BOM with tem coma button, fill al the fields and then use the New product in the Bill of Material button, in the next window, where I’m supposed to specify the items list, even using the ellipsis button, it doesn’t show any item at all.
What’s wrong?

Thanks in advance,
Sergio

 
wtonra's picture
Offline
Joined: 10/28/2007
BOM

Sergio,
You first need to have the Manufactured item in the item list. Along with the Purchased Items for your components, you need to create the Manufactured Item. It will then show up in the list. If you don't have any Manufactured Items in your database, then nothing will show when you search for an item to create a BOM for. Once you have created the Manufactured item, you can create the BOM right from the Item Master, by clicking the "Materials" button at the top.

 
sdifiore's picture
Offline
Joined: 10/21/2009
That is then problem... I

That is then problem...

I'm doing exactly you're saying, so I have already a item created as Manufactured item.

Whenever I try to add a component to one of the manufatured item, cliking in the "New" button, it shows me another window, with a elipses button to add a componente, no components are shown at all...

I added a screen shot of this, to try to make easier to undestand...

Tks Again,

Sergio

AttachmentSize
bom.jpg 51.09 KB
 
carolyn's picture
Offline
Joined: 12/10/2008
BOM Items

Hi Sergio,

It looks like your Preferences are set to Search, not List, so if you enter .* in the search field, you should see the list of items.

Best,
Carolyn

 
sdifiore's picture
Offline
Joined: 10/21/2009
NOP It's set for List, and

NOP

It's set for List, and using * does not change anything :o\

 
ptyler's picture
Offline
Joined: 12/10/2008
Item sites defined?

Hi, Sergio:

Have you created Item Sites for your purchased Items? If not, that could explain the problem. Try creating Item Sites and see if that fixes it.

Regards,
Pierce

 
sdifiore's picture
Offline
Joined: 10/21/2009
Not yet

In fact I didn’t create the Item Site, what I did now.

Still the same problem… As if there were no products in the system…

I appreciate any solution, it’s taking to much time, and my customer understands that there is something going on, and that’s not good.

Appreciate any hint that can enlighten this mystery.

Tks again
Sergio

 
ptyler's picture
Offline
Joined: 12/10/2008
Version of database

Hi, Sergio:

This functionality is working fine for me in my PostBooks 3.3 demo database. What database are you using as your starting point: empty, quickstart, demo? Also: Did you by any chance import these items into the database? We sometimes see behavior like this if items are imported incorrectly.

If you're not too far along, you might also consider doing a clean install of version 3.4. That's the current release. Perhaps there was something wrong with your original installation.

Regards,
Pierce

 
sdifiore's picture
Offline
Joined: 10/21/2009
Started from empty

Hi Pierce,

Acctually, the demo base here works fine. I infact however started a new production database database, with the postbooks_empty-3.3.0.backup file.

I'llm make a try with 3.4 and let you know.

 
sdifiore's picture
Offline
Joined: 10/21/2009
Database

3.4 instaled, and the message saying that the database maight not be compatible.

Do I have to run any scrypt over the database?

Tks

 
ptyler's picture
Offline
Joined: 12/10/2008
Log in options

Hi, Sergio:

Check the OPTIONS on the log in screen to make sure you are connecting to the correct database and port. If you are using a 3.4 GUI client, you will need to connect to the 3.4 database you installed.

Regards,
Pierce

 
sdifiore's picture
Offline
Joined: 10/21/2009
Ok, but is there any way to

Ok, but is there any way to migrate the database from 3.3. to 3.4?

 
Rydeljh's picture
Offline
Joined: 07/17/2009
Update DB Version

Look for the update file (PB331to340.gz) from 3.3.1 to 3.4.0 @ http://sourceforge.net/projects/postbooks/files/ then just us the updater to upgrade your DB version to match your client installation.

 
sdifiore's picture
Offline
Joined: 10/21/2009
Script error

Well, I guess that is an sql script to run againt the database with pdAdminIII

I got the error:

ERRO: erro de sintaxe em ou próximo a "0000775"
LINE 1: ... 0000775 00...
^

********** Erro **********

ERRO: erro de sintaxe em ou próximo a "0000775"
SQL state: 42601
Caracter: 90

Or in englisg, something like:

ERROR: sintax error in or neat "0000775"
LINE 1: ... 0000775 00...
^

********** Error **********
ERROR: sintax error in or neat "0000775"
SQL state: 42601
Caracter: 90

 
sdifiore's picture
Offline
Joined: 10/21/2009
Step-by-step

I thought that if I migrate from 3.3.0 to 3.3.1 and so forth, I'd may accomplish that, but, to my surprise in the files available at sourceforge (specifically http://sourceforge.net/projects/postbooks/files/), I can't find a migration script over 2.2.0 Where are the other files?

 
ned
ned's picture
Offline
Joined: 10/20/2008
They're all there. Each set

They're all there. Each set of upgrade scripts is in the PostBooks-databases directory for an individual release. So:

PostBooks-databases / 3.4.0

contains pb331to340.gz (for migrating from 3.3.1 to 3.4.0) as well as the incremental testing upgrade of pb340rcto340.gz (migrating from the 3.4.0 release candidate).

Unless you're testing alpha/beta/RC software, you should only go from one final release to the next. But you do have to hit each release. So if you're migrating from 3.2.2 to 3.4.0, you'd need:

pb322to330.gz
pb330to331.gz
pb331to340.gz

And of course, these scripts are intended for use only in the xTuple Updater. The latest release of this tool is available here (currently 2.2).

 
sdifiore's picture
Offline
Joined: 10/21/2009
Solved

Just keeping here, as record in case someone needs in the future.

My mistake was, I did the Item Site only for the product I was trying to build.

All components that compose a product list have to have an Item Site!

Tks everybody for the time, trying to help me!!!