Frequently Asked Questions

Download and read the FAQ document:

PDF version FAQs for SAP Customer Connection

In case you have a specific question, please contact us by email at influencing@sap.com.

Why is a Feedback Agreement (FbA) needed?

The Feedback Agreement describes the principles of the working relationship with all involved parties. The most important ones are:

Intellectual Property (IP):

Customers want to influence SAP software (maybe even services). Customers want to see their feedback/ideas in SAP software. For being able to actually incorporate such feedback in our software, SAP needs the right to do so. That's why SAP needs a royalty free license. SAP does not want the Intellectual property on the feedback/ideas. This remains with the customers, such that customers could use that IP to create own solutions or even products. Section 6 of the Feedback Agreement says that very clearly.

Non-disclosure:

All information and feedback exchanged needs to be treated as confidential, needs to stay within the group. This is true for information SAP discloses as well as info customers disclose to SAP or to each other. In many cases we share either immature planning or internal information, that needs to be treated confidential. This is being handled in the feedback agreement section.

Customer Commitment:

In many cases we discuss software to be built or shipped in 1-2 years time. Sometimes (when we discuss research topics) even longer. As you never know what the future will bring, SAP needs to have the ability to change plans. 

 

FbA Chinese version Chinese translation of the FbA rationale

Japanese translation of FbA rationale Japanese translation of the FbA rationale

Status Values of Customer Connection Requests
Please find more information about the status values ... under construction!
 
Customer Connection Request Status Flow
Meaning of request status values
Status Explanation
Identified Request has been submitted 
Qualified Request has reached the required number of subscriptions to be treated as qualified. It will be analyzed by the development team during the Select phase.
Pending A final decision has not been made yet. SAP either require more time for evaluation or more detailed information. The improvement request owner will be contacted in the later case for clarification.
Scoped Request has been included into the development planning for this project. SAP plans to deliver an improvement based on this request. Nevertheless, there is no commitment about the scope what or timeline when to deliver. The request might even be rejected if SAP changes mind during the implementation.
Handed over Request has been analyzed and belongs to a different department at SAP. The request has been transferred into the responsibility of this department. No further follow up within the Customer Connection project.
Rejected Request has been rejected; rejection reason is given in the status change comment. It will not be  
Delivered Request has been implemented and delivered. Please see the status change comment in order to learn how to use the new improvement.
Under Review for Portfolio

Request has been analyzed and indentified as exceeding the capabilities of the Customer Connection project.

The request is currently under review whether it fits into the portfolio planning for future product releases.

Rejected for Portfolio

Request has been analyzed and indentified as exceeding the capabilities of the Customer Connection project.

It also does not fit into the future product portfolio and will not be followed on any further by SAP. 

Planned for Portfolio

Request has been analyzed and indentified as exceeding the capabilities of the Customer Connection project.

The request has been taken into the planning for the future product portfolio. Nevertheless, there is no commitment about the scope what or timeline when to deliver. The request might even be rejected if SAP changes mind during a later time.