Technical and Installation Discussions

[photo7589]

Hi Everyone

Customer is on 3.71 with extended solutions in SO, BR, and Paperless along with Custom Programming in IM and MRP.  They have UDF's in AR Customer Maintenance along with some in SO, PO & RMA.  Ran utilities in GL, converted (test mode), received Error 27 @ line 391 of SY_LevelConversion.PVC.  Removed the SY_Enhancements per resolution, converted, reinstalled extended solutions and custom programming.  UDF's did not come thru for any of the modules.  I see the PO90's so the PO UDF data is there but no UDF's in UDF maintenance.  AR_Customer doesn't show any fields for the UDF's nor are there any in UDF Maintenance. 

Tried rebuilding all key files and sort files, migrated & converted, again no UDF's. 

Sage recommended doing a plain vanilla install, did that, same result, so can't blame ES or CP (Custom Programming).  Sage then recommended creating and placing an add'l UDF (in 371) on every screen that had one so it forces an update.  Still nothing.

At this point, planning to export UDF info in 371, recreate UDF's in 430 and import into AR_Customer and where ever else I may need to in order to move ahead with this upgrade.

Anybody have any ideas on how to get the UDF's to come thru like they should or do I just need to take the alternative route go forward.

Thanks for any input you might have.

Nancy

[mjpolk]

Mas90 or Mas200?

Did you go live Right away or are you still in testing phase?

Did you go straight from 3.71 or did you stair step 3.71 to 4.0 to 4.3?

Did you download all updates before you imported the data from the parallele 3.71 install?

Message Edited by mjpolk on 10-29-2009 10:38 PM

[BigLouie]

Nancy:

1. Can you see the UDFs in Custom Office? 

2. Did you go into Custom Office and update the UDFs?

3. What order did you install. The normal order is

a. Install MAS

b. Install Patches

c. Install third party enhancements

d. Install modifications/custom programming.

e. Install Extended Solutions.

[VKZIMM]

A/R went to the new format, so you would have to re-create the UDF's in the new version, but the data should be there. 

The Purchase Order UDF's shoud have migrated.

So if you enter the Purchase order UDF's in your test system, does the data appear?

[photo7589]

Thanks for the responses,

MJPOLK:  MAS200, Still in test upgrade phase, didn't stair step, generally don't, have always gone direct, haven't imported data yet, still hoping for some magical answer that will bring the UDF's thru.

LOUIE: In my plain vanilla, I don't have anything but MAS200 4.30 and SU13.  I did go into Custom Office, but no UDF's to update (they are not there), even in the legacy modules.  Did run the 'update screens to current level' and 'rebuild customizer log'. 

VZKIMM: I did recreate the AR UDF's and place on screen, but even then I don't see the info in AR_Customer.  I I do see the information in the PO_90's tables, but will still need to recreate the UDF's as they don't show in Custom Office either. 

[mjpolk]

You wouldn't by any chance have the 4.3 Upgrade Guide would you?  There is a whole section that explains the proper way to handle UDF's.  If you don't have it let me know and I'll see if I can get you the PDF version. 

I'm sure you know this, but with all thebackend redesign Sage has been doing you really have to read the upgrade guide right know.  It does explain a lot and helps avoid some major issues.

[VKZIMM]

Have your tried going into Custom Office in 3.71 and updating the UDF's before the upgrade?  Maybe the data dictionary has a problem. 

I have gone from 3.71 to 4.2 and 4.3 and did not lose any UDF data.

[photo7589]

VZKimm:  I did update the UDF's in 371 prior to migrating. 

MJPolk:  While I appreciate the offer on the 4.30 upgrade guide, I have done many upgrades and have not had any problems with UDF's prior.  This one is really throwing me though. 

[VKZIMM]

In 4.3 did you update the UDF's in Custom Office before you did the Convert on the data?

It's Friday!!!!!

[photo7589 · Accepted solution]

Finally figured this out (awhile ago, but realized I didn't update the community).  I happened to glance at the migration logs that I was receiving an Error 13 SY_LevelConversion.pvc F=SY1USR.SOA during system file migration.  I reinitialized the Sy1usr table security and redid the migration and now everything came thru.

Thanks for all your suggestions.

Nancy