How To Fix J2071 - &4 Costing not possible; transaction & deleted or canceled

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 071

• Message text: &4 Costing not possible; transaction & deleted or canceled

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 J2071 - &4 Costing not possible; transaction & deleted or canceled ?

  The SAP error message J2071, which states "Costing not possible; transaction & deleted or canceled," typically occurs in the context of cost accounting and product costing within SAP. This error indicates that the system is unable to perform costing calculations for a specific transaction because that transaction has been deleted or canceled.
  Causes:
  
  Deleted or Canceled Transactions: The most direct cause of this error is that the transaction you are trying to cost has been deleted or marked as canceled in the system.
  Data Integrity Issues: There may be issues with data integrity, where the transaction data is not consistent or has been altered in a way that makes it invalid for costing.
  Configuration Issues: Incorrect configuration in the costing settings or master data may lead to this error.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the transaction data, leading to this error.
  
  Solutions:
  
  Check Transaction Status: Verify the status of the transaction in question. If it has been deleted or canceled, you will need to either restore it (if possible) or create a new transaction.
  Review Change Logs: Look at the change logs to understand when and why the transaction was deleted or canceled. This can provide insights into whether it was an intentional action or an error.
  Data Consistency Check: Run data consistency checks in the relevant modules (like CO, MM, etc.) to ensure that all related data is intact and valid.
  Recreate the Transaction: If the transaction is essential for costing, you may need to recreate it. Ensure that all necessary details are correctly entered.
  Consult Configuration Settings: Review the configuration settings related to costing and ensure they are set up correctly. This may involve checking the costing variant, valuation classes, and other related settings.
  User Authorizations: Ensure that the user attempting to perform the costing has the necessary authorizations to access the transaction data.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CK11N (Create Cost Estimate), CK40N (Change Cost Estimate), and CK24 (Display Cost Estimate) to navigate costing processes.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review SAP documentation related to product costing and transaction management for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a technical consultant who can provide more in-depth analysis and assistance.