How To Fix SOI1123 - Start: Saving objects of container &1 (phys. name &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI1 - Safe Online Import/Upgrade Messages continued

• Message number: 123

• Message text: Start: Saving objects of container &1 (phys. name &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 SOI1123 - Start: Saving objects of container &1 (phys. name &2) ?

  The SAP error message SOI1123 typically indicates an issue related to the saving of objects in a container, where the system is unable to save the specified objects due to various reasons. Here’s a breakdown of the potential causes, solutions, and related information for this error message:
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to save objects in the specified container.
  Container Lock: The container might be locked by another user or process, preventing the current user from saving changes.
  Technical Issues: There could be underlying technical issues, such as database connectivity problems or issues with the SAP system itself.
  Object Status: The objects being saved may be in a status that does not allow them to be saved (e.g., they may be in a "locked" or "incomplete" state).
  Transport Issues: If the objects are part of a transport request, there may be issues with the transport configuration or the request itself.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to save objects in the specified container. This can be done by reviewing the user's roles and authorizations in the SAP system.
  Release Locks: If the container is locked, identify the user or process that has locked it and request them to release the lock. You can use transaction codes like SM12 to check for locks.
  Technical Troubleshooting: Investigate any technical issues that may be affecting the SAP system. This may involve checking system logs, database connections, and other technical parameters.
  Review Object Status: Check the status of the objects being saved. If they are in a locked or incomplete state, take the necessary steps to unlock or complete them before attempting to save again.
  Transport Request: If the objects are part of a transport request, ensure that the transport request is correctly configured and that there are no issues with the transport system.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE11 (Data Dictionary), and SE09/SE10 (Transport Organizer) for managing objects and transport requests.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to the SOI1123 error message. SAP Notes can provide patches or workarounds for known issues.
  System Logs: Review system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  SAP Community: Engage with the SAP Community or forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.