Hall 3 of the FCCS EPM Cloud Study Tour

Data Integration Gallery

Getting the numbers in. From flat-file CSV loads and Data Management mappings to EPM Automate scripting and REST API calls — every pathway that moves GlobalMerge Corp's trial balances into FCCS and keeps them current.

Data Management / FDMEE EPM Automate File-Based Load REST API Mappings & Transformations Error Handling
🔌 Why Data Integration Matters in FCCS
Bridging the gap between source ERPs and the consolidation engine

FCCS is a consolidation and close platform, not a general ledger. It does not natively hold transactional data. Every balance that enters FCCS — revenue, expenses, assets, liabilities — must be loaded from an external source system such as Oracle ERP Cloud, SAP, NetSuite, or a subsidiary's local accounting package.

Data Integration (formerly known as FDMEE — Financial Data Management Enterprise Edition) is the Oracle-native ETL layer that sits between source systems and FCCS. It handles extraction, transformation, mapping, validation, and loading in a governed, auditable pipeline.

🔑 Core Concept

Data Integration is not optional. Even if you load a flat CSV file, it passes through the Data Management mapping rules before landing in FCCS dimensions. Understanding this pipeline end-to-end is a critical exam topic — and a daily operational reality for every FCCS administrator.

🛣️ Integration Pathways
Four routes to load data into FCCS
Data Management UI
Browser-based wizard for defining data load rules, import formats, and dimension mappings. Best for ad-hoc loads and initial setup.
Navigator → Data Exchange → Data Integration
EPM Automate
Command-line scripting tool. Automates uploads, data rule execution, metadata imports, and consolidation runs. Ideal for month-end schedulers.
epmautomate.bat / epmautomate.sh
File-Based Load (.dat / .csv)
Direct delimited file load via the FCCS Inbox. Bypasses mapping for pre-mapped data; fastest pathway for simple structures.
Inbox/Outbox folder · fixed format
REST API
Programmatic access using Oracle REST APIs. Enables custom integrations, middleware orchestration (MuleSoft, OIC), and real-time pushes.
POST /jobs/dataRule · Bearer token
Oracle Integration (OIC)
Low-code integration platform that connects ERP Cloud, FCCS, and other SaaS apps with pre-built adapters and visual workflow design.
OIC FCCS Adapter · managed service
Smart View (Manual Entry)
Excel add-in for ad-hoc data submission directly into data forms. Used for adjustments, supplemental schedules, and journal-style inputs.
Oracle Smart View for Office
🔄 The Data Management Pipeline
Five stages from source to consolidated cube
🏭 Stage 1 Source System
→ Extract
📥 Stage 2 Import
→ Validate
🗺️ Stage 3 Map
→ Transform
✅ Stage 4 Validate
→ Load
🧮 Stage 5 FCCS Cube

Import pulls raw source data into the Data Management staging area. Mapping translates source codes (e.g., SAP GL accounts) into FCCS dimension members. Validate checks for unmapped members and data type errors. Load pushes clean, mapped data into the FCCS Essbase cube. A failed step at any stage stops the pipeline and generates an error log.

⚠️ Load Mode — Replace vs. Accumulate vs. Subtract

When running a data load rule you must select a load mode. Replace overwrites existing data for the selected entity/period/scenario. Accumulate adds incoming values to what's already there — useful for loading multiple files that together make one period's balance. Subtract is used to reverse a previously loaded batch.

🌐 GlobalMerge Corp — Source System Landscape
Four subsidiaries, four source systems, one consolidation
Entity Currency Ownership Source System Integration Method
BritEdge Ltd GBP 100% Oracle ERP Cloud OIC Adapter · automated nightly
DeutschWerk GmbH EUR 80% SAP S/4HANA CSV extract → Data Management mapping
AsiaLink Pte Ltd SGD 50% JV NetSuite REST API push via EPM Automate script
NovaTech Inc USD 30% Equity QuickBooks / Excel Manual .dat file upload via Smart View
💡 NovaTech — Equity Method Note

Because NovaTech uses the Equity Method (PCON = 0), only the Investment in NovaTech account balance and NovaTech's net equity share (30%) need to be loaded into FCCS. Loading the full trial balance would waste storage and create confusing zero-contribution data. Many teams load only the equity pickup journal entry for equity-method investees.

