How To Fix /PM0/ABJ_MSG229 - &1/&2: No journal entry for start date shift exists

SAP Error Message - Details

• Message type: E = Error

• Message class: /PM0/ABJ_MSG -

• Message number: 229

• Message text: &1/&2: No journal entry for start date shift exists

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 /PM0/ABJ_MSG229 - &1/&2: No journal entry for start date shift exists ?

  The SAP error message /PM0/ABJ_MSG229 &1/&2: No journal entry for start date shift exists typically occurs in the context of Asset Accounting (FI-AA) when there is an attempt to post or process transactions related to asset management, but the system cannot find the necessary journal entries for the specified date range.
  Cause:
  
  
  Missing Journal Entries: The error indicates that there are no journal entries available for the specified start date. This could happen if:
  
  The journal entries have not been created for the asset transactions.
  The posting period is closed, and no entries can be made for that period.
  The asset was not properly initialized or has not been assigned to a valid fiscal year.
  
  
  
  Incorrect Date Range: The date range specified in the transaction may not correspond to any existing journal entries.
  
  
  Configuration Issues: There may be configuration issues in the Asset Accounting settings that prevent the creation of journal entries.
  
  
  Solution:
  
  
  Check Journal Entries: Verify if the journal entries for the specified date exist. You can do this by:
  
  Navigating to the relevant transaction (e.g., transaction code FB03 for displaying documents) and checking for entries around the specified date.
  Ensuring that the asset has been properly posted in the system.
  
  
  
  Open Posting Periods: Ensure that the posting period for the date in question is open. You can check this in the transaction code OB52 (Maintain Posting Periods) to see if the period is open for posting.
  
  
  Asset Initialization: If the asset has not been initialized correctly, you may need to perform the necessary steps to initialize the asset. This can include creating the asset master record and ensuring that it is assigned to the correct company code and fiscal year.
  
  
  Review Configuration: Check the configuration settings in Asset Accounting to ensure that everything is set up correctly. This includes checking the settings for asset classes, depreciation areas, and posting rules.
  
  
  Consult Documentation: If the issue persists, refer to SAP documentation or consult with your SAP support team for further assistance. They may provide insights specific to your system configuration.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  AS01 (Create Asset)
  AS02 (Change Asset)
  AS03 (Display Asset)
  FB03 (Display Document)
  OB52 (Maintain Posting Periods)
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message number in the SAP Support Portal.
  
  
  User Authorization: Ensure that you have the necessary authorizations to view and post asset transactions.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.