How To Fix T8066 - Result for transaction &1 per date &2 taken from price table

SAP Error Message - Details

• Message type: E = Error

• Message class: T8 - Analysis system evaluations

• Message number: 066

• Message text: Result for transaction &1 per date &2 taken from price table

What causes this issue?

The transaction was not calculated, but instead a value was taken from
the OTC price table.

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?

You maintain the price table as follows: in the market risk management
menu under Market data -> Current settings -> OTC price table.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message T8066 - Result for transaction &1 per date &2 taken from price table ?

  The SAP error message T8066 typically indicates an issue related to pricing or valuation in the system. This message is often encountered in the context of material management or sales and distribution modules when the system is unable to retrieve the expected pricing information from the price table for a specific transaction and date.
  Cause:
  
  Missing Price Data: The price data for the specified transaction and date may not exist in the price table.
  Incorrect Date: The date specified in the transaction may not correspond to any valid pricing records.
  Configuration Issues: There may be configuration issues in the pricing procedure or the condition records.
  Data Inconsistencies: There could be inconsistencies in the master data or transaction data that prevent the system from fetching the correct price.
  Authorization Issues: The user may not have the necessary authorizations to access the pricing information.
  
  Solution:
  
  Check Price Records: Verify that the price records exist for the specified transaction and date in the relevant condition tables (e.g., KONP for sales pricing).
  Update Pricing Conditions: If the price records are missing, you may need to create or update the pricing conditions using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
  Review Date Settings: Ensure that the date used in the transaction is correct and falls within the validity period of the pricing records.
  Check Configuration: Review the pricing procedure configuration in the customizing settings (transaction SPRO) to ensure that it is set up correctly.
  Data Consistency Check: Run consistency checks on the master data and transaction data to identify any discrepancies.
  Authorization Check: Ensure that the user has the necessary authorizations to access the pricing information.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13 (Display Condition), and SPRO for configuration.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to pricing errors.
  Documentation: Review SAP documentation or help files related to pricing and condition records for further insights.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to diagnose and resolve the T8066 error message effectively.