.png)
Oracle EPM Cloud Integration Guide
Integrate Oracle EPM Cloud with enterprise systems through REST APIs, asynchronous jobs, file exchange, and secure scheduled workflows.
Oracle EPM Cloud integration options at a glance
Oracle EPM Cloud provides REST APIs for administration, metadata, data integration, jobs, calculations, and application-specific operations. Its asynchronous processing model supports data loads, exports, metadata changes, and business rules through jobs that can be monitored by identifier. EPM Cloud also exchanges import files, export files, error files, snapshots, reports, and other artifacts through inbox and outbox locations. Authentication can use permitted Basic Authentication or OAuth 2.0 with Oracle identity and EPM permissions. Martini can schedule workflows, consume REST APIs, upload and download files, map multidimensional data, poll job status, and expose APIs for upstream planning or finance applications.
| Integration point | Supported by Oracle EPM Cloud? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Oracle EPM Cloud REST APIs support administration, metadata, data integration, jobs, files, and application-specific operations. The available resources depend on the subscribed EPM application. | Martini can consume REST APIs from workflows, map JSON responses and requests, apply business rules, and route results to other systems. |
| Bulk, asynchronous, and batch processing | Yes | EPM Cloud uses jobs for data loads, exports, calculations, business rules, metadata operations, and Data Management processes. Operations commonly return a job identifier for later polling. | Martini can submit a job, persist its identifier, poll with bounded retries and backoff, retrieve results, and distinguish success, warning, and failure states. |
| File and artifact exchange | Yes | EPM inbox and outbox locations support import files, export files, error files, snapshots, reports, and other application artifacts. | Martini can generate, upload, list, download, archive, and transform files within workflows, subject to the specific EPM operation and format. |
| Authentication | Yes | Authentication can use permitted Basic Authentication or OAuth 2.0 through Oracle identity services, with EPM roles, groups, application permissions, and scoped access controlling authorization. | Martini can use secured environment configuration and secrets for credentials, tokens, endpoints, and separate deployment environments. |
| Scheduled synchronization | Yes | Recurring EPM loads, exports, reconciliation processes, and job checks can be initiated through scheduled workflows or EPM scheduling features. | Martini can trigger workflows on a schedule, coordinate multi-step processing, and record checkpoints and outcomes. |
| Webhooks and outbound callbacks | Not confirmed | No general Oracle EPM Cloud webhook framework for business events was confirmed. A specific EPM application or related Oracle service may document a callback for a particular operation, but this requires validation. | Martini can receive webhook-style requests when a confirmed source endpoint exists, but EPM integrations should otherwise use schedules, APIs, polling, or files. |
| GraphQL APIs | Not confirmed | No official Oracle EPM Cloud GraphQL API was identified in the reviewed documentation. | Martini should use the confirmed REST and file-based mechanisms for EPM Cloud rather than assuming GraphQL availability. |
| SOAP APIs | Not confirmed | SOAP services exist elsewhere in the Oracle portfolio, but no current general-purpose Oracle EPM Cloud SOAP API was confirmed. | Martini can consume SOAP services when a specific supported endpoint is documented, but this is not the recommended EPM Cloud assumption. |
| Database access | No | A direct public connection to the managed Oracle EPM Cloud application database was not confirmed and should not be used as the integration boundary. | Martini can work with supported APIs, files, reports, and external databases, but should not connect directly to the managed EPM application database. |
How Oracle EPM Cloud exposes data and business events
Oracle EPM Cloud REST APIs
Oracle EPM Cloud documents REST APIs for administration, metadata, data integration, jobs, files, and application-specific operations. The exact resources and payloads vary across Planning, Financial Consolidation and Close, Account Reconciliation, Enterprise Data Management, and other subscribed applications.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the environment, calls the relevant REST resource, transforms the JSON response or request, applies validation and business rules, and sends the result to the next system or processing stage.
Implementation sequence
Oracle EPM Cloud asynchronous jobs
Many EPM operations are asynchronous, including data loads, exports, calculations, business rules, metadata operations, and Data Management processes. The initial response commonly provides a job identifier rather than a completed result.
Martini implementation pattern
Martini implementation pattern: the workflow submits the operation, stores the EPM job identifier, waits between status checks, stops after a bounded timeout, and retrieves job details or error files for downstream reconciliation.
Implementation sequence
Oracle EPM Cloud file exchange
EPM Cloud uses inbox and outbox locations for import files, export files, error files, snapshots, reports, and other artifacts. File exchange is relevant for high-volume planning data, metadata, journals, and scheduled reporting.
Martini implementation pattern
Martini implementation pattern: a workflow retrieves source data, generates an EPM-compatible file, uploads it to the appropriate location, initiates or monitors the related operation, and archives the input and output artifacts.
Implementation sequence
Oracle EPM Cloud scheduled synchronization
No general EPM Cloud business-event webhook framework was confirmed. Recurring synchronization is therefore commonly initiated by schedules, external API calls, file delivery, EPM scheduling features, or job polling.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow retrieves incremental or batch data, processes it in controlled stages, records checkpoints and batch identifiers, and alerts or routes exceptions without relying on unconfirmed EPM callbacks.
Implementation sequence
Common Oracle EPM Cloud integration patterns
Pattern 1: Load ERP balances into EPM
When to use this pattern
Use this pattern when general ledger balances, account structures, entities, periods, or currencies must be transferred from a finance system into Planning or Financial Consolidation and Close. It supports scheduled close and planning cycles while preserving a clear batch and job trail.
Integration direction
Example Mapping
| Oracle EPM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| LedgerAccount | account | Account member |
| LegalEntity | entity | Entity member |
| AccountingPeriod | period | Period member |
| BalanceAmount | amount | Data value |
Martini implementation pattern
Martini retrieves the source batch, validates that EPM members exist, applies sign, currency, precision, and period rules, creates an import file or REST request, submits the EPM job, and polls for completion. Failed validation, transport errors, and EPM rejection files are handled separately, with deterministic batch identifiers preventing duplicate loads.
Martini capabilities used
- scheduled workflows
- API consumption
- file generation and processing
- data mapping
- business rules
- asynchronous orchestration
- error handling
Pattern 2: Synchronize EPM dimensions and members
When to use this pattern
Use this pattern when approved account, cost-center, product, organization, or legal-entity changes must be propagated from a master-data or source finance system into EPM. It is useful before loading transactional or planning data that depends on the updated hierarchy.
Integration direction
Example Mapping
| Oracle EPM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| CostCenterCode | memberCode | Member name |
| ParentCostCenter | parentMember | Parent member |
| HierarchyStatus | memberStatus | Member property |
| EffectiveDate | effectiveFrom | Metadata load control |
Martini implementation pattern
Martini receives approved changes, normalizes hierarchy and member properties, validates parent-child relationships, and submits metadata updates or a metadata import file. The workflow versions mappings, records the EPM job ID, and quarantines invalid hierarchy changes rather than mixing them with valid updates.
Martini capabilities used
- workflow orchestration
- data mapping
- validation
- business rules
- REST API consumption
- file processing
- error routing
Pattern 3: Distribute EPM close exceptions
When to use this pattern
Use this pattern when EPM job failures, reconciliation exceptions, journal issues, or close-process results need to reach operational teams. It separates finance processing from task management while retaining the EPM execution reference.
Integration direction
Example Mapping
| Oracle EPM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| JobId | sourceExecutionId | Correlation ID |
| ErrorDescription | exceptionMessage | Description |
| ApplicationName | sourceApplication | Service |
| JobStatus | exceptionStatus | State or priority |
Martini implementation pattern
Martini retrieves job details or error files, classifies the exception by severity and ownership, and creates or updates a ServiceNow task. Deterministic keys prevent duplicate tasks when a status is polled more than once, while failed downstream writes are retried and logged for reconciliation.
Martini capabilities used
- REST API consumption
- scheduled workflows
- data transformation
- business rules
- idempotency controls
- retry handling
- monitoring
Pattern 4: Orchestrate planning input through an API
When to use this pattern
Use this pattern when a budgeting portal or business application needs a controlled API for submitting planning inputs without directly managing EPM credentials, file formats, or job polling.
Integration direction
Example Mapping
| Oracle EPM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| budgetLine.account | account | Account member |
| budgetLine.entity | entity | Entity member |
| budgetLine.period | period | Period member |
| budgetLine.value | amount | Data value |
Martini implementation pattern
Martini exposes a REST API, validates dimensions and members, transforms the request into an EPM-compatible payload or file, submits the relevant job, and returns a correlation identifier. The workflow applies authorization and validation rules, records the job state, and exposes a controlled status response rather than passing through raw EPM errors.
Martini capabilities used
- API exposure
- authentication and authorization
- workflow orchestration
- data mapping
- validation
- asynchronous processing
- error handling
Applications commonly integrated with Oracle EPM Cloud
Oracle EPM Cloud is commonly positioned alongside finance, workforce, operational planning, and enterprise workflow applications. These integrations are normally implemented through each system’s supported APIs, files, or middleware rather than through an assumed dedicated Oracle EPM Cloud connector.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Oracle ERP Cloud | Transfer general ledger balances, chart of accounts, legal entities, and financial data into EPM for planning, consolidation, and reporting. | Oracle ERP Cloud → Martini → Oracle EPM Cloud | A scheduled Martini workflow retrieves finance data, maps accounts, entities, periods, currencies, and values to an EPM import structure, uploads the file or invokes the relevant REST operation, then monitors the EPM job and routes error output. |
| Oracle HCM Cloud | Provide workforce, employee, position, compensation, and organization data for workforce planning and budgeting. | Oracle HCM Cloud → Martini → Oracle EPM Cloud | Martini consumes approved workforce data, validates required EPM dimension members, transforms the payload into a multidimensional import format, and submits the resulting load or job with bounded polling. |
| Oracle NetSuite | Consolidate or plan financial data from NetSuite environments alongside other entities and business units. | Oracle NetSuite → Martini → Oracle EPM Cloud | Martini retrieves NetSuite financial data through supported interfaces or files, applies account and entity mappings, creates an EPM-compatible batch, and reconciles accepted and rejected rows after job completion. |
| Salesforce | Use pipeline, bookings, customer, or account information in revenue planning and operational forecasting. | Salesforce → Martini → Oracle EPM Cloud | A Martini workflow retrieves selected Salesforce data, applies business rules and dimensional enrichment, formats planning inputs for EPM, and records the EPM job identifier and outcome. |
| Workday | Supply workforce and organizational data for headcount, compensation, and workforce planning. | Workday → Martini → Oracle EPM Cloud | Martini receives or retrieves approved Workday data, validates organization and employee-related members, maps values to EPM dimensions, and processes the load asynchronously with retry and reconciliation controls. |
| SAP S/4HANA | Load financial, management accounting, and master-data information into EPM for consolidation, planning, and reporting. | SAP S/4HANA → Martini → Oracle EPM Cloud | Martini consumes SAP APIs or controlled files, transforms source financial structures into EPM import files or REST requests, submits the operation, and separates transport failures from EPM validation failures. |
| ServiceNow | Publish close, reconciliation, planning, or data-quality exceptions as operational tasks and track remediation. | Oracle EPM Cloud → Martini → ServiceNow | Martini retrieves EPM job results or exception data, applies severity and ownership rules, and creates or updates ServiceNow tasks while retaining the EPM batch or job identifier for traceability. |
| Jira | Track implementation, close-process, and data-quality issues identified by EPM workflows. | Oracle EPM Cloud → Martini → Jira | A Martini workflow converts EPM failures or validation exceptions into Jira issues, maps project and priority fields, prevents duplicate issue creation with deterministic keys, and records the resulting issue reference. |
How to build a Oracle EPM Cloud integration in Martini
Objective
Establish the EPM Cloud endpoint and authentication model for each environment without embedding credentials in workflow logic.
Instructions in Martini
- Confirm the application-specific EPM endpoint and permitted Basic Authentication or OAuth 2.0 configuration.
- Create a least-privilege integration identity with required EPM roles and application permissions.
- Store credentials, tokens, client secrets, and environment-specific values in Martini secrets or secure configuration.
Objective
Select a trigger that matches the EPM process and avoids reliance on unconfirmed business-event webhooks.
Instructions in Martini
- Use a scheduler for recurring loads, exports, reconciliations, or job checks.
- Expose a Martini REST API when an upstream portal or application initiates the process.
- Use file arrival or an external orchestration call where the source process is batch-oriented.
Objective
Bring source data, EPM metadata, job results, or artifacts into the workflow in a controlled batch.
Instructions in Martini
- Consume the relevant REST resource or retrieve an EPM inbox or outbox artifact.
- Use filters, pagination, incremental checkpoints, or controlled file batches where supported.
- Capture source batch IDs, file names, job IDs, and timestamps for traceability.
Objective
Coordinate API calls, file exchange, asynchronous EPM operations, and downstream actions as one maintainable process.
Instructions in Martini
- Separate submission, polling, result retrieval, and downstream publishing into clear workflow stages.
- Persist the EPM job identifier and correlation information before polling.
- Use bounded delays, maximum attempts, and an overall timeout for asynchronous operations.
Objective
Convert source structures into EPM dimensions, members, data values, metadata files, or application-specific request formats.
Instructions in Martini
- Maintain explicit mappings for Account, Entity, Scenario, Version, Period, Year, Currency, and custom dimensions.
- Apply sign, precision, date, decimal, encoding, hierarchy, and member-property rules.
- Generate and validate EPM-compatible files when file exchange is more appropriate than individual API requests.
Objective
Validate data and control whether a batch should be submitted, rejected, or routed for review.
Instructions in Martini
- Validate that required members, parents, periods, currencies, and application contexts exist.
- Check source transaction IDs, batch IDs, and deterministic file names for duplicate processing.
- Route validation failures separately from authentication, authorization, transport, and EPM job failures.
Common Oracle EPM Cloud data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Applications | Represent EPM applications and their configuration for administration and environment-aware processing. | Oracle ERP Cloud, Oracle HCM Cloud, administration repositories, deployment records | Martini retrieves application information through REST calls and uses it to select environment-specific mappings, endpoints, or workflow branches. |
| Cubes | Represent multidimensional planning, Essbase, calculation, and reporting structures. | Data warehouses, planning portals, reporting applications | Martini treats cube context as part of the data model and preserves dimensional meaning when transforming values or generating import files. |
| Dimensions and Members | Represent Account, Entity, Scenario, Version, Period, Year, Currency, custom dimensions, and their hierarchy members. | Master-data systems, Oracle ERP Cloud, Oracle HCM Cloud, SAP S/4HANA | Martini validates member identifiers and properties, applies explicit hierarchy mappings, and submits metadata or data operations through REST or files. |
| Forms | Represent Planning data-entry, review, and submission structures. | Planning portals, budgeting applications, reporting workflows | Martini can use form-related API resources where available and transform upstream planning inputs into the required EPM structure. |
| Jobs | Represent asynchronous data loads, imports, exports, calculations, business rules, and metadata operations. | Monitoring platforms, ServiceNow, Jira, operational dashboards | Martini stores job identifiers and correlation data, polls status with bounded retries, retrieves details or error files, and publishes outcomes. |
| Data files and artifacts | Represent inbox and outbox import files, export files, error files, snapshots, reports, and related artifacts. | File repositories, data warehouses, Oracle ERP Cloud, ServiceNow | Martini creates or consumes files, validates format and encoding, applies controlled naming and archiving, and routes successful or rejected artifacts. |
Authentication and security considerations
Authentication and authorization
Oracle EPM Cloud REST APIs can use permitted Basic Authentication or OAuth 2.0 through Oracle identity services. Access remains controlled by identity-domain users, groups, roles, application permissions, and any applicable OAuth scopes.
Secure Martini configuration
Store credentials, client secrets, refresh tokens, access tokens, and environment-specific endpoints in Martini secrets or secured configuration. Use separate integration identities and configurations for development, test, and production.
- Apply least-privilege EPM roles and application permissions.
- Confirm the authentication method enabled for the specific EPM environment.
- Protect API exposure with appropriate Martini authentication and authorization controls.
Operational considerations for Oracle EPM Cloud integrations
Asynchronous processing
Many EPM operations return a job identifier and complete later. Persist the identifier, poll with bounded retries and backoff, apply an overall timeout, and retrieve job details or error files.
Data and throughput
Use pagination where an EPM resource supports it, process large files in controlled batches, and prefer bulk imports over one request per cell or member. Confirm service-specific throttling behavior and avoid high-frequency polling.
Idempotency and reconciliation
Use source transaction IDs, batch IDs, deterministic file names, and persisted job identifiers to prevent duplicate processing. Reconcile source rows, accepted rows, rejected rows, job results, and downstream writes.
Application change and testing
Dimensions, members, forms, cubes, business rules, and custom properties can differ between EPM environments. Version mappings and import templates, validate members before loading, and test application changes before production deployment.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than API calls
Scripts often combine authentication, file handling, polling, mapping, retries, and reporting in code that is difficult to govern. Martini represents these concerns as reusable workflows and APIs with explicit stages and operational controls.
Handle EPM’s asynchronous model
Martini can coordinate submission, job polling, output retrieval, error routing, and downstream reconciliation while preserving correlation identifiers and bounded retry behavior.
Adapt to multidimensional data
Martini provides mapping, transformation, validation, and business-rule capabilities for EPM dimensions, members, files, and application-specific payloads. It can also expose a controlled API façade so upstream systems do not need direct EPM credentials or implementation details.
Maintainable enterprise delivery
Centralized secrets, environment configuration, workflow logging, reusable services, and deployment practices provide a more maintainable integration boundary than multiple point-to-point scripts.
Frequently asked questions
Oracle EPM Cloud can be integrated through its REST APIs, asynchronous jobs, inbox and outbox file exchange, supported authentication methods, and scheduled or externally initiated workflows. The exact resources depend on the EPM application, such as Planning, Financial Consolidation and Close, Account Reconciliation, or Enterprise Data Management.
Yes. Martini can consume Oracle EPM Cloud REST APIs, upload and download EPM files, submit and monitor asynchronous jobs, transform multidimensional data, and expose APIs for upstream planning or finance applications. No native Martini Oracle EPM Cloud connector is documented in the supplied materials.
No. A dedicated Oracle EPM Cloud connector is not required. Martini can use Oracle EPM Cloud’s confirmed REST APIs, file exchange mechanisms, authentication methods, scheduled processing, and asynchronous job interfaces.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Oracle EPM Cloud. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Oracle, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment model.
REST APIs are the primary integration method for administration, metadata, data, jobs, and application-specific operations. Bulk and asynchronous processing, EPM inbox and outbox files, and scheduled workflows are also important for larger loads and recurring processes. GraphQL and a general current SOAP API were not confirmed for EPM Cloud.
A general Oracle EPM Cloud webhook or business-event callback framework was not confirmed. Safer documented patterns use scheduled Martini workflows, external API calls, file delivery, EPM scheduling features, and polling of EPM job status. Any application-specific callback should be validated against that service’s documentation.
Martini can retrieve or receive source data, map it explicitly to EPM dimensions and members, validate hierarchies and application-specific properties, and submit REST requests or import files. Synchronization should preserve batch identifiers, job IDs, checkpoints, dimensional context, and reconciliation results rather than treating EPM data as a flat table.
Martini can capture HTTP responses, Oracle error details, EPM job states, and generated error files, then apply bounded retries and backoff. Deterministic batch IDs, source transaction IDs, file names, and persisted job identifiers help avoid duplicate loads after timeouts. Validation, authorization, transport, and EPM processing failures can be routed separately.
Related Martini documentation
Workflows
Build a maintainable Oracle EPM Cloud integration
Use Martini to connect Oracle EPM Cloud REST APIs and file processes with finance, planning, workforce, and operational applications through secure, observable workflows.