The starting point is represented by a BEx query similar to the one described in the first airline report. A remote function module is created to load the query data. Based on it, a web service is generated. This web service will be used by Xcelsius to load the query data into an Excel spreadsheet.
read more »
The business graphic chart gets updated every time the table showing the BEx query data changes its selection. Selected table rows represent chart series and table column names represent the chart categories. read more »
Now that BEx query data is reflected into a context node, we can use this node to create dynamic tables to show its content. The first column of the dynamic webdynpro table will always represent the query Y axis, the rest of the columns representing the query X axis. read more »
Having a context node reflect the structure and content of a query data makes it easier to display it via webdynpro UI elements. InfoCube query calls are available via RRW3_GET_QUERY_VIEW_DATA function allowing advanced query control via run-time defined parameters. These parameters represent the query variables defined using BEx query designer. read more »
All Flight Routes webdynpro search dropdowns controls are dynamically populated at runtime based on some inner joins on table data. One may expect dropdown values contain direct data binding from inner tables just like it’s the case for webdynpro tables but this is not the case.
read more »
Create, populate and display an internal table at runtime without knowing in advance the table type. This can be achieved with the help of field symbols and data reference variables. read more »
