Все статьи

12 Ways to Identify Yourself in the SAP Community

There are plenty of random people in the SAP community. Happens, today you show the person how to save tables from ALV to Excel, and tomorrow he already tells others, how to do posting in accounting. This picture is exaggerated, no doubt, but not so much, as it may seem at first glance. New consultants appear out of nowhere, waving certificates before their eyes about the webinars and courses they have listened to, they do not speak knowledge and skills, but generously sprinkle advice - "as necessary."

The user, whose main task is to perform his direct work, in conditions of an unfamiliar interface (a specialist SAP-based workstation), intricate transactions, and unfamiliar fields with strange names, it is not at all easy to distinguish "purely technical specialist "from someone who can really understand his problems and help solve them.

Many interested users, for the first time acquainted with SAP solutions and work consultants, they already decide to become consultants themselves and to bring to the world "light", simplification, convenience and benefit other people. How to become a real consultant? What should we strive for? Answer It's simple: do what is in the zone of confident control and not promise to help someone in issues that you can not control, constantly, however, expanding the available control zone.

For each of us, this means continuing education and professional development qualifications. Practice is the criterion of truth, and time puts everything in its place. Important daily work to develop.

When conducting interviews, sometimes it becomes insulting when a person with a beautiful record list "floats" on conceptual things. A consulting company can track this on time,

and the client ordering consulting works, will estimate the choice only by results of carried out work, when sometimes all budgets have been exhausted, and the terms are broken. Consequently, suffers reputation of a consulting company against a backdrop of a flawed result.

The author offers a dozen ways how you can improve in SAP specificity without losing productive load:

1. To study the latest trends in technology and approaches, and also look for ways to use them.

For example, a method of storing large amounts of in-memory data that uses the SAP S / 4 platform HANA, together with new production facilities, allows to organize storage and use of data in tables of individual positions without using periodic totals records, which makes the processing of data convenient, simple and significantly shortens the time for development of applications for this platform (in contrast to SAP ERP 6.0 solutions). One more example - use of mobile terminals with preinstalled SAP Fiori applications. If the most tech, what you know is ABAP, you have something to think about!

2. Understand methodology for implementing products.

ASAP, ASAP focus, Scrum, GOST 34 * and others. It is important not only to consistently follow methodology, but also understanding why one or another step is being implemented, what is its purpose and contribution to final result. It is also important to understand when to follow one methodology, and in which cases it is more efficient to use the other, so that as a result get a high-quality implementation. Often, knowledge is limited only to the names of the stages.

3. Understand the industry specificity.

Understanding the industry specificity and distinguishing problems that are characteristic, as for most enterprises, as well as for individual enterprises, will help you to offer effective business solutions. Periodically study the special literature on the organization of production, for example, The steel brands and their specificity, by solutions of logistics and transport tasks. It will help you understand customer problems and offer solutions adequate solutions. Knowledge and use industry terms will help you understand the customer and be most understood.

4. Know methods of decision-making and management consulting approaches.

Conducting quality interviews with the customer, researching existing documentation on processes, standards and methodologies allows us to highlight the main emphases and main problems that must be addressed first. How to identify problems and their priorities, seek their solutions, assess risks? How to compare alternatives? In what order do the steps? What kind there are notations of the description of business processes depending on the problem being solved?

5. Not Be afraid to take responsibility for yourself.

In some things, primarily technical, the customer has consulting services and the user systems do not always have sufficient understanding and ability to assess possible consequences of the adoption of a decision. In these cases, it is necessary to take responsibility for themselves, proving their competence and inspiring confidence, while at the same time, insuring themselves documenting the solution. And often it is not too bad to get on it

  • b-blog-artice-aside-1
  • b-blog-artice-aside-2
  • b-blog-artice-aside-3
  • b-blog-artice-aside-4
Recommended articles