How To Fix VN340 - Description and mail text are redefined during determination

SAP Error Message - Details

• Message type: E = Error

• Message class: VN - Nachrichtensteuerung

• Message number: 340

• Message text: Description and mail text are redefined during determination

What causes this issue?

The condition record contains no language.

System Response

During output determination, the description and the notification text
of the mail are redefined using the partner language and the defaults
of the Customizing settings.
Changes made during the processing of the mail concerning the
description or the notification text will not be copied.

How to fix this error?

If you also want to use the texts entered by you for the final
messages, you have to specify a language in the condition record.

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 VN340 - Description and mail text are redefined during determination ?

  SAP Error Message:
  
  VN340 - Description and mail text are redefined during determination
  
  Cause:
  The error message VN340 occurs in SAP when the system detects that both the description and the mail text for a message determination procedure are being redefined simultaneously during the message determination process. This typically happens in the context of Vendor Master Data or Purchasing Document message determination, where the system tries to assign texts to messages (like email notifications) but finds conflicting or duplicate definitions.
  In other words, the system expects either the description or the mail text to be redefined, but not both at the same time during the message determination. This conflict leads to the error.
  
  When does it occur?
  
  During message determination in purchasing documents (e.g., Purchase Orders, RFQs).
  When customizing or enhancing message determination procedures.
  When user exits or BADIs are used to modify message texts.
  When there are conflicting entries in message control customizing (transaction NACE).
  
  
  Solution:
  
  
  Check Message Determination Configuration:
  
  Go to transaction NACE.
  Select the application (e.g., EF for Purchasing).
  Check the message types and their determination procedures.
  Verify that the description and mail text are not both redefined for the same message type or condition record.
  
  
  
  Review Custom Enhancements:
  
  If user exits or BADIs are implemented to modify message texts (e.g., EXIT_SAPMV13Z_001 or BADI ME_PROCESS_MSG), check the code to ensure that only one of the description or mail text is redefined.
  Avoid simultaneous redefinition of both fields in the same logic.
  
  
  
  Adjust Condition Records:
  
  In message determination condition records, ensure that the text assignments are consistent.
  Remove or correct any duplicate or conflicting entries.
  
  
  
  SAP Notes and Support:
  
  Check for relevant SAP Notes that might address this issue for your SAP version.
  Sometimes, patches or support packages fix inconsistencies in message determination.
  
  
  
  
  Related Information:
  
  Transaction NACE: Used for message control customizing.
  Message Determination: Process that decides which messages (print, email, fax) are triggered for business documents.
  User Exits / BADIs: Custom code can influence message texts.
  SAP Help Portal: Documentation on message control and determination.
  Common Messages: VN340 is specific to Vendor or Purchasing message control.
  
  
  Summary:
  
  Cause: Both description and mail text are being redefined simultaneously during message determination, causing a conflict.
  Solution: Ensure only one (either description or mail text) is redefined; check customizing in NACE and any custom code.
  Check: Message control customizing, user exits/BADIs, condition records.
  
  
  If you provide more context (e.g., which transaction or process triggers the error), I can help with more specific steps.