🗺️ Data Management — Key Configuration Objects
The four building blocks of any Data Management integration
Import Format
Defines the structure of the incoming file: delimiter, header rows, which column maps to which FCCS dimension (Entity, Account, Period, Amount…).
Setup → Import Format
Location
A named target point — the combination of entity, category (Scenario), and the import format to use. One location per source/entity combination.
Setup → Location
Data Load Mappings
Translation rules converting source codes to FCCS member names. Four types: Explicit, Between, In, and Like. Applied per dimension per location.
Setup → Mappings
Data Load Rule
The execution object. Combines location + period mapping + load method. Running a data load rule triggers the full import → map → validate → load pipeline.
Workflow → Data Load Rule
🔀 Mapping Rule Types
Translating source GL codes to FCCS dimension members
Type Source Value Target Member Use Case
Explicit 4001-GBP Revenue_UK Exact one-to-one match; highest priority
Between 4000–4999 Revenue Range of numeric GL codes to one target
In 5001,5003,5007 DirectCosts Discrete list; non-contiguous codes
Like IC_* ICElimAcct Wildcard/pattern match; lowest priority
⚠️ Mapping Priority Order

When multiple rules could match the same source value, Data Management applies them in priority order: Explicit → In → Between → Like. Explicit always wins. A common exam scenario: an account matches both an Explicit rule and a Like wildcard — the Explicit rule takes precedence regardless of the order rules were created.

📄 Import File Format — .dat Reference
Header syntax and column structure for direct file loads

Direct file loads use a .dat file (tab-delimited or comma-delimited) that FCCS can accept via the Inbox. The first row must be the header defining dimension column positions. Amount columns must use the correct sign convention based on account type.

! GlobalMerge_BritEdge_Actual_Jan25.dat ! Entity: BritEdge | Scenario: Actual | Year: FY2025 | Period: Jan Scenario,Year,Period,View,Entity,Account,ICP,Movement,Amount Actual,FY2025,Jan,Periodic,BritEdge,Revenue,ICP_None,Periodic,1250000 Actual,FY2025,Jan,Periodic,BritEdge,ICSales,ICP_DeutschWerk,Periodic,500000 Actual,FY2025,Jan,Periodic,BritEdge,COGS,ICP_None,Periodic,-720000 Actual,FY2025,Jan,Periodic,BritEdge,Cash,ICP_None,Movements.Closing,3400000 Actual,FY2025,Jan,Periodic,BritEdge,ICPayables,ICP_AsiaLink,Movements.Closing,-80000
💡 Sign Convention

FCCS uses natural sign for most account types. Revenue is positive when a credit (income). Expenses are negative (debit side outflow). Assets are positive. Liabilities and Equity are negative on the BS. Always confirm the application's sign convention setting before loading — some teams configure Reverse Sign to match their ERP's output.

🤖 EPM Automate — Key Commands
Month-end automation commands for the GlobalMerge integration pipeline
## ── Step 1: Login ──────────────────────────────────────────── epmautomate login admin@globalmerge.com Pa$$w0rd https://fccs-a123456.epm.oraclecloud.com ## ── Step 2: Upload source file to Inbox ────────────────────── epmautomate uploadFile "BritEdge_Jan25.dat" inbox/BritEdge_Jan25.dat ## ── Step 3: Run Data Load Rule (maps + loads to FCCS cube) ─── epmautomate runDataRule "BritEdge_Actual_Monthly" Jan 2025 Jan 2025 REPLACE ## ── Step 4: Import metadata refresh (if new accounts) ──────── epmautomate importMetadata "GlobalMerge_Metadata_v2.csv" epmautomate refreshCube ## ── Step 5: Run Consolidation for BritEdge ─────────────────── epmautomate consolidate "BritEdge" "Actual" "FY2025" "Jan" "YTD" ## ── Step 6: Download error/process log ─────────────────────── epmautomate downloadFile "outbox/logs/BritEdge_Jan25_error.log" ## ── Step 7: Logout ─────────────────────────────────────────── epmautomate logout
⚡ Scheduling EPM Automate

