Backend Search Functionality in ESDMA Tool
Mobile user needs to search the backend data from his device and needs to get the relevant results based on his requirements. This functionality can be achieved creating backend search function modules in backend system and mapping it to data object in ESDMA. The application developer can create multiple backend function modules as per the application requirement and add to ESDMA to be called from the client application.
User can invoke backend search synchronously or asynchronously. Both the synchronous and asynchronous outputs are exactly same and only difference is that Asynchronous Outputs are covered under reliable messaging. To achieve the backend search functionality a backend function module shall be associated with the participating data object. The backend search function module shall have the same signature of GETLIST BAPI wrapper with an additional input search parameter fields. There could be multiple search function module associated with one data object so in this case there will be multiple entries for one data object. In the ESDMA design time there is a separate tab named backend search where application modeler can go and specify the search function module for different data objects. In this tool user have an option to add a function module as well an option to remove the already added function module. Below picture depicts that how we can use the ESDMA tool for the backend search.
Here after the addition of back end search function module activation of ESDMA is required. During the generation of ESDMA the methods get generated to invoke the search functionality. Before the activation of ESDMA the backend destination has to be maintained in the system where the backend function module will be executed otherwise the generation of ESDMA will fail. The backend destination shall be maintained in the transaction SDOE_PARAM. In this transaction the backend destination entry can be maintained per backend search function module or maintain the backend destination at ESDMA level. If user maintains the backend destination for a ESDMA then it applies for all data object. Now here we will see that how to maintain the backend destination entry for backend search in different steps:
- Go to transaction SDOE_PARAM.
- In the parameter keys select DOE_CONNECTOR.
- In the parameter name select BE_SEARCH_RFC.
4A. If user wants to maintain an entry for a data object then ESMBO_ID shall be entered in the Validity Area, backend search function module name in the validity subarea and backend destination name in the text value. Users can get the ESMBO_ID for all the participating data objects by clicking on the ‘Display Guids’ button In the ESDMA design time tool.
4B. If user wants to maintain an entry per ESDMA level then ESDMA_TRANS shall be entered in the validity area, validity subarea shall be left blank and backend destination name in the text value. Users can get the ESDMA_TRANS by clicking on the ‘Display Guids’ button In the ESDMA design time tool.
5. Finally save the values.
Here we have seen that 5 steps are required to maintain the backend destination in a development system but the same can be achieved in Quality or Production systems with the feature ‘Application Setup Wizard’. In the application setup wizard user can choose the ESDMA and in the step 3 of road map user can configure the destination for backend search function module. This user interface is convenient and simpler way to maintain the backend destination. Below picture shows the use of application setup wizard for the backend search function configuration.
Now the creation part is done and this module can be called from the client application wherever required.