When you want both ERP Analytics and HCM Analytics in the same FDI instance, what action should you take during activation?

When you want both ERP Analytics and HCM Analytics in the same FDI instance, what action should you take during activation?

• A. Activate the new subscription and then link it to the required FDI instance during the activation process
• B. Activate and skip linking; link later
• C. Create a separate FDI instance for HCM
• D. Merge subscriptions manually after activation

Answer: (A)

When you want ERP Analytics and HCM Analytics to share one FDI instance, you should activate the new analytics subscription and link it to the existing FDI instance during the activation process. Linking at activation ties the analytics services to the same environment, giving you a unified setup where data connections, security, and user access are managed in one place. This avoids fragmentation and ensures both analytics offerings are immediately available under the same instance. If you activate but don’t link right away, the subscription will exist but won’t be connected to that FDI instance, which means extra steps later to attach it and potential configuration drift. Creating a separate FDI instance for HCM adds unnecessary complexity and maintenance, and attempting to merge subscriptions after activation isn’t the intended workflow. Linking during activation provides a clean, consolidated setup from the start.

When you want ERP Analytics and HCM Analytics to share one FDI instance, you should activate the new analytics subscription and link it to the existing FDI instance during the activation process. Linking at activation ties the analytics services to the same environment, giving you a unified setup where data connections, security, and user access are managed in one place. This avoids fragmentation and ensures both analytics offerings are immediately available under the same instance. If you activate but don’t link right away, the subscription will exist but won’t be connected to that FDI instance, which means extra steps later to attach it and potential configuration drift. Creating a separate FDI instance for HCM adds unnecessary complexity and maintenance, and attempting to merge subscriptions after activation isn’t the intended workflow. Linking during activation provides a clean, consolidated setup from the start.