EPM Automate scripts are typically wrapped in a Shell (.sh) or Batch (.bat) file and scheduled via the OS scheduler (cron on Linux, Task Scheduler on Windows) or an enterprise scheduler like Control-M. Oracle recommends running the month-end script after the ERP close and before the FCCS consolidation deadline. For GlobalMerge, this means BritEdge (Oracle ERP) loads first via OIC, then DeutschWerk (SAP CSV) and AsiaLink (REST API) in parallel.

⚠️ Error Handling & Load Status
Common load errors and resolution paths
🔴 Unmapped Member — source code has no mapping rule in Data Management LOAD_ERROR
🟡 Period Mismatch — file period header does not match the Data Load Rule period range VALIDATION_WARN
🔴 Invalid ICP — ICP partner code not found in ICP dimension (entity may have been renamed) LOAD_ERROR
🟡 Locked Period — target entity/period is locked; no data can be written LOAD_BLOCKED
🟢 Load Complete — all rows mapped and committed to the FCCS cube successfully SUCCESS
🔵 Partial Load — some rows loaded; unmapped rows written to error file in Outbox PARTIAL
🟠 Currency Not Defined — entity's default currency has no exchange rate for the load period RATE_MISSING
⚠️ GlobalMerge DeutschWerk Scenario — Unmapped Account

DeutschWerk's SAP trial balance includes account 491000 (Sonstige Erträge) — a German-specific miscellaneous income code not yet in the Data Management mapping table. The load will fail with LOAD_ERROR for all rows containing 491000. Resolution: add an Explicit mapping rule 491000 → OtherIncome in the DeutschWerk location, then re-run the data load rule with Replace mode.

🔬 Lab Overview
End-to-end data load for GlobalMerge Corp — January 2025

In this lab you will configure the complete data integration pipeline for GlobalMerge Corp's January 2025 close cycle. You'll set up Import Formats, define Account and Entity mappings for the DeutschWerk SAP extract, execute a data load via EPM Automate, diagnose and fix an unmapped member error, and confirm successful load by reviewing SC status and spot-checking data in a form.

🧰 Prerequisites

Service Administrator role · Data Integration configured in your FCCS sandbox · Files: DeutschWerk_Jan25.csv, AsiaLink_Jan25.dat, BritEdge_Jan25.dat in your local working directory · EPM Automate installed and authenticated

1️⃣ Exercise 1 — Define Import Format for DeutschWerk SAP CSV
Estimated time: 20 minutes
  1. 01 Navigate to Navigator → Data Exchange → Data Integration. Click Actions → Create Import Format.
  2. 02 Name: DeutschWerk_SAP_CSV. File type: Delimited — Comma. Header rows to skip: 1.
  3. 03 Map columns: Col 1 → Account, Col 2 → Cost Centre (custom attr), Col 3 → Amount, Col 4 → Currency. Entity and Period will be set at the Location level.
  4. 04 Set Amount multiplier to 1 (SAP exports debit-positive, credit-negative — matching FCCS convention). Save.
  5. 05 Create a Location named DeutschWerk_Actual. Link it to: Import Format = DeutschWerk_SAP_CSV, Entity = DeutschWerk, Category = Actual.
✅ Expected Outcome

Import Format and Location appear in the Data Integration setup table. The Location shows Status = Active and Target Application = your FCCS instance.

2️⃣ Exercise 2 — Configure Account Mappings
Estimated time: 25 minutes
  1. 01 Open Location DeutschWerk_Actual → Mappings tab. Select dimension: Account.
  2. 02 Add an Explicit mapping: Source = 491000 → Target = OtherIncome. This resolves the DeutschWerk SAP unmapped member error.
  3. 03 Add a Between mapping: Source from 400000 to 499999 → Target = Revenue. This covers all SAP revenue GL codes.
  4. 04 Add a Between mapping: Source 500000–599999 → Target = COGS.
  5. 05 Add a Like mapping: Source = IC_* → Target = ICSales. This catches all SAP intercompany codes.
  6. 06 Switch to dimension Entity. Add Explicit: Source = DE01 → Target = DeutschWerk. Save all mappings.
⚠️ Verify Priority Order

