Wiring - Transferring Information between UIBBs 
A wire controls the runtime interdependencies between two user interface building blocks (UIBBs), that is, wires determine the data content of a target UIBB depending on the user interaction changing the outport of the source UIBB.
Floorplan Manager (FPM) enables you to define wires between UIBBs as a means of transferring information from the source to the target. Each user interface building block can only be defined as a target once, otherwise the system cannot decide at runtime where the user interface building block takes its information from. An application can use a UIBB as a source multiple times.
Each wire consists of the following parts:
Source UIBB
The source is always a UIBB and is always specified using its Web Dynpro component name as well as, if necessary, an assigned configuration.
Outport Specification
The outport specification of the source UIBB is comprised of the following parts:
Outport Type
Specifies which information the system transfers across the wire. There are three outport types:
Collection
Transfers information about all entries in the source UIBB to the connector class.
Lead Selection
Transfers information about the entry that has been selected in the source UIBB to the connector class.
Selection
Transfers information about all entries selected in the source UIBB to the connector class.
Outport Identifier
Allows you to have multiple instances of the outport types.
Target UIBB
The target is always a UIBB and is always specified using its Web Dynpro component name as well as, if necessary, an assigned configuration.
Connector Class
Implements a connector interface between the source and target UIBBs. The connector class controls the information overall by defining the dependencies between the UIBBs. The connector class can define separate parameters that the administrator can edit in the wire attributes.
On the tabbed component level, it is also possible to define wires between individual components of a tabbed component. For tabbed components, a UIBB is determined as a wire plug (WIRE PLUG). This wire plug is used by the surrounding Web Dynpro component to access the tabbed component. In an FPM application, the surrounding Web Dynpro component is either the floorplan or another tabbed component. One wire for this plug is then defined on the level of the surrounding floorplan or tabbed component. This architecture makes it possible to reuse the tabbed component in other floorplans or tabbed components without having to redefine all of the wires each time.
Integration
Wires are defined in the FPM configuration editor, FLUID, in the Wire Schema panel on the floorplan component level.
Example
An application wants to define a search with a search component, but wants to display the results in a list defined using a separate list component. Below this list, the application wants to show the details of the selected list entry in a form defined using a form component.
To map this, the application must define two wires: one between the search and the list and one between the list and the form. The source of the wire between the search and the list is the search component; the target is the list component. The COLLECTION outport type is selected to transfer all of the search data to the list. The source of the wire between the list and the form is the list component; the target is the form component. Since only the detailed data for lead entry is to be displayed in the form, the LEAD SELECTION outport type is selected.
The execution of a search on the search component will change its collection outport and may therefore change the data content of the result list displayed in the list component. Similarly, changing the lead selection in a list of sales orders may change the data contents of another list displaying the associated sales order items.