The SAP HR blogosphere is rich with content focused on thought leadership, technology trends and case studies which describe both successful and failed projects. While any of my clients will attest to the fact that I am unafraid to share my opinions, I do not intend to add more content to the internet which might be considered esoteric, out of context, or heaven forbid a drag simply because a potential reader had to wade through it to get to something more worthy of their time.
Back in my days as a business analyst, I loved doing research to keep current with the industry trends – it made me feel intelligent when talking to consultants. Every now and then, however, I would come across a gem of information which taught me job specific, time-saving and immediately valuable information which helped me work smarter. It is my intent to periodically add nuggets of useful information, which a reader with access to a SAP HR system might feel compelled to log in and immediately begin using.
Remember way back when somebody first taught you how to search for a person in SAP by using =n.lasname? Gem! How about =n.lastname.firstname? Another gem!
Oversimplified examples for sure, but there’s so much other stuff out there to share!
My humble goal is to add more little gems (perhaps a little more complex than the ‘=n.’ matchcode trick) which will help actual SAP users make better use of tools they have, but perhaps don’t know about. My noble goal is to help them leave work at 5:00 more often and take Fido for a long walk. Hell… I once had an E-Recruiting customer print up a t-shirt which looked a little something like this after I shared a few tips, but let’s not get carried away:
For the record, that client was in San Francisco….
At AspireHR, we often jest about the ‘Hero Mentality’ fostered by the larger consultancies we spent time with in our early careers. Hero Mentality is the tendency of those in knowledge based environments to hoard information, so they may guarantee themselves to be the one called upon to save the day what a particular issue arises. Typically, it’s just a little nuance that one learns from doing some targeted research or testing, then guards the information as if it’s a trade secret.
I must admit that I am guilty of my own Hero Mentality. However in my version, I feel like a small-scale hero when I share little tidbits of information which makes SAP a little more usable for people. These are the simple tips I share for the selfish pleasure of enriching others, and I thank you for allowing me to indulge!
I sure hope my sharing of SAP HR tips are better received than the skiing tips I provide to my wife…
So goes my first blog post…and unless you were unaware that you could search for a person in PA20 by typing =n.firstname.lastname in the Personnel Number field, I haven’t shared any useful information yet.
Here is a trick that will be super helpful to anybody in the ESS/MSS world:
For the longest time, we used to go through this contrived process involving SE16N to find out which employee is associated with a particular SAP username. Did you know that you can find a person by typing all or a portion of the username into the ‘Personnel Number’ field in PA20. Simply type in =U..username
(Note that there are 2 dots!) and voila!
That was an easy one that only recently learned. Here is a small list of my upcoming topics which might prove a little more useful to you:
1) What ‘Getting your house in order to prepare for MSS’ really means
2) Simple ways to identify inconsistent data in your managerial structure
3) How to do joins, unions and intersections in Ad Hoc Query
4) How to create a link directly to an ESS or MSS iView in the Portal
5) How to create transaction codes for commonly run Ad Hoc Reports
Thanks for reading! I promise less drivel, more content in my next post!