Every time a user navigates to a transaction, the system
retrieves a navigation option to determine which transaction
should open. For example,
- A navigation option is associated with every menu item.
When a user selects a menu item, the system retrieves the
related navigation option to determine which transaction to
open.
- A navigation option is associated with every
favorite link. When a user selects a
favorite link, the system retrieves the related navigation
option to determine which transaction to open.
- A navigation option is associated with every node in the
various trees. When a user clicks a node in a tree, the
system retrieves the related navigation option to determine
which transaction to open.
- Etc.
Many navigation options are shipped with the base package
and cannot be modified as these options support core
functionality. As part of your implementation, you will
probably add additional navigation options to support your
specific business processes. For example,
- A user can define their
home page on their user
preferences. They do this be selecting a navigation
option.
- Etc.
The topics in this section describe how to maintain
navigation options.
CAUTION:
In order to improve response times,
navigation options are cached the first time they are used
after a web server is started. If you change a navigation
option and you don't want to wait for the cache to rebuild, you
must clear the cached information so it will be immediately
rebuilt using current information. A special button has been
provided on the Main tab of the navigation option transaction
that performs this function. Please refer to
Caching Overview for information on the
various caches.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.