Skip to main content

How To Delete UBEs and UBE Versions from EnterpriseOne

Hi

 

It is important to determine all the environments a UBE exist in. One way to make this determination is to use UTB and view the table F9861 - "Object Librarian-Status Detail". In the F9861, enter the report ID into column SIOBNM and the environments (column SIPATHCD) where the UBE template exists will display. If a record displays with a workstation ID in the column SIMKEY, this indicates that the object is currently checked out to that workstation.

To delete the UBE and the associated UBEVERS from the environments, use OMW. For example, this is an example where a UBE and the associated UBEVERs exist in DV812, PY812 and PD812 and explain the steps to do the delete in OMW and how OMW will use the appropriate Transfer Activity Rules (TARs).
 
1. Sign onto the development environment and create a project that has a status of 21. Add to the UBEs that needs to be deleted to your project. Note, the UBEVERs will not need to be added to the project because when the UBE is deleted the system will automatically delete the associated UBEVERs.
 
2. Highlight each UBE and click the Delete button. In the [Delete of...] form check: "Delete Object from Server" and "Mark Object To Be Deleted From Transfer Location". Note, the delete object from server will delete from the location defined in the TAR for a project status of 21 and object type of UBE and action 02-delete. We ship the TAR to delete from DV812 (this means the UBE will be deleted from DV812 Central Objects).

3. With each UBE deleted,  promote the project to status 26 and this promotion will delete the UBE from PY812 Central Objects and will also delete all the associated UBEVERs in the F983051 of PY812. This is based on the TAR we ship for a transfer from 21 to 26.

4. Promote the project status to 28, then to 38 and the promotion will delete the UBE from PD812 Central Objects and will also delete all the associated UBEVERs in the F983051 of PD812.
 
5. Please note the above steps only affected Central Objects for each environment, the F983051 for each environment and the F9860 and F9861. The local spec on fat clients, terminal servers and enterprise servers will not be updated. The next time a full package is built and deployed to the fat clients, terminal servers and enterprise servers the spec for the UBEs and UBEVERs will be removed. Don't worry about the spec remaining because the UBE cannot be used without the F983051.

 


Regards,

JDEHelp
This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks

______________________________________________________________________

Comments

  1. Tim HamiltonNovember 20, 2009 at 1:17 PM

    I wish to delete a report in DV that has been promoted to PY and PD. I then wish to recreate the report from a copy of another report. In OMW I have deleted the report object and subsequent versions then updated the status of the project from 21 to 26.

    My question is would I have to promote the project (change status) all the way through to 38 before I could reuse the Object Name (OBNM)?

    Thanks in advance for your help.

    ReplyDelete

Post a Comment

Popular posts from this blog

Solution for ER Debugger Issue(Debugger not working from web client)

Hi All   Please follow the steps as mentioned below to resolve ER debugger problem. Minimum requirements:- Install jdk-1_5_0_18-windows-i586-p.exe (Setup launcher) Restart the fat client and follow these steps. a) Steps to be followed while using ER Debugger:- 1)       Always take remote session by MSTSC /CONSOLE 2)       Before login into JDE fat client, go to Task Manager->Processes and check for java.exe and rdpclip .exe 3)       If processes java.exe and rdpclip.exe exists end these processes. 4)       Login to JDE fat client and open Debugger.exe from fastpath. 5)       If multiple objects are added then rebuild DIA for that object before debugging.   b) If Debugger doesn't work follow these steps:- 1)       Logout of JDE fat client. 2)       Go To Task Manager->Processes 3)       Delete processes java.exe and rdpclip.exe . 4)       Login to JDE fat client and can use debugger. c) Still if debugger doesn't work: - Contact your  CNC team. Regards,...
1 comment
Read more

Change the role sequence number for a role

Hi All,   Below are the steps to change an existing role to have a higher role hierarchy. 1. In P0092 Work With User/Role Profile, from the Form Exit Menu, select Role Sequence. 2. In the Work with Role Sequence screen, use the mouse to drag and drop a role to a desired position i.e. up or down in the role sequence tree.  The lower the role appears in the tree, the higher the sequence number. 3. It is easier to drag a role of a lesser sequence number down to replace one with a higher sequence number. 4. Click on the "Set Sequence".  This will refresh the roles with a new role sequence number based on their position in the Role Sequence tree. 5. To undo step 3, select Close Without Set Sequence. Regards, JDE Help This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks ______...
1 comment
Read more