1. Administer and Secure Your Service
  2. Object Migration
  3. Troubleshooting Object Migration - AFCS

5.7 Troubleshooting Object Migration - AFCS

Refer to the following troubleshooting.

SLA Import Failed

Connector Import Failed

In case, the migration of SLA object definitions doesn't complete, verify the following points. Ensure to complete these requirements before proceeding with the SLA migration.

  • DM models in sync in terms of extensions.
  • The SLA Code and SLA Name should be the same for a specific definition, in both source and target environments.
  • Event type or attributes for a specific definition should be the same in both source and target environemnts.

    Note:

    When the Event Type is Both' in source environment and Passthru or Transaction in Target environment, the import will fail.
  • If the same SLA definition is available in both source and target environment, then unpublish the SLA definition in the target environment, for sucessful import.
  • Event Name and Event code details should be the same in both source and target environments.
  • When a SLA definition is in Configured or Available state, in both source and target environment, then it will Configured state, after import.
  • If Exported SLA is in Draft/Ready for Registration state and SLA is not present in target system, after importing the SLA status is maintained.
  • If Exported SLA is in Registered/Configured/Available state and is not present in target system, it is set to Ready for Registration, after import. After registration, the header, line mapping and ledger assignment details from the source are also available for the target environment.
  • If Exported SLA is in Configured/Available state and if the same SLA definition is available in the target system, then
    • Ledger Information is also updated
    • Create or update the Edds and import the Header and Line Mappings, so that when a SLA is registered respective mappings are used.

      If a SLA is present on the importing system and is set to Registered/Configured status and the attributes are also matching, then update Ledger/Product/Mapping Information and retain status. If the attributes are not matching then Import will fail.

    • When an exported SLA is in Configured/Available state, and any extended column is mapped in Header/Line mapping, and if this extended column is not available in the importing system then SLA is imported but the status is set to failed as the dependent mappings are not imported.

When the connector import is not successful, ensure to verify the following details and complete the prerequsites.

  • The attributes in the entity used in the migrated connector (for both Extract and Insert connector), must be the same in source and target environments.
  • When a connector with the same name is already available in the target environment, the imported connector will overwrite based on the set overwrite option.
  • OOTB Extract connector is the only valid OOTB metadata during the import.
  • When a connector is migrated, all the underlying metadata of EDD and Parameters are also migrated.