How To Fix OD685 - Mismatch of field names for check call and authorization.

SAP Error Message - Details

• Message type: E = Error

• Message class: OD - IS-Oil: TSW Traders' and Schedulers' Workbench messages

• Message number: 685

• Message text: Mismatch of field names for check call and authorization.

What causes this issue?

The field names of the check call in the progam do not match those of
an authorization. Either the authorization or the call is incorrect.

System Response

The execution of the transaction is prohibited.

How to fix this error?

Please inform your system administrator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message OD685 - Mismatch of field names for check call and authorization. ?

  The SAP error message OD685, which states "Mismatch of field names for check call and authorization," typically occurs in the context of SAP's authorization checks, particularly when there is a discrepancy between the fields expected by the authorization check and those provided in the check call.
  Cause:
  
  
  Field Mismatch: The error usually arises when the fields defined in the authorization object do not match the fields being passed in the check call. This can happen if:
  
  The authorization object has been modified (fields added or removed).
  The program or function module calling the authorization check is not aligned with the current definition of the authorization object.
  There are inconsistencies in the configuration or custom development.
  
  
  
  Custom Development: If there are custom programs or enhancements that involve authorization checks, they may not be correctly aligned with the standard SAP authorization objects.
  
  
  Transport Issues: If changes to authorization objects or related configurations were transported from one system to another (e.g., from development to production), there may be inconsistencies if the transport was not executed properly.
  
  
  Solution:
  
  
  Check Authorization Object: Verify the definition of the authorization object involved in the error. Ensure that the fields defined in the authorization object match those being used in the check call.
  
  
  Review Custom Code: If the error is occurring in a custom program, review the code to ensure that it is correctly calling the authorization check with the appropriate fields. Make sure that the fields being passed match the expected fields in the authorization object.
  
  
  Consistency Check: Perform a consistency check on the authorization objects and related configurations. This can be done using transaction codes like SU21 (for authorization objects) and SU24 (for authorization checks).
  
  
  Transport Validation: If the issue arose after a transport, check the transport logs and ensure that all necessary objects were transported correctly. You may need to re-transport or adjust the objects in the target system.
  
  
  Debugging: If the issue persists, consider debugging the program to trace the exact point of failure and identify the specific fields causing the mismatch.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on similar issues.
  
  
  Related Information:
  
  Authorization Objects: Understanding how authorization objects work in SAP is crucial. They define the fields and values that control access to various transactions and data.
  Transaction Codes: Familiarize yourself with transaction codes like SU53 (to analyze authorization failures) and SUIM (to check user authorizations).
  Documentation: Review SAP documentation on authorization management for best practices and troubleshooting tips.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or Security team for further assistance.