Past PO Header not converting correctly during 7.8 upgrade

Hi, I've spoken to support about this, but they haven't seen it reported, but they suggested I also check here. During any express upgrade I've done from 6.6 to 7.8, the past PO header file does not seem to get upgraded. None of the changes to the file are present, i.e. PO number is still a length of 6, PO numbers are not in separate fields, etc. The only thought I have on my end, is maybe some modification or larger record size is causing an issue. These are accounts we previously didn't support, so I'm not as familiar with them. I did notice a larger record size on POPAST then another 6.6 system I checked, but I also visually compared the file and didn't see any additional data present, but I may have missed something... Has anybody encountered this?? I did similar conversions to 7.7 and didn't have this problem...

0911060553270289.pdf

Find more posts tagged with

Comments

skyler-williams

I had this same issue. Fixed POPASH; PO num field was only 6 characters, expanded it to 12 with 6 blanks in front. Then access to all the line items in POPASL worked perfectly.

salbritton

I just ran a FACTS 6.6 to 7.8 upgrade (last night) with the 7.8.5 incremental applied, and this is still an issue. The PO# in POPASH did not get properly padded to 12 characters.

0712050808501819.doc

jeff-christie

Thanks Guys, at least it's reassuring to know it just wasn't me!! I actually found it to be more than just the PO number length, all changes to the past header were not present, like they broke out the numbers (total amt, freight) into separate fields, they just broke out the ship to address into separate fields as well in 7.8. None of that was there. I ended up writing a fix program to go through the header and apply all the changes through the years, if anyone's interested. But just yesterday I think I discovered a side effect, it looks like in ICRCPT it couldn't load the PO vendor into the file during the upgrade (ended up defaulting to primary vendor) I'm guessing because it couldn't find the past po header when loading ICRCPT. I had opened an incident on this when I first discovered this, I'll revisit and see if anything can be done/tested on the Infor end before I have to run another one of these!

salbritton

Bob,

I'd be interested in that fix program if you're willing to share.

Thanks.

Brad Kraft
bkraft@dsa.us

Legacy Contributor

Bob, John and Brad - I have submitted a defect for this and created KB# 1523333. All 3 of you are signed up to receive updates for the KB. You will be notified via e-mail when a fix is available.

Legacy Contributor

i've been looking at the code, and the only thing i see that seems suspect is line 210 of UPPOPASH - it should be

i also think that line 635 should be goto *return, not goto SET_COUNTRY.

can either of you tell me whether those changes solve the problem?

salbritton

Tim, unfortunately, that would require a re-upgrade of all the data that took 8 hrs to complete. If there's some way I can reasonably just re-upgrade the only POPASH, please contact me offline and I'd be willing to make the changes and try it for you.

Brad

skyler-williams

Bob, your comments got me to look at my recent conversion a little more closely and I find that the REF# is missing, as is the address of the SHIP-FROM. I have no idea what else may be missing.
I, too, as Brad is, am interested in your fix program if you're willing to share.
John Ford jford@dsa.us

v10 Cust Day - 10.1.0 User Experience.pdf

thamm

Bob

If we could get a copy of your fix program as well that would be great. We have checked out past upgrades, and have notices that the 7.5x or later versions do not seem to have a problem with the upgrade. However, our 6.7 upgrade customer did run into the same issue.

Thanks !

Tammy Hamm
Aktion Associates

Copyright © 2025 Infor. All rights reserved.