My favorite ASUG News journalist, Courtney Bjorlin, just penned an interesting article titled ‘SAP Software and Divestitures: 4 Hard-Earned Lessons Learned’. And “Hard-Earned” is spot on. In it, she chronicles the struggles of Cooper Industries as they tackle the divestiture of their Tools division. I was happy to have played a small role in the article as a contributor, sharing some of my experiences in the four divestiture projects (not including my current pseudo-divestiture assignment) I have been involved with. The delicate arrangement of stakeholders — the buying entity, the selling entity, systems integrators, divested personnel, legal representation, etc. — can make for some unique challenges. For more details and insights into my divestiture experience, also check out my Divestiture Project Profile page.
One of the constant struggles for SAP users and consultants alike is the attempt to recollect transaction codes and table names that are infrequently used. Having a reliable list at your fingertips has proven to be helpful in those times of need. That concept inspired me to compile and publish a couple of ‘quick user guides’ that can be used for that purpose. I submit for your approval the first draft of a user-oriented guide: SAP Sales and Distribution – Quick Reference Guide for the User.
This post is dedicated to the four hours of my life I lost trying to figure out why my mandatory header texts were misbehaving. A client had requested that a header text be mandatory for all Credit Memo (CR) and Debit Memo (DR) documents. Makes sense. Standard SAP only prescribes an order reason be maintained, but sometimes you want to capture more details behind the rationale for such transactions. “Easy breezy,” I thought. Wrong.
In the next installment of my SAP Tips and Tricks series, I will explore some additional user interface features that you can use to be a more efficient SAP user. You may also want to check out Part 1 in the series. Continue reading to find out more.
I have continued to develop additional project profiles which expand upon some of my specific project experience noted in my Resume. The new entries are available through the Resume menu above, or by clicking on the links below:
One thing that clients repeatedly ask for are time-saving tips and shortcuts that they can use while navigating SAP using SAP GUI. A few years ago, I started a collection of exactly that. I would like to share them here in a series called ‘SAP Tips and Tricks’.
I recently decided that my Resume is a bit one-dimensional. It focuses on my particular involvement in the project, but doesn’t acknowledge the overall scope and goals of that effort. I’ve decided to create Project Profiles to provide some of that context. So far, I have created two but when I’m done, there should be a total of five. Here are the ones I’ve completed:
They’re also accessible through the Resume menu above.
If you’ve read past the title of this post, then you’re probably already familiar with SAP’s Hierarchical Access (HA) debacle. Long story short: SAP was sued for patent infringement in the US and they are now forced to disable one particular pricing feature for all of their US installations — the HA function. Therefore, this affects ALL of my clients.
Based on my personal experience, this feature isn’t widely used. And for those customers NOT using it, there is a relatively simple process to remove the feature, validate the removal and move onto more pressing matters. However, I recently encountered my first client who actively utilizes the HA function and the process becomes somewhat more involved.