Sage 100

Sage 100 v4.5 Advanced. Is it my imagination or is there no longer a rebuild for the ALE files? Installed and ran the ASI consolidation software. Went remarkably well but now the ALE does not display the division code in vendor maintenance lookup. We did turn division codes on for the consolidation. Customer divisions are displaying properly but they were active prior to the consolidation. Waiting for a call back from ASI.

Are you referring to Lookup Conversion under Library Master / Utilities? I see it on my 4.50

If it's not on the menu you can do File / Run / SWQSCR

TG it wasn't a snake!!!!! Thanks AC.

And now I get Error 42, swqscr line 7370. These #$%^& ALE files.....

Was there an upgrade from 4.30 involved here? Also which 4.50 PU are you on? If you search here on SC on ""I am doing a test upgrade from 4.3 to 4.5 on MAS 200"" this error was posted by @JohnLeonard before. I also see it on Sage City (answer unknown) for someone test upgrading from 4.3 to 4.5 where he references the Sage KB article - http://sagecity.na.sage.com/support_communities/sage100_erp/f/98/t/39726.aspx I don't know. Maybe wait for the call back from ASI.

450 MAS90 home folder - pvxwin32.exe, at prompt type: run ""sy_rebuildsystem.m4p"" will prompt to log in and then get the rebuild.

v4.5.4. Not an upgrade. Client had three separate MAS companies. Wanted to combine into one. Use the ASI consolidation program. Very function. Give that program a thumbs up. However, since they wanted to keep their vendors separate, we activated the divisions in AP. The ALE works fine in the original companies, just not in the consolidated. ASI suggested rebuilding the lookup which threw an error code. Now I will delete the custom ALE and see what effect that has. This is the worst problem so far.

Did you try running the embedded IO replacement script? We used this as one of the possible resolutions in the SO Ship Address missing in lookup

Nope, What is it?

from within MAS, File / Run / program = syzcon, at the prompt type: o=new(""sy_activation_bus"",%sys_ss) second line at the prompt type: print o'activate(""m/m"",""xxx"") The m/m = module code and the xxx = company code. '1' should be returned for successful execution of repair. I would do this for the CI and the AP modules.

EPILOGUE - I tried renaming the five ALE SOA files and replacing them with original copies but that had no effect whatsoever even after running the rebuild utility. So I restored the originals. I then opened the AP options file to verify the division code was set to yes. It was. I then scrolled down to see if there might be another field controlling this function. Field 52 - Vendor Mask - caught my eye. Knowing that the divisions were working in AR, I looked the field up in AR Options and there was a difference. The z was uppercase in AR (working) but lower case in AP (not working). So I changed the z to uppercase and tested. Success!!!!!!! I wonder how long it would have taken tech support to figure this one out? FWIW, the file layout definition for AP Options doesn't even list that field. Double checked my copy of v2013 and the field is absent from the file layout definitions there also.

Good sleuthing @JeffSchwenk !

Oh you've got to be kidding me. And the answer is 4 months unless there is any customizations or mods, then 6 mo to year when another case is reporting it. :0 ;)

In looking at the circumstances, it was an issue with me not setting the primary consolidation company to use divisions. The other two companies were set up to use divisions but in the late hour on New Year's I forgot to turn on the primary company's division. The consolidation software did not stop me from proceeding thus creating the issue. I reached out to ASI today to review. Maybe they will tweak their consolidation code as a result.