A small note alongside this week's What's New in SAP Logistics Management, on something that didn't make it into the headline list but is worth a few minutes of your attention if you spend time in Define Processing Rules.
For a while now, several of you have been telling us — through tickets, partner sessions, and the occasional hallway conversation — that authoring a business rule meant knowing your data by heart. The product ID. The packing work center ID. The print queue name. Every field a blank text box, every typo discovered later, every lookup an alt-tab to another app.
We heard you. As of this week, those fields offer input help.
What that looks like
Open the rule editor. Click into a condition or output value field that references master data, and instead of a blank text box you get a dropdown of the values your tenant actually has, with search-as-you-type.
The dropdown is context-aware, so as you fill in earlier fields the choices for later ones narrow to what makes sense in your scenario.
The same input help shows up in the rule testing dialog, so trying out a rule no longer means hunting for valid input parameters in another tab.
And if you do manage to enter a value that no longer exists — a `OUTB_STANDRD` where you meant `OUTB_STANDARD` —, the system stops the save and tells you what's wrong, rather than letting a broken rule sit there waiting to fail at runtime.
It isn't a revolutionary change. But we believe it'll save real time for the people who configure these rules every day, and we wanted to make sure it didn't go unnoticed.
To the customers and partners who raised this — including the very direct ones who told us, in so many words, “please give us a search help, this is painful” — thank you. Keep the feedback coming. It's the most useful thing you can send us.
