Ellipse Gradient for Header

Prophix Integration Guide

Prophix integrates financial planning and performance data with enterprise systems through tenant-specific APIs, batch processes, and structured file exchange.

Prophix integration options at a glance

Prophix supports enterprise data exchange for planning, budgeting, forecasting, reporting, and consolidation workflows. REST capabilities should be confirmed for the specific Prophix One tenant, including available endpoints and authentication requirements. Batch and asynchronous processing are relevant for large financial loads, while CSV and Excel exchange can support planning inputs and reporting workflows when configured by the customer. General-purpose webhooks and outbound callbacks are not confirmed, so scheduled polling is usually the safer event alternative. Martini can consume documented Prophix interfaces, schedule workflows, transform dimensions and financial values, validate batches, expose controlled APIs, and write results to ERP, HCM, CRM, warehouse, or database targets.

Integration pointSupported by Prophix?Common use casesHow Martini supports it
REST APIsLimitedProphix provides integration capabilities for exchanging information with external applications, but the available REST endpoint catalog and authentication model must be confirmed for the customer’s Prophix One tenant.Martini can consume documented Prophix REST endpoints, orchestrate calls, transform payloads, validate data, and expose a controlled downstream API when required.
Bulk, asynchronous, and batch exchangeLimitedBatch loads are relevant for financial values, planning models, dimensions, scenarios, and large period-based data exchanges. Job semantics, limits, and status endpoints require tenant-specific confirmation.Martini can submit batches, store job identifiers, poll documented status endpoints, reconcile accepted and rejected totals, and apply timeout and retry policies.
File import/exportLimitedCSV and Excel exchange can support financial planning inputs, templates, reporting extracts, and integrations where API access is unavailable or not selected.Martini can process Excel and structured files, validate rows, map columns to Prophix dimensions, generate target files, and route rejected rows for correction.
Webhooks and outbound callbacksLimitedGeneral-purpose Prophix webhooks for all business events were not verified. A callback or notification may exist for a selected operation or module and must be confirmed.If a documented callback is available, Martini can receive it through an API workflow; otherwise, Martini can use scheduled polling or batch exchange instead.
AuthenticationLimitedProphix integrations are permissioned through users, roles, and access to models, dimensions, scenarios, or data areas, but no universal public authentication method was confirmed.Martini can manage confirmed request authentication through secure API configuration and environment secrets, without embedding credentials in workflows.
Database and analytics accessNot confirmedDirect access to the Prophix-managed production database should not be assumed. Customer-managed reporting warehouses populated from Prophix are a separate integration target.Martini can connect to supported customer-managed databases such as a reporting warehouse through JDBC, while using Prophix APIs or exports as the source.

How Prophix exposes data and business events

Prophix REST APIs

Prophix provides integration and API capabilities for exchanging financial and planning information with external applications. The exact REST endpoints, resources, permissions, and authentication requirements depend on the Prophix One tenant and enabled services.

Martini implementation pattern

Martini implementation pattern: Martini consumes the documented Prophix REST endpoints, retrieves or submits model data, maps dimensions and members to canonical structures, applies validation rules, and writes results to the target system or exposes a controlled API for downstream consumers.

Implementation sequence

Confirm the Prophix tenant API base URL and enabled endpoints
Configure the confirmed authentication method in Martini secrets
Retrieve or submit the required Prophix resource
Map models, dimensions, members, scenarios, and values
Validate periods, currencies, and required members
Write the result to the target system and record the integration outcome

Prophix batch exchange

Prophix supports integration workflows suitable for bulk financial and planning data exchange. Batch and asynchronous behavior, including job status and row-level errors, should be confirmed for the tenant implementation.

Martini implementation pattern

Martini implementation pattern: A scheduled workflow prepares a deterministic batch, submits it through the documented Prophix mechanism, stores the returned batch or job identifier, polls status when required, and reconciles submitted, accepted, and rejected totals before completion.

Implementation sequence

Start the workflow for a defined model, scenario, entity, and period range
Retrieve source financial or operational data
Transform source values into the Prophix batch structure
Submit the batch and store the returned job identifier
Poll the documented status endpoint until completion or timeout
Capture row-level errors and reconcile accepted totals

Prophix file exchange

CSV and Excel files are relevant to Prophix planning inputs, templates, reporting extracts, and environments where file-based integration is selected. The exact upload, download, SFTP, or storage arrangement must be confirmed.

Martini implementation pattern

