How To Fix WV314 - Pricing date change: log entries exist

SAP Error Message - Details

• Message type: E = Error

• Message class: WV - Messages about Sales Price Calculation

• Message number: 314

• Message text: Pricing date change: log entries exist

What causes this issue?

Log entries have been generated for the change in price determination
date.
Just as in standard sales price calculations, log entries are created
for pricing items for which no price calculation could be performed on
the price determination date, or for which warnings are generated.
If the price determination date is changed using the setting that the
parameters Vendor and Purchasing organization and the sales-side prices
are to remain the same and that the additional entries are to be taken
into account, the pricing items that return errors when the parameters
named are taken into account are logged with appropriate error messages
(see example).

System Response

Pricing items that contain errors are not displayed in the pricing
table.
For those pricing items that return errors when the additional entries
are taken into account, the new calculations that are performed on the
new price determination date are displayed.
These pricing items are highlighted in color for easy recognition.
The log contains information on why the desired pricing parameters
could not be taken into account.

How to fix this error?

Check the log and process the affected pricing items as necessary.

How can this happen?

There are two vendors (no regular vendor) for article 4711:
Vendor 1000, price 10 USD, delivery period 01.03.2000 - 31.12.9999
Vendor 2000, price 11 USD, unrestricted delivery period. You calculate
for article 4711 in distribution chain 0001/01 on 01.07.2000. Supply
source determination finds vendor 1000.
You change the pricing date to 01.01.2000 and select the option "Retain
Vendor, Purchasing Organization and Prices".
Vendor 1000 cannot be used with a delivery date of 01.01.2000 due to
the restricted delivery period. The new price calculation (highlighted)
that was performed using vendor 2000 is therefore displayed. The log
entry explains that vendor 1000 is not an allowed source of supply.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WV314 - Pricing date change: log entries exist ?

  The SAP error message WV314 ("Pricing date change: log entries exist") typically occurs when you attempt to change the pricing date in a sales document (like a sales order or quotation) but there are existing log entries that prevent the change. This is often related to the pricing conditions that have been applied to the document.
  Cause:
  
  Existing Log Entries: The primary cause of this error is that there are log entries associated with the pricing conditions of the document. These logs are created to track changes and ensure data integrity.
  Document Status: The document may be in a status that does not allow changes to the pricing date.
  Custom Logic: There may be custom logic or enhancements in place that restrict changes to the pricing date under certain conditions.
  
  Solution:
  To resolve the WV314 error, you can follow these steps:
  
  
  Check Log Entries:
  
  Navigate to the document in question and check for any existing log entries related to pricing. You can do this by using transaction codes like VA03 (Display Sales Order) and looking for the pricing condition logs.
  
  
  
  Delete or Archive Logs:
  
  If the logs are no longer needed, you may need to delete or archive them. This can often be done through specific transaction codes or by contacting your SAP administrator for assistance.
  
  
  
  Change Document Status:
  
  Ensure that the document is in a status that allows for changes. If the document is completed or has been processed in a way that locks certain fields, you may need to revert it to a status that allows changes.
  
  
  
  Consult Custom Logic:
  
  If there are custom enhancements or user exits that affect the pricing date, consult with your ABAP developer or SAP consultant to review the logic and determine if it can be adjusted.
  
  
  
  Use Alternative Methods:
  
  If changing the pricing date is not possible, consider creating a new document with the desired pricing date and transferring the necessary information from the old document.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VA03 (Display Sales Order), VA02 (Change Sales Order), and VK13 (Display Condition).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for specific notes that may address this issue.
  Documentation: Review SAP documentation related to pricing and condition records to understand how logs are managed and how they can affect pricing changes.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to your SAP support team for further assistance.