Create Wire Model in webdynpro FPM.

Question

Hi Friends,
Please , Help Me How to create Wire Model by Webdynpro FPM. Please Give me Step by Step  process.
i have done Form, list, search and Tree but i am not geting how to do Wire Model. So Please Give me Step by step Review to create Wire Model with FPM.
it's Urgent.
Thanks.
Pappu  Mehta
Edited by: Pappu Kumar Mehta on Nov 18, 2011 3:38 AM

Answer 1

Wire Model
The wire model can be used to create running FPM application by pure configuration or at least with minimal coding effort. The runtime interdependencies between UIBBs are defined by configuration entities called “wires” which are based on reusable “connector” classes implementing the dependency semantics. The primary use cases for the wire model are object models with generic access interfaces (for example, ESF, BOPF, or BOL).
A wire controls the runtime interdependencies between two UIBBs; that is, they determine the data content of the target UIBB depending on user interaction changing the “outport” of the source UIBB. Outports can be of type lead selection, selection or collection. For example, the execution of a search on a Search GUIBB will change its collection outport and may therefore change the data content of a result list displayed in a separate List GUIBB. Similarly, changing the lead selection in a list of sales orders may change the data content of another list displaying the associated sales order items.
In order to be part of a wire model, a UIBB needs to implement a certain Web Dynpro interface which in turn provides a feeder model implementation. The FPM GUIBBs are automatically integrated if their feeder classes implement the feeder model interface.
Application areas or object models define their own namespaces for which their connector classes, feeder model classes can be reused. Moreover, they typically need to provide a transaction handler class which manages transaction events like save, modify or check and global message handling.
Wires are defined on the level of the floorplan configuration. For each model UIBB contained in the floorplan configuration, a source UIBB with specified outport can be defined. Furthermore, a connector class and, potentially, connector parameters must be maintained.
If the floorplan contains composite components (tabbed components), the model UIBBs contained in the tabbed components can also be wired. However, in order to provide better reusability of composite components, it is also possible to define intrinsic wiring for tabbed components. A tabbed component can define a model UIBB as a “wire plug” (this is usually a master UIBB), which serves as an entry point for the wiring of the tabbed component from the enveloping floorplan component. If a wire plug is configured for a tabbed UIBB, only the wire plug UIBB can be wired from outside.
Transaction Handler class
    The transaction interface provides methods for handling global and transactional events. In the FPM configuration editor, one transaction handler implementation can be assigned on the level of the wire model. However, it is not mandatory to specify. But it can be used for wring some specific logic for Application level events.
Interface “IF_FPM_WIRE_MODEL_TRANSACTION” is implemented for creating transaction handle class.
Method
Method description
START
It is called at the starting of FPM application. It provides 3 things “FPM Massage manger instance”, “Property bag of FPM Application”, and “Runtime information of FPM”.  Here, we can also specify application commit capability.
AFTER_FLUSH
This method is called after FLUSH has been called for all current UIBBs. It can be used to flush buffers.
AFTER_PROCESS_EVENT
This method is called after PROCESS_EVENT has been called for all current UIBBs. It can be used for handling transactional events for example SAVE or CHECK. Moreover, it can be used to collect messages which here not handled inside UIBBs and to forward them to the FPM message handler.
AFTER_PROCESS_BEFORE_OUTPUT
This method is called after PBO has been called for all current UIBBs. It can be used to collect messages at the latest possible point in time before screen output.
AFTER_NEEDS_CONFIRMATION
This method is called after NEEDS_CONFIRMATION has been called for all UIBBs. It can be used to analyze and add confirmation requests.
IS_DIRTY
This method can be used to indicate a dirty state for the work protection mode.
Connector Class
    The “IF_FPM_CONNECTOR” connector interface comprises an interface, “IF_FPM_CONNECTOR_DEF”, defining the access by the FPM framework and an interface “IF_FPM_CONNECTOR_RUN” for runtime access by the application feeder model.
