Default File Location

Default File Location

On Windows, EPM Automate uses a default file location for the following:

• Files to be uploaded to the environment
• Files downloaded from the environment
• Log files
• Encrypted password file
• User preferences file
• Files used by, or generated as a result of, these commands:
  • cloneEnvironment
  • copyFileFromInstance
  • copyFromObjectStorage2
  • copyFromSFTP
  • copySnapshotFromInstance
  • copyToObjectStorage2
  • copyToSFTP
  • replay
• Parameter files used to pass values for command execution

For relative local file paths on Windows, EPM Automate selects the default file location in the following order:

• The directory defined by the EPMAUTOMATE_BASE_DIR environment variable. The Windows user executing EPM Automate must have read and write access to this directory.

  If the specified directory does not already exist, EPM Automate creates and normalizes the directory path.

• The ProgramData\Oracle\EPM Automate directory, if it contains EPM Automate runtime files from previous sessions.
• The current working directory if ProgramData\Oracle\EPM Automate does not contain previous EPM Automate runtime files.

  This option assumes that the Windows user running EPM Automate has read and write permissions for the current working directory.

• The ProgramData\Oracle\EPM Automate directory if the current Windows user:
  • does not have read and write access to the current working directory.
  • has permission to create the ProgramData\Oracle\EPM Automate directory, if it does not already exist.

Absolute local paths used with command parameter values are used as provided. Relative local paths resolve under the appropriate default local file location.

Note:

If you do not specify a path when redirecting command output to a file (for example, empautomate listfiles >> myfile.txt), the file is created in the current directory from which EPM Automate is run (by default. Program Files\Oracle\EPM Automate\bin), not in ProgramData\Oracle\EPM Automate. If you do not have write permission to the current working directory, redirect the output to a directory where you have write access.

On Linux, the default file location is the current directory from which the EPM Automate command is invoked.

If the file name specified as a parameter to an EPM Automate command does not exist in the default location, specify the fully qualified file name.

Inbox and Outbox

The inbox and outbox locations may differ across Oracle Fusion Cloud Enterprise Performance Management business processes. You use the inbox to upload files that you want to import or otherwise process in a Cloud EPM business process other than Profitability and Cost Management. Data Management can process files stored in the inbox or a subdirectory of the inbox.

Typically, Cloud EPM stores generated by business processes, for example, data or metadata export files, in the outbox.

• The inbox to which EPM Automate uploads files and the outbox that stores the files for download is accessible to these applications. You must upload files to this location if you plan to process them using a process that is native to these applications. You can also upload files to the outbox.
  • Planning
  • Planning Modules
  • Account Reconciliation
  • Financial Consolidation and Close
  • Tax Reporting
  • Narrative Reporting
  • Enterprise Profitability and Cost Management

  You can use the Inbox/Outbox Explorer to browse the files stored in the default location. Application snapshots that you create using EPM Automate are not listed in the Inbox/Outbox Explorer; you can view them from the Snapshots tab of Migration.

• Files processed by Profitability and Cost Management must be uploaded into profitinbox. You can also upload files to the profitoutbox. Files exported by Profitability and Cost Management processes are stored in profitoutbox. You use the File Explorer to browse these files.
• Files for processing by Data Management must be available in the inbox or in a subfolder of the inbox. By default, Data Management export files are stored in the outbox, while Data Management report output is stored in the outbox/report folder. You use the Data Management File Browser to browse these files.
• Oracle Enterprise Data Management Cloud uses the default location for import and export files that are uploaded, copied, or downloaded. Files in the default location can be viewed using the ListFiles command.

Log Files

Each EPM Automate command execution generates a debug file, which is automatically deleted if the command is successful. If an error occurs during command execution, the debug file for the failed command is maintained in the selected default local file location (see Default File Location) on Windows and in home/user/epmautomate/bin on Linux/UNIX computers.

EPM Automate debug files use the following naming convention:

commandname_date_timestamp.log. For example, if you run a failed listfiles command at 09:28:02 on November 23, 2025, the debug file name is listfiles_23_11_2025_09_28_02.log.

You cannot suppress the creation of the debug file for a failed command. You can, however, write debug information and command output to a file in a different directory by appending the -d option and redirecting the output and error streams. For example: (empmautomate listfiles -d >> c:\logs\LOG_FILE_NAME.log 2>&1) to end of the command as shown in the following Windows example:

epmautomate listfiles -d >> c:\logs\listfiles.log 2>&1