Sage 100

Shiptos - new client on 4.50 - shipto lookup doesn't work anywhere. Tried custom, tried standard. Tried custom via the User Lookup thing. Tried partial lookups. Can't even look them up in Customer Maintenance - we are totally screwed EVERYWHERE. I typed a new code in, saved it - lookup shows nothing. This is PU2 for 4.50. I'm going to go sob somewhere - we go live Monday.

I've had this issue before - can't for the life of me remember the fix. Are the ship-to codes saving in the SO_ShipToAddress table? What about changing the ship via options, Expand Modules, Sales Order, and Setup. In Sales Order Options, Click the Entry tab, Select Yes or Actual from the Use Shipping Code to Calculate Freight list. Not sure if this will help but I'll try to remember what we did to fix this.

Here's what I did - I looked up the old problem with Alias lookup. It advised to do this: 1.Delete the ######Z00IM_AliasItemNumber START FILTERfrom the Sy1Q03.soa file using Data File Display and Maitenance. 2.Delete the ######Z00IM_AliasItemNumber FSTART FILTER record from the SyQ04.soa file using Data File Display and Maintenance SO I did basically the same thing with the Shipto records AND IT WORKED as long as I didn't have a custom lookup. I am SCREAMING with joy right now.

This has been an issue since v4.4 PU 7 (?). For the life of me, why is it still an issue in v4.5 pU2? C'mon Sage, spend less money marketing and more money in R&D. At the end of the day, you WILL move more licenses because we are spending LESS time fixing the crap............... BTW, PU3 is available for download.............

Ok to blog?

go for it

PS - Someone else be brave and load PU3

I'm working on a MAS 200 4.3 to 4.5 upgrade now and installed PU3 yesterday. Ship To ALE working fine, so this may have been a 4.5 PU2 issue? In 4.4, copying the PU5 SY1Q*.SOA files over existing ones occasionally worked.

I also tested in ABC company, and it works on my 4.5.3.0.

It works on MY4.5.2 (not 3). Perhaps it was because this was an upgrade from 4.4? I don't know which PU it was on before I did the upgrade (I stepped into this in the middle of the process). So it wasn't working in 4.4 and the file wasn't changed in 4.5 so continued to not work.

Just received a report from client that I upated 4.4.4 to v4.4.8 last week. The ship to codes no longer work. Is it me or do others wonder why this issue hasn't been fixed yet? I first reported it when PU 7 broke it. Here it is, nearly six months later and installing PU 8 still breaks the lookup. What Sage needs to find is a service company with a motto like BASF - ""We don't create the code, we just make it better!

An update to my issue. After I forked around with the SY1Q files, it was working, or so I thought. Then after I imported all of the shiptos, I did a lookup again and it showed ALL of them in the lookup. EVERY LAST ONE for every customer, no matter what customer I chose. If I did a partial lookup, though, it worked OK. SIGH. I put the SY1Q03 and SY1Q04 from my system onto their system - still happening. Reloaded MAS. Still happening. Finally I looked at ALL of the SY1Q files (1,2,3,4) and found that all of them had extra records at the very beginning pertaining to the Shipto lookup that mine did not have. I deleted all of these records (some were B recs, some were Y recs) and then my lookup began to work as it should. One other note - the person who had been working on this conversion before me had loaded someone's BOL mod at some time. It was no longer installed, but it left a ton of records out in various places (and files, too). I don't know how it was uninstalled, but either it wasn't properly done, or the uninstall doesn't work for poop on this mod. So I don't know if some of these Shipto recs were because of it, because in some of the files there were also BOL recs at the top of the files (B recs, Y recs), too. But it works now and we're not even live yet - who could ask for a better weekend? (Spent exporting history files from Peachtree and importing them into MAS...)