Back promoting Objects

Good day Jdelist,

Can someone tell me whats the best way to back promote objects from PD7333 to PY7333.

Thank your assistance in advance.

I would create a project in omw and advance the empty project to a status
38. Then log in the PD environment and move the object in the project. You
must also make sure that you have the OMC setup to correctly allow the
object to be transfered back to PY. Under the Activity Rules as an examble
you would need to have under the status 38, a status of 28 with the Object
Transfer Rules set up for the object type.

Some Examples:

*PUBLIC APPL OL Application PD7333 PY7333
*PUBLIC APPLVER OL Application Version PD7333 PY7333
*PUBLIC BSFN OL Business Function PD7333 PY7333
*PUBLIC BSVW OL Business View PD7333 PY7333

Joy

If its only a few number of objects, a nice way is using OMW. I'm not sure if sombody who setup our system installed the activity rules or they are standard in OneWorld.

Start at Project Status 11 goto 40 (Production Development). Grab your objects into your project and promote to status 41 (Xfer Production to Prototype)

OneWorld Xe Update 2 moving to Update 5
SP 18 & B_1 moving to I_1
Enterprise Server - Sun Solaris / Oracle 8i
Clients - Windows 2000 / Citrix Metaframe xp
Deployment Server - Windows 2000

Those statuses are standard OW.

Thank you griffithsc

That's one way and I guess this is more of a question...

If it's only a few objects and a one-time deal, can you do a selective GET
(OMW row exit not middle-column icon) from the PD path code and check in to
PY?

Please advise.

Regards,
Gerald





CNCTech
<nmkassim@teluspl To: Gerald Kastanek/Toronto/IBM@IBMCA
anet.net> cc:
Sent by: Subject: Back promoting Objects
owner-jdelist@jde
list.com


05/16/2002 11:41
AM
Please respond to
jdelist





Good day Jdelist,Can someone tell me whats the best way to back promote
objects from PD7333 to PY7333.Thank your assistance in advance.
--------------------------
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=34610
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list / forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+

I agree. Setup some Transfer Activity Rules pushing your objects from (38)
PD7333 to (28) PY7333.

Perhaps I have missed the point of this post, but surely the Object will already be in PY7333, if it has been supercede then no amount of messing with OMW statuses will get the object back into PY7333 from PD7333. More drastic measures are required. the simplest is to set up OMW rules to allow a Checkout from PD7333 followed by a Checkin to PY7333, in between you must update the Object - to give it a more recent date, otherwise the checkin will do nothing, you cannot replace a Newer object with an Old one.

Hope this helps.

Now I am more confussed.

I think that what everyone is saying is this:

The normal progression of promotion through Oneworld starts in DV and flows
to PY and PD respectively.

An object is changed in DV and now has the most recent change date/time
stamp.
Promotion through OMW uses the existing Activity rules to copy the source
over top of the older PY source (21 to 26)
Then promotion again through OMW again uses the activity rules to copy the
PY source over the older PD source (28 to 38).

If you want to back-promote objects you need to create special activity
rules to copy the source code from PD back to PY.

However the point was brought up that if the source in PD is OLDER than the
source in PY, OMW will not copy older source on top of newer source. So
even if you create the activity rules to go from PD to PY the copy may not
happen if the date/time stamp in PD is older than in PY.

I think what you have to assume for a back-promotion to work is that the
source in PD is newer than the source in PY.

I hope that helps. Please correct me if I've misunderstood the thread.

Regards,
Gerald.






CNCTech
<nmkassim@teluspl To: Gerald Kastanek/Toronto/IBM@IBMCA
anet.net> cc:
Sent by: Subject: Re: Back promoting Objects
owner-jdelist@jde
list.com


05/17/2002 11:41
AM
Please respond to
jdelist





Now I am more confussed.
--------------------------
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=34681
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list / forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+

By the way...

Can anyone answer/comment on my last question??

If you want to get source from another environment can you use the
selective GET from the Row Exit in OMW?

ie: Get from PD to update your local specs and then Checkin to PY
(assuming the check in is allowed in PY (status 26/28)).

Please advise. That might negate the whole back-promotion stuff.

Regards,
Gerald.






CNCTech
<nmkassim@teluspl To: Gerald Kastanek/Toronto/IBM@IBMCA
anet.net> cc:
Sent by: Subject: Re: Back promoting Objects
owner-jdelist@jde
list.com


05/17/2002 11:41
AM
Please respond to
jdelist





Now I am more confussed.
--------------------------
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=34681
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list / forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+

I think this will accomplish what you want better that backwards movement of the objects.

Check the object out in PY if it's allowd, then do an advanced GET on the object choosing PD as your path code; then to verify that you have the correct specs do a ER compare on you local specs against you PD specs then check the object back in.

You might also want to do the same in DEV so that your path codes will have the correct specs. Then you can safely promote the objects to be.

If your OMW rules does not allow checkin/checkout in PY then you can temporarily change them or add a few that allow checkin/out just for yourself.

Hope this helps.

I think this was mentioned previously, but you are essentially right. You can use the row exit Get and selectively update your local specs from PD.

As for the check-in to PY, you probably will have to create a custom status that allows check-ins to go to PY instead of DV. As a consequence, you would also have to allow check-outs from this status. Hmm, I guess that means that the status code would handle all of it. You could set it to check out from PD, then check in to PY ...

So the flow of events would be:
- create project
- change status to 21
- add object
- change status to <new status>
- OMW rules for this status will handle check-in/out from/to your preferred locations