How To Fix FSH_SD_COMMON036 - Non requirement relevant contract

FSH_SD_COMMON036 - Overview

• Message type: E = Error

• Message class: FSH_SD_COMMON -

• Message number: 036

• Message text: Non requirement relevant contract

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FSH_SD_COMMON036 - Non requirement relevant contract ?

  The SAP error message FSH_SD_COMMON036 indicates that a contract is not relevant for requirements processing in the context of Sales and Distribution (SD) and Flexible Sales Handling (FSH). This typically occurs when trying to create or process a sales order or contract that does not meet the necessary criteria for requirements determination.
  
  Cause:
  
  Contract Type: The contract type may not be set up to be relevant for requirements processing. Certain contract types are designated as non-requirement relevant.
  Contract Status: The status of the contract may not allow it to be used for requirements. For example, if the contract is inactive or has been completed.
  Item Category: The item category used in the contract may not be configured to allow for requirements processing.
  Configuration Settings: There may be specific configuration settings in the system that determine whether a contract is considered relevant for requirements.
  
  
  Solution:
  
  Check Contract Type: Review the contract type being used and ensure it is