How To Fix J3058 - Costing date and posting date are inconsistent

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 058

• Message text: Costing date and posting date are inconsistent

What causes this issue?

For current transfers of period values, costing should be run with the
transfer. If this is the case, period values can be transferred with
record type 'E' only for the periods to be costed.
The costing date '&V1&' falls within period '&V2&'. At least one period
value with record type 'E' was transferred with company code '&V3&',
which is in period '&V4&'.

System Response

The external data transfer was canceled because the costing run cannot
be carried out.

How to fix this error?

Change all of the transferred period values so that all the ones with
record type 'E' belong to the same period. It is possible that several
files will have to be generated, one for each period.
Choose a costing date which falls within the same period as the
transfer period values with record type 'E'.
If the period values cannot be changed, or if it is not possible to
generate more than one file, the external data transfer can be carried
out without triggering the costing run. The costing run will then have
to be done later for the financial objects in questions.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message J3058 - Costing date and posting date are inconsistent ?

  The SAP error message J3058, which states "Costing date and posting date are inconsistent," typically occurs during the posting of a financial document or during the execution of a transaction that involves cost accounting. This error indicates that there is a mismatch between the costing date and the posting date, which can lead to inconsistencies in financial reporting and cost calculations.
  Cause:
  
  
  Date Mismatch: The costing date (the date used for determining the cost of goods sold or inventory valuation) and the posting date (the date the transaction is recorded in the financial system) are not aligned. This can happen if:
  
  The costing date is set to a period that is closed or not open for posting.
  The posting date is in a different fiscal period than the costing date.
  
  
  
  Configuration Issues: There may be configuration settings in the system that enforce strict rules regarding the relationship between costing and posting dates.
  
  
  Transaction Type: Certain transaction types may have specific requirements regarding the dates used.
  
  
  Solution:
  
  
  Check Dates: Verify the costing date and posting date in the transaction. Ensure that both dates are within the same fiscal period and that the period is open for posting.
  
  
  Adjust Dates: If the dates are inconsistent, adjust either the costing date or the posting date to ensure they match or are within the same open period.
  
  
  Review Configuration: If the issue persists, review the configuration settings in the SAP system related to costing and posting. This may involve checking:
  
  The fiscal year variant settings.
  The period control settings in the controlling (CO) module.
  
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on handling costing and posting dates.
  
  
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  CK11N: Create Cost Estimate with Quantity Structure
  CK40N: Change Cost Estimate
  FB50: General Ledger Account Document Entry
  
  
  
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  
  
  Training and Documentation: Ensure that users involved in financial postings are trained on the importance of date consistency and the implications of posting in closed periods.
  
  
  By addressing the date inconsistency and ensuring proper configuration, you should be able to resolve the J3058 error in SAP.