• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Package Builds on Projects

lessardj

Well Known Member
When we try to do an update package build, we cannot see our project names; we can only pull individual objects into the package. Are others out there able to assemble their packages using project names? If so, do you use a particular naming convention? Perhaps we have something in our setup that is not allowing us to build on projects, but I am not sure where to look.

Thanks in advance for any help you can give.

Judy.

Xe, ES=AS/400 V4R5, CO=AS/400, Deployment=AS/400 INS Card, Thick & Citrix Clients
 

DRezanka

Reputable Poster
Judy,

I agree that I'd like to be able to build by project. I'd also like to be able to checking all objects for a project (at once).

When you select the individual objects for the package, you are able to enter the project name as QBE. Does that help?

Regards

Doug
dougrezanka@eaton.com

Xe SP13.1, AS400 V4R3, CO-Oracle806, Co-A73c10, Citrix, NT JAS
 

sean_gilbert

Well Known Member
Hello list,

Please keep in mind the following:

You can only create packages using the name of the project which the object
was last updated in.
Example:

Modify P4210 in Project1 THEN modify P4210 a second time but within
Project2
If you build a package against Project1 it will not pickup P4210 since it
is now associated to Project2.


By doing a full checkout of Project1 then checking it back in you can
re-associate all its objects to Project1 THEN package build against
Project1.


Sean Gilbert
JDEdwards Consultant
PricewaterhouseCoopers
Montreal

Tel: 514.205.5000 x3619
Fax: 450.655.0163



DRezanka
<dougrezanka@eato To: jdelistml@jdelist.com
n.com> cc:
Sent by: Subject: Re: Package Builds on Projects
owner-jdelistml@j
delist.com


04/26/2001 01:27
PM
Please respond to
jdelist






Judy,

I agree that I'd like to be able to build by project. I'd also like to be
able to checking all objects for a project (at once).

When you select the individual objects for the package, you are able to
enter the project name as QBE. Does that help?

Regards

Doug
dougrezanka@eaton.com

Xe SP13.1, AS400 V4R3, CO-Oracle806, Co-A73c10, Citrix, NT JAS
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat
=&Board=OW&Number=9846
 

ben_klahm

Active Member
Judy,
I build 95% of my packages from projects...just using the QBE line...we do
have a naming convention....RPxxxx: reports.....INxxxx Interfaces....ENxxxx:
enhancements....CNxxx: Conversions....etc. It Is CaSe SeNsItIvE...so I
usually type in CN004* for example and that will pull up all of our
projects starting with CN004. Don't forget OMW promotion making sure all
that has worked too!!!
Hope that helped,

Ben Klahm
Xe SP15_006 AS/400 ES CO
 

pwplus

Member
Hello,

I don't have an answer but let me add some more to the conversation.

I am new to JDE and haven't created many packages but the update packages I
have created happen like Judy describes with 1 exception. We are in the
middle of implementation and often we will promote a project such that
objects are transferred from DV to PY to PD. After promotion, I then create
update packages for PY containing the objects which were transferred (nobody
is using PD much yet so I haven't created any update packages for it). When
creating an update package for PY containing objects which have already been
transferred to PD, I have found that I have to add each object to the
package by QBE'ing for each individual object. The exception occurred when
I created a package which contained objects which had not yet been
transferred to PD, i.e. the project had been promoted such that the objects
had been tranferred from DV to PY only. I was able to QBE on the project
name successfully during the update package creation in this case.

Regards,
Pat

----- Original Message -----
From: lessardj <lessardj@timken.com>
To: <jdelistml@jdelist.com>
Sent: Thursday, April 26, 2001 6:47 AM
Subject: Package Builds on Projects


names; we can only pull individual objects into the package. Are others out
there able to assemble their packages using project names? If so, do you use
a particular naming convention? Perhaps we have something in our setup that
is not allowing us to build on projects, but I am not sure where to look.
Clients
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=9
827



Patrick Plusnick
OneWorld/XE SP 14.2, ES AS/400, DS NT 4, JAS NT 4
 

rgz

Active Member
We can see our project names no problem in update package builds. Naming
doesn't seem to matter.
When you click find on the form that searches for objects/projects in
package build, the F9861 is being read. A field in that table stores the
project name - can't remember off hand which one (SIMODCMT maybe?).
Check this field is being populated with the project name - you could also
manually modify the field for one object as a test.
Also, check the individual OMW_* fixes for the SP level you're on.


hanks in advance for any help you can give.
 

HSICKEL

Well Known Member
Hello Judy,

I build several update-packages where I included the project. There was no
naming convention...
Herbert
On 26 Apr 2001, at 6:47, lessardj wrote:

that is not allowing us to build on projects, but I am not sure where to look.
 
Top