A "Budget Entry Database" is the domain used in conjunction with the value shown for a specific Workstation ID (e.g. desktop or laptop computer) for the OFA Management Plan application. Workstation ID's in the central campus are displayed in the format of BW_1xxxx, while Workstation ID's in the Medical School are displayed in the format of BW_2xxxx. Workstation ID's are linked to specific Budget Org(s) which are maintained by the Budget Office.

A " Budget Org" is the domain used, in conjunction with the Oversight Hierarchy value to restrict access, for the OFA Management Plan application for a specific Workstation ID. The hierarchy of Budget Orgs are linked to a specific Workstation ID and are maintained by the Budget Office.

Access Orgs are the domains that are used, in conjunction with the Oversight Hierarchy value to restrict access, for three specific Oracle applications: JSA, VIP, and the Data Warehouse. Since these Oracle applications share the access org domains, they should have the same access org value. If an individual has different access org values listed for any of these three applications, the default value for access will always be at the highest access org level.

The ID Location identifies the origin of the Oracle responsibility or function (e.g. Apps, Web, or DWH) and is shown on the table below:

This is the actual name of the Oracle Responsibility as defined on the HOP1 database for the Oracle Financial and Human Resource Applications (e.g. YULD_Phase 2 Dept LD Accountant) and for the Oracle Self-service Web Applications (e.g. Procurement Inquiry). The Responsibility name will not show for functions with the Data Warehouse Application.

This is the name of the YASified (Yale Authorized Security) functionality, which has been associated with Domains and Values to restrict user access. In many cases, the YAS Function name will be identical to the Oracle Responsibility name and will be shown for both the Oracle Applications and the Data Warehouse Application. The Function name will not be shown for the Oracle Self-service Web Applications.

This is the YAS Domain name category that has also been selected to restrict access. The categories of Domain names that you will see in the User Access Profile Report include: Access Org, Confidential Org, Confidential Job, Casual Time Approval Org, Payroll C+T Approval Org, Budget Entry Database, Budget Org, and Access Project. The Domain name will not show for the Oracle Self-service Web Applications.

If an employee has attended a Requisition Approver class or an Executive Express workshop, a "Y" flag will appear in the Requisition Approver column next to the Oracle Responsibility name of "Requisitions (by Preparer)". For all other Oracle Responsibilities or functions, this field will remain blank.

A "Confidential Job" is the domain used to describe the job position value to restrict access for the LD, HR Lookup, and HR Update applications. The "Confidential Job" always requires the use of the "Confidential Org" domain in order for the Oracle responsibility to work. The full name of the "Confidential Job" shown in the value field is shown on the following table:

This is the YAS Value name which has been selected to further restrict access to the associated Domain name category. This Value name is the level of hierarchy (e.g. Org, Dept, Div. etc.) that has been chosen to restrict access as defined by the combination of Oracle Responsibility Name, YAS Function Name, and YAS Domain Name. The Value name can also be a specific HR job category (e.g. CAS, CT, MP, etc.

A "Confidential Org" is the domain used, in conjunction with the Oversight Hierarchy value to restrict access, and are shared by the LD, HR Lookup, and HR Update applications. The "Confidential Org" always requires the use of the "Confidential Job" domain in order for the LD, HR Lookup, and HR Update responsibilities to work.

The new layout was designed to take advantage of your entire browser window. In a few cases, the browser may not display this correctly, and if this is the case, you can use this page to manually adjust the width of the website in your browser.

The Problem Report database of all user change requests may be queried (or submitted to) by using our web-based PR submission and query interfaces. The send-pr(1) command can also be used to submit problem reports and change requests via electronic mail.

Yes. Desktop Authority centrally records user attempts to utilize secured devices. Turnkey reports exist to provide detail on both the configuration of the device lockdown, as well as user access.

You have the ability to view and correct the personal information that is kept in your registration profile on usps.com. You can access and correct the information right from the registration sign on page on usps.com.

You should not create database users with user id 0 (root). They will be unable to access the database. This is a security precaution because of the ability of users to dynamically link object modules into the database engine.

Only one user at a time can log in with a username and password. If a second user attempts to use the same login information, the first user will be logged out. For addition user accounts, contact Targeted Inc. at info@targeted.com or call us at 416-523-5150.

Go to www.getinsights.com, click on "Get Insights" and click on the link "Review Your Profile Results".