B732 to XE Upgrade



We are in the process of upgrading from B732 and have experienced a quite major problem. In short ALL custom developments (system 55 objects etc) are not being loaded correctly in XE. High Level data for 55 objects like object names are being loaded but the underlying detail specifications are not. In other words the TAM files RDASPEC, FDASPEC and so on are not being updated whilst the OMW files are. We have been in touch with JDE Denver who sent an internal memo detailing some possible solutions - they are aware of the problem but haven't yet found a suitable resolution.

Has anyone else experienced this problem and found a solution? Before embarking upon our upgrade we asked JDE (UK) to provider a reference site for another client who has upgraded from B732 to XE successfully - as they have yet to reply maybe we should have realised problems awaited us :)



B7322 sp12.2. AS/400 V4R4. NT Deployment Server.
AW: B732 to XE Upgrade


We have upgraded from OW 7322/SP12.2 to Xe/SP13 and in my opinion -
successfully in a sense how the upgrade is designed. Of course, all the
customization that are not supported by an upgrade as form customizations or
changes in vanilla JDE event rules of APPL or UBE have not been upgraded.
But this is how is designed.
Please, clarify your problem in more detail.


-----Ursprüngliche Nachricht-
Re: AW: B732 to XE Upgrade


The problem we've encountered is that none of our new custom developments have been upgraded - system code 55 objects. The F98305 and F983051 tables have been updated with records referencing 55 objects, but the spec files F98760, F98761, F98740, F98741 etc have not. We have, eventually, managed to speak to someone at JDE who is aware of this problem and has given us a possible solution. Not sure at the moment how successful this will be.

Did your upgrade run smoothly? Did all of your custom objects (not JDE native) upgrade correctly?



B7322 sp12.2. AS/400 V4R4. NT Deployment Server.
Did you run the Specification Merge Selection application ? Did any of the specification merges produce error logs ?

I have upgraded B7322 to Xe with only a little more difficulty than B733x to Xe. Have you tried to perform the upgrade yourselves or was it with a Consultancy/JD Edwards ?

It can be costly if you are in production if you do not use assistance from someone who has in-depth experience of the upgrade procedures. The upgrade is not as "simple" as JDE would hope it is, and very few customers make the leap from B732x.

My hope is that you used a sandbox environment to upgrade. Without hopelessly advertising - our transporter will be available soon to help fix issues you have encountered.

Jon Steel
Xe Upgrade Specialist

ERP Sourcing
[email protected]
Re: AW: B732 to XE Upgrade

Roland, where are your Central Objects located? I'm wondering if it makes a difference if it is on AS/400 vs. SQL.

C Ho

Intermediate Programmer/Analyst
Dundee Realty
B7322 SP 12.4
AS/400 coexistant with SQL Server 7.0
Sandbox: installing Xe
AW: AW: B732 to XE Upgrade


Check with Specification Merge Selection P98401 if all objects of the
upgraded pathcode have the modification flag set to 'C' and the merge option
set to '1' and all your object must have a system code between 55 and 59.
Your referenced tables are linked to UBEs and I can confirm that they were
fine. Some minor modifications had to be made but in general according to
the upgrade rules.


-----Ursprüngliche Nachricht-
Re: AW: AW: B732 to XE Upgrade

We have followed the instructions JDE provide for the Upgrade to the letter. Spec Merge Selection ran correctly and all custom developments have a valid system code (55). We have come to one possible conclusion that our hardware setup is somehow causing problems so if anyone has run the B732 to Xe Upgrade on an AS/400 then we want to hear from you. Our NT Deployment server runs SQL 7. Granted not many clients have done this but someone must have! We were the second site in the UK to go-live on OneWorld (back on B731) hence why we are still on B732.


B7322 sp12.2. AS/400 V4R4. NT Deployment Server.