SAP Continuous Influence for SAP S/4HANA Cloud, Public Edition – Session List and Rules of Engagement

Below find a list of influence sessions to product influence SAP S/4HANA Cloud, Public Edition. Before you submit and vote on a request, kindly check out the rules of engagement.

The product in focus

• In product scope: SAP S/4HANA Cloud, public edition
• Not in product scope: SAP S/4HANA Cloud, private edition, SAP S/4HANA (on-premise).
  If not-in scope product requests are submitted, SAP reserves the right to close such requests in the named channels.

Who is entitled to submit and vote

• Customers and partners implementing and using SAP S/4HANA Cloud, public edition
• Partners selling and implementing SAP S/4HANA Cloud, public cloud or providing this solution as part of a managed-cloud solution to customers
• You require an S-User to submit and vote in Customer Influence portal, you need to accept respective terms and conditions once.

What you submit and vote for

• You submit and vote on none go-live critical feature requests for the above name product, hereby expressing an underlying business need.
• You indicate the following:
  • You require this functionality to improve your business operations or
  • You expect this functionality to close a gap in your business operations
• Kindly refrain from supporting or duplicate votes for features which you do not use or do not intend to use.

As a partner implementing and operating the solution for a customer, you apply such criteria on behalf of the customer.

How it works and what we check

1. Initial response: SAP continuously checks your requests and provides an initial response via the status “Acknowledged”. This indicates the request is understood and in the right session. It does not reflect any sort of planning status. The request is now open to other community members for voting.
2. Qualified response: Once the voting threshold is achieved, SAP evaluates the requests in more detail. Depending on a variety of factors, incl. strategic fit, technical feasibility, existing commitments, backlog and capacity, a request receives a more specific response indicating if the request is accepted short-term, planned mid-term or considered longer-term. This may also translate to a “Not planned” if above criteria are not met. Such proceeds will give you more planning security.
3. Request delivered: Once the request is delivered, SAP will indicate the delivery via the corresponding status “Delivered” and delivery release. If a solution already exists for a requested functionality, this is generally indicated via “Already Offered”.

2. and 3. are typically processed as part of a dedicated and more focused review phase, currently running on a quarterly basis. Additionally, the sessions communicate latest progress and deliveries.

More details on our SAP Continuous Influence community page, section Latest Updates.

Session list

What is a session? A session is an LoB or topic-related feedback channel for which SAP offers to submit and vote for improvement requests. Please note: Not every topic has its own session.
Additionally, SAP reserves the right to open, extend, size down and close sessions anytime as needed.

Prior to submission

Has a similar request already been raised? Kindly check prior to submission using the “Search” functionality. If not yet available, this is where you can file your requests: