Things have been quite busy for me as of late leaving me very little time for posting new content on this blog. Lately, though, I had the opportunity to write a blog post for my employer, itelligence, and I thought I would share that link with you here (itelligencegroup.com). You are more than welcome to request access to the accompanying webinar recording (at the bottom of the linked page), but keep in mind the applicants may be screened beforehand. Enjoy.
I’ve been playing a bit of catch up this week. I’ve got a rather large backlog of articles to publish. Today, I’m starting with some new content in my SAP SD Reference Guide series:
One of the best weapons in a support consultant’s arsenal is the ability to review document changes. Sometimes, being able to build a precise timeline around occurrences of an issue can be crucial to finding a solution. Let’s discuss more about the structure and use of change records in Sales and Distribution.
I recently took a trip into my own personal way-back machine — an old Western Digital Passport drive — and found this golden oldie: A diagram I made years ago in MS Visio illustrating the intricate complexities of SAP’s Route, Leg and Packing determination.
The term “backorder” is common across most industries. They are also the bane of most customer service organizations who are often caught in between struggling processes and angry customers. In this two part series, I’ll discuss how to recognize a backorder issue, approaches to identify sources, and how SAP can help?
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.
It’s not uncommon for me to receive questions regarding date fields on SAP Sales Orders. That should not be surprising considering that users will be confronted by no less than 10 date fields during normal order maintenance. That number can rise to more than 15 depending on how you slice the numbers. In this article, I will explore these date fields and how they impact other activities.
While researching solutions for a client, I learned quite a bit about SAP’s rounding capabilities. In my experience, I haven’t encountered a situation where this EXACT functionality would be necessary, but I’m sure it will come in handy for a few of you folks out there. Let’s find out a bit more about this function.
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.