How To Fix DD_MT_SHARING_CHK021 - &1 direct usage(s) in HANA native objects found (probably uncritical)

SAP Error Message - Details

• Message type: E = Error

• Message class: DD_MT_SHARING_CHK - DDIC Multi Tenancy Sharing: Messages

• Message number: 021

• Message text: &1 direct usage(s) in HANA native objects found (probably uncritical)

What causes this issue?

Write access from HANA native objects (for example<(>,<)> function or
trigger) to shared tables is forbidden. HANA calculation views do not
work with shared tables.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DD_MT_SHARING_CHK021 - &1 direct usage(s) in HANA native objects found (probably uncritical) ?

  The SAP error message DD_MT_SHARING_CHK021 indicates that there are direct usages of certain objects in HANA native objects, which may not be critical but still require attention. This message typically arises during the transport or activation of objects in the SAP HANA environment, particularly when dealing with database views, tables, or other database objects.
  Cause:
  The error is triggered when the system detects that there are direct references to certain database objects (like tables or views) in HANA native objects (like calculation views or other database artifacts). This can happen due to:
  
  Direct Usage: The object is being directly referenced in a HANA native object, which may not be the best practice as it can lead to dependencies that complicate future changes or transports.
  Object Changes: If the underlying object has been modified or is being transported, it may lead to inconsistencies or issues in the dependent objects.
  Transport Issues: When transporting objects between different systems (e.g., from development to production), direct references can lead to problems if the referenced objects are not present or are different in the target system.
  
  Solution:
  To resolve this issue, consider the following steps:
  
  
  Review Direct Usages: Identify the objects that are being directly referenced. You can use tools like the HANA Studio or SAP HANA Database Explorer to analyze the dependencies.
  
  
  Refactor Code: If possible, refactor the HANA native objects to avoid direct references. Instead, consider using views or other abstraction layers to minimize direct dependencies.
  
  
  Check Object Availability: Ensure that all referenced objects are available and consistent in the target system where the transport is being applied.
  
  
  Documentation: Document the direct usages and their implications for future reference. This can help in understanding the impact of changes in the future.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes or documentation that may provide additional context or solutions specific to your version of SAP HANA.
  
  
  Testing: After making changes, thoroughly test the affected objects to ensure that they function correctly without the direct references.
  
  
  Related Information:
  
  SAP HANA Documentation: Review the official SAP HANA documentation for best practices regarding object usage and dependencies.
  SAP Community: Engage with the SAP Community forums to see if others have encountered similar issues and what solutions they have implemented.
  Performance Considerations: Be aware that direct references can impact performance, so consider optimizing your database design to improve efficiency.
  
  By addressing the direct usages and ensuring that your database design follows best practices, you can mitigate the risks associated with this error message and improve the maintainability of your SAP HANA environment.