Realization

Once the Blueprint Phase is complete, the team transitions from the conceptual world into a series of build activities. Here requirement documents are turned into configuration and development activities in SAP.

Functional analysts configure the system by manipulating the various settings within SAP’s configuration tables to influence everything from how a specific sales order type works, to when and where invoice forms print.

Developers skilled in ABAP (SAP ‘s programming language) code what are known as RICEFW (Reports, Interfaces, Conversions, Enhancements, Forms, and Workflow) objects to conform to the requirements defined by the business. In most cases, they are able to leverage pre-existing objects and simply tailor them to suit the requirements. For example, many forms exist already in SAP and simply need to have company logos added and the look and feel (fonts, etc.) changed to suit that company’s specific form requirements.     
 
For our implementation, we’ve identified a total of 22 RICEFW items – about 1/3 of which are related to printed forms. We also have identified a few reporting changes to SAP delivered reports as well as our most complex requirement – workflow to support the approval process around time and expenses. Since we support our own projects as well as those of our consulting partners, the requirements around approval of time and expenses will be tricky. We plan to invest more resource time in this area.

links: digg this    del.icio.us    technorati    reddit