Clear External Mappings
- Your implementation tenant successfully activated either:
- A financial planning configuration manager.
- A workforce planning configuration manager.
- Your implementation tenant successfully migrated to Production or Sandbox.
- Security:Model Managementpermissions in Adaptive Planning.
When a tenant migrates from Implementation to Production or Sandbox, the Workday ID (WID) values can change. Changed WIDs may cause mapping conflicts for the data and metadata loaders in Adaptive Planning created by a planning configuration manager. To resolve mapping conflicts from changed WIDs, you can clear external mappings in Adaptive Planning.
Clearing external mappings can also help following a:
- Swap from a planning configuration manager after initial testing to traditional Workday Data Management, leaving behind locks on the Adaptive Planning user interface
- Parallel deployment of Workday Core and Adaptive Planning that included metadata changes or repurposed dimension values that cause external ID conflicts
- In Adaptive Planning, navigate to .
- In theOtherssection, selectClear External Mappings.This link is only available when a planning configuration manager successfully activates.
After a few moments, the external mappings clear.
A user with Integration Operator permissions must navigate to Design Integrations in Adaptive Planning and run the Orchestration task. Then run either:
- The Unified FPA task followed by the United FPI task for the financial planning configuration manager.
- The SYS-HPA metadata loader task followed by the SYS-HPA data loader task for the workforce planning configuration manager.