Martini implementation pattern: Martini receives or retrieves a configured file, validates its headers and dimensional values, transforms rows into the required Prophix import or export format, and records the source file and processing result for audit and replay.

Implementation sequence

Receive or retrieve the configured CSV or Excel file
Validate the file structure and required columns
Map account, entity, department, period, and scenario values
Reject invalid rows with actionable validation details
Generate or submit the Prophix-compatible file
Store the file identifier, result, and reconciliation totals

Selected Prophix callbacks

General-purpose Prophix webhooks and outbound callbacks for all business events were not verified. A customer tenant may provide a documented callback for a selected operation or module, but this must be confirmed before using an event-driven design.

Martini implementation pattern

Martini implementation pattern: When a documented Prophix callback exists, Martini exposes an authenticated API workflow to receive the notification, retrieves the current resource or job status, applies idempotency checks, and forwards the normalized event to downstream systems. Without such a callback, scheduled polling is used.

Implementation sequence

Confirm that the Prophix operation provides a documented callback
Receive the callback through a protected Martini API workflow
Validate the notification and check for duplicate delivery
Retrieve the current Prophix resource or job status
Map the event to the downstream canonical model
Write the result and record processing status

Common Prophix integration patterns

Pattern 1: Load ERP actuals into Prophix planning models

When to use this pattern

Use this pattern when general-ledger actuals, entities, currencies, and periods from an ERP must populate Prophix models for budgeting, forecasting, or variance analysis. Batch or file-based loading is generally preferable to individual financial-value requests.

Integration direction
SAP S/4HANA
Martini
Prophix
Example Mapping
Prophix FieldCanonical FieldTarget Field
GL accountaccountCodeAccount member
Company codeentityCodeEntity member
Fiscal periodfiscalPeriodTime member
Ledger amountamountCube measure
Martini implementation pattern

A scheduled Martini workflow retrieves a defined accounting slice, applies account and entity cross-references, converts fiscal periods and currencies, validates members and numeric precision, and submits a deterministic Prophix batch or import file. The workflow stores the source batch ID and Prophix job ID, isolates rejected rows, and retries only operations that are safe to repeat.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • file processing
  • data mapping
  • business rules
  • validation
  • error handling

Pattern 2: Publish Prophix budgets and forecasts to a data warehouse

When to use this pattern

Use this pattern when approved budgets, forecasts, scenarios, and planning outputs must be made available for enterprise analytics, reporting, or variance analysis in Snowflake or another customer-managed database.

Integration direction
Prophix
Martini
Snowflake
Example Mapping
Prophix FieldCanonical FieldTarget Field
Model identifierplanningModelIdmodel_id
ScenarioscenarioCodescenario_code
Entity memberentityCodeentity_code
Amountamountamount
Martini implementation pattern

Martini extracts documented Prophix data or files, normalizes scenario, model, entity, period, currency, and amount fields, and writes them to warehouse tables through the supported database interface. The workflow uses a source-load key for idempotency, compares extracted and inserted totals, and retains rejected rows for remediation.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • JSON and file handling
  • database connectivity
  • business rules
  • reconciliation

Pattern 3: Synchronize workforce planning drivers

When to use this pattern

Use this pattern when Workday workforce, organization, position, or compensation data drives Prophix workforce-planning models. Effective dates, privacy controls, and department or legal-entity changes require explicit processing rules.

Integration direction
Workday
Martini
Prophix
Example Mapping
Prophix FieldCanonical FieldTarget Field
Workday supervisory organizationdepartmentCodeDepartment member
Worker positionpositionCodeProduct or planning-driver member
Effective dateeffectiveDateTime member
Compensation amountcompensationAmountCube measure
Martini implementation pattern

Martini retrieves effective-dated source data, filters the relevant planning cycle, masks or excludes unnecessary personal fields, maps organizational structures to Prophix members, and loads a scenario-specific batch. Duplicate processing is prevented with a cycle and source-snapshot key, while unmapped departments and invalid dates are reported as business errors.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data transformation
  • mapping
  • validation
  • business rules
  • secure secrets

Pattern 4: Send CRM forecasts to Prophix scenarios

When to use this pattern

Use this pattern when Salesforce pipeline or revenue forecasts must inform Prophix planning and what-if analysis. A mapping layer is needed because CRM products, territories, and calendars rarely match financial planning hierarchies directly.

