How To Fix EB356 - A total of &1 print documents locked for CI transfer (integration cat.&2)

SAP Error Message - Details

• Message type: E = Error

• Message class: EB - IS-U invoicing

• Message number: 356

• Message text: A total of &1 print documents locked for CI transfer (integration cat.&2)

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 EB356 - A total of &1 print documents locked for CI transfer (integration cat.&2) ?

  The SAP error message EB356 indicates that there are print documents that are locked for CI (Consolidation Integration) transfer. This typically occurs in the context of document processing in SAP, particularly when dealing with print documents that are part of a consolidation process.
  Cause:
  
  Locked Documents: The error usually arises when there are print documents that are currently locked by another process or user. This can happen if a document is being processed or if there is a transaction that has not been completed.
  Integration Category Issues: The integration category mentioned in the error message (CI category &2) may also indicate that there are specific settings or configurations that are causing the documents to be locked.
  System Performance: High system load or performance issues can also lead to locking problems, as processes may take longer than expected to complete.
  
  Solution:
  
  Check Document Locks: Use transaction codes like SM12 to check for locked entries in the system. You can identify the user or process that is holding the lock and take appropriate action, such as waiting for the process to complete or contacting the user.
  Release Locks: If you find that a lock is no longer needed, you can manually release it using the same transaction (SM12), but be cautious as this can lead to data inconsistencies if the document is still being processed.
  Review Integration Settings: Check the configuration settings related to the integration category mentioned in the error message. Ensure that all necessary settings are correctly configured and that there are no discrepancies.
  System Performance Monitoring: Monitor system performance to ensure that there are no underlying issues causing delays in processing. This may involve checking system logs, performance metrics, and possibly optimizing database performance.
  Retry the Process: After addressing the locking issue, retry the process that triggered the error to see if it completes successfully.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (for checking locks), SM21 (for system logs), and ST22 (for dumps) to diagnose issues further.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  User Permissions: Ensure that users have the necessary permissions to access and process the documents in question, as permission issues can also lead to locking problems.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.