Wiring
A wire is created in an Overview Pattern (OVP) configuration to specify the data transfer mechanism. It primarily contains the following:
The transaction class
The destination screen where data needs to be transferred.
The source screen from where the data is transferred.
The connector class used to transfer the data.
The parameters to be used by the connector class.
The way a data record is to be identified (for example
LEAD SELECTION
).
Transaction Class
The transaction behavior for the Personal Profile
application is the result of the CL_HRESS_TRANSACTION transaction class. This class is called by the Overview Pattern (OVP) configuration on execution of any of the standard Create/Read/Update/Delete (CRUD) FPM
events.
Connector Class
A connector class is responsible for transferring data across User Interface Building Blocks (UIBBs) in the FPM OVP. In the Personal Profile
application, the following connector classes are used to communicate between the different UIBBs:
CL_HRESS_CONNECTOR_PER_OVR
This connector is used to transfer data from the initial screen to an overview screen or biz card UIBB.
CL_HRESS_CONNECTOR_IDENTITY
This connector is used to transfer data from the overview screen UIBBs to the detail screen UIBBs in the case that both, overview screen and detail screen use objects from Business Object Layer (BOL) model nodes at the same level. This connector is also used to transfer data from the detail screen UIBB to the validity section UIBB. For more information, see Validity Section in Detail Screens.
CL_HRESS_CONNECTOR_RELATION
This connector is used to transfer data from the overview screen UIBBs to detail screen UIBBs in the case the detail screen uses the object from the BOL model which is one level lower to the object used by the overview screen.
For more information, see class documentation.