The definition interface possesses a static attribute, “SV_NAMESPACE”, which should be filled with the namespace (ex. ‘FPM_DEMO’ or ‘BOL’ or user specific) in the class constructor of a connector implementation (for example in a common superclass).
Method for “IF_FPM_CONNECTOR_DEF”
    Method
Method description
GET_PARAMETER_LIST
Connector classes can be parameterized to flexibly control their runtime behavior. The parameter values are maintained for the wires in the FPM configuration editor. A parameter is defined by a name, its data type and a descriptive text.
INITIALIZE
With this method the connector is initialized with the parameter values. This method is called by the FPM runtime upon UIBB instantiation.
GET_PARAMETER_VALUE_SET
With this method, a connector implementation can provide a value set for each parameter. For example, in an object model a parameter may carry the association name. For a wire between specified UIBBs, the method may provide a list of all associations between the source and target business object node.
SET_INPUT
Receives an object reference carrying the actual data of the connected outport. This method is called before the UIBB‟s PBO by the FPM runtime.
Method for “IF_FPM_CONNECTOR_RUN”
    Method
Method description
GET_OUTPUT
Returns an object reference carrying the actual data to be displayed by a UIBB. This method can be called by the UIBB at PBO for example in the GET_DATA method of a feeder class.
IS_CREATE_ALLOWED
Returns a Boolean indicator whether entity creation is allowed. This method can be called by the UIBB at PBO to dynamically control the activation of create buttons for example to maintain the action usage parameter in the GET_DATA method of a feeder class.
CREATE_ENTITY
Creates and returns a data entity which can be arbitrarily typed. This method can be called by an action handler of the UIBB for example in the PROCESS_EVENT method of a feeder class.
There are total seven methods in connector interface “IF_FPM_CONNECTOR” that should be implemented in connector class. We should also create class constructor for setting “Namespace”. “SET_OUTPUT” and “GET_OUTPUT” is bridge between FPM components, so these methods should be implemented properly.
Wire for Free UIBBs
    Wire model is implemented on Web Dynpro component by implementing “IF_FPM_UIBB_MODEL” Web Dynpro interface. It contains only one method “GET_MODEL_API” which is used to set “FPM Feeder Model” for Free GUIBBs. It contains only one parameter “RO_FEEDER_MODEL”. So, we have to create a FPM Feeder Model class and assign to that parameter.
    FPM Feeder Model Class – Interface “IF_FPM_FEEDER_MODEL” is implemented for creating Feeder Model Class.
    Method for “IF_FPM_ FEEDER_MODEL”
    Method
Method description
GET_NAMESPACE
Returns the namespace of the underlying application area. Method is called at design time.
SET_CONNECTOR
Called upon instantiation of a UIBB. It hands over the connector (reference to IF_FPM_CONNECTOR_RUN) which can be accessed for data retrieval at PBO.
GET_INPORT_KEY
Returns a reference to an object key which characterizes the meta data type expected at the import (for example the business object node). Method is called at design time.
GET_OUTPORTS
Provides a table of outports comprising the object key, the port type an identifier and a descriptive text. Method is called at design time.
GET_OUTPORT_DATA
Returns an object reference carrying the actual data identifier for a certain port. Method is called at runtime.
        Assistance class can also be used as Feeder Model Class and reference “WD_ASSIT” can used as Feeder model instance.
Ex:    METHOD get_model_api .
  ro_feeder_model = wd_assist.
ENDMETHOD.
Wire for GUIBBs
    Nothing special we need to do that.  Interface “IF_FPM_FEEDER_MODEL” is also implemented on feeder class for getting port support. We need to set port manually using structure “IF_FPM_FEEDER_MODEL=>CS_PORT_TYPE”. It contains three constants “COLLECTION”, “SELECTION” and “LEAD_SELECTION”. It should be properly configured.
Source Codes:
Code for Transaction handler class:
class ZCL_MY_TRAN_HANDLER definition
  public
  create public .
public section.
*"* public components of class ZCL_MY_TRAN_HANDLER
*"* do not include other source files here!!!
  interfaces IF_FPM_WIRE_MODEL_TRANSACTION .
