How To Fix BSANLY_CONT_ACT_MSG065 - Bundle &1 belongs to a different package than surrounding bundle &3

BSANLY_CONT_ACT_MSG065 - Overview

• Message type: E = Error

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

• Message number: 065

• Message text: Bundle &1 belongs to a different package than surrounding bundle &3

What causes this issue?

Bundle &V1& is assigned to package &V2& and contained in bundle &V3&.
However, this bundle is assigned to a different package &V4&.

System Response

If the bundles are transported into different target systems, it may not
be possible to activate the BI content consistently.

How to fix this error?

You should assure that both packages &V2& and &V4& belog to the same
transport layer in order to avoid incosistencies in the target systems.

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_MSG065 - Bundle &1 belongs to a different package than surrounding bundle &3 ?

  The SAP error message BSANLY_CONT_ACT_MSG065 indicates that there is a mismatch in the package assignments of bundles in the SAP system. Specifically, it means that the bundle you are trying to work with (Bundle &1) belongs to a different package than the surrounding bundle (Bundle &3). This can occur during activities such as transport requests, bundle management, or when trying to activate or deploy bundles.
  
  Cause:
  
  Package Mismatch: The primary cause of this error is that the bundles involved are assigned to different packages. In SAP, bundles are often grouped by packages, and having them in different packages can lead to inconsistencies.
  Transport Issues: If bundles were transported from one system to another (e.g., from development to production), and the packages were not aligned, this error can occur.
  Configuration Errors: Incorrect configuration or manual changes in the package assignments of bundles can also lead to this error.
  
  
  Solution:
  
  
  Check Package Assignments:
  
  Verify the package assignments of both