The integration lifeline
A profitability model without data is just a hypothesis. Data Integration is how EPCM connects to the world - loading actuals from Oracle ERP Cloud, importing cost drivers from flat files, orchestrating multi-step pipelines, and writing allocated costs back to the General Ledger. This hall teaches you how to make your model production-ready.
What is Data Integration in EPCM?
Data Integration is the bridge between your source systems and the EPCM profitability model. Without it, you're allocating imaginary numbers.
EPCM can be registered as both a source and a target in Oracle's Data Integration framework. This means you can pull actuals into EPCM from Oracle ERP Cloud, Oracle Financials Cloud, or flat files - and push allocated results out to the General Ledger or downstream reporting systems. The result is a closed-loop profitability process: actuals in, allocations run, results written back.
For NovaPrism Group, the integration challenge is clear: $134M in indirect costs sitting in four corporate cost pools (IT $52M, Facilities $38M, Finance $28M, HR $16M) need to flow from the ERP General Ledger into EPCM, get allocated across 60 client engagements, and then the per-engagement profitability needs to be visible back in the ERP for executive dashboards.
Integration types - direct vs file-based
Choose direct integration when you have Oracle ERP Cloud. Choose file-based when you don't - or when you need maximum control over the data transformation.
Writeback - closing the loop
Writeback enables allocated costs to flow from EPCM back to Oracle ERP Cloud General Ledger as journal entries - completing the profitability cycle.
When NovaPrism's $52M IT allocation runs in EPCM, the result is a detailed breakdown showing how much IT cost each of the 60 engagements consumed. That's useful for management reporting - but the real value comes when those allocated costs appear in the ERP system where executives can see them alongside revenue and margin in their standard financial reports.
Writeback creates journal entries in Oracle ERP Cloud's General Ledger. The process extracts EPCM allocation results, maps them to GL account codes and legal entity structures, and posts journals that offset the original cost pool while crediting the receiving cost objects. The result: your ERP now shows fully-loaded costs at the engagement level.
| Writeback Method | Target | Use Case |
|---|---|---|
| Oracle ERP Cloud Writeback | General Ledger journals | Standard writeback for Oracle Fusion Cloud customers. Creates actual or budget journals. |
| EPM Integration Agent | On-premises databases | Writeback to on-premises Oracle DB, SQL Server, or other databases via the EPM Agent. |
| File Export | CSV/TXT files | Export allocation results to files for manual upload or third-party ETL processing. |
| REST API Export | External systems | Programmatic export for custom integrations, data warehouses, or reporting systems. |
Registering EPCM as source and target
Before you can integrate data, you must register the EPCM application in Data Integration. The registration type depends on where the data is coming from or going to.
| Registration Type | When to Use | Configuration |
|---|---|---|
| Local Application | Integrating within the same EPM instance (e.g., EPCM to same-instance FCCS) | Select the EPCM application directly from the instance application list. |
| Cloud EPM Application | Pulling from a separate EPM instance | Configure a source connection specifying the remote instance URL and credentials. |
| Oracle ERP Cloud | Direct integration with Oracle Fusion ERP | Configure ERP Cloud connection with credentials and ledger/chart of accounts mapping. |
/* Data Integration registration path */ Navigator > Data Integration > Actions > Applications > Register > EPM Cloud Application > Application: [Your EPCM App Name] > Application Type: Enterprise Profitability and Cost Management > Category: Planning /* Note: EPCM is categorised under Planning */ > Prefix: "EPCM_" /* Optional naming prefix */
Member mapping - source to target
Mapping transforms source system values (GL account codes, cost centre IDs) into EPCM dimension members. Get this wrong and your data lands in the wrong places.
NovaPrism's GL uses account code 6100-IT-CORP for corporate IT costs. EPCM's Account dimension has a member called IT_Cost_Pool. The mapping rule transforms the source value to the target member. Mappings can be explicit (one-to-one), like (pattern matching), between (range), or multi-dimensional (combining multiple source columns).
6100-IT-CORP -> Target: IT_Cost_PoolUse when source values have a direct 1:1 relationship with EPCM members. Most common for account and entity mappings.
61* -> Target: IT_Cost_PoolUse when multiple source values should map to the same target. The asterisk (*) matches any characters. Good for account ranges.
6100 to 6199 -> Target: IT_Cost_PoolUse for numeric account codes where a range of values should map to a single target. Cleaner than multiple explicit mappings.
Account=6100 + CostCentre=CORP -> Target: IT_Cost_PoolUse when the target member depends on multiple source values combined. Essential for complex GL structures.
6150-IT-CLOUD but forgets to add a mapping, those costs won't load. Always review the integration error log after each run and add mappings for new source values before they accumulate.Smart View integration
Oracle Smart View for Office provides Excel-based data entry, retrieval, and ad-hoc analysis for EPCM data. It's how power users interact with the model without using the web interface.
Smart View connects to EPCM via the EPM Cloud connection URL. Users can retrieve allocation results into Excel for analysis, submit driver data (headcount, square footage) directly from spreadsheets, and refresh forms to see the latest calculated values. For NovaPrism, the finance team uses Smart View to submit monthly driver updates for all 60 engagements - much faster than web form entry.
/* EPM Cloud Smart View connection URL */ https://[instance].epm.[datacenter].oraclecloud.com/epmcloud/SmartViewProviders /* Example for US datacenter */ https://novaprism-epm.epm.us6.oraclecloud.com/epmcloud/SmartViewProviders /* After connection, select: */ > EPM Cloud > Enterprise Profitability and Cost Management > [Application Name] > [Cube/Database]
The Pipeline - orchestrating end-to-end integration
A Pipeline chains multiple jobs into a single automated process - from data extraction through transformation, loading, calculation, and writeback. It's the backbone of production EPCM deployments.
NovaPrism's monthly pipeline runs on the 3rd business day of each month. It extracts the prior month's GL actuals, maps them to EPCM dimensions, loads into the Actuals scenario, executes all five allocation rulesets (seq:10 through seq:50), validates balances, and writes allocated costs back to the ERP. Total runtime: ~12 minutes for $134M across 60 engagements.
Pipeline job types for EPCM
Not all Pipeline job types are available for EPCM. Here are the four platform job types supported, plus key integration jobs.
| Job Type | Purpose | EPCM Support |
|---|---|---|
| Integration | Load data from source to EPCM target | Supported |
| Clear Cube | Clear data from specific POV before load | Supported |
| Export Data | Export EPCM data to file or target system | Supported |
| EPM Platform Job | Execute platform-level operations | 4 Types Only |
| Business Rule (Calc Mgr) | Run Calculation Manager business rules | Via Pipeline |
| EPCM Rules/Rulesets | Run native EPCM rules and rulesets | Not Supported |
Designing NovaPrism's Pipeline
A well-designed Pipeline handles errors gracefully, logs each step, and can be restarted from the point of failure.
Lab: Create a file-based integration for driver data
NovaPrism's driver data (headcount, IT tickets) comes from a monthly CSV export. In this lab, you'll create a Data Integration job to load that file into EPCM.
NP_Drivers_M01.csv containing: Entity, Account, Driver_Value columns. Preview the data to confirm format.Entity,Account,Driver_Value DS,Headcount,340 DS,IT_Tickets,1240 DS,SqFt,12000 IS,Headcount,520 IS,IT_Tickets,2890 IS,SqFt,18500 CL,Headcount,85 CL,IT_Tickets,410 CL,SqFt,3200 ES,Headcount,55 ES,IT_Tickets,0 ES,SqFt,2100
Lab: Configure ERP Cloud writeback
After allocations run, write the results back to Oracle ERP Cloud General Ledger as journal entries.
Data Integration Quiz — 8 Questions
Test your understanding of EPCM Data Integration concepts. These questions reflect topics covered in the 1Z0-1082-25 exam.
What to remember for 1Z0-1082-25
| Topic | Key Point | Exam Tip |
|---|---|---|
| EPCM Registration | EPCM can be both source and target | Know that EPCM registers under "Planning" category despite being a separate application. |
| Integration Limitations | EPCM does not integrate with EPM Planning or Projects | This is a common trap question. EPCM integrates with ERP Cloud and other EPM processes except Planning. |
| Pipeline EPCM Rules | Native EPCM rules cannot be called directly from Pipeline | Only Calculation Manager rules work in Pipeline. Use Groovy to call EPCM REST APIs as workaround. |
| Writeback | Creates GL journal entries | Understand that writeback creates actual journal entries, not just data exports. |
| Mapping Types | Explicit, Like, Between, Multi-Dimensional | Know when to use each: Like = wildcards (*), Between = numeric ranges, Explicit = exact match. |
| copyDataByPointOfView | EPCM command — not copyPov | copyPov is Planning. EPCM uses copyDataByPointOfView. Tested when candidates work across both products. |
| refreshCube | After metadata import only — not after data loads | Common exam trap. Running refreshCube after every data load wastes time — only metadata changes require it. |
| Smart View submission | Business users submit driver data from Excel | Self-service path for Finance Controllers and analysts — no Service Administrator involvement needed. |