protected section.
*"* protected components of class ZCL_MY_TRAN_HANDLER
*"* do not include other source files here!!!
private section.
*"* private components of class ZCL_MY_TRAN_HANDLER
*"* do not include other source files here!!!
  data MO_MSG_MAN type ref to IF_FPM_MESSAGE_MANAGER .
ENDCLASS.
CLASS ZCL_MY_TRAN_HANDLER IMPLEMENTATION.
* <SIGNATURE>---------------------------------------------------------------------------------------+
* | Instance Public Method ZCL_MY_TRAN_HANDLER->IF_FPM_WIRE_MODEL_TRANSACTION~AFTER_FLUSH
* +-------------------------------------------------------------------------------------------------+
* +--------------------------------------------------------------------------------------</SIGNATURE>
method IF_FPM_WIRE_MODEL_TRANSACTION~AFTER_FLUSH.
  return.
endmethod.
* <SIGNATURE>---------------------------------------------------------------------------------------+
* | Instance Public Method ZCL_MY_TRAN_HANDLER->IF_FPM_WIRE_MODEL_TRANSACTION~AFTER_NEEDS_CONFIRMATION
* +-------------------------------------------------------------------------------------------------+
* | [--->] IO_EVENT                       TYPE REF TO CL_FPM_EVENT
* | [--->] IT_UIBBS                       TYPE        FPM_T_UIBB_COMPONENTS
* | [<-->] CT_CONFIRMATION_REQUESTS       TYPE        FPM_T_CONFIRMATION_REQUESTS
* +--------------------------------------------------------------------------------------</SIGNATURE>
METHOD if_fpm_wire_model_transaction~after_needs_confirmation.
*----- which event
  CASE io_event->mv_event_id.
*----- start over
    WHEN if_fpm_constants=>gc_event-start_over.
*----- raise confirmation request if state is dirty
      CHECK if_fpm_wire_model_transaction~is_dirty( ) = abap_true.
      APPEND cl_fpm_confirmation_request=>go_data_loss TO ct_confirmation_requests.
  ENDCASE.
ENDMETHOD.
* <SIGNATURE>---------------------------------------------------------------------------------------+
* | Instance Public Method ZCL_MY_TRAN_HANDLER->IF_FPM_WIRE_MODEL_TRANSACTION~AFTER_PROCESS_BEFORE_OUTPUT
* +-------------------------------------------------------------------------------------------------+
* +--------------------------------------------------------------------------------------</SIGNATURE>
method IF_FPM_WIRE_MODEL_TRANSACTION~AFTER_PROCESS_BEFORE_OUTPUT.
  RETURN.
endmethod.
* <SIGNATURE>---------------------------------------------------------------------------------------+
* | Instance Public Method ZCL_MY_TRAN_HANDLER->IF_FPM_WIRE_MODEL_TRANSACTION~AFTER_PROCESS_EVENT
* +-------------------------------------------------------------------------------------------------+
* | [--->] IO_EVENT                       TYPE REF TO CL_FPM_EVENT
* | [<-()] RV_RESULT                      TYPE        FPM_EVENT_RESULT
* +--------------------------------------------------------------------------------------</SIGNATURE>
method IF_FPM_WIRE_MODEL_TRANSACTION~AFTER_PROCESS_EVENT.
  CASE io_event->mv_event_id.
    WHEN ''.
    WHEN ''.
    WHEN OTHERS.
  ENDCASE.
endmethod.
* <SIGNATURE>---------------------------------------------------------------------------------------+
* | Instance Public Method ZCL_MY_TRAN_HANDLER->IF_FPM_WIRE_MODEL_TRANSACTION~IS_DIRTY
* +-------------------------------------------------------------------------------------------------+
* | [<-()] RV_IS_DIRTY                    TYPE        BOOLE_D
* +--------------------------------------------------------------------------------------</SIGNATURE>
METHOD if_fpm_wire_model_transaction~is_dirty.
  rv_is_dirty = cl_fpm_wire_model_col_factory=>work_protection_is_dirty( )