How To Fix 0D628 - Posting run cannot be started: posting data transfer running

SAP Error Message - Details

• Message type: E = Error

• Message class: 0D - FS-CD General Messages

• Message number: 628

• Message text: Posting run cannot be started: posting data transfer running

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 0D628 - Posting run cannot be started: posting data transfer running ?

  The SAP error message 0D628 indicates that a posting run cannot be started because a posting data transfer is currently in progress. This typically occurs in the context of financial postings or data transfers where the system is processing a batch of transactions, and another attempt to initiate a posting run is made before the current one has completed.
  Cause:
  
  Concurrent Posting Runs: Another posting run is already in progress, which prevents the initiation of a new one.
  System Lock: The system may have a lock on the posting data transfer process, which can happen due to various reasons, such as a long-running transaction or a system error.
  Background Job: A background job related to posting might be running, causing the system to block new posting requests.
  
  Solution:
  
  
  Check Running Processes: 
  
  Use transaction code SM37 to check for any background jobs that are currently running. Look for jobs related to posting or data transfer.
  If you find a job that is stuck or taking too long, you may need to analyze it further or terminate it if appropriate.
  
  
  
  Wait for Completion: 
  
  If you identify that a posting run is in progress, the simplest solution is to wait until it completes. Once the current process finishes, you should be able to start a new posting run.
  
  
  
  System Lock Release: 
  
  If you suspect that a lock is causing the issue, you can check for locks using transaction code SM12. Look for locks related to the posting process and release them if they are no longer needed.
  
  
  
  Review Logs: 
  
  Check the application logs (transaction code SLG1) for any errors or warnings that might provide more context about why the posting run is blocked.
  
  
  
  Consult Basis Team: 
  
  If the issue persists and you cannot identify the cause, it may be necessary to involve your SAP Basis team. They can help investigate system performance issues or locks that may not be visible to end-users.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM37: Monitor background jobs.
  SM12: Display and manage locks.
  SLG1: Application log display.
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for relevant notes.
  
  
  Documentation: Review SAP documentation related to the specific module you are working with (e.g., FI, CO) for more details on posting runs and data transfers.
  
  
  By following these steps, you should be able to resolve the error and successfully initiate your posting run.