I came across a rather humorous comment in SAP code while debugging with a colleague the other day. It gave me a chuckle and I thought I would share it here. Read on for more regarding “the new spaceship BERID”!Continue reading “SAP Humor: “the adventures of the new spaceship BERID””
I have had the opportunity to steep myself in SAP S/4’s new SAP Settlement Management module. While I’m sure that I’ve barely scratched its surface, it has a demonstrated a strong capability to provide a framework for structuring complex Trade Promotions agreements. One particular scenario seemed like it was going to require some development, but I was surprised at some of the legwork SAP has already done to assist us consultants. Read on to learn more.Continue reading “SAP Settlement Management: The Multiple Contract Condition Problem”
If you’re writing an ‘Open Orders’ report, chances are you are intersted in the delivery status of your Sales Order. You man have noticed that there are two delivery statuses (stati?) found on the Sales Document Header and Item level: “Delivery Status” and the “Overall Delivery Status”. What do these statuses represent? Read on to learn more about the SAP Sales Order Delivery Status fields.
For consultants and power users, viewing SAP table contents is a necessity. I use the SAP SE16n table display transactions daily to sift through records while analyzing data issues, finding example records, or simply finding that Sales Order I created months ago in a client system. I nearly always rely on SAP’s SE16n transaction for these activities for a variety of reasons, but during a recent client meeting, I learned that there appears to be some hold-outs who still use the older SE16 transaction. If you choose not to use SE16n, or are simply not aware of its capabilities, read on for my top 6 reasons to become an SAP SE16n Table Display fanatic.
Picking, Packing, Shipping… Seems straightforward, right? But when you introduce batch splitting and factor in product availability issues, reporting against delivery quantities can be a challenge. But there are some interesting fields that exist under the hood that can help you build a more powerful report. I have previously demystified Sales Order Date fields. This time, let’s dive into SAP Delivery Quantity fields.
Within the Logistics Execution module, there are few functions as important as Delivery Creation. After all, you can’t bill for what you don’t ship. Even within S/4 Hana, the VL10 transactions seem to offer the best, most flexible way to create deliveries. But what if you need to adjust the way SAP selects delivery scope in these transactions? Read on to see how I used the SAP Delivery Due Index routine to filter out certain deliveries from the list.
This question on SAP discounts 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 SAP change records in Sales and Distribution.
SAP User Exits… Depending on your perspective, they are either a saving grace which allows you to bend SAP to your liking, or a frightening Carte Blanche which allows your clients to do the most crazy stuff (and later ask you to fix it). Either way, they are a critical tool for an SAP consultant. Their number is legion and here is how to find them. …all of them.
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 SAP Condition Update function.