How To Fix ARC_DAS_CON127 - No migration possible from &1 to &1 for BOR type &3 and doc. type &4

ARC_DAS_CON127 - Overview

• Message type: E = Error

• Message class: ARC_DAS_CON - XML DAS Connector: Messages

• Message number: 127

• Message text: No migration possible from &1 to &1 for BOR type &3 and doc. type &4

What causes this issue?

An existing resource on a WebDAV archive store is to be assigned to
another WebDAV archive store. Presumably you have changed an existing
rule, so that the WebDAV archive store is now changed. A migration of
existing references is not possible.

System Response

The WebDAV archive store was not changed on the existing resource of the
processing BOR type and the document type. Thus the original storage
location is kept.

How to fix this error?

Check the storage rule for the BOR type and the document type.
If you want to store new resources not yet stored which belong to the
BOR type and the document type on another WebDAV archive store, you
should use a suitable selection to ensure that resources already entered
are not selected again. Otherwise, this will only have a negative effect
on the running times.

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 ARC_DAS_CON127 - No migration possible from &1 to &1 for BOR type &3 and doc. type &4 ?

  The SAP error message ARC_DAS_CON127 indicates that there is an issue with the migration of documents in the Archive Development Kit (ADK) related to Business Object Repository (BOR) types. This error typically arises when there is an attempt to migrate documents from one type to another, but the system determines that the migration is not possible due to certain constraints.
  
  Cause:
  
  Incompatible Document Types: The error suggests that the source and target document types are not compatible for migration. This could be due to differences in the structure or attributes of the document types.
  Missing Configuration: There may be missing or incorrect configuration settings in the Archive Management or the Business Object Repository that prevent the migration.
  Data Integrity Issues: There could be data integrity issues with the documents being migrated, such as missing references or invalid data.
  Authorization Issues: The user may not have the necessary authorizations to perform the migration between the specified