The Internet Graphics Service (IGS) is already integrated in SAP Netweaver 7.x but it may not be enabled or even present in the start profile. RFCs also need to be working properly in order to access the IGS from webdynpro. Continue reading IGS Engine Configuration – Airline Report
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.
Continue reading Dynamic Dropdowns – Flight Routes
Two way communication between a flash island and its webdynpro container is possible and you can achieve it in more than one way.
Continue reading Flash Island Communication – Flight Routes
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.
Continue reading Google Maps in Flex – Flight Routes
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. Continue reading Dynamic Internal Tables – Custom Data Explorer
Custom data explorer is structured as one screen (screen number 100) with three subcreens: table search (150), table query where clauses (200), table data (300). Each screen is a view inside MVC. These views are totally independent of each other actions, they’re just coded to reflect model current data and dispatch controller events based on user commands. Data storage and data handling happens in model and controller. Continue reading View Elements â€“ Custom Data Explorer
Controller is responsible for updating model data based on events received from views/abap screens. It does this by defining the events it will listen to (the abap screen will dispatch these) and by registering method listeners for each controller event type. Continue reading Controller Overview â€“ Custom Data Explorer
Model acts as a central location to store data from ddic based on commands triggered by controller. It is crucial that only one instance of model exists through out the report execution ensuring all views and the controller itself access the same data. Because of this we don’t allow for a model instance to be created outside the model class. Continue reading Model Overview – Custom Data Explorer