Account 491000 would also match the Between rule (400000–499999). Confirm that the Explicit rule 491000 → OtherIncome takes precedence. In the mapping list, Explicit rules are processed first regardless of row order. You can verify by clicking Validate and checking which target member is shown for source value 491000.

3️⃣ Exercise 3 — Run the Full Pipeline via EPM Automate
Estimated time: 30 minutes
  1. 01 Open terminal. Run: epmautomate login admin@globalmerge.com [password] [url]
  2. 02 Upload the source file: epmautomate uploadFile "DeutschWerk_Jan25.csv" inbox/DeutschWerk_Jan25.csv
  3. 03 Run the data load rule: epmautomate runDataRule "DeutschWerk_Actual_Monthly" Jan 2025 Jan 2025 REPLACE
  4. 04 Monitor the job in Jobs → Process Details in the FCCS UI. Wait for status Completed.
  5. 05 If status = Error, download the log: epmautomate downloadFile "outbox/logs/DeutschWerk_Jan25_error.log". Review the unmapped member list and add missing mappings.
  6. 06 After successful load, navigate to Consolidation → System Check. Verify DeutschWerk for Actual / Jan 2025 shows status 4 (No Data) → after load it should move to 1 (OK) (not yet consolidated).
  7. 07 Open a data form for DeutschWerk. Spot-check: Revenue account should show EUR balance near the source file's GE revenue total. Confirm ICSales has partner ICP_BritEdge tagged.
🏆 Lab Challenge — Load All Four Entities

Extend the EPM Automate script to load all four GlobalMerge entities in sequence: BritEdge (.dat), DeutschWerk (.csv), AsiaLink (.dat), NovaTech (equity journal entry only). After all four load successfully, run consolidation for the group and confirm SC status moves to 2 (Consolidated) for GlobalMerge at the group level.

📝 Exam Preparation
Data Integration questions mapped to Oracle FCCS Certification objectives

Data Integration and Data Management are high-weight topics in the Oracle FCCS Implementation Specialist exam. Expect 10–15% of questions to cover load methods, mapping priority, EPM Automate syntax, error codes, and load mode behaviour.

Question 1 of 8 · Mapping Priority
A Data Management Account mapping table contains the following rules for DeutschWerk: (1) Explicit: 491000 → OtherIncome, (2) Between: 400000–499999 → Revenue, (3) Like: 49* → MiscIncome. When source account 491000 is processed, which target member does Data Management use?
  • AOtherIncome — the Explicit rule takes highest priority.
  • BRevenue — the Between rule was created before the Like rule.
  • CMiscIncome — the Like rule is most specific for 49* pattern.
  • DData Management returns an error because multiple rules match.
Correct: A. Data Management applies mappings in priority order: Explicit → In → Between → Like. An Explicit rule always wins over Between or Like regardless of creation order. Account 491000 will be mapped to OtherIncome.
Question 2 of 8 · Load Mode
The DeutschWerk January 2025 data was loaded in REPLACE mode. The finance team then discovers a posting error and needs to load a corrected file. Which load mode should be used for the corrected file?
  • AREPLACE — it will overwrite the erroneous data with the corrected values.
  • BACCUMULATE — it will add the correction to the existing balance.
  • CSUBTRACT — it will remove the original load before adding the correction.
  • DYou must manually zero out all cells before loading the corrected file.
Correct: A. REPLACE mode clears the existing data for the entity/scenario/period combination and loads the new file from scratch. It is the safest correction method when a full restated trial balance is available. ACCUMULATE would double-count; SUBTRACT is used only to reverse a specific batch.
Question 3 of 8 · EPM Automate
Which EPM Automate command uploads a local file to the FCCS application's Inbox folder?
  • Aepmautomate importData "BritEdge_Jan25.dat" inbox
  • Bepmautomate uploadFile "BritEdge_Jan25.dat" inbox/BritEdge_Jan25.dat
  • Cepmautomate sendFile "BritEdge_Jan25.dat" --target inbox
  • Depmautomate pushData "inbox/BritEdge_Jan25.dat"
