Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Visual Integrator Bill of Matrial Import Problem

Status
Not open for further replies.

Markus99

Technical User
May 18, 2008
3
US
For the life of me I cannot get VI to import my BOM correctly. I've setup the import for all required fields and have a .CSV file of data, snippet below:

1,68,RBWWH03-0000,RB- W White 3-6m,ARJ-1120-45-00,Fabric - White Woven,0.54,36.72
2,68,RBWWH03-0000,RB- W White 3-6m,SCO-PK-3/8-WH,"Elastic - 3/8"" White Poly",0.59,40.12
3,68,RBWWH03-0000,RB- W White 3-6m,SCO-1/8-IMP-NAT,"Elastic - 1/8"" White Rayon",1.23,83.64

Fields are Index, # Products Produced, Bill # (Inv#), Bill Description (InvDesc), Item #, ItemDesc, Qty in Bill, Total Qty Used

The import passes the validation test fine, though it does NOT import each item. I've attached screenshots for each the import and the validation summary. You'll notice the .CSV file is read fine, but NOT the individual items...

VI-BOM-ImportProblem.jpg


I've exported a test BOM and made sure to import all fields that were exported, but still is giving me fits. I've also recreated the import with an XLS version 4 file, same result.

Anyone have any thoughts? Thanks in advance for the help!

Mark
 
Two things. We need to see how you setup the Records tab and the Bill Revision should be "*" if the Revision is the Current one.
 
Nail on the head. I just found the problem this morning, after beating my head against the wall repeatedly. I added a component line to the records tab (which was previously blank) and set it with value <> blank one of the fields in the import file. You'd think that setting the switch on the configuration tab to header info included in detail line would default to reading ALL lines in the file... Also quirky that the ProductionEntry import has to have a unique key field and doesn't automatically lump rows with the same Bill# together... I'll switch the Revision code to * on the next import. Thanks for the help!!
 
Because there are different line types and because you can import just header info ( to update header info ) you have to tell VI how to know what type of record the line detail is or if there is a line detail.
 
Worked like a charm. Quick ?. What, in the Production Entry import is the ITEM_COSTING represent? Options are 1,2,3,4,5,6 though I can't find what each represents. Thanks!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top