I make a lot of trips to the home improvement store throughout the year. Unfortunately, many of my trips are necessary because I neglected to put an important item in my cart on a previous trip. If only there was a way for the store clerk to prompt to purchase additional items related to those already in my cart. This could simultaneously increase the store’s sales — reducing the risk I purchase items elsewhere — while saving me extra trips to the store. Fortunately for companies running SAP, this feature DOES exist and it is called Cross-Selling. Let’s take a deeper dive.
First off, this post is mostly stemming from frustration. So, if you’re expecting some sort of magic bullet to handle this scenario, I can’t offer you much. What I can offer you is a list of options, how they work, and why they may not fully satisfy the requirement. It seems simple: You want to offer your customers gradually reduced pricing — or gradually increased discounts — as they purchase throughout the year across multiple sales orders. Though seemingly simple, the solution is not.
Announcing one of the latest additions to the Windows Phone Store: the SAP SD Reference Guide. This is an app that I made using the App Studio (detailed on my blog here). As of this afternoon, my app officially gained certification and is now available in the Windows Phone Store. For more information, please visit my Apps 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.