How To Fix 9J536 - Dominance price determination not found for & & & &

SAP Error Message - Details

• Message type: E = Error

• Message class: 9J -

• Message number: 536

• Message text: Dominance price determination not found for & & & &

What causes this issue?

No entry was found for the key in the dominance indicator table:
Document type : &v1&
Transaction type : &v2&
Sender/recipient type : &v3&
Resourcen type : &v4&

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

System Response

How to fix this error?

In Customizing, enter an appropriate entry.
<DS:SIMG.J_3GV_MEMPFDOM>Execute Function</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 9J536 - Dominance price determination not found for & & & & ?

  The SAP error message 9J536, which states "Dominance price determination not found for & & & &," typically occurs in the context of pricing and valuation in SAP, particularly when dealing with condition records for pricing in sales and distribution (SD) or materials management (MM).
  Cause:
  This error usually arises when the system is unable to find a valid pricing condition record for the specified combination of parameters (like material, customer, plant, etc.) in the pricing procedure. The "& & & &" placeholders represent the specific fields that are missing or not correctly configured.
  Common causes include:
  
  Missing Condition Records: There are no condition records defined for the pricing conditions that are required for the transaction.
  Incorrect Configuration: The pricing procedure may not be correctly configured to handle the specific combination of parameters.
  Dominance Price Not Defined: The dominance price determination logic may not be set up correctly in the system.
  Data Inconsistencies: There may be inconsistencies in the master data (like customer or material master) that prevent the system from finding the correct pricing conditions.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the necessary condition records exist for the pricing conditions involved.
  Ensure that the condition records are maintained for the relevant combination of material, customer, and other relevant fields.
  
  
  
  Review Pricing Procedure:
  
  Use transaction code V/08 to review the pricing procedure assigned to the sales document type or purchasing document type.
  Ensure that the pricing procedure includes the necessary condition types and that they are correctly configured.
  
  
  
  Check Master Data:
  
  Verify the master data for the customer and material to ensure that all necessary information is correctly maintained.
  Check if the customer is assigned to the correct sales area and that the material is available in the relevant plant.
  
  
  
  Dominance Price Configuration:
  
  If applicable, check the configuration for dominance price determination in the customizing settings (transaction code SPRO).
  Ensure that the settings for dominance price determination are correctly defined.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help notes related to pricing and condition records for further insights.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the pricing procedure to identify where the determination is failing.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11, VK12: For maintaining condition records.
  V/08: For reviewing pricing procedures.
  SPRO: For accessing the SAP Customizing Implementation Guide.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  Community Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify and resolve the cause of the 9J536 error in your SAP system.