This chapter contains the following topics:
This section provides an overview of user overrides and discusses:
Search hierarchy
Cached override information
User Overrides enable you to change the appearance of an application to fit the needs of your business. For some user overrides, such as an object linking and embedding (OLE) attachment to a form, no consequences exist when you upgrade your software because your user overrides are merged into the new release. For other user overrides, such as grid or toolbar formats, the system gives you the options of reconciling your user overrides with the new software or deleting your user overrides.
A user override changes only the appearance of an application; it does not affect the application's functions. You can set overrides by user ID, role, or the keyword *PUBLIC. If you set your override by user ID, only that user is affected when he or she signs on to any workstation in the enterprise. If you set your overrides by role, those users who are set up within User Profiles to be members of that group are affected. If you set your user overrides by *PUBLIC, all users in the enterprise are affected. After you create an override for a role or *PUBLIC, each employee inherits that override, regardless of the workstation he or she signs on to. Even with role or *PUBLIC overrides, each employee can further customize a version to fit individual needs. For example, if someone in a department has trouble seeing text on a form, he or she can switch to a larger font. This change applies only to the individual, not to the entire group or company.
Oracle's JD Edwards EnterpriseOne stores these modifications in the User Overrides Table (F98950). Because the system tracks the overrides by your user ID or role, the modifications will appear on any workstation that you sign on to. User overrides enable you to make the following modifications:
Resequence the grid.
Change the sort order of rows and columns.
Freeze columns and rows.
Move and resize columns and rows.
Change the magnification and font size.
Add charts and graphs to an application, and embed third-party products that support OLE automation.
The following overrides are local only; they can be considered workstation preferences. The system stores these overrides on your workstation; therefore, they are accessible only from that workstation:
Sizing of the parent and child windows.
Changing the parent window.
Changing fonts on a form.
Maximizing the form.
Turning on the exit bar.
During the execution of an application, the system uses a search hierarchy to locate a user override. The system searches by user and group for each unique combination of application, form, version, and language in the following order:
| Hierarchy | Description |
|---|---|
| User ID | When you access a specific application, the system searches first for an override for the application under your user ID. |
| Role | If the system does not find an override under your user ID for the application, it then searches for it at the role level. For example, if you are in the Accounts Payable role, the system searches for an override for that role. |
| *PUBLIC | If the system does not find an override for the application at the role level, it searches for it under *PUBLIC. If no override is found at the *PUBLIC level, the system uses the No Overrides default value. |
The first time that a user opens an application form, the system reads the User Overrides Table (F98950) and creates a disk cache on the workstation. This table contains form-specific information such as menus, buttons, and formats. This cache improves network performance because multiple database fetches are not required to retrieve individual form elements.
However, if a system administrator or the user modifies user overrides with the User Overrides Revision application (P98950), the system writes the override information directly to the F98950 table, and not to the cached table. Because the system always reads overrides from the cached information, any modified user overrides cannot become effective until the user exits and reenters the system, causing the cached table to be refreshed.
For example, assume that you want to modify a journal entry by adding tabs and then associating those tabs with your user overrides. You would create the tab and then use the P98950 application to associate the tab with your user profile. You would not immediately see any records of the journal entry form because the user override is stored in the User Overrides Table, and the system is looking at the cached information. This process does not affect your ability to create and use local form changes, or workstation preferences, that are not stored in the User Overrides Table.
If for some reason you have two users who share the same user ID, be aware that the system does not share user override records. If both users sign on to the system at about the same time, the first of these two users to sign on will see the user overrides; the second user to sign on will not. Furthermore, the first user to make an override change during simultaneous sessions takes control of the F98950 record, and all other users signed on to the same user ID are locked out.
This section provides an overview of how to create user overrides and discusses how to:
Create user overrides.
Change an individual user override to a group user override.
Fix user overrides after a form change.
You can create user overrides for a user ID, a group, or for *PUBLIC. After you create a user override, your user override will be available on any workstation that you sign on to in the enterprise.
If a form for which you have created user overrides has changed after upgrading your software, the system attempts to merge your user overrides with the changed form. You might need to reset your user overrides; at the least, you will need to verify that your user overrides are still intact.
You can create individual user overrides in which the changes that you make to an application reside on an enterprise server and are associated with your user ID. This override is available to you at any workstation that you sign on to. To create a group override, you first create an individual override, and then you change that override to a group override, thereby making the override available to employees within a group or to the entire company (*PUBLIC).
Access the application for which you want to create an override (for example, Standard Voucher Entry).
Modify the application (for example, rearrange columns or rows on the grid). When you exit the application, the preferences that you just set up are stored in User Overrides under your user ID.
Enter P98950 in the Fast Path.
Note:
The User Overrides application (P98950) is available on the Microsoft Windows client and the web client.On the Work With User Overrides form, enter a user ID in the User/Role field, and then click Find to locate and select the individual override record that you wish to make available to a group.
Note:
Be sure that you select the correct type of override. The two types available are GF for grid tab format overrides, and HC for menu and toolbar overrides. For example, to deploy a grid tab to other users, you need to select a GF record; to deploy a changed menu bar or toolbar, you need to select an HC record.On the Work With User Overrides form, scroll to the right to see the override type, and then click Copy.
On the Copy Overrides form, in the User/Role field, enter either a valid role, which has been set up in User Profiles, or *PUBLIC to copy the user override to a role or the entire company.
If you want to change a JD Edwards EnterpriseOne demo version and want the copied version to use the same user overrides as the demo version, do not change the User/Role, but name the version to represent your custom version.
In the Version field, enter the version name to copy user overrides set up for one version to another version.
Note:
User Overrides does not create versions.In the Language field, enter a valid language code to select the user override language for the specified user and application.
If you copied and modified the version, delete the individual user record that you copied.
Deleting this record ensures that when you log on, you are viewing the overrides for the sign on role, not the override that is specific to your user ID.
Note:
The system creates a record for each form that you modify.When you install a package on your workstation, you might have a discrepancy between the changed forms included with the new package and the grid, menu, or toolbar user overrides that you made before the installation. For example, a new column might have been added to a grid for which you have user overrides. After the package installation, the first time that you access the changed form, the system detects the discrepancy between the newly installed form and your existing user overrides. The system asks if you want to fix your user overrides to include the new column or delete your user overrides altogether. If the system cannot fix the discrepancy between the changed form and your user overrides, the system automatically deletes your user overrides.
The system performs this fix only for grid, menu, or toolbar user overrides because all other user overrides, such as an OLE attachment to a form, do not interfere with changes to a form.
The first time that you access a form after a package installation and have a discrepancy between the newly installed form and your user overrides, a message box appears. This box prompts you to either delete your user overrides for that form or have the system try to fix your user overrides to match the changed form.
On the message box that appears, perform one of these tasks:
To delete your user overrides, click Delete.
The system deletes your user overrides for that form. You can add your overrides again by following the process for creating user overrides.
To try to fix your user overrides, click Fix.
The system tries to merge the changes from the newly installed form with your user overrides for that form. If successful, verify that the form works properly with your user overrides. If any errors exist with the grid formats or menu and toolbar customization after the system tries to fix the discrepancy, you should delete your user overrides for that form. On the Work With User Overrides form, select your overrides and then click Delete.
If the system is unable to merge the changes with your user overrides, the system automatically deletes your user overrides for that form. You can add your overrides again by following the process for creating user overrides.