Oracle Fusion Cloud ERP

Oracle Fusion Cloud ERP can deliver report files to Files.com over SFTP. Files.com can also collect and prepare files for an Oracle import pipeline. These directions serve different jobs: Oracle Analytics Publisher, also known as BI Publisher, sends extracts to an external destination, while File-Based Data Import (FBDI) loads prepared data through Oracle's content repository and import processes.

Files.com provides the file exchange around the ERP. It receives partner submissions, separates access by counterparty, and routes prepared output. The Oracle application or its integration platform still owns the business layout, import submission, and acceptance of the records.

Publisher Exports to Files.com

Create a dedicated Files.com machine account with SFTP enabled and upload access to the report's destination folder.

In Publisher administration, add an FTP or SFTP server as a delivery channel. Enter the Files.com hostname or custom domain and port 22, then select Use Secure FTP. Choose password or private-key authentication to match the Files.com account. For a private key, register the matching public key on that user. See SFTP connection settings for account and network requirements.

Configure the report schedule or bursting delivery with that server, the account-visible directory, and the intended filename. Publisher's bursting delivery settings distinguish the configured server from the destination directory and file. An SFTP client root changes the path visible to the report's account.

Publisher can use a .part extension during transfer and rename the completed file. If enabled, let the account perform that rename and make any onward selection match the finished filename. Keep incomplete deliveries outside the next system's processing selection.

Files.com can then route the report through an Automation or deliver it to another server. A successful Publisher delivery establishes the first transfer, not the recipient's later processing.

FBDI Import Staging

FBDI is not an SFTP pickup job inside the ERP. Oracle's external data integration model separates preparation of the required files, loading to interface tables, and application-specific import processing.

Use Files.com as the controlled location before that pipeline. For example, a supplier submits a source file to its own folder. Oracle Integration or another integration platform collects the prepared input, constructs the required package, uploads it to Oracle WebCenter Content, also called UCM, and submits the appropriate import. The pipeline needs its own Oracle credentials and application permissions in addition to its Files.com access.

Prepare the package for the particular FBDI process, including its required CSV layouts and ZIP contents. Files.com Transformations can reshape source data, but transferring or renaming a file does not make it a valid Oracle import package. Oracle's FBDI orchestration example explains how its integration platform prepares and collects those files.

Publish the complete input to a dedicated pickup folder after preparation succeeds. If the pipeline uses a separate completion file, publish that signal only after the data or package is ready. Keep original submissions available according to the workflow's recovery and retention policy.

Import Results and Resubmission

Track file collection, package upload, and the Oracle load and import results as separate stages. A file can leave Files.com successfully while Oracle rejects its layout or business data.

Use the integration platform's run history and Oracle's load and import logs to identify the stage needing correction. Check for records already accepted before resubmitting a package. Files.com SFTP Logs establish the file operations, while Oracle supplies the result of its application processing.