Integration direction
Salesforce
Martini
Prophix
Example Mapping
Prophix FieldCanonical FieldTarget Field
Opportunity forecast amountforecastAmountCube measure
Product familyproductCodeProduct member
Sales territoryterritoryCodeEntity or planning member
Forecast categoryscenarioCodeScenario member
Martini implementation pattern

A Martini workflow retrieves approved or in-scope Salesforce forecasts, translates product, territory, and fiscal-period values, applies inclusion and approval rules, and submits a Prophix batch or generated file. The workflow records the CRM extract version, rejects unmapped hierarchy values, and supports controlled reruns for the same scenario and period range.

Martini capabilities used
  • API consumption
  • scheduled workflows
  • data mapping
  • business rules
  • batch orchestration
  • validation
  • retry handling

Applications commonly integrated with Prophix

Prophix commonly participates in financial planning architectures that exchange actuals, workforce drivers, operating forecasts, and approved plans with named enterprise applications. Exact endpoints, modules, and file or API capabilities should be confirmed for each customer environment.

Application Scenario Direction Martini Pattern
SAP S/4HANA Load general-ledger actuals, cost-center data, entities, and chart-of-accounts structures into Prophix for budgeting and forecasting. SAP S/4HANA → Martini → Prophix Martini schedules an extraction from SAP S/4HANA, maps accounts and entities to Prophix dimensions, validates periods and currencies, then submits a documented Prophix batch or creates the required import file. Rejected rows and load identifiers are retained for reconciliation.
Oracle Fusion Cloud ERP Synchronize ledger actuals, projects, suppliers, entities, and accounting structures with Prophix planning models. Oracle Fusion Cloud ERP → Martini → Prophix A Martini workflow retrieves the required Oracle Fusion Cloud ERP data, applies cross-reference mappings and fiscal-calendar rules, and writes a tenant-supported Prophix batch or file. The workflow records target job status and separates business validation failures from transport errors.
Microsoft Dynamics 365 Finance Transfer ledger actuals, financial dimensions, budgets, and operating data into Prophix, with approved budgets returned where the customer process supports it. Microsoft Dynamics 365 Finance → Martini → Prophix Martini incrementally retrieves Dynamics 365 Finance data, normalizes dimensions and amounts, validates required Prophix members, and loads data by scenario, entity, and period. Optional outbound processing can expose an API for approved-plan handoff.
NetSuite Import financial actuals and subsidiary data into Prophix and optionally return approved budgets or forecasts to NetSuite. NetSuite → Martini → Prophix Martini orchestrates scheduled NetSuite retrieval, maps subsidiaries and accounts to Prophix members, applies sign and currency rules, and submits an idempotent planning load. A separate workflow can publish approved outputs to NetSuite through its supported interface.
Workday Synchronize workforce, organization, compensation, and planning-driver data with Prophix workforce-planning models. Workday → Martini → Prophix Martini retrieves effective-dated Workday data, filters employee and organizational changes for the planning cycle, protects sensitive fields, and maps departments, legal entities, positions, and compensation units to Prophix dimensions. The workflow prevents duplicate reloads for the same cycle.
Salesforce Provide pipeline and revenue forecast data for Prophix planning, scenario analysis, and operating forecasts. Salesforce → Martini → Prophix A Martini workflow retrieves Salesforce forecast data, translates product, territory, and fiscal-period hierarchies, applies inclusion and approval rules, and submits a Prophix batch or structured file. Mapping exceptions are routed for review rather than silently loaded.
Snowflake Centralize Prophix budgets, forecasts, scenarios, and planning outputs for enterprise analytics and reporting. Prophix → Martini → Snowflake Martini extracts documented Prophix outputs, preserves model, scenario, entity, period, currency, and source-load metadata, transforms the result into warehouse tables, and writes it to Snowflake. Reconciliation compares extracted and loaded totals before completion.
Microsoft Excel Exchange budget templates, planning inputs, and reporting extracts for spreadsheet-oriented planning processes. Microsoft Excel → Martini → Prophix Martini receives or retrieves a configured Excel file, validates headers and dimensional members, converts rows into the Prophix import structure, and submits the file or batch through the customer-approved mechanism. Invalid rows are reported separately from accepted data.

How to build a Prophix integration in Martini

Objective

Establish access to the Prophix tenant and adjacent systems using the authentication methods confirmed for each environment.

Instructions in Martini

  • Confirm the Prophix API base URL, enabled services, permissions, and integration identity.
  • Store credentials and tokens in Martini secrets or environment configuration.
  • Configure source and target API, file, or JDBC access without embedding credentials in workflows.

Objective

