How To Fix B1067 - Number of IDocs: total &, dispatched &, still open (tRFC queue) &

SAP Error Message - Details

• Message type: E = Error

• Message class: B1 - ALE group messages

• Message number: 067

• Message text: Number of IDocs: total &, dispatched &, still open (tRFC queue) &

What causes this issue?

Status conversion for outbound IDocs.

System Response

IDocs have been selected and checked whether they have been sent
already. They are assigned the status 12. If the IDocs are still in the
tRFC queue, the status is not changed.

How to fix this error?

Send any IDocs not yet sent using the <DS:TRAN.SM58>tRFC Queue</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message B1067 - Number of IDocs: total &, dispatched &, still open (tRFC queue) & ?

  The SAP error message B1067 indicates an issue with the processing of IDocs (Intermediate Documents) in the system. This message provides information about the number of IDocs that are total, dispatched, and still open in the tRFC (Transactional Remote Function Call) queue. Here’s a breakdown of the cause, potential solutions, and related information for this error:
  Cause:
  
  
  IDoc Processing Issues: The error typically arises when there are IDocs that have not been processed successfully and are still open in the tRFC queue. This can happen due to various reasons, such as:
  
  Errors in the receiving system.
  Network issues preventing the IDocs from being sent.
  Configuration issues in the IDoc processing.
  Application errors that prevent the IDocs from being processed.
  
  
  
  tRFC Queue Overload: If the tRFC queue is overloaded with too many IDocs, it can lead to performance issues and delays in processing.
  
  
  System Configuration: Incorrect configuration of the IDoc processing or tRFC settings can also lead to this error.
  
  
  Solution:
  
  
  Monitor IDoc Status: Use transaction codes like WE02 or WE05 to monitor the status of IDocs. Check for any IDocs that are in error status and analyze the error messages associated with them.
  
  
  Reprocess IDocs: If you find IDocs that are in error status, you can attempt to reprocess them using transaction BD87 or WE19 (for testing purposes).
  
  
  Check tRFC Queue: Use transaction SM58 to check the tRFC queue for any entries that are stuck or have errors. You can manually delete or reprocess these entries if necessary.
  
  
  Review Application Logs: Check the application logs for any specific errors that might indicate why the IDocs are not being processed. Use transaction SLG1 to view application logs.
  
  
  System Configuration: Review the configuration settings for IDoc processing and tRFC. Ensure that the settings are correct and that the receiving system is properly configured to accept IDocs.
  
  
  Performance Tuning: If the tRFC queue is overloaded, consider tuning the performance of the system or increasing the resources allocated to the IDoc processing.
  
  
  Consult Documentation: Refer to SAP documentation or support notes related to IDoc processing and tRFC for additional troubleshooting steps and best practices.
  
  
  Related Information:
  
  IDoc Types: Understand the specific IDoc types being processed and their configurations.
  Error Handling: Familiarize yourself with error handling mechanisms in SAP for IDocs.
  SAP Notes: Check for any relevant SAP Notes that might address known issues related to IDoc processing and tRFC.
  
  By following these steps, you should be able to identify the root cause of the B1067 error and implement a solution to resolve the issue.