How To Fix J2739 - &4 Costing for transaction &1 &2 contains errors

SAP Error Message - Details

• Message type: E = Error

• Message class: J2 - Message Class for Development Class JBT

• Message number: 739

• Message text: &4 Costing for transaction &1 &2 contains errors

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 J2739 - &4 Costing for transaction &1 &2 contains errors ?

  The SAP error message J2739 typically indicates that there are issues with the costing data for a specific transaction. This error can occur in various contexts, such as during the execution of a transaction related to material management, production, or financial accounting. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  
  Missing or Incorrect Costing Data: The costing data for the transaction may be incomplete or incorrect. This can include missing cost estimates, incorrect valuation classes, or missing master data.
  
  
  Configuration Issues: There may be configuration issues in the costing settings, such as incorrect settings in the controlling area or cost center.
  
  
  Master Data Issues: Problems with master data, such as material master records, cost center master records, or internal order master records, can lead to costing errors.
  
  
  Currency Issues: If there are discrepancies in currency settings or if the transaction involves multiple currencies, this can lead to costing errors.
  
  
  Authorization Issues: Lack of proper authorizations for accessing certain data or executing specific transactions can also trigger this error.
  
  
  Solutions:
  
  
  Check Costing Data: Review the costing data for the transaction in question. Ensure that all necessary fields are filled out correctly and that the data is complete.
  
  
  Review Configuration Settings: Check the configuration settings in the controlling area, cost center, and other relevant areas to ensure they are set up correctly.
  
  
  Validate Master Data: Ensure that all relevant master data (material, cost center, internal orders) is correctly maintained and up to date.
  
  
  Currency Settings: Verify that the currency settings are correct and consistent across the relevant transactions and master data.
  
  
  Authorization Check: Ensure that the user executing the transaction has the necessary authorizations to access the required data.
  
  
  Use Transaction Codes: Utilize transaction codes like CK11N (Create Cost Estimate) or CK40N (Change Cost Estimate) to analyze and correct costing issues.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to costing, such as CK11N, CK40N, and CK24 (Display Cost Estimate).
  SAP Documentation: Refer to SAP Help documentation for detailed information on costing and configuration settings.
  Support Forums: Engage with SAP community forums or support channels for additional insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who can provide more in-depth analysis and assistance.