Select a trigger that matches the Prophix capability and business latency requirement.

Instructions in Martini

  • Use a scheduler for periodic actuals, budgets, forecasts, and warehouse extracts.
  • Use a file-arrival process when the customer relies on CSV or Excel exchange.
  • Use a callback-triggered API workflow only when the Prophix tenant documents the relevant callback.

Objective

Acquire the source data or Prophix response for a defined model, scenario, entity, period, or batch.

Instructions in Martini

  • Retrieve data through documented APIs or configured file exchange.
  • Process large financial datasets in controlled batches or slices.
  • Store source batch IDs, file identifiers, and pagination or continuation state where applicable.

Objective

Coordinate calls, batch submission, status checks, target writes, and compensation logic in a maintainable Martini workflow.

Instructions in Martini

  • Separate extraction, transformation, Prophix loading, reconciliation, and notification stages.
  • Poll documented asynchronous job status endpoints with bounded timeouts.
  • Route transport failures and business validation failures to distinct handling paths.

Objective

Convert source structures into Prophix models, dimensions, members, scenarios, and financial values.

Instructions in Martini

  • Maintain explicit cross-reference mappings for Account, Entity, Department, Product, Time, Scenario, and Version.
  • Apply fiscal-calendar, currency, sign, precision, unit, and null-value rules.
  • Validate expected model and dimension structures before submitting a load.

Objective

Ensure that only valid, approved, and appropriately scoped data reaches Prophix or downstream systems.

Instructions in Martini

  • Reject unmapped members, invalid periods, duplicate batches, and disallowed scenarios.
  • Apply planning-cycle, approval, entity, and data-privacy rules.
  • Preserve rejected rows and actionable validation messages for correction.

Common Prophix data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
ModelsPlanning or reporting environments containing financial and operational data.ERP platforms, data warehouses, reporting databases, and planning workflowsMartini discovers tenant-specific model identifiers, validates that the expected model is available, and includes the model in batch, extraction, and reconciliation metadata.
DimensionsAnalytical structures such as Account, Entity, Department, Product, Time, Scenario, or Version.SAP S/4HANA, Oracle Fusion Cloud ERP, Dynamics 365 Finance, NetSuite, Workday, SnowflakeMartini maintains explicit cross-reference mappings, validates required dimensions, and transforms source hierarchies and identifiers into the Prophix model structure.
MembersIndividual values within dimensions, such as accounts, legal entities, departments, or periods.ERP, HCM, CRM, warehouse, and file-based planning processesMartini validates member existence, handles unmapped values as business errors, and records source-to-Prophix member mappings for repeatable loads.
CubesMultidimensional structures containing measures and dimensional data intersections.Data warehouses, reporting platforms, ERP planning outputsMartini extracts or loads cube-oriented values in controlled slices, preserving dimensional keys, measures, currency, period, and source batch metadata.
ScenariosPlanning or reporting perspectives such as Actual, Budget, Forecast, or What-if versions.ERP, CRM, HCM, Snowflake, reporting databasesMartini maps source planning cycles to Prophix scenarios, applies scenario-specific validation, and uses scenario identifiers in idempotency and reconciliation keys.
Templates and reportsUser-facing planning, reporting, or data-entry structures used to collect or present information.Microsoft Excel, file exchange processes, reporting and analytics systemsMartini can process configured template files or exports, validate their structure, transform rows, and route results into approved Prophix import or reporting workflows.

Authentication and security considerations

Tenant-specific authentication

Prophix authentication details vary by product edition, deployment, enabled services, and tenant configuration. Confirm the API base URL, authentication method, scopes or permissions, and supported file-transfer security with the Prophix administrator.

Least-privilege access

Use a dedicated integration identity with access only to the required models, dimensions, scenarios, templates, and data areas. Prophix access should be governed by its users, roles, and permissions.

Martini secrets

Store Prophix credentials, tokens, file-transfer credentials, and target-system secrets in Martini environment configuration or secrets management. Do not embed sensitive values in workflows, mappings, or files.

Financial and workforce data

Protect financial and workforce-planning data in transit and at rest. Minimize personal data in workforce loads and expose only the API operations required by downstream systems.

Operational considerations for Prophix integrations

Tenant variation

Confirm enabled endpoints, models, dimensions, authentication, import formats, batch behavior, and permissions before implementation. Prophix structures are configurable and should not be hard-coded without discovery.

Pagination and batch size

Determine whether API responses paginate, how continuation works, and what limits apply. Prefer documented batch or file mechanisms for large planning loads rather than many individual requests.

