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 »
Two way communication between a flash island and its webdynpro container is possible and you can achieve it in more than one way.
read more »
Main application mxml is ZSAB_ISL_SPFLIGHT following an ABAP like naming convention. Everything is built on two variables shared between flex and webdynpro: flightList and currentFlight. Every time they get updated, the map overlays get updated as well.
read more »
