How To Fix VER_MESSAGES085 - Status "&1" returned; status "&2" expected

SAP Error Message - Details

• Message type: E = Error

• Message class: VER_MESSAGES - Message Class for FP Examples

• Message number: 085

• Message text: Status "&1" returned; status "&2" expected

What causes this issue?

Status "&1" returned; status "&2" expected

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VER_MESSAGES085 - Status "&1" returned; status "&2" expected ?

  The SAP error message VER_MESSAGES085 indicates a mismatch between the expected status and the actual status returned during a process. This error typically occurs in the context of document processing, such as when dealing with sales orders, purchase orders, or other transactional documents in SAP.
  Cause:
  The error message is triggered when the system receives a status that does not match the expected status for a particular operation. This can happen due to several reasons, including:
  
  Data Inconsistency: There may be inconsistencies in the data that the system is processing, leading to unexpected statuses.
  Configuration Issues: Incorrect configuration settings in the relevant modules (e.g., Sales and Distribution, Materials Management) can lead to mismatched statuses.
  Custom Code: If there are custom enhancements or modifications in the system, they might not handle certain statuses correctly.
  Workflow Issues: If the document is part of a workflow, issues in the workflow configuration or execution can lead to unexpected statuses.
  System Bugs: Occasionally, bugs in the SAP system or specific patches may cause this error.
  
  Solution:
  To resolve the VER_MESSAGES085 error, you can take the following steps:
  
  Check the Status: Review the status of the document or transaction that triggered the error. Compare the actual status with the expected status to identify discrepancies.
  Review Configuration: Ensure that the configuration settings for the relevant modules are correct. This may involve checking the status profiles, document types, and other related settings.
  Analyze Custom Code: If there are any custom developments, review the code to ensure it correctly handles the statuses. Debugging the code may help identify where the mismatch occurs.
  Check Workflows: If the document is part of a workflow, verify that the workflow is configured correctly and that all steps are being executed as expected.
  Consult SAP Notes: Search for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Testing: If changes are made, conduct thorough testing to ensure that the issue is resolved and that no new issues are introduced.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may need to use various transaction codes to investigate the issue, such as:
  
  SE80: Object Navigator for checking custom code.
  SE37: Function Module for debugging function modules.
  SLG1: Application Log for checking logs related to the error.
  
  
  SAP Community: Engaging with the SAP Community forums can provide insights from other users who may have encountered similar issues.
  SAP Support: If the issue persists and cannot be resolved internally, consider reaching out to SAP Support for assistance.
  
  By following these steps, you should be able to identify the root cause of the VER_MESSAGES085 error and implement a solution to resolve it.