How To Fix BSANLY_CONT_ACT_MSG033 - Data saved only locally

SAP Error Message - Details

• Message type: E = Error

• Message class: BSANLY_CONT_ACT_MSG - Messages for BI Content Activation Workbench

• Message number: 033

• Message text: Data saved only locally

What causes this issue?

One or more BI Content bundles have been saved to the database, but no
transport request has been created.

System Response

You do not have transport authorization, or you have chosen to assign a
local package to one of your BI Content bundles. To prevent data loss,
the system enables to save the data locally.

How to fix this error?

The BI Content bundle is only available in the current system. If you
want to transport the data to other systems, you have to assign a
transportable package to the content bundle, and assign it to a
transport request. This can be done choosing <LS>Content Bundles</> ->
<LS>Transport Content Bundle</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BSANLY_CONT_ACT_MSG033 - Data saved only locally ?

  The SAP error message BSANLY_CONT_ACT_MSG033 indicates that data has been saved only locally and not in the central database. This typically occurs in scenarios where the system is unable to synchronize or save the data to the central database due to various reasons.
  Causes:
  
  Network Issues: There may be connectivity problems between the local system and the central database.
  Authorization Issues: The user may not have the necessary permissions to save data in the central database.
  Database Locking: The database might be locked due to ongoing transactions or maintenance activities.
  Configuration Issues: There may be misconfigurations in the system settings that prevent data from being saved centrally.
  System Errors: There could be bugs or errors in the SAP system that are causing the data not to be saved properly.
  
  Solutions:
  
  Check Network Connectivity: Ensure that there are no network issues preventing communication with the central database.
  Review User Authorizations: Verify that the user has the necessary permissions to perform the action that is generating the error.
  Check Database Locks: Investigate if there are any locks on the database that might be preventing data from being saved. You can use transaction codes like SM12 to check for locks.
  Review Configuration Settings: Ensure that the system is properly configured for data synchronization. This may involve checking settings in transaction codes like SPRO or other relevant configuration areas.
  Consult SAP Notes: Look for any relevant SAP Notes that might address this specific error message. SAP frequently releases updates and patches that can resolve known issues.
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM21 (System Log), SLG1 (Application Log), and SM12 (Lock Entries) to diagnose the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Review SAP documentation related to the specific module or functionality you are working with, as it may provide insights into common issues and their resolutions.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to ensure that data is saved correctly in the central database.