Preparing to Use Cost Advisor for AI

Prepare the access, provider information, and Fusion EPM environment needed to set up a Cost Advisor workspace.

Important

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.

To review Cost Advisor data and insights in Fusion EPM, you need a workspace, at least one AI provider, and a Fusion EPM destination. Before starting the guided setup, coordinate with your AI provider, EPM, and identity domain administrators. We recommend completing Fusion EPM preparation before adding AI providers. Complete the EPM setup before entering destination connection details in the OCI Console.

Required OCI Permissions

Cost Advisor for AI is part of the OCI Generative AI service. If you have permission to use OCI Generative AI, you can use Cost Advisor for AI within the scope of that permission. If you have manage generative-ai-family permission, you can also manage Cost Advisor for AI within the same tenancy or compartment scope.

For policy examples, see Give User Groups Access to All Generative AI Resources.

Required Preparation

OCI access: Select a supported region and compartment for the workspace, and confirm your permission to create and manage Cost Advisor for AI resources there.
AI provider access: Identify the AI provider connections whose usage and costs you want to include. Arrange for an authorized administrator to supply the credentials and permission scopes listed in Provider Credentials and Permissions.
Fusion EPM environment: Identify the target Fusion EPM instance and confirm that you have an EPM Enterprise license. Have your EPM Service Administrator prepare the Cost Advisor Planning application. See Preparing Fusion EPM for Cost Advisor for AI.
EPM deployment environment: Arrange for your EPM administrator to install EPM Automate on a customer-managed Windows computer or server and prepare an account with permission to import the application configuration. The administrator uses this environment to run the onboarding batch supplied in the setup package.
EPM integration and identity access: Have your EPM and identity domain administrators create or identify a dedicated integration user and grant the EPM permissions needed for file delivery. Have the identity domain administrator set up and activate a confidential application using the public certificate downloaded during destination setup. A confidential application is an OAuth client registration in the identity domain. It lets Cost Advisor authenticate and obtain access tokens to connect to Fusion EPM. See Setting Up Identity Access for Fusion Connections.
Cost Advisor reporting data: Work with your finance team and EPM administrator to review the Cost Advisor metadata and data needed for the initial EPM load, including organizational information such as departments and entities. Follow the setup package instructions for sample files, file formats, and the data to prepare.

Recommended Mapping Preparation

Person and project ID mappings associate AI spending with management hierarchies and cost centers, supporting more detailed cost allocation and reporting in Fusion EPM. Person mapping applies to per-user costs, and project ID mapping applies to OpenAI API, Anthropic Console, and OCI Generative AI costs. We recommend that you add both optional mappings to cover these different usage sources.

Person mapping: Select one of two sources:
- Fusion HCM: Arrange for HCM and identity domain administrators to import the supplied HCM Extract definition, authorize a dedicated account, and set up identity access. See Preparing Fusion HCM for Person Mapping.
- CSV file: Select this option if you don't have Fusion HCM or prefer to upload person and organizational information manually. Prepare each person's work email address, manager email addresses ordered from highest to lowest, and cost-center code using the person mapping template. See Adding a Person Mapping from a CSV File.
Project ID mapping: CSV upload is the only option. Prepare a separate file with OpenAI project IDs, Anthropic workspace IDs, or an OCI tenancy OCID and the associated management hierarchies and cost-center codes. Include the project owner's email at the lowest populated hierarchy level. You can include all three providers in one file, using provider codes OPENAI, ANTHROPIC, and OCI. See Adding a Project ID Mapping from a CSV File.

Each CSV template has hierarchy columns m1 through m11. Start with the highest management level in m1 and leave unused levels blank without removing columns. Each file supplies its hierarchy independently. Project mapping doesn't require matching person mapping records.

Add both mappings before connecting the Fusion EPM destination so that the delivered Cost Advisor data includes your cost allocations.

Protect Connection Information

Use dedicated integration accounts and grant only the access required for the selected data and operations. Enter API keys only in the intended setup fields. Don't include passwords, API keys, private keys, access tokens, or encrypted credential files in support messages or screenshots.

When adding a Fusion HCM or Fusion EPM connection in the OCI Console, you use a public signing certificate and OAuth. The connection requires an integration username, but not the account password or an OAuth client secret. EPM Automate credentials are set up separately in the EPM deployment environment.

Setup Sequence and Estimated Times

The processing times below are estimates. Allow additional time to prepare credentials and mapping files and to set up the Fusion EPM environment.

Create a workspace. Creation takes about 12 minutes.
Open the workspace's Destination tab and select Add destination. In step 1, Prepare Fusion EPM, download the setup package containing the application configuration, onboarding files, and setup guide. Have your EPM administrator complete the EPM setup and application configuration import before you continue with providers and mappings.
Add at least one AI provider. Adding each provider takes about 10 minutes.
Add the recommended person and project ID mappings for cost allocation. Adding a Fusion HCM connection takes about 6 to 8 minutes. Each person or project ID mapping CSV upload takes 5 to 10 minutes. CSV validation is a separate check and takes about 5 minutes. Both CSV timings depend on file size.
Return to destination setup to set up identity access and complete the Fusion EPM connection. Adding the connection takes about 6 to 8 minutes.
Have your EPM administrator set up daily pipeline runs to load ongoing Cost Advisor deliveries into Fusion EPM for reporting.