How To Fix J2057 - &4: Transaction not yet costed for current period

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 057

• Message text: &4: Transaction not yet costed for current period

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 J2057 - &4: Transaction not yet costed for current period ?

  The SAP error message J2057 &4: "Transaction not yet costed for current period" typically occurs in the context of controlling (CO) and financial accounting (FI) when you attempt to perform an action on a transaction that has not yet been costed for the current period. This can happen in various scenarios, such as when trying to post a journal entry, run a report, or execute a transaction that relies on cost data.
  Cause:
  
  Costing Period Not Open: The most common cause is that the costing period for the relevant transaction has not been opened in the system. If the period is closed, the system will not allow any cost postings or adjustments.
  Transaction Not Processed: The transaction may not have been processed or costed yet, meaning that the necessary calculations or postings have not been completed.
  Configuration Issues: There may be configuration settings in the controlling module that prevent the transaction from being costed.
  Data Entry Errors: Incorrect data entry or missing information in the transaction can also lead to this error.
  
  Solution:
  
  
  Open the Costing Period: Check if the costing period is open. You can do this by navigating to the controlling area settings and ensuring that the period is open for posting. If it is closed, you may need to open it or wait until it is opened by the responsible personnel.
  
  
  Costing Run: If the transaction has not been costed, you may need to run the costing run for the relevant period. This can usually be done through transaction codes like CK40N (for product costing) or similar, depending on your specific scenario.
  
  
  Check Transaction Status: Verify the status of the transaction in question. Ensure that all necessary steps have been completed and that there are no outstanding issues preventing it from being costed.
  
  
  Review Configuration: If the issue persists, review the configuration settings in the controlling module to ensure that everything is set up correctly for costing.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance related to your version of SAP and the particular transaction you are working with.
  
  
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CK11N (Create Cost Estimate), CK40N (Costing Run), and others that may be relevant to your specific situation.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles and Authorizations: Ensure that you have the necessary authorizations to perform the actions you are attempting, as lack of permissions can also lead to errors.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.