Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/69747241-1550-8008-8dcb-0501d3d7b74a
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: 😅 You’re not wrong — and yes, lots of customers have complained about this. === 😅 You’re not wrong — and yes, lots of customers have complained about this. You’re very much not alone. ===== 👉 Yes, this has been asked for repeatedly ===== 👉 No, SAP still hasn’t opened it up in S/4HANA Cloud (Public) 👉 It’s a deliberate “clean-core / UI consistency” choice, not an oversight ==== Across SAP Community, TechEd Q&A, and Customer Influence sessions, the same asks keep coming back: ==== * “Why can I fully tailor the email, but not the My Inbox task title?” * “Managers can’t see what actually changed in a PR/PO without drilling in.” * “Inbox items are too generic for high-volume approvers.” * “Let me at least add context like WBS / WO / delta amount / budget status.” This comes up a lot in: * Purchase Requisition workflows * Service Entry Sheet approvals * Project / WBS-based spend approvals * Central Finance & shared-service inboxes So yes — you’re echoing a very common frustration. ==== SAP’s official stance is basically: ==== : In other words: * 🧱 Inbox = rigid, standardized UI * ✉️ Email = flexible, customer-specific communication From a clean-core and lifecycle perspective: logical From a manager productivity perspective: 🤦♂️ ==== SAP has acknowledged the pain, but instead of letting you change the inbox text directly, they’re pushing indirect mitigations: ==== ===== You already mentioned this — and yes, this is SAP’s preferred workaround: ===== * Add more context fields to the task * They appear in the right-hand pane, not the title * Still requires clicks → still sub-optimal for bulk approval ===== - Column visibility tweaks ===== * Sort/filter improvements * Still no control over task title text ===== SAP is clearly betting on: ===== : That’s… optimistic 😬 And today, Joule Base does NOT fix this gap. ==== For high-volume approval environments like yours: ==== * 2–2.5k PRs/month * Many-line PRs * WBS + WO driven spend * Managers approving between meetings 👉 Inbox text quality directly affects cycle time and stress 👉 SAP knows this 👉 But Inbox title customization is still not on the public roadmap ==== None are great, but these are the patterns: ==== # Over-invest in email content - Put all critical context + deltas in the email - Inbox becomes just a “click-through launcher” # Aggressive context enrichment - WO / WBS - Old vs new value - Budget availability flag - Still one extra click, but tolerable # External approval dashboards - Datasphere / Power BI “Approval cockpit” - Inbox only used for final action - Very common with finance-heavy customers # Wait-and-hope strategy - Many have raised this via Customer Influence - No committed delivery yet ==== : ==== : : If you want, next step I can: * Pull together exact SAP Community threads echoing this * Help you phrase a Customer Influence request SAP actually listens to * Or help you design the least-bad inbox + email + Joule combo for PRs specifically Just say the word.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)