Beginner Who Wants To Be SAP S/4HANA Sourcing and Procurement Consultant

The best method to learn any subject is to first get to know as to how the user will be using the application provided by you. The best implemented application will fail if the user is not using it properly due to reasons such as too complex to use, too many clicks and fields to fill for doing any transaction, and difficult to understand screens and fields even when a good documentation is provided in the shape of a user guide. Many users may end up having difficulties in navigation, filling forms, and so on, if the application is too cumbersome. There are always bugs or defects that prevent the end user in suing the application effectively.

For a beginner who wants to be an SAP S/4HANA Sourcing and Procurement consultant, it is advisable to learn SAP as a user.  He/she will become familiar with the nomenclature, screen flows, typical SAP transaction styles, and so on. Once he/she is familiar with the application, he/she can be introduced to customize the standard SAP interface and transactions to make the application specific to the user needs of the customer.

An SAP S/4HANA Sourcing and Procurement consultant needs to customize the SAP application as per customer needs and then train the end users so that they can use the customized application effectively. Tasks involved in the customization project includes requirement gathering of user needs for the application, making a blueprint of these needs, making necessary changes (customization) in the standard application, testing the application, and finally installing it at customer premises so that users can start using it. For all these activities, an SAP consultant needs to have expertise and experience so that he/she can be efficient in all these project activities. 

Generally, a project team consists of a project manager and SAP consultants. For each module of SAP, there could be a module lead as well if the project is large. There could be a team of SAP consultants under the module lead. For instance, there could be a module lead for SAP S/4HANA Sourcing and Procurement and under him/her there could be a team of SAP S/4HANA Sourcing and Procurement consultants.

SAP projects can be categorized as follows:

  • Implementation projects
  • Support projects
  • Roll-out projects
Implementation projects are the one in which a customer wants to implement an SAP system for its own internal use. These projects are further divided into two types: green field projects and brown field projects. Green field projects are the one in which the customer does not use any kind of software application before going for SAP implementation. In this case, no legacy data from the previous system need to be migrated to the SAP system. In case of brown field project, customer already uses some legacy application, which needs to be migrated to the SAP system. In this case, legacy data need to be ported to SAP. Generally, porting legacy data is a major effort as legacy data need to be cleansed and formatted, and then only it can be made portable.

Support projects are the one in which SAP has been already implemented by the customer and users have now started using it. These users need technical support on a day-to-day basis. At the same time, for enhancement or repair of defects, SAP technical skills are required. Similarly, an older version of SAP implementation may need to be ported to a new version, which also requires
SAP technical skills. All of these activities are taken care of in support projects.

Most of SAP implementations are done in a phased manner. First, SAP is implemented at some divisions (legal entity) of any corporate entity where users are ready to use it. Later, other divisions also go for SAP. Implementations at these divisions are covered under roll-out projects. In these projects, the effort required for implementation is significantly lower than that required for SAP implementation at the initial corporate division. It is because, in roll-out projects, most of the features of SAP that are implemented at initial division are simply replicated. 

An SAP consultant should know about the environment in which he/she is supposed to work. So, he/she should be aware of the differences among implementation, roll-out, and support projects. Skills required to work on these different kinds of projects also vary as it is evident from the explanation of these kinds of projects outlined above.

SAP MM Tips

See also
Material Master Multiple Choice Questions Answers

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP MM Books
SAP Material Management Certification, Interview and Configuration Reference Books

SAP Material Management Tips
SAP MM Configuration Tips and Materials Management

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.