This is how we implemented it..
- Defined a number of Business Object to manage retrieval of data from some of the base CC&B objects in a flattened format (ie. Characteristics mapped to descriptive elements, unused fields not defined, etc).
- Defined a UI map which forms the canvas for 'painting' the application within our framework.
- A Query Zone to ensure that the required data associated with the Context Zones are retrieved (using Zone type F1-DE-QUERY).
- A Business Service to wrap the call to the Query Zone into a usable service.
- A Script to initiate the call to the Business Service with the associated Context Identifiers (from the global context).
- A Portal used to render the solution within the Framework.
- An Application Zone to link the Business Service to the UI Map (using Zone type F1-MAPEXPL) and the Portal.
- A Navigation key to reference the Portals Service Program.
- A Navigation Option to link the new functionality into the Menu subsystem.
- Context Menu Items to link the new functionality to the Service Point and Service Agreement entities (our link to the external application is based on the Geographic Identifiers on the SP).
- The required User Group entries to ensure that access is provided to the new Application Service associated with the Menu defined above.
Resulting in the application being rendered as:
We have used similar methods to render our online bill viewer within a pop-up window (using an in-house developed webpage, which calls our CC&B Bill Extract algorithm, resulting in the use of common code for both the online bill view and batch bill extract routines with no need for additional software such as Business Objects or DOC1).
Feel free to drop me a message if you want any further detail.