In general, OMW is used by software developer or administrator to control the object development until end of the lifecyle.
Initially, a project will be created with status 11 or 21 depending on activity rule - P98230 . You may change the default begining status in P98230 - Constant
Development to Production
Status 11: New project pending review - 01 originator
Status 21: Programming - 02 Developer . In this stage, Object librarian and non-OL can be check out / in for developing. When checked out, object spec will be copied from DV path code central object to local path code.
Status 26: QA testing - When the object is ready to be tested in PY, it will be advanced to 26. And the object spec. from F987* table will be promoted from DV to PY as well as all objects like C, H,hxx and obj will be transfer from DV folder to PY folder on deployment server.
Status 25 : After status is advanced to 26, a PY package can be built and deployed to workstations and/or servers so that these objects can be tested in the PY environment. If any objects need to be reworked after testing, the project can be advanced back to status 25-Rework-Same Issue and then advanced to 21-Programming in which the objects can be reworked in the DV environment again. When advancing from status 26 to 25 and back to 21, there are no object transfers that occur, only a status change is happening.
Status 28 - QA Test/Review Complete
If testing of the objects is completed, the project can be advanced from status 26 to 28-QA Test/Review Complete. Again, this is only a status change, there are no object movement or transfers happening at this stage.
Status 38 - In Production
Once the objects are ready for production users, the project is advanced to status 38-In Production. When the project status is advanced from 28 to 38, OL objects are promoted from PY pathcode to PD pathcode, that is from data source 'Central Objects - PYxxx' to 'Central Objects - PDxxx'. OL objects with C components are also transferred from PY folders to PD folders on the deployment server. Non-OL objects with records in tables in Control Tables data source are also promoted from data source 'Control Tables - CRP' to 'Control Tables - Prod'. After the project is advanced to 38, a PD package can be built and deployed so that end users can run these objects.
Status 01 - Complete
The project can be advanced to status 01 - Complete if desired. However, note that when a project is moved to a status of 01-Complete, OMW is hard coded to not allow the ability to delete the project if there are objects in that project. For more information, seeDocument 1138583.1. Note that as of E910 release, the option to advance to status 01 from status 38 is deleted and thus users no longer advance to this status.
Prerequisites for this promotion cycle:
- Constants. Depending on whether you wish to start the promotion cycle from status 11 or 21, you will need to make sure the default Constants settings in Object Management Configuration (P98230) are set up accordingly. If you wish to start this cycle from status 11, the initial project status for all new projects needs to be set as 11 and the User Role to use when assigning the originator to a project should be 01-Originator. If you wish to start this cycle directly from a 21 status, you can set the the initial project status for all new projects as 21 and the User Role to use when assigning the originator to a project as 02-Developer.
Production to Development
Status 11 - New Project Pending Review
This promotion cycle starts with a new project being added in OMW (P98220) with an initial project status of 11-New Project Pending Review and an initial user role of 01-Originator added.
Status 40 - Production Development
The project is advanced to status 40-Production Development. In this status, objects and users with the associated OMW roles can be added into the project. Object Librarian (OL) types of objects in this project can be checked-out and modified in PD environment. During Check-out, object specifications are copied from the PD pathcode Central Objects location to the local workstation sign-on pathcode. Non-OL objects can also be added in this project to be modified. After the modification is completed, the objects can then be checked-in to the PD pathcode. During Check-in, object specifications are copied from the local specs on the workstation to the PD pathcode Central Objects. For more detail information, please see Document 1554659.1 E1: OMW: JD Edwards EnterpriseOne Objects.
Status 41 - Xfer Production to Prototype
The project is then advanced to status 41-Xfer Production to Prototype. When the project is advanced from 40 to 41, OL objects are transferred from PD pathcode to PY pathcode, that is from data source 'Central Objects - PDxxx' to 'Central Objects - PYxxx'. OL objects with C components are also transferred from PD folders to PY folders on the deployment server. Non-OL objects with records in tables in Control Tables data source are also transferred from data source 'Control Tables - Prod' to 'Control Tables - CRP'. After the project is advanced to 41, a PY package can be built and deployed so that prototype environment users can run these modified objects.
Status 42 - Xfer Prototype to Development
Next the project is then advanced to status 42-Xfer Prototype to Development. When the project is advanced from 41 to 42, OL objects are transferred from PY pathcode to DV pathcode, that is from data source 'Central Objects - PYxxx' to 'Central Objects - DVxxx'. OL objects with C components are also transferred from PY folders to DV folders on the deployment server. Non-OL objects with records in tables in Control Tables data source are also transferred from data source 'Control Tables - CRP' to 'Control Tables - Test'. After the project is advanced to 42, a DV package can be built and deployed so that development environment users can run these modified objects.
Prerequisites for this promotion cycle:
- Constants. The default Constants settings in Object Management Configuration (P98230): the initial project status for all new projects need to be set as 11 and the User Role to use when assigning the originator to a project should be 01-Originator
No comments:
Post a Comment