How To Fix RSMIGRATE013 - DTP can load without PSA after DS migration; Adjust DTP and chain

RSMIGRATE013 - Overview

• Message type: E = Error

• Message class: RSMIGRATE - Migration

• Message number: 013

• Message text: DTP can load without PSA after DS migration; Adjust DTP and chain

What causes this issue?

InfoPackage &V1& is configured to load without PSA. In data transfer
process (DTP) &V2& it is also possible to make this setting. However
this DTP option is only available if the DataSource has been migrated.
The usual settings from the InfoPackage have already been applied to the
DTP.

System Response

In process chains to be migrated, the DTP&V2& <ZH>is also</> inserted
behind the InfoPackage&V1& as required when loading with PSA. This
ensures that the migrated process chain works, even if the DataSource
has not been migrated.

How to fix this error?

As soon as the DataSource is migrated, you can set the relevant flag for
<LS>Loading without PSA </> in the DTP &V2& and remove the InfoPackage
&V1& from the process chain.

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.

RSMIGRATE013 - Details

• The SAP error message RSMIGRATE013 indicates that a Data Transfer Process (DTP) can load data without a Persistent Staging Area (PSA) after a DataSource (DS) migration. This typically occurs when you have migrated a DataSource from an older version to a newer version, and the DTP settings need to be adjusted accordingly.
  
  Cause:
  
  DataSource Migration: The error arises after migrating a DataSource, which may have changed the way data is handled. In newer versions, the DTP may be configured to load data directly without using the PSA.
  DTP Configuration: The DTP may still be configured to expect a PSA, but the new DataSource does not require it, leading to a mismatch.
  Process Chain Dependencies: If the DTP is part of a process chain, the chain may still reference the old configuration, causing the error.
  
  
  Solution:
  To resolve the error, you need to adjust the DTP and possibly the process chain. Here are the steps to follow:
  
  
  Check