Monitoring Cost Advisor Work Requests
Review the progress and errors of background operations for a Cost Advisor workspace.
Pre-General Availability: 2026-10-27
The following legal notice applies to Oracle pre-GA releases. For copyright and other applicable notices, see Oracle Legal Notices.
Pre-General Availability Draft Documentation Notice
This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
This documentation is not a commitment by Oracle to deliver any material, code, functionality or services. This documentation, and Oracle Pre-GA programs and services are subject to change at any time without notice and, accordingly, should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality for Oracle’s Pre-GA programs and services remains at the sole discretion of Oracle. All release dates or other predictions of future events are subject to change. The future availability of any future Oracle program or service should not be relied on in entering into any license or service agreement with Oracle.
For a Fusion HCM person mapping or Fusion EPM destination, connection checks start after you select Add mapping or Add destination. There is no separate connection-validation action. You can continue working while the checks run.
Updating an EPM destination's connection details also starts a new validation work request for that connection.
Person and project ID mapping CSV files are validated separately from upload. Validation takes about 5 minutes, depending on file size. Review the validation result and error log as well as the mapping state on the Integrations tab. A successful upload alone doesn't confirm that validation succeeded.
The completion checkboxes in the preparation steps acknowledge that you've completed the external setup. They don't test the connection.
For issues preparing the EPM environment or integration account, work with your EPM and identity domain administrators. See Resolving EPM Preparation Issues.
Resolving Connection Setup Issues
Use the work request's error details to identify the failed operation. Check the following with the administrator responsible for that system:
- Environment URL: Use the HTTPS base URL of the intended environment, without an application or REST path, query string, or fragment.
- Identity domain: Confirm that the URL identifies the domain associated with the intended HCM or EPM environment.
- Confidential application: Confirm that the application is active, the OAuth client ID is correct, and the public signing certificate and alias required for that connection are set up. See Setting Up Identity Access for Fusion Connections.
- Scope and user access: Copy the scope for the correct target service. Confirm that the dedicated integration account is active and has the required access. For EPM, also verify the target service's secondary audience.
- Fusion HCM extract: Confirm that Oracle Cost Advisor for AI is imported, compiled, and validated, and that the dedicated account can run it and access its results. Check that the account's payroll flow security profile includes the exact imported flow, especially after replacing an earlier definition. See Preparing Fusion HCM for Person Mapping.
- EPM data availability: If the connection succeeds but expected data or insights aren't available, review the processing schedule and have the EPM administrator check file delivery and import and load results. For environment preparation issues, see Resolving EPM Preparation Issues.
For an EPM destination, follow Resolving EPM Connection Validation Issues to correct the configuration and validate the same connection again. For a person mapping, check whether the mapping was created before attempting to add it again. Don't share passwords, API keys, private keys, tokens, or encrypted credential files when reporting an error.
Resolving EPM Connection Validation Issues
Use the EPM validation work request's error details to identify the failure category. The following table explains what the categories mean and which configuration details to review.
| Failure category | Meaning and what to check |
|---|---|
| Signing credential error | The service couldn't read or use its signing credential. Cost Advisor for AI manages this credential. Include the work request details when contacting support about this error. |
| IDCS authentication failure | Check the identity domain URL, OAuth client ID, confidential application's activation, public certificate registration and validity, exact integration username, and OAuth scope. See Setting Up Identity Access for Fusion Connections. |
| EPM access denied | Confirm that the integration user is provisioned in the target EPM environment and has the required permissions. Verify that the OAuth scope and EPM secondary audience identify the same target environment. |
| EPM API validation failure | Authentication might have succeeded, but the EPM API check didn't complete successfully. Review the error message for details of the failed check. |
| Validation execution failure or timeout | Validation couldn't complete or didn't return a result within the allowed time. Review the latest work request and destination state before submitting another update. |
| Data-plane configuration rejection | Authentication might have succeeded, but the validated connection configuration couldn't be applied, for example because of an ownership conflict with an existing binding. Include the work request details when contacting support about the conflict. |
| Data-plane acknowledgement timeout | Validation succeeded, but confirmation that the connection configuration was applied didn't arrive in time. Review the latest work request and destination state. The timeout alone doesn't establish whether the configuration was applied. |
After correcting a configuration issue, open the workspace's Destination tab, select Edit destination, and update the same connection. Save the changes and review the new validation work request.
If the issue requires support, provide the work request identifier, error code, message, and timestamp. A failed or timed-out connection validation doesn't establish the outcome of an EPM file delivery or application load.
Resolving EPM Preparation Issues
If the onboarding batch fails, review its output and the timestamped log in the deployment folder's logs subfolder. Check the target environment, account access, configuration values, credentials, and paths to the Cost Advisor metadata and data files against Preparing Fusion EPM for Cost Advisor for AI.
| Issue | Resolution and responsible contact |
|---|---|
| EPM authentication, identity domain, license, or encrypted password file issue | Contact your EPM administrator. For an authentication failure, retain the relevant logs. Don't send the password or encrypted password file. |
| Deployment host permissions, package placement, or batch execution issue | Contact the IT team responsible for the deployment host and shared location. |
| Missing input file or pipeline load failure | Verify all six local CSV files, the EPM inbox paths, and the start and end period mappings. Have the EPM administrator review both pipeline results and their job logs. |
| Cost Advisor navigation isn't displayed | Verify that the imported Oracle Cost Advisor for AI navigation flow is active. Then select Reload Navigation Flow from the username menu. |
| Cost Advisor LCM import failure | Retain the LCM import logs and contact the Oracle representative identified for the deployment. |
If the integration account can't access the target EPM environment, have the administrators confirm that it is active, exists in the associated identity domain, and is provisioned in the intended EPM environment. Verify that the username matches exactly and that its EPM roles allow upload, listing, download, and deletion of the integration files.
For application import errors, open Migration in EPM, select Reports, and then select Migration Status. Review the failed import's status and error details. See Generating the Migration Status Report.
After a batch failure, retain the log and have the EPM administrator identify which steps completed. Confirm the recovery procedure before rerunning EPM_Cost_Advisor_for_AI_Onboarding.bat because it imports the snapshot and reloads the local files. Record the correction and retain the final import and pipeline results for the onboarding handoff.
After resolving the preparation issues, return to Prepare Fusion EPM in Add destination and continue the connection setup. See Preparing Fusion EPM for Cost Advisor for AI.