Generic Analytics Application
FPM provides you with a ready-to-use analytical application. In addition to the Analytics component, it includes Search and Chart components.
This generic application can be used for simple scenarios involving one query only.
- Search component for the supply of variables to the query
- Analytics component for the display and manipulation of query data
- Chart component for visualization of query data
The generic application exposes one application parameter FPM_BICS_QUERY_ID in which the name of the query can be specified.
Additionally, URL parameters can be passed to pre-fill certain variables. The syntax of these URL parameters is the same as for previous analytical components (see here for examples).
The generic application uses an application controller to analyze the URL parameters, and to adjust the layout of the application accordingly. If no variables are found, the Search component is not displayed at all. The application controller is based on class CL_FPM_BICS_APP_CC.
- Configuration of Query ID and Query Instance ID
Interaction with the BICS API requires all the components to interact with an instance of IF_BICS_QV. To allow separate UIBBs (like the Analytics and Chart UIBBs) to read and interact with the same instance of IF_BICS_QV, query instances will be stored in IF_FPM->MO_APP_PARAM under a key consists of the query ID and an optional instance key. If a UIBB requires access to a query to read data from it, it must first check if the required instance already exists in IF_FPM->MO_APP_PARAM. It can only create an instance if it does not already exist there, and it must store the instance in IF_FPM->MO_APP_PARAM.
- Wiring
Each BICS-based UIBB exposes data using two defined ports; one port for the whole query instance, and one port for the selection data inside the query. Using these ports, data transfers can be graphically defined with the Graphical Wire Editor in FLUID. To use the selection data port, the receiving UIBB must have a query ID and an instance ID defined in the configuration. The outports of the Search feeder class are different compared to the outports of the Analytics and the Chart feeder classes. In the Search feeder class, two outports for each configured query are available to allow distinct routing of information.
The class CL_FPM_BICS_WIRE_ENTITY is delivered as a connector object class for transporting the selection data and the query instance data over the wire. The wire processing is enabled in the Analytics UIBB re-usable feeder class as well as in the generic BICS Chart feeder class. To retrieve the selection criteria, the methods GET_SEARCH_CRITERIA and GET_SELECTION of the entity class must be called. The first method returns all variable values. The second method returns all fixed, dynamic, and current UI filters. All methods return references to IF_FPM_BICS_SELECTION.