Today we’re going on a deeper dive into the newly released Consolidation & Close (formerly known as FCCS) adapter within Enterprise Data Management (formerly known as EDMCS, now EDM).

Like the Enterprise/Planning & Budgeting (EPBCS/PBCS) & Oracle Cloud Financials adapters, there is a setup wizard to register your application to generate the necessary Data Chain objects & properties necessary to support Consolidation & Close.


Registering the Application Adapter

First, in my app I go to the Applications card and register a new application. You can see there is now a Financial Consolidation & Close Application Type option:2019-10-07_14-57-20

You simply name your application (note, this can be the real FCCS app name or just what you want to call it in your app. I prefer naming it what I want it in my EDM application so I don’t get confused when I see the Default View). You’ll also set up a default connection. This is similar to the rest of the OOTB adapters – you’ll want to set up some kind of service account that has access to your FCCS app so it can read & write into the inbox/outbox.

The next step in the setup wizard allows for customizing the application setup for your FCCS application. For this you will need to know:

  1. If your FCCS application is Multi-Currency
  2. What currencies are in the FCCS application
  3. What is the main currency
  4. Is Intercompany enabled (most likely so)
  5. Is Multi-GAAP enabled
  6. Is this an Extended Dimensionality application?
  7. What are the Alias tables
  8. What custom SmartLists are in the app? –> this auto-fills the Smart list dropdowns in the EDM properties


Next up is setting the dimensions. It’s important to note that you should name your dimensions for Account, Entity, and Movement exactly as they are in the FCCS application. Only “Custom” dimensions allow for an override in their setup to have an “EDM name” and a different “FCCS name”.

Create the dimensions one by one in the wizard, ensuring to select the correct “Dimension Type” for each one. Below is the example setup for the Account dimension for FCCS:


Attribute dimension setup is available for Entity, Movement, and Custom dimensions.

Because this is an OOTB application adapter, you do not need to select or create any custom properties, as you would with a Custom adapter.

Finally, review and submit the Registration. You can go an edit/add any additional details or dimensions after initial registration.

After the adapter is set up, the next steps are to go into FCCS and create dimension exports for each dimension (or a .zip of all dimensions, if you want) and import them into the application. This is the same process as setting up E/PBCS data in EDM.

EDM Objects Created for FCCS

Like any EDM OOTB Application Adapter, all objects for the Data Chain are created to support the target system data model. This includes Node Types, Hierarchy Sets, Node Sets, and Viewpoints/Default Application View.

However, with the FCCS adapter, we also get some additional Properties to support the FCCS attributes for metadata.

If you go review the Node Types created for the FCCS application and click the Properties tab, we can review the properties set up automatically in the registration process. For Accounts, there are 38 properties to support the metadata for FCCS, most of which are Planning type properties that come with the EPBCS adapter, which start with a “PLN.” prefix. This due to FCCS being based upon the E/PBCS platform.


However, if you scroll to the bottom of the Properties panel you’ll see there are new properties with a “FCCS.” prefix that are generated for FCCS support:


The properties added for FCCS include 5 Account properties and 1 Entity property:

Screen Shot 2019-10-09 at 12.25.01 PM

There is a difference between the EDMCS Display vs. Output for FCCS File, if you open the FCCS View to look at the Account or Entity viewpoint, the properties will display in the right-hand panel. I opened a new Request, and for those properties the “EDMCS Display” is “Yes” but the output file from EDM that FCCS imports will have the value of the Output FCCS File column. Just another way to make the user experience more simple.



Similarities to the E/PBCS OOTB Adapters

For next steps, maintaining and integrating EDM to the Consolidation & Close application is the same process used for the E/PBCS adapters; the Viewpoints can be managed via Requests to make updates to the hierarchies and attributes to support FCCS metadata.

From an integration standpoint, this is also similar to the E/PBCS adapter, in that it will export files to the FCCS inbox/outbox so you can import the dimension updates either manually, or via EPM Automate. The Connection Information from set up in the Application Registration is how EDM knows which application inbox/outbox to place the files, or the Inspect > Connections > Edit menu can be used to add additional connections.

The FCCS adapter also leverages the same features to import data from the FCCS inbox/outbox into the View/Viewpoints in EDM, as well as validations to ensure that the metadata in EDM is managed appropriately.




Thank you very much for reading – as always, please let me know if you have questions. Hoping to catch up and get more content out there soon on EDM Expressions & the new Audit card soon! Happy Wednesday!