Sage 100

Data Conversion Error - ERP 100 from v4.20 to v4.50 PU#3 - All modules (AR,AP,GL,IM,SO, and BR) coverted with no errors. When I look in the v4.50 data folder POxxx the reported missing file PO_PurchaseOrderHeader.M4T file is there. I searched Atlas but came up with nothing. Any Ideas?

Don't know if this is relevant any more but you have MAS90 in the path twice. I know that used to be a problem...

@ThereseLogeais I always thought that you could have MAS90 included as part of a level - like \SAGE\MAS90v450\MAS90\. As long as you never had MAS90 twice in the path - like \MAS90\SAGE\MAS90\

Do the migration or conversion logs hold any clues?

I looked in both the Migration Log and the Activity Log Report. The only thing I found was a duplicate of the error message in the Activity Log Report.

Have you tried converting another company with PO, e.g. ABC or a backup company?

I do have another company to convert - one with less activity - I received the same error message for PO - all other modules converted.

Here's another idea - can you open that file through DFDM?

Regarding the MAS90 in the path, I just stay away from it. Akin to having less than three characters for the user code. You get burned so infrequently you waste too much time figuring out. I just stay away from it. Use M90 or MAS instead.

@ThereseLogeais No I get an error message when I try to open the PO_PurchaseOrderHeader.M4T file with DFDM for either company. In looking at the POxxx directory for both companies only three files at the 4.50 level were created PO_PurchaseOrderHeader.M4T, PO_VendorPurchaseAddress.M4T, and PO_VendPurchAddressListingWrk.M4T. Was the PO module brought into BF in version 4.40? Should I try to convert to level 4.40 and then to level 4.50?

@JeffSchwenk I guess in the near future I will be using ERP or ERP100 or something other than MAS90 in my directory paths.

Yes it was but so was IM. Worth a shot though.

@JimWoodhead I know you installed the alpha version of 2013 from Summit. Does it still install to a MAS90 directory? I've been wondering...

@MichaelMcDonald Did you make sure the PO directory files are all there and when you pull the data over did it bring all the PO files for the companies?

Look to see if there is a bad record in the table in 4.2. I have experienced conversion problems when one or more tables had problem records, especially when it is hte first record.

@DianeRuth Yes it appears that all the v4.20 files were migrated (for both companies) to the 4.50 system but the PO conversion was halted right after it started. @GeneUlrich The PO_PurchaseOrderHeader.M4T file did not exist in version 4.20. Thanks everyone for all your ideas.

I think Gene means rebuilding PO1 in 4.2.

Right. Bad records in the equivalent file in 4.2. In this case the likely file would be PO1.

@GeneUlrich I will rebuild all PO Key, Index and Sort files in version 4.20 in both company codes and re-migrate and try the data conversion again.

UPDATE: I have never ran into this before. The client I was upgrading from 4.20 to 4.50 had two SAGE Extended Solutions - Alt Unit of Measure - IM-1038 and PO1033. The client will not need these two enhancements in version 4.50. So when I upgraded from 4.20 to 4.50 the migration program displayed a warning - two MD enhancements existed in version 4.20. Like many times before, I took note and continued on with the upgrade. Long story short - with ES PO-1033 a special PO_LevelConversion.pvc program has to be subsituted in version 4.30 because ""The Extended Solution created extra record lines in PO2 that are now used in version 4.30"". So I had to upgrade to version 4.30 using this special PO_LevelConversion.pvc program and then upgrade again from 4.30 to 4.50. The inventory module (w/ ES IM-1038) converted just fine without any special conversion program. Why didn't SAGE include the logic to convert the PO files in the PO_LevelConversion.pvc in version 4.50? Another case of TLTF? How many other Extended Solutions require a ""special"" conversion program when upgrading and the Extended Solution is NOT included in the upgrade?

Just in case someone else needs to deal with this issue - The ATLAS searchable document code is: 110-500527. The old Knowledgebase Res ID is:500527

What does ""TLTF"" mean? Can't find it on my acronym translator.

Too Lazy to Fix..............

Thanks - no wonder I couldn't find it.

It is exclusive to 90Minds.........