Building a update Package with custom Mods.

I have created custom modifications in OMW (DV7333) checked in the objects,
retained the token and promoted to a status of 26 (automatically moved to
PY7333). Now I assemble a package (an UPDATE). I have UBE's (R55*)as a
part of the build with their respective versions (RS000*). When I add the
UBE's to the package I do not see the respective version. The version has
been promoted as well and I can check them in and out. I have spoken to JDE
but they are not sure why this does not work, they have not tested this
process as of yet to validate if it works as they say it should. We are on
SP13 and I have applied ESU JD8430. AS400 as ES.
Thanks Scott Whipple

Scott, I have come across this as well. I don't know if you are building
the package just for that object...or for the project that the object is
in....but I always make sure that whatever environment I am building for is
the current environment I am signed into...then when I build the package
make sure that when you choose your objects you are actually choosing a
project, then when you click select, it will pull up each available version
for each object in that project. Also, verify your Object Management
Configuration making sure your event rules include versions and that the
paths are correct for the 26 status. Also, make sure there are no errors in
the OMW logs pertaining to that project during promotion.
Hope that helps,

Ben Klahm
OW Xe SP15_006 AS/400 CO

Ben:

When you build packages don't you use the DEP7333 environment? Or are you
saying that you log into a specific environment on the Deployment Server?

Joy

Joy:

No. and No. Always log into the deployment server in the DEP7333 or
JDEPLAN environments and use it mainly for ESU downloads & upgrades. But
when it comes to normal package builds...I usually am logged into our PY7333
environment on our CNC workstation ...dedicated package build machine
(single 450 processor). ...and for whatever reason it is faster at
building packages than our dual 733 deployment server....still have not
figured that one out yet.

Re: RE: Building a update Package with custom Mods.

I have found that if I build the package while logged into the environment that I am building for, it will cause some file locking errors during the package build.
So our solution is to log into the appropriate environment and define the builds (to make sure we can see all of the objects). Then we log into the deployment environment to actually submit the builds.
I don't know if this is necessarily the best way but it has worked fine for us for a while now.
Of course we are on 7.332 not XE so it may be different now?

B73.3.2 SP 11.1_UPKG, NT, MS-SQL 7.0, WIN2K/Metaframe 1.8a & Fat

Jeff Hill
IS Division Manager
Yamazen Inc.