Preparing Fusion EPM for Cost Advisor for AI

In the target EPM environment, open Settings and Actions by selecting your user name, select Downloads, and download the EPM Automate installer. See Downloading and Installing Clients and Installing EPM Automate on Windows.

Create a stable deployment folder, such as C:\EPMAutomate, outside individual user profile folders. Restrict access to authorized operators and grant the permissions needed to manage deployment files, data, credentials, and logs.

The examples in this topic use C:\EPMAutomate. If you select another location, update the paths in ConfigFile.bat and the commands accordingly.

Locate the extracted package folder that directly contains ConfigFile.bat, EPM_Cost_Advisor_for_AI_Onboarding.bat, and Instruction.txt. If extraction creates an outer folder, open it to locate the package folder. Copy the package contents directly into C:\EPMAutomate, preserving the subfolders. Verify that the configuration file is at C:\EPMAutomate\ConfigFile.bat.

Keep the Lifecycle Management (LCM) snapshot ZIP compressed. Preserve the supplied filenames. Modify only the documented configuration settings and the Cost Advisor metadata and data files.

Record the HTTPS base URL of each, without a path, query string, or fragment. For the EPM environment, omit /epmcloud. For the identity domain, omit the OAuth token endpoint path. Don't use a sign-in redirect URL.

Keep these values for the EPM environment URL and Identity domain URL fields when connecting the destination.

Record the approved pairing of identity domain and EPM environment. Authorization for this connection applies to the selected EPM environment. If your deployment requires a different identity domain, have the EPM and identity domain administrators confirm and complete the supported domain-access or federation configuration before activating the confidential application. The configuration depends on the EPM release and tenancy setup.

Before running the onboarding batch, create or identify the deployment and integration accounts and assign their roles. The account that runs the batch needs access to the deployment folder and permission to import the application configuration into the target EPM environment. The supplied batch uses importUsers=FALSE, so it doesn't import users or their application role assignments.

For ongoing file delivery, create or reuse an active, dedicated integration account in the associated identity domain and provision it in the target EPM environment. Use an operational username, such as svc_cost_advisor_epm_upload, rather than an individual administrator's personal account. Record its exact sign-in username for the Integration username field. This username becomes the JWT sub value. Don't use the display name or OAuth client ID. Verify that the username identifies the user provisioned in EPM.

Have the EPM administrator grant only the roles needed to upload, list, download, and delete the files used by the integration. Deletion is required when replacing changed files at the target path. Upload permission alone isn't enough. Record the assigned roles and the administrator who approved them. The roles needed for ongoing delivery can differ from those needed to import the application configuration.

For user and role setup, see Creating User and Assigning Roles. For file operation requirements, see Upload, List Files, Download, and Delete Files.

Set EPM_URL, EPM_USERNAME, EPM_AUTOMATE, EPM_PASSWORD_FILE, EPM_SNAPSHOT_PATH, EPM_SNAPSHOT_NAME, and EPM_INTEGRATION_PATH. Omit the .zip extension from EPM_SNAPSHOT_NAME. The supplied batch doesn't pass EPM_IDENTITY_DOMAIN to its sign-in command. Set the identity domain URL of the Cost Advisor destination separately.

Set EPM_AUTOMATE to the full path of the installed epmautomate.bat. For the example deployment folder, use these package paths:

SET EPM_PASSWORD_FILE=C:\EPMAutomate\Epmpassword.epw
SET EPM_SNAPSHOT_PATH=C:\EPMAutomate\Cost_Advisor_for_AI_Snapshot
SET EPM_SNAPSHOT_NAME=Cost_Advisor_for_AI_Onboarding_Snapshot
SET EPM_INTEGRATION_PATH=C:\EPMAutomate\Cost_Advisor_for_AI_Integration

On the administrator's workstation, open a command prompt from which you can run EPM Automate. Replace PASSWORD and KEY with your values and run:

epmautomate encrypt PASSWORD KEY "C:\EPMAutomate\Epmpassword.epw"

If you specified a different EPM_PASSWORD_FILE path, use that exact path as the final argument. Verify that the generated file exists and that its path matches EPM_PASSWORD_FILE in ConfigFile.bat. Save the configuration file.

For command syntax and passwords that contain special characters, see encrypt.

The batch uses this file in the EPM Automate environment. The Cost Advisor for AI destination connection uses certificate-based OAuth. Don't enter or upload the deployment password or encrypted password file in destination setup.

Work with your finance team and EPM administrator to review the organizational and financial data in the supplied Cost Advisor metadata and data files before loading them. Keep Metadata_Provider.csv, Metadata_Department.csv, Metadata_Entity.csv, Metadata_Model.csv, Metadata_Intent.csv, and Cost_Data.csv in the local Cost_Advisor_for_AI_Integration folder. Preserve the supplied filenames, headers, and column order. The batch uploads all six files to the EPM inbox and loads their contents.

Confirm with the EPM administrator that the Cost Advisor metadata and data files use the identifiers and periods expected by the integrations. Changing EPM_INTEGRATION_PATH changes the local source folder. It doesn't change the EPM input paths in the imported pipelines.

Update both the METADATALOAD and ACTUALDATALOAD commands.

The periods must exist in Data Integration period mappings. The supplied commands use IMPORTMODE=Replace, EXPORTMODE=Merge, SEND_MAIL=Always, and ATTACH_LOGS=Y. Have the EPM administrator confirm these settings for the target environment. See runPipeline.

Confirm the target environment, accounts, configuration values, credentials, Cost Advisor metadata and data files, and pipeline parameters before starting. The batch performs these actions in order:

1. Signs in to the target EPM environment.
2. Uploads and imports Cost_Advisor_for_AI_Onboarding_Snapshot.zip with importUsers=FALSE. Prepare users and their application roles separately. See importSnapshot.
3. Uploads the five metadata files and Cost_Data.csv to inbox.
4. Runs METADATALOAD to load the five metadata dimensions and refresh the application.
5. Runs ACTUALDATALOAD, which reads inbox/Cost_Data.csv for the cost, credits, data, and user integrations.
6. Signs out.

Sign in to the Windows deployment host with an account authorized to access the deployment files. Open a command prompt and run:

cd /d C:\EPMAutomate
EPM_Cost_Advisor_for_AI_Onboarding.bat

Adjust the deployment path if needed. Keep the command window open until the batch finishes.

Review the batch output and logs in the package's log folder. In EPM, open Migration, select Reports, and then select Migration Status. Review the import status and any errors. See Accessing Migration for Lifecycle Management and Generating the Migration Status Report.

The batch writes Cost_Advisor_for_AI_EPMAutomate_YYYYMMDD_HHMMSS.log in the logs folder beside the batch. Review the execution results for METADATALOAD and ACTUALDATALOAD in Data Integration and confirm the expected data was loaded.

Retain the import and pipeline results with the batch log for the onboarding handoff.

If any step fails, work with the EPM administrator to identify completed steps and confirm the recovery procedure before rerunning the batch. Rerunning imports the snapshot and reloads the local files. See Resolving EPM Preparation Issues.