Idempotency and retries

Use source batch identifiers and deterministic model, scenario, entity, and period keys. For asynchronous loads, store the Prophix job identifier, poll with bounded timeouts, and do not resubmit completed work unless the operation is safe to repeat.

Financial correctness

Explicitly manage fiscal calendars, currency, sign conventions, decimal precision, units, null values, open periods, and forecast cut-off dates. Reconcile submitted, accepted, and rejected amounts.

Schema and testing

Monitor changes to Prophix models, dimensions, members, scenarios, templates, and integration processes. Test representative actual, budget, forecast, empty, duplicate, invalid-member, and partial-failure cases before production use.

Why use Martini instead of scripts or point-to-point integrations?

Reusable orchestration

Martini provides workflows that coordinate scheduled retrieval, API calls, file processing, batch submission, asynchronous status checks, target writes, and notifications in one maintainable integration asset.

Controlled transformation

Financial integrations usually require semantic mapping rather than simple field copying. Martini can apply cross-reference tables, fiscal-calendar rules, currency and precision handling, scenario logic, and validation before data reaches Prophix or a target warehouse.

Reliable operations

Martini can separate transport errors from business validation failures, preserve batch and job identifiers, support bounded retries, and provide reconciliation and monitoring data for operational teams.

API-led access

Instead of exposing Prophix-specific credentials and structures to every consumer, Martini can expose a controlled REST API façade and centralize authentication, authorization, mapping, and workflow behavior.

Maintainable architecture

Compared with isolated scripts or point-to-point flows, reusable Martini workflows make tenant-specific Prophix assumptions visible, configurable, testable, and easier to extend as planning models and adjacent systems change.

Frequently asked questions

How can Prophix be integrated with enterprise systems?

Prophix can exchange planning, budgeting, forecasting, and reporting data through tenant-specific integration capabilities, documented REST endpoints where enabled, batch processes, and structured CSV or Excel file exchange. The exact API, authentication, and file-transfer options depend on the Prophix One environment. Scheduled workflows are a conservative approach when general-purpose event notifications are unavailable.

Can Martini integrate with Prophix?

Yes. Martini can integrate with Prophix by consuming documented Prophix REST endpoints, orchestrating scheduled or batch exchanges, processing CSV or Excel files, transforming financial and dimensional data, and writing results to ERP, HCM, CRM, warehouse, or database targets. The required Prophix endpoints and authentication method must be confirmed for the tenant.

Do I need a connector to integrate Prophix with Martini?

No. A dedicated Prophix connector is not required. Martini can use Prophix’s confirmed native integration mechanisms, such as documented REST APIs, configured batch processes, file exchange, or a selected documented callback, and provide the workflow orchestration, validation, mapping, and error handling around them.

Is there any extra Lonti cost to integrate Prophix with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Prophix. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Prophix, cloud infrastructure, file-transfer services, or other third-party systems depending on subscription, usage, and deployment model.

Which Prophix integration methods should an architect use?

Use documented REST endpoints where the Prophix tenant exposes the required resources and authentication. Use batch or asynchronous exchange for large financial loads and CSV or Excel exchange where the implementation is file-based. Direct access to the Prophix application database should not be assumed, and GraphQL and SOAP APIs were not confirmed.

Does Prophix support webhooks or outbound callbacks?

General-purpose webhooks and outbound callbacks for all Prophix business events were not verified. A selected module or operation may provide a documented notification, but it must be confirmed for the tenant. Martini can receive a confirmed callback through an API workflow; otherwise, scheduled polling and batch exchange are safer patterns.

How should Prophix data synchronization handle mapping and duplicate loads?

Maintain explicit mappings for models, Account, Entity, Department, Product, Time, Scenario, and Version members rather than relying only on display names. Use deterministic keys based on the source batch, model, scenario, entity, and period, and prefer replacement, clear-and-reload, or other documented idempotent strategies for retries.

Can Martini expose an API façade for Prophix processes?

Yes. Martini can expose a REST API that validates requests, invokes workflows, retrieves or submits Prophix data through the mechanisms available in the tenant, and returns a controlled response to downstream applications. This can isolate Prophix-specific mappings and authentication from consuming systems.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Prophix with your enterprise systems

Use Martini to orchestrate Prophix data exchange, transform planning structures, validate financial loads, and connect Prophix with the applications and data platforms your organization relies on.

EXPLORE MARTINI
BOOK A DEMO