How To Fix J3474 - Acct.&2, co.code &3: No condition header w. validity date &1 was created

J3474 - Overview

• Message type: E = Error

• Message class: J3 - Dialog Messages for Data Pool Entry Transactions

• Message number: 474

• Message text: Acct.&2, co.code &3: No condition header w. validity date &1 was created

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message J3474 - Acct.&2, co.code &3: No condition header w. validity date &1 was created ?

  The SAP error message J3474 typically indicates that there is an issue with the condition records in the pricing procedure for a specific account and company code. The message states that no condition header with the specified validity date was created, which means that the system cannot find the necessary pricing conditions for the transaction being processed.
  
  Cause:
  
  Missing Condition Records: The most common cause is that the required condition records for the specified validity date do not exist in the system.
  Incorrect Validity Date: The validity date provided in the transaction may not match any existing condition records.
  
  Configuration Issues: There may be issues with the configuration of the pricing procedure or condition types.
  Data Inconsistencies: There could be inconsistencies in the master data or transaction data that prevent the system from finding the correct condition records.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the