Posted by: ahmedashfaque | April 1, 2014

Road map to learn SAP MM: part 5


So far you may have got good idea about SAP implementation projects from my previous posts. In this post i will concentrate about the real life scenario on SAP projects where support and mixed environments are involved.

the simplest SAP projects are those where a new installation of SAP system is required. there will not be any other systems to which SAP system needs to be interfaced. These are known as greenfield SAP projects. In real life, this is not the case. On most SAP projects, some existing SAP installation is already present and you may need to work on providing support to the existing system or do upgrade or do roll-out. These kind of projects are known as grey field projects.

Let us discuss these projects and what kind of roles are required of SAP MM consultants on these projects.

Roll-out: Your client may already be running on SAP system. But not all of its organizations may be running on SAP. Some of the organizations may be running on some legacy system and some may be running on SAP. the organizations which are running on some legacy system may need to be moved on SAP. The projects where this has to be done are known as roll-out projects. There is a terminology associated with these projects which is known as cut-over. When the SAP system is developed and tested and is ready to be ported to production then the organization needs to cut its use of legacy system transaction and move over to SAP. One by one functionalities are moved to SAP system. First of all, the master and transaction data is ported to SAP system from legacy system. SAP is then run in parallel to the legacy system. Finally when SAP is fully functional, the legacy system is completely cut off and all the transactions are completely done in SAP system.

Upgrade: Your client may be running SAP with some old version. Now it wants to run on a new version of SAP. In this case, you need to upgrade the existing system to the newer version of SAP. Some of the tasks involved in upgrade projects include taking a snapshot of existing data, archiving existing transaction data, running and testing the new system in parallel and finally handing over the upgraded system to end users. Sometimes, tricky situations arise on such projects. Suppose the client has some data on old box (old version of SAP) and at the same time, some transaction is being invoked from the newer version. Both systems are running in parallel and this transaction command uses data from tables located on both the boxes. In such cases, getting reports or transactions which need data from both boxes become difficult. In such cases, you may need to join tables (creating and using some table view) on both boxes so that your transaction works.

Support: On support projects, the project team needs to fix some defects or provide user support on daily basis. many end users find some issues in performing their day to day transaction on SAP and need immediate assistance when some issue arises. the support consultant may need to help end users on these issues. Generally there are 4 levels of support depending on the criticality and response time in resolving the issue.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: