Results in the Treasury Development DepartmentProduct ImprovementDuring the site visits, the teams and the software engineers in particular acquired direct knowledge of the work centers where the Treasury component is used by customers. Consequently, it was possible very quickly to produce a Corporate Treasury role-based work center model. The roles thus defined (foreign exchange trader and so on) were implemented in Release 4.6A as role-based menus with the associated applications and reports, and validated by means of feedback from customers and consultants. The results of the customer survey, the site visits and the evaluation of problems reported by customers led, in addition, to a consolidated list of requirements containing a large number of items that could be processed successively and on the basis of priorities. These included dialog sequences with a similar structure that before Release 4.6A had a different structure and have now been standardized. In addition, guidelines and notes were produced for software engineers that resulted in a uniform appearance for the user interface and consistent usability. Available elements from the usability-enabling technology, such as tab strips, table controls, drop-down list boxes, tree-like structures and the ABAP List Viewer (ALV), a report output tool, were integrated throughout the Treasury application component. In addition, many smaller inconsistencies that came to light in the course of automatic quality checks or broad-based usability reviews were eliminated by the software engineers. As a result, the Treasury component has certainly benefited at last from the new, SAP-wide visual design.
Figure 3: Example of a Release 4.5B user interface about to be revised
Figure 4: Example of a revised user interface in Release 4.6A A typical example of the redesign of an application system is shown in figures 3 and 4. In addition to the new visual design, which is evident at first glance, interaction with the application has also been improved. A number of different screen templates have been combined in it (including the one shown in figure 3), and the tree structure now facilitates navigation through all objects. Warrant details, for example, can now be accessed by pointing and clicking, whereas previously several dialog steps were required. In addition, in the interests of personalization, a number of fields can be assigned defaults by the user, and no entries therefore need to be made in them.
Source: EnjoySAP - Success Factors |