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:
This question comes courtesy of Val:
I’m configuring a series of % discounts in SD. Each needs to apply a % to the price, not to the value (SAP default), so the price per unit decreases with each discount. The result is a slightly different final total value from the standard method. I can’t find a way in standard config, all I can do is a standard value: can you suggest anything? Do I need a custom requirement?
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.
This question comes courtesy of Krishna. He writes (edited for clarity):
My requirement is to give a discount for the first 50 sales orders. I tried this using the condition update tool. It is limited to only 3 sales orders. I want to make it for 50 sales orders, but I am not getting anywhere. Please help me.
I’m not sure there’s much good news ahead on this one, but let’s take a closer look at the ‘Maximum number of orders’ in the Condition Update function.
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.
My clients’ pricing procedures come in all shapes and sizes — from the bizarrely complex to Spartan simplicity. I also find a huge variance in the number of procedures. I was in a system the other day whose procedures numbered in the DOZENS. All of this got me to thinking about the standard SAP pricing procedures and how their structure and rationale may help with inspiration to stick with the standard structure.
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.