• 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!

E9.2 Promoting/Transferring UDOs from PY to PD - HELP

jgagnon

Member
I am trying to understand the process necessary to promote (or transfer, not clear on the nomenclature) a User Defined Object (UDO) (or a whole collection of them) from where it was developed on the PY system to the production (PD) system.

From what I've seen and read, I need to create a project in the Object Management Workbench (OMW), add whatever objects I want to promote to it and then process some sort of transfer.

I have read through lots of documentation on the Oracle site with respect to UDOs and the OMW. There appears to be a whole ecosystem of permissions and roles and statuses, and it's not clear what it all means as a whole. I suspect that at least a bare minimum of set up and configuration was performed on our JDE system (well before my time on the project), but really not sure what capabilities are enabled.

In any case, I decided to try a small experiment. By the way, I have the equivalent of system admin privileges on both the PY and PD systems.

On my PY system, I went into the OMW and created a project. I added myself with the Developer role - this seemed important. I added one of our existing UDOs (an E1 classic page, if it matters) to the project and then attempted to "advance" the project to transfer it to PD. I'll admit, I really don't know what I should be doing (hence this post). I also don't know whether the correct permissions to allow all of this are in place.

I then logged onto the PD system and tried to see if the UDO was available. Well, it's a little weird. If I go into the Work with UDOs application (P98220U) and select UDO type E1PAGE and search, not only do I see the UDO I hopefully transferred, but I also see all the other classic page UDOs I created on the PY system. How can this be? If you need to advance/transfer from PY to PD, why do they already show up on PD?

OK, I think to myself, let's see if I can access the page from the UDO design tool. Nope, it's not in the list. There's just the default "Create" to make a new one.

Hmm, let me take a look at UDO view security. So I open P98220U again, select the form exit View Security and enter my user name into the QBE and search. I see ALL of the E1PAGE UDOs I created on the PY system showing up with view security assigned to my user - on PD! On the PY system, that is true, but on the PD system? I'm very confused. To boot, none of these pages show up on my PD home page (they do on PY). It's like they're there, but really they're not.

Does anyone have suggestions on an up-to-date tutorial (or what have you) that goes over OMW projects and their lifecycle? Does anyone have information on what permissions/settings should be in place in the OMW configuration to permit what I'm trying to do here? As I said, I've read a lot of the Oracle documentation, but it's a bit overwhelming. I've also read items found on JDETips and other sites, but they are either out of date (you can tell), or they don't go into the level of detail I need. It's easy to get lost in the sea of stuff and not really know what is the "right" way to do it.
 
Last edited:
Hello,

I went through this process this week and it worked well for me.

Here are the steps I followed:
  1. From the PY env., open the web OWM (P98220W).
  2. Create a new project.
  3. On the "Project Members" tab, make sure your user is assigned with role 06 - PVC Administrator.
  4. In my case, the project was initially at status 21. To promote the UDO from PY to PD, it has to be at status 28 and then move to 38. So I had to move my project from 21 to 26 and then from 26 to 28. You may skip this step if your project is already at status 28.
  5. Add the UDOs you wish to promote.
  6. Check out and check in all UDOs. This step is required to ensure your project has the token for all objects.
  7. Advance the project to 38.
  8. Go to your PD env. and validate that the UDOs are there (P98220U). They should be in status 07 - Pending Promote.

I used this reference to figure it out:

Hope this helps.
 

jgagnon

Member
Hello,

I went through this process this week and it worked well for me.

Here are the steps I followed:
  1. From the PY env., open the web OWM (P98220W).
  2. Create a new project.
  3. On the "Project Members" tab, make sure your user is assigned with role 06 - PVC Administrator.
  4. In my case, the project was initially at status 21. To promote the UDO from PY to PD, it has to be at status 28 and then move to 38. So I had to move my project from 21 to 26 and then from 26 to 28. You may skip this step if your project is already at status 28.
  5. Add the UDOs you wish to promote.
  6. Check out and check in all UDOs. This step is required to ensure your project has the token for all objects.
  7. Advance the project to 38.
  8. Go to your PD env. and validate that the UDOs are there (P98220U). They should be in status 07 - Pending Promote.

I used this reference to figure it out:

Hope this helps.
I tried to follow the steps provided, but got an error when attempting to advance from 21 to 26. I've attached screen shots to show the process from project creation to the error. I also reviewed the URL you included. It looks like scenario 2. I used data browser to look at table F98700R and my UDO appears to be there, so not sure what else could be wrong.
 

Attachments

You should advance the project to status 28 (21-->26-->28) before adding any UDO in it.
The other steps are looking good, except maybe the step "Project_Users" where, in my case, I did keep only the line with role = "PVC Admin".

I encountered the issue with the table F98700R: I could see 2 lines for the same UDO, 1 with env. DV920 and 1 with env. PY920.
I deleted the record with DV920 (but saved it before, just in case) and then I could promote it from PY to PD.
 
Last edited:

jgagnon

Member
You should advance the project to status 28 (21-->26-->28) before adding any UDO in it.
The other steps are looking good, except maybe the step "Project_Users" where, in my case, I did keep only the line with role = "PVC Admin".

I encountered the issue with the table F98700R: I could see 2 lines for the same UDO, 1 with env. DV920 and 1 with env. PY920.
I deleted the record with DV920 (but saved it before, just in case) and then I could promote it from PY to PD.
Ah ha!

Yes, that worked now.

I then logged in to the PD system and found the UDO in status 07. I Approve/Shared it. I then logged out and back in and it was visible on my home screen. I already had view security for it on PY, so it also now shows up on PD.

Thank you very much.

BTW, having myself as a user with the OMW Developer role appears to have had no negative effects.
 
Top