How To Fix VN526 - Missing auditor rights: & blocked conditions not shown

SAP Error Message - Details

• Message type: E = Error

• Message class: VN - Nachrichtensteuerung

• Message number: 526

• Message text: Missing auditor rights: & blocked conditions not shown

What causes this issue?

You don?t have sufficient authorization to access blocked condition
records

System Response

Blocked condition records are not being displayed.

How to fix this error?

To access blocked condition records, you need to sign on to the system
with a user who has sufficient auditor rights.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VN526 - Missing auditor rights: & blocked conditions not shown ?

  SAP Error Message:
  
  VN526 - Missing auditor rights: & blocked conditions not shown
  
  Cause:
  This error occurs when a user tries to display or process blocked purchasing conditions (such as blocked pricing conditions) but does not have the necessary auditor authorization to view these blocked conditions. In SAP, certain conditions can be blocked for various reasons (e.g., price changes under review), and only users with specific auditor rights can access or display these blocked conditions.
  The message indicates that the user lacks the required authorization object or role that grants the "auditor rights" to view blocked conditions in purchasing documents or condition records.
  
  Explanation:
  
  Blocked conditions are conditions that have been flagged (blocked) during condition maintenance or document processing, often for audit or control reasons.
  SAP restricts access to these blocked conditions to prevent unauthorized users from seeing or modifying them.
  The authorization check is typically related to the authorization object M_BEST_BSA (Purchasing Document Types) or M_BEST_EKG (Purchasing Document Groups), or more specifically to condition-related authorizations.
  The user needs the auditor role or specific authorization to view blocked conditions.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Verify if the user has the necessary authorization roles or profiles assigned.
  Specifically, check for roles that include the authorization to display blocked conditions in purchasing.
  The authorization object often involved is M_BEST_BSA or M_BEST_EKG, but also check for any custom authorization objects related to condition auditing.
  
  
  
  Assign Auditor Role:
  
  Assign the appropriate auditor role or authorization to the user.
  This role is usually named something like SAP_MM_AUDITOR or a custom role created for auditors.
  The role should include permissions to display blocked conditions and related purchasing documents.
  
  
  
  Use Transaction SU53:
  
  Have the user execute transaction SU53 immediately after the error occurs.
  This will show the failed authorization check and help identify the missing authorization object and field values.
  
  
  
  Consult with Security Team:
  
  Work with your SAP security team to grant the required authorizations.
  Ensure that granting these rights complies with your company’s security and segregation of duties policies.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  MEK1 / MEK2 / MEK3 – Condition maintenance transactions where blocked conditions might be visible.
  ME23N – Display Purchase Order, where blocked conditions might be shown.
  SU53 – Authorization check failure analysis.
  
  
  
  Authorization Objects:
  
  M_BEST_BSA – Purchasing Document Type
  M_BEST_EKG – Purchasing Document Group
  Possibly custom authorization objects related to condition auditing.
  
  
  
  Notes and Documentation:
  
  Check SAP Notes related to VN526 for any updates or patches.
  Review SAP Help Portal documentation on condition records and authorization concepts in MM (Materials Management).
  
  
  
  
  Summary:
  
  Cause: User lacks auditor authorization to view blocked purchasing conditions.
  Solution: Assign the appropriate auditor role/authorization to the user.
  Check: Use SU53 to identify missing authorizations and consult with security team.
  
  
  If you need further assistance, please provide the user ID, transaction code used, and the exact scenario where the error occurs.