Importing and Exporting FCCS Dimensions in Oracle EDM (formerly EDMCS)

In this tutorial we'll walk through importing and exporting Financial Consolidation and Close (FCCS) dimensions in Oracle Fusion Cloud Enterprise Data Management (the product most of us still call EDMCS).

Following along with screenshots? Rather than reproduce Oracle's copyrighted UI images, this walkthrough links to Oracle's official documentation for the current Import and Export screens. Oracle's Importing Dimensions, Importing FCCS Dimensions, and Exporting FCCS Dimensions references walk through every screen described below.

Unlike importing Oracle Financials Cloud General Ledger dimensions into EDM, importing FCCS dimensions is straightforward: EDM supports importing from a local comma-delimited (CSV) file, or from a connected external application's outbox using a compressed (ZIP) file.

Below are the steps for importing an FCCS dimension after setting up an FCCS application in EDM.

Importing FCCS Dimensions

1. From the Applications list, locate your FCCS application, click the ellipsis (⋯) button next to it, and select Import.
2. Click the dimension you want to import data into.
3. Choose your import source: File to select or drag-and-drop a local comma-delimited (CSV) file, or Connection to pull a compressed (ZIP) file from a connected external application's outbox. If you're importing via ZIP, note that each CSV filename inside it must end with the dimension name (or external dimension name): a file named acc1.csv will be rejected, while something like myaccounts_acc1.csv will work.
4. Select an Import Mode: Reset, Replace, or Merge.
   • Reset clears all existing nodes and relationships in the dimension and rebuilds it from the import file. This is required for the first import into an empty dimension: Merge and Replace cannot be used until the dimension already has data in it.
   • Replace keeps hierarchy relationships that exist in both the source file and the current viewpoint, removes relationships that only exist in the viewpoint, and adds new nodes and updated property values. It expects a full dataset, not a partial one.
   • Merge reconciles the viewpoint against your source file: it adds new nodes, updates changed property values, and can remove nodes no longer present in the source depending on your merge options, all while still enforcing full validation. Like the other modes, it still expects the complete dataset for the viewpoint, not just the changed rows.
5. Optionally, click the dimension name in the Summary section to review the import options before committing.
6. Click Import. A success message (green) or an error message (red) will appear, and the outcome is also logged in the history for that dimension.

A couple of details worth keeping in mind: import files should be UTF-8 encoded (in Excel, save as "CSV UTF-8 (Comma delimited)"), and beyond the UI, you can also trigger an FCCS dimension import through EPM Automate's importDimension command, the EDM REST API, or Task Manager, useful if you want this step to run as part of a scheduled or automated process rather than a manual one.

Exporting FCCS Dimensions

1. From the Applications list, find your FCCS application, click the ellipsis (⋯) button, and select Export.
2. Select the dimension you want to export.
3. Choose your Export Target: File to download a local CSV (EDM auto-generates a filename in the format ApplicationName_DimensionName_Date, which you can edit before exporting), or Connection to export directly into the FCCS application's inbox via a preconfigured connection.
4. Optionally, click the dimension name in the Summary section to adjust export options (for example, substituting specific text for null or blank values), or enable Validate Before Export to have EDM validate the viewpoint automatically before the file is generated.
5. Click Export. As with import, you'll see a success message (green) or an error message (red); if validation errors come up, you can resolve them and click Return to Export to try again.

Being able to move FCCS dimension data in and out of EDM this cleanly is what makes EDM useful as the system of record for metadata: you can make and validate changes centrally, then push them out to FCCS (or pull a snapshot back in) without hand-editing hierarchies inside the target application itself.

Contact us today to learn more.