Professional Documents
Culture Documents
1 Página 1 de 4
E1: OMW: How to Transfer Objects from Production (PD) to Prototype (PY) then to
Development (DV) (Doc ID 662248.1)
In this Document
Goal
Solution
References
APPLIES TO:
GOAL
How can I copy the object specifications from my Production (PD) path code to my Prototype (PY) path code
and then to Development (DV) path code?
SOLUTION
The following steps shows an example of how Central Object specifications of an object can be transferred from
PD to PY and then to DV using existing Project Statuses that are available in the Object Management
Configuration application (P98230). This example is for UBE and UBE version objects. A similar method can be
applied for other object types.
2. In OMC application, choose Constants. Set the "Initial Project Status for all new projects" to 11. Save the
Constants settings.
3. In OMC application, choose Activity Rules. Select the root status 11. For the grid row where To Project
Status is 40-Production Development, change "User/Role" from "Admin" to a User ID or Role that is allowed to
Advanced Project Status from 11 to 40 in OMW. In this example, the keyword *PUBLIC is used. Click OK to save
settings.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ew3tzgckm_40... 26/05/2015
Document 662248.1 Página 2 de 4
4. In OMC application, choose Activity Rules. Select status 40 to 40. For the grid rows where Object Type is UBE
and UBEVER, change the "User/Role" from "Admin" to a User ID or Role that is allowed to perform Get/Check-
Out/Check-In actions in OMW for the 40-Production Development Project Status. In this example the keyword
"*PUBLIC" is used. Click OK to Save.
5. In OMC application, choose Activity Rules. Select status 40 to 41. For the grid rows where Object Type is UBE
and UBEVER, change the "User/Role" from "Admin" to a User ID or Role that is allowed to perform Transfer or
Delete actions in OMW when project status advances from 40 (PD) to 41 (PY). In this example the keyword
"*PUBLIC" is used for the "03-Transfer or Delete" action. Click OK to Save.
6. In OMC application, choose Activity Rules, highlight on the root status 40 and click the Select
button. Change User/Role from "Admin" to a User ID/Role/*PUBLIC for the 11, 40 and 41 statuses. In this
example *PUBLIC is used. Click OK to save.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ew3tzgckm_40... 26/05/2015
Document 662248.1 Página 3 de 4
7. In OMC application, choose Activity Rules. Select status 41 to 42. For the grid rows where Object Type is UBE
and UBEVER, change the "User/Role" from "Admin" to a User ID or Role that is allowed to perform Transfer or
Delete actions in OMW when project status advances from 41 (PY) to 42 (DV). In this example the keyword
"*PUBLIC" is used for the "03-Transfer or Delete" action. Click OK to Save.
8. In OMC application, choose Activity Rules, highlight on the root status 41 and click the Select button. Change
User/Role from "Admin" to a User ID/Role/*PUBLIC for the 40, 41 and 42 statuses. In this example *PUBLIC is
used. Click OK to save.
1. Go to OMW application (P98220), add a new project. The initial project status should be 11.
3. Add the objects (e.g. UBE Template and its Versions) into the project.
6. Advance the project from Status 40 to 41. The object specifications is now copied from Production path code
to the Prototype path code.
7. Advance the project from Status 41 to 42. The object specifications is now copied from Prototype path code
to the Development path code.
As the default P98230 activity rules are set up for a ADMIN role, the above steps shows how to change the
ADMIN role to *PUBLIC role or another valid user or role in the system so that the user can promote objects
from PD to PY and then to DV path code. Another method is also available which allows you to use the
default standard transfer activity rules in the system directly, is to add a Role "ADMIN" in the User Profile
application (P0092). Next, in Work with Role Relationships application (P95921), assign the Role ADMIN to
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ew3tzgckm_40... 26/05/2015
Document 662248.1 Página 4 de 4
the sign-on user who will be working in OMW. You will need to re-login to the fat client in order for this
change to take effect.
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join
or start a discussion in the Design Tools & Output Technologies - JDE1 Community.
To look at upcoming or archived Advisor Webcasts please see Advisor Webcast Details Document
1450327.1. If your topic is not currently scheduled please suggest it.
REFERENCES
NOTE:1556649.1 - E1: OMW: Standard Promotion Life Cycles in Object Management Workbench (P98220)
Didn't find what you are looking for?
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ew3tzgckm_40... 26/05/2015