ASAP methodology

In the ASAP methodology we also distinguish the so-called phase of each stage of the SAP system implementation. The stages may concern the implementation of individual system modules, and the phase of individual groups of tasks in the stage. Generally, however, at each stage of the project implementation, we will be carrying out tasks related to the preparation of the implemented system or, in fact, its part.

After preparing the configuration and testing the prototype and after approving the results of the third phase, the next implementation phase begins. The tasks that remain to be done can be classified as follows:

  • preparing and conducting a series of end user training,
  • development of the concept of system management,
  • developing a plan for moving to a new system and way of supporting work,
  • end users by consultants and members of the implementation team,
  • making a reliable assessment of the implementation of works, verification of risks.

The first group of activities is to prepare end users to work with the system. The system’s operating instructions should be prepared in such a way that based on them or on their basis the training of future users will be carried out. After completing the training cycle, it is necessary to check the level of knowledge acquired by users. The checking process is best carried out in the form of verification exercises.

The second group of activities includes creating and testing a productive environment and accompanying the necessary technical infrastructure, ensuring the system’s correct performance and data security.
The third group of activities is usually associated with the transfer of data to the productive system. It is very important to create a detailed schedule for moving data together with a list of master data, responsible persons and deadlines. Data transfer includes:

  • ABAP programs and system configuration – system prototype data are transferred from the test and development environment to the productive environment by means of a transport order mechanism (transport system is a tool available in R/3 and used to manage configuration data, including exporting and importing data from and to the system),
  • basic data materials, contractors, etc. In this case, you can use the data transfer interface (LSMW) mechanism.

Before the productive start, the task of the implementation team is to check the readiness of the system for productive work. The task of the technical team is to perform load tests of the productive system, as well as verification of end users’ rights and access to the system from workstations.

Leave a Reply

Your email address will not be published. Required fields are marked *