Different Types of SAP Projects

PARSIPPANY, N.J. - May 2, 2013 - PRLog -- Different Types of SAP Projects

This press release highlights the different types of SAP projects that are relevant to all modules of the SAP system. The classification is based on the requirements of a company undertaking an SAP implementation or initiating changes to the current SAP system.

Brief History of SAP

SAP (Systems, Applications, and Products in Data Processing) was founded in 1972 by five ex-IBM engineers. SAP has been a success and has a global reputation as a world class provider of Enterprise Resource Planning (ERP) solution. The software provides organizations with an integrated financial ledger, sales ledger, purchase ledger, and management information system.

The Different Types of SAP projects

Fresh Implementation projects

In a fresh implementation project, the end system is developed from scratch. For example, a company that decides to change major functionality of its system to a more advanced version. This type of project can be further subdivided into two categories:

o   Complexity-based projects

§  A high-complexity project scope includes many components within the SAP system and also involves heavy integration with other systems, such as Oracle or third-party tax accounting software. The challenge of seamless integration of all these areas adds to the complexity of the project.

§  A medium-complexity project scope includes only a few areas within and outside the SAP system. The integration is not overly complex.

§  A low-complexity project scope is restricted to one or two components within and outside of the SAP system.

o   Priority-based projects

§  New legal regulations or compliance issues may necessitate a high-priority project. If a high-priority project doesn't go live in a certain time period, it could result in serious penalties.

§  A medium-priority project may enhance the current functionality  but it is not initiated due to a legal regulation.

§  Low-priority projects may only be improving functionality based on users' wish. However, there is no real urgency to implement such projects.

Upgrade Projects

An upgrade project is undertaken when a company wants to implement a newer version of SAP with added functionality such as SAP ERP 6.0 and the New General Ledger functionality.

Request-Based Support Projects

The request-based support project is based on a user's request. These projects are focused on improving the existing areas, which can involve introducing new processes and also involves the support of any existing and new functionality. This type of project can sometimes last many months if improvements are done on a piecemeal basis.

Production-Support Projects

A production-support project normally runs after the go-live of an implementation project. Such projects support on-going issues with day-to-day activities of a live SAP implementation. Production-support projects are based on the concept of 'tickets' to resolve issues. The following types of tickets are commonly used during this project:

o   Low priority: A low priority ticket involves a low impact issue and the production system will continue to run without issues if this problem is not fixed immediately.

o   Medium priority: A medium priority issue doesn't impact the production system currently but will eventually affect the system in the future.

o   High priority: A high priority issue needs to be fixed as soon as possible or it can impact the day-to-day functioning of the system.

o   Critical priority: This issue should be fixed immediately. The production system cannot run if the problem is not fixed.

Rollout Projects

Many large multinational companies use rollout projects to create a template project and roll it out to its other affiliate companies. It involves following key elements:

o   Using a template means that the affiliates companies will be harmonizing the SAP processes across various regions, branches, offices, etc.

o   Common processes such as reporting, consolidation, etc

o   Common master data structure for customer master data, vendor master data, material master data, etc.

o   Harmonizing processes across different locations regionally and globally can lower support costs.

For more information log on to http://www.sapknowledgecenter.com