UDO Object Promotion ================= The following shows the detail steps needed to promote a UDO object using Object Management Workbench (OMW) Web application (P98220W). Example of UDO object used in this document is a Grid Format object. 1. Enable Security Access to UDO Objects and enable access to both the OMW Web application (P98230W) and Work With User Defined Object application (P98220U) in Security Workbench (P00950). Refer to the following documents for more detail: - Document E1: SEC: Setting up View, Manage, and Action Security for the User Defined Objects (UDO) available with 9.2 and newer ( Doc ID 2072336.1 ). - JD Edwards EnterpriseOne Tools Security Administration Guide - See Chapter 24 Managing Security for User Defined Objects 2. Ensure Allowed Actions and Transfer Activity Rules are set up in Object Management Configuration application (P98230) for UDO objects. Refer to D...
Sometimes users start working and then forget which EnterpriseOne environment they are logged into. Can you tell which environment you are logged into? Luckily, there is a new UDC that allows you to change your EnterpriseOne environment color. You can now set up environments to be color-coded for when you need a clear visual distinction as to which environment you are logged into. This enables you to quickly identify the non-production environments by color. The new UDC is 98/CO and is available in EnterpriseOne Tools Release 9.2.4 with Applications Release 9.1 and 9.2. The image below shows the default EnterpriseOne environment color. However, you can easily change the color to reflect different environments. For example, DV could be red, PY could be green, and PD could be yellow, as shown below. To do so, just add a new row in the User Defined Codes section, enter the EnterpriseOne environment name and the HEX value of the color you want the environment to be, and ...
Find out all checked out objects using SQL ============================ select * from ol920.f9861 where sistce=3; Access To Environments ================== To find out what users or groups have access to a certain environment run the following SQL: select * from sy920.f0093 where llll='<enviornment>'; Package Build Count =============== How many packages of each type per environment did you build last year? Here is the SQL : select hhpkgname, hhpathcd, year(date(char(hhblddte+1900000))) as hhblddte from sy920.f96215 where hhpkgname not like 'JJ%' --remove the ESUs and hhdatp='CLIENT' --type of build and hhbldsts=50 --build completed successfully Changing Status of Package Using SQL ============================= Below is the SQL statement that I use to mark the package as not deployed if it shows deployed:- update sy920.f9603 set PHISPTF=0 where phpkgname="PACKAGENAME"; ?Important Tables used by Object Management Workbench (OMW) or Object Librari...
Comments
Post a Comment