IS ANYONE ELSE HAVING TROUBLE WITH PURCHASED PARTS AND ASSIGNED VENDORS.
 
PO'S NOT ALLOWING ENTERING OF ITEM EVEN THOUGH IT CLEARLY SHOWS VENDOR IS ASSIGNED IN THE ITEM NUMBER.
 
HOWEVER, IT SEEMS WE HAVE TO GO TO PO-L AND ASSIGN VENDORS THERE ADDITIONALLY, BECAUSE EVEN THOUGH THEY ARE ASSIGNED IN ITEM ENTRY, THEY ARE NOT IN PO-L.  
 
ALSO, HAS THERE BEEN AN ANSWER TO MY PREVIOUS EMAIL REGARDING FATAL ERRORS UPON PRINTING PURCHASE ORDERS

Assigned Vendors is still a problem.  We have to re-assign all vendors to items, as the update does not recognize already assigned vendors.
 
When is the fix coming?

Karen,
 
Looks  to me like it is still there in IN-A and IN-B.

Hmm.....I checked in our data and unfortunately (for testing purposes) all of the items I checked had an entry under PO-L.  Our buyer stated that almost always, if something was entered in IN-B for a vendor, it propagates to PO-L.  I wonder if it is a database problem??  I also wonder if PO-L works like PO-H, which will override anything entered in IN-B.  
 
Tried an experiment - took an item just recently entered, with vendor data, and deleted the vendor in PO-L.  It didn't complain, and oddly enough the vendor still shows up in IN-A?!  Maybe a disconnect somewhere in your data??? (just speculating - back to real work....)

There are 2 sets of data.  The "Primary" vendor which is entered in IN-B, is stored in the inventory master file and automatically also saved to the other file, BKSBVEND.  The BKSBVEND file stores the many different vendors and vendor part numbers as entered in PO-L or BM-K.  Deleting an entry from PO-L or BM-K will NOT remove that vendor as Primary Vendor if they have been so designated.
 
What has been happening (and reported on a couple of other threads) with increasing frequency is that some or all of the data is being deleted from BKSBVEND.  Unfortunately, we can not determine when, or how.  There have been fingers pointing at the update process but the update does not even open the BKSBVEND file.  And others have had it lose data out of the blue with no update involved.  Some Evo users and some Classic users and no discernable pattern.  
 
So what you need to do is keep a backup copy of BKSBVEND handy because you can restore that file by itself without affecting any other transactions or other detail.  Debbie, you can restore an older copy rather than re-enter all the information.  And everybody, pay attention.  If we can figure out what is making it blow up, we can fix it.

Yes, there was a problem that was fixed but this is something new.  It seems to be update related but we can't figure out how or why.

Quote from Lenette on 03/28/07 at 15:04:26:

 
I have had to delete the PRIMARY VENDOR entry in IN-B for this reason. The part #'s are in SBVEND but do not print on the PO. This doesn't always happen, but I found that deleting that entry worked..... I found this prob at the end of last year

I have installed all the fixes, and we still can't enter Purchase orders.  With the new T7POA.RWN, can't event enter PO's, vendor info doesn't pull through at all nor does it issue a new PO#.
 
When will there be a fix?