Object-and-Action Based Navigation
You use object-and-action based navigation to display or to start the processing of master data objects.
The typical navigation sequence for the user is as follows:
Launch the search application from the SAP NetWeaver Business Client
(transaction NWBC
).
To do this, you can choose an entry from the role menu, click a link from the service map, or click a link from the home page.
Search for an object.
You search for a business object of interest and display the object in a new window. By clicking the link to display the business object, you initiate a logical action. Another possibility is choosing the New
button. In all cases, the system opens a new window with the target UI.
Process the object in the target user interface.
Sometimes you can directly edit the object in the target user interface and sometimes you must choose the Edit
button first. Choosing the Edit
button triggers another logical action.
The Web Dynpro application Generic Search
(USMD_SEARCH
) is available in the menu. The USMD_SEARCH
node of the menu can include the object-independent configuration USMD_SEARCH
or an object-specific configuration. With the generic configuration, you can set default values for the data model and for the entity type, by specifying the following parameters in the menu node:
USMD_MODEL
USMD_ENTITY
The user can still override the defaults you set by selecting different options on the user interface.
If you specify a Business Object Type
with the parameter USMD_OTC
, users can no longer change the data model and the entity type. For more information on the required parameters, see Configuration of the Generic Search.
Note
In the following description, the Generic Search
is used as an example of the Current UI
.
If you do not specify the USMD_OTC
parameter for the USMD_SEARCH
Web Dynpro application, the system derives an Business Object Type
for the data model and entity type based on Customizing.
The relevant settings are as follows:
Activity: Customizing for Master Data Governance, Central Governance
(transaction MDGIMG
) under
View: Business Object Type
When a user clicks a link to a business object, the system triggers logical action DISPLAY
. Further logical actions are possible, for example CREATE
. The availability of logical actions (defined in Customizing for Master Data Governance
under ) depends on the UI, the UI configuration, and the state of the chosen business object type.
To determine the target user interface, the system considers the current user interface and its configuration, the logical action, and the Business Object Type
of the selected business object. Relevant settings are available in the following Customizing activities:
Standard Definition: Customizing for Master Data Governance, Central Governance
(transaction MDGIMG
) under
Custom Definition (Overrides Standard Definition): Customizing for Master Data Governance, Central Governance
(transaction MDGIMG
) under
You can use other search applications than USMD_SEARCH
. In particular, the initial page of the single-object processing UI USMD_OVP_GEN
can provide an object-specific search. The logic for determining a target UI is the same for other search applications as it is for the generic search.
If a logical action triggers the creation of a change request, the system gives precedence to the logic of the change-request-based navigation (see Change-Request Based Navigation) over object-and-action based navigation for the initial change request step 00
. If you have defined a target UI for the change request step 00
, the system uses that UI. (Path: Customizing for Master Data Governance, Central Governance
under ). If you have not defined a target UI, the system uses the logic for object-and-action based navigation to determine a target UI.
Note
If the current UI application is the generic single-object processing UI USMD_OVP_GEN
and the same UI is also the target UI application, the system ignores the value of Configuration ID
from the view User Interface per Change Request Step
. Instead, USMD_OVP_GEN
uses its current configuration for the initial change request step.