How To Fix RSMIGRATE063 - No automatic migration of exits with InfoPackage &1

RSMIGRATE063 - Overview

• Message type: E = Error

• Message class: RSMIGRATE - Migration

• Message number: 063

• Message text: No automatic migration of exits with InfoPackage &1

What causes this issue?

The InfoPackage &V1& uses either a function module exit or a BAdl to
postprocess the request. This function from SAP BW Release 2.x cannot be
automatically migrated. The exits are retained but they lead to
unexpected processes when loading.

System Response

The function continues.

How to fix this error?

Stop the migration and transfer your process model to a process chain.
Depending on the complexity, you can create either a process of type
ABAP or a user-defined process type (in which you can call your current
coding) for the activities that are executed in the exit/BAdl.
As soon as the InfoPackage &V1& is part of an active process chain, the
systems stops executing the exits. You can then continue with the
migration of the data flow.

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 RSMIGRATE063 - No automatic migration of exits with InfoPackage &1 ?

  The SAP error message RSMIGRATE063 indicates that there is no automatic migration of exits for a specific InfoPackage. This typically occurs during the migration process from an older version of SAP BW (Business Warehouse) to a newer version, particularly when transitioning from BW 3.x to BW 7.x.
  
  Cause:
  The error arises because the system has detected that there are custom exits (user-defined enhancements) associated with the specified InfoPackage that cannot be automatically migrated. This can happen for several reasons:
  
  The custom exit is not compatible with the new version of BW.
  The exit is not defined in a way that the migration tool can recognize or handle.
  The InfoPackage may have been customized in a way that does not align with the new migration standards.
  
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Identify the Custom Exits: 
  
  Check the InfoPackage in question to identify any custom exits that have been implemented. You can do this by