Correct: B. The correct EPM Automate command is uploadFile [localFile] [serverPath]. The server path must include the inbox/ prefix. The other options use incorrect command names that do not exist in EPM Automate.
Question 4 of 8 · Integration Methods
NovaTech Inc uses the Equity Method (PCON = 0, POWN = 30%). The consolidation team asks what data should be loaded into FCCS for NovaTech each month. Which is the correct answer?
  • ALoad NovaTech's full trial balance — FCCS will automatically apply 30% weighting.
  • BLoad 30% of each NovaTech balance line by line.
  • CLoad only the Investment in NovaTech balance and GlobalMerge's share of NovaTech's net equity (30%).
  • DNo data load is needed; FCCS calculates equity pickup automatically from metadata.
Correct: C. Under the Equity Method (PCON = 0), FCCS does not aggregate NovaTech's trial balance line by line. The only data needed is the Investment account balance (what GlobalMerge paid / book value) and the equity pickup amount (30% of NovaTech's net equity). FCCS does not auto-calculate this from metadata alone — it must be provided as input.
Question 5 of 8 · Data Management Components
An administrator needs to configure Data Management to load BritEdge's Oracle ERP Cloud trial balance. They have already created an Import Format. What must be created next before a Data Load Rule can be executed?
  • AA Mapping Table and a Consolidation Rule.
  • BA Location that links the Import Format to the target entity and category.
  • CAn Exchange Rate table for GBP to USD translation.
  • DA Smart View data form pointing to the BritEdge entity.
Correct: B. The Data Management setup sequence is: Import Format → Location → Mappings → Data Load Rule. The Location is the critical link that ties the Import Format to a specific target entity and scenario (category). Without a Location, you cannot create or run a Data Load Rule.
Question 6 of 8 · File Format
When loading data via a .dat file directly into FCCS, which dimension column must be included if the account being loaded has IsICP = Y?
  • AThe Currency column — FCCS needs to know the local currency for ICP transactions.
  • BThe ICP column — every ICP-enabled account row must specify a partner (or ICP_None for third-party).
  • CThe Movement column — ICP transactions always affect the cash flow statement.
  • DThe View column — ICP transactions must specify YTD or Periodic view to resolve correctly.
Correct: B. For any account with IsICP = Y, every data row must include a valid ICP dimension value — either a specific partner entity (e.g., ICP_DeutschWerk) or ICP_None for external transactions. Omitting the ICP column for an ICP-enabled account causes a load error.
Question 7 of 8 · Error Resolution
An EPM Automate runDataRule command completes with status PARTIAL. What does this mean, and what should the administrator do next?
  • AThe load was successful for all rows; PARTIAL is the normal success status for batch loads.
  • BThe load failed completely; all data must be reloaded after fixing the root cause.
  • CSome rows loaded successfully; unmapped or invalid rows were written to an error file in the Outbox. Review the error file, fix mappings, and re-run.
  • DThe load is still running; PARTIAL means the job is 50% complete and the administrator should wait.
Correct: C. PARTIAL status means Data Management loaded the rows it could map successfully and wrote the problem rows to an error log in the Outbox. The administrator should download the error file (epmautomate downloadFile "outbox/logs/..."), identify unmapped members, add missing mapping rules, and re-run the data load rule using REPLACE mode (which will include the previously-failed rows).
Question 8 of 8 · AsiaLink Proportional Load
AsiaLink Pte Ltd (50% JV, SGD) loads its full SGD trial balance into FCCS. When the administrator views the GlobalMerge parent entity after consolidation, they notice only SGD 1,000,000 of AsiaLink's SGD 2,000,000 Revenue appears (translated to USD). Is this correct, and why?
  • ANo — this is a data load error. The full SGD 2,000,000 should consolidate into the parent.
  • BYes — FCCS applies PCON% = 50% during consolidation, so only 50% of AsiaLink's data flows to the parent.
  • CNo — the SGD-to-USD translation rate is wrong; the full amount should appear in USD equivalent.
  • DYes — but only because the mapping rules cut the amount in half during the data load.
Correct: B. You always load the full trial balance for an entity regardless of its ownership percentage. FCCS applies the PCON% property during the consolidation calculation — not during the data load. Loading only 50% would be incorrect and would require recalculating source data outside FCCS. The proportional weighting is the engine's job, not the loader's.