Do you have any question about this error?
Message type: E = Error
Message class: SD - Online doc., terminology, translation, help
Message number: 836
Message text: & & & &
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.
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.
SD836
- & & & & ?The SAP error message SD836 typically relates to issues in the Sales and Distribution (SD) module, particularly concerning the pricing procedure or the condition records. The error message may indicate that there is a problem with the pricing conditions for a sales document, such as a sales order or a quotation.
Cause:
- Missing Condition Records: The pricing procedure may not have the necessary condition records defined for the specific sales area, customer, or material.
- Incorrect Pricing Procedure: The pricing procedure assigned to the sales document may not be appropriate for the transaction.
- Inconsistent Data: There may be inconsistencies in the master data, such as customer master, material master, or info records.
- Configuration Issues: The configuration of the pricing procedure in the system may not be set up correctly.
Solution:
Check Condition Records:
- Go to the transaction code
VK13
(Display Condition) to check if the necessary condition records exist for the relevant pricing conditions.- Ensure that the condition records are maintained for the specific sales area, customer, and material.
Review Pricing Procedure:
- Use transaction code
V/08
to review the pricing procedure assigned to the sales document type.- Ensure that the pricing procedure is correctly configured and that all required conditions are included.
Verify Master Data:
- Check the customer master data (transaction code
XD03
) and material master data (transaction codeMM03
) to ensure that they are correctly maintained.- Look for any missing or incorrect entries that could affect pricing.
Configuration Check:
- If you have access to configuration, check the settings in the SPRO transaction under Sales and Distribution > Basic Functions > Pricing > Pricing Control.
- Ensure that the pricing procedure is correctly assigned to the sales document type and that all necessary condition types are included.
Consult Documentation:
- Review SAP documentation or notes related to the specific error message for additional insights or updates.
Contact Support:
- If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for further assistance.
Related Information:
VK13
- Display Condition RecordsV/08
- Maintain Pricing ProceduresXD03
- Display Customer MasterMM03
- Display Material MasterBy following these steps, you should be able to identify and resolve the issue causing the SD836 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
SD835
Object locked (already being edited by another user)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SD834
Documentation element saved
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SD837
Object & does not have a long text
What causes this issue? There is no entry for the object in the table DOKIL.System Response Message SD (E)837How to fix this error? The system iss...
SD839
Object & does not have any exceptions
What causes this issue? no exceptions have been defined for the object, i.e. there are no entries in the table TSKT6.System Response Message SD (I)8...
Click on this link to search all SAP messages.