How To Fix SOI_UPG073 - SSOI_TBCLDY should only written in system BSK by User DDIC

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI_UPG - Message for SOI upgrade

• Message number: 073

• Message text: SSOI_TBCLDY should only written in system BSK by User DDIC

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 SOI_UPG073 - SSOI_TBCLDY should only written in system BSK by User DDIC ?

  The SAP error message SOI_UPG073 indicates that the system is enforcing a restriction on the table SSOI_TBCLDY. Specifically, it states that this table should only be written to in the system identified as BSK by the user DDIC. This error typically arises during system upgrades or migrations, particularly when dealing with Single Sign-On (SSO) configurations or related system settings.
  Cause:
  
  User Permissions: The user attempting to write to the table SSOI_TBCLDY does not have the necessary permissions, or the operation is being attempted in a system other than BSK.
  System Configuration: The system may be misconfigured, leading to attempts to write to the table in an unauthorized environment.
  Upgrade/Migration Issues: The error may occur during an upgrade or migration process where certain tables are locked down to prevent unauthorized changes.
  
  Solution:
  
  
  Check User Permissions: Ensure that the user attempting to perform the operation has the necessary permissions. The user DDIC typically has the highest level of access, so if you are not using this user, you may need to switch to it or grant the necessary permissions to the current user.
  
  
  Verify System Context: Confirm that you are operating in the correct system (BSK). If you are in a different system, you will need to switch to the BSK system to perform the required operation.
  
  
  Review Upgrade/Migration Steps: If this error occurs during an upgrade or migration, review the upgrade documentation to ensure that all steps have been followed correctly. There may be specific instructions regarding the handling of the SSOI_TBCLDY table.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that can resolve the issue.
  
  
  Contact SAP Support: If the issue persists after checking permissions and system context, consider reaching out to SAP Support for further assistance. They can provide guidance based on the specific version and configuration of your SAP system.
  
  
  Related Information:
  
  SSO Configuration: Understanding how Single Sign-On is configured in your SAP landscape can help in troubleshooting related issues.
  User Roles and Authorizations: Familiarize yourself with the roles and authorizations in your SAP system, especially those related to system administration and table access.
  System Logs: Check system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.