Where-Used List 

Use

With where-used lists you can determine who used the objects and the dependencies between the objects.

Prerequisites

You can call the where-used list by

·        selecting an object in the navigation tree and choosing Object  ® Where-Used List () in the main menu bar of the Integration Builder

·        selecting an object in the navigation tree and choosing Where-Used List () in the context menu

In both cases the where-used list for the selected object is displayed.

·        Select <Object>  ®  Where-Used List () in the menu bar of the object editor.

Select the object type from the dropdown list in Where Used List for field. Use the Display Input Help icon () to display a list of all the objects having this type from which you can select an object.

Features

Integration Builder (Integration Repository)

The Integration Repository has object dependencies for one or more levels: Objects can use other objects either directly or indirectly over other objects. The objects that can be used directly or indirectly depend on the type of object used (see Object References).

A message type contains a direct data type. A message interface contains an indirect data type (over a message type).

The where-used list is predefined so that only the direct users of an object are displayed. To display other (indirect) users, deselect the checkbox Direct Users Only.

Integration Builder (Integration Directory)

The screen Where-Used List for <Object> is divided into different screen areas in the Integration Builder (Integration Directory).  The object uses are grouped into the following categories.

Screen Areas in the Where-Used List (Integration Directory)

Screen Area	Description
Object of the logical routine and collaboration agreement	Displays the receiver determinations, interface determinations, sender agreements and receiver agreements in which the object is used. The key attributes and object type are displayed in a table (with a symbol, see Legend (Configuration)).
Scenario objects	Displays the configuration scenarios in which the object is used.