gerd_renz3
VIP Member
Jeff,
I have always wondered why JDEdwards promisses that these kind of changes to
a standart objects would be preserved. Here's my theory why this will not
work and why JDE still believes (writes in their documentation) that it
does.
Prior to Xe there used to be Upgrades and Updates. An Upgrade was a major
version change like B732 to B733. An Update was a change in cume level, like
B733.1 to B733.2. Other then that, upgrades und updates were technically
very different.
In Updates, a new Pristine set of Central Objects was installed and then the
object merge was Pristine Objects over Your-Central-Objects, say Central
Objects -CRPB733. If you had an extra object in a standart programm, you
essentially had some extra lines of specs in the F98750, F98751 Central
Objects tables. In the above merge, new lines substitute old lines, but your
custom code lines in the spec table did not get overwritten. Thats why such
objects might(?) have been preserved.
Now, Upgrades are different. You would install a new set of Central
Objects - PY7333, then mark (select) the objects that you wanted to merge.
The merge process would attempt to merge all objects you marked from Central
Objects - CRPB733 to Central Objects - CRPB7333, your new pathcode. As far
as I know, one cannot merge customized standart objetcs in upgrades. I
opened the merge function some time ago and found the condition for NOT
merging: if (syscode not between 55-59 AND objects does exist in target
pathcode). In other words, objetcs are merged if they do not exist in the
target or if their syscode os 55-59. So your standart objetcs never make it
and I know of no merge process, that merges only the custom part of your
object.
Summing it up: I think the part that promisses to maintain the customization
of o standart object is a leftover (copy paste) from some old upDATE manual.
They should upGRADE the manuals as well.
Hope I this helped.
Cheers, Gerd
-----Mensagem original-----
De: [email protected] [mailto
[email protected]]Em nome
de jwhite
Enviada em: segunda-feira, 3 de dezembro de 2001 16:37
Para: [email protected]
Assunto: Custom Mods and XE Updates
We have made minor modifications (like adding a column to a grid) to
standard JDE applications. According the JDE documentation, these changes
should be preserved during an upgrade. We are upgrading from XE Update 1 to
XE Update 3 and are finding that these modifications are missing or
incorrect after the merge. Has anyone else run into this? Thank You.
Jeff White [email protected]
Orlando Utilities Commission - XE Update 1 SP16 HP9000/Oracle 8.1.6
--------------------------
I have always wondered why JDEdwards promisses that these kind of changes to
a standart objects would be preserved. Here's my theory why this will not
work and why JDE still believes (writes in their documentation) that it
does.
Prior to Xe there used to be Upgrades and Updates. An Upgrade was a major
version change like B732 to B733. An Update was a change in cume level, like
B733.1 to B733.2. Other then that, upgrades und updates were technically
very different.
In Updates, a new Pristine set of Central Objects was installed and then the
object merge was Pristine Objects over Your-Central-Objects, say Central
Objects -CRPB733. If you had an extra object in a standart programm, you
essentially had some extra lines of specs in the F98750, F98751 Central
Objects tables. In the above merge, new lines substitute old lines, but your
custom code lines in the spec table did not get overwritten. Thats why such
objects might(?) have been preserved.
Now, Upgrades are different. You would install a new set of Central
Objects - PY7333, then mark (select) the objects that you wanted to merge.
The merge process would attempt to merge all objects you marked from Central
Objects - CRPB733 to Central Objects - CRPB7333, your new pathcode. As far
as I know, one cannot merge customized standart objetcs in upgrades. I
opened the merge function some time ago and found the condition for NOT
merging: if (syscode not between 55-59 AND objects does exist in target
pathcode). In other words, objetcs are merged if they do not exist in the
target or if their syscode os 55-59. So your standart objetcs never make it
and I know of no merge process, that merges only the custom part of your
object.
Summing it up: I think the part that promisses to maintain the customization
of o standart object is a leftover (copy paste) from some old upDATE manual.
They should upGRADE the manuals as well.
Hope I this helped.
Cheers, Gerd
-----Mensagem original-----
De: [email protected] [mailto
[email protected]]Em nomede jwhite
Enviada em: segunda-feira, 3 de dezembro de 2001 16:37
Para: [email protected]
Assunto: Custom Mods and XE Updates
We have made minor modifications (like adding a column to a grid) to
standard JDE applications. According the JDE documentation, these changes
should be preserved during an upgrade. We are upgrading from XE Update 1 to
XE Update 3 and are finding that these modifications are missing or
incorrect after the merge. Has anyone else run into this? Thank You.
Jeff White [email protected]
Orlando Utilities Commission - XE Update 1 SP16 HP9000/Oracle 8.1.6
--------------------------
