.png)
Workday Adaptive Planning Integration Guide
Connect Workday Adaptive Planning with finance, workforce, operational, and data platforms through REST APIs, SOAP web services, batch exchange, files, and scheduled workflows.
Workday Adaptive Planning integration options at a glance
Workday Adaptive Planning integrations commonly exchange accounts, versions, levels, dimensions, time periods, sheets, reports, actuals, budgets, and forecasts. Workday REST APIs are available for supported services, while Adaptive Planning web services may use XML and SOAP-style operations for imports, exports, metadata, and reporting. Bulk and batch exchange can use files, reports, exports, or web-service operations. Martini can consume these interfaces, authenticate with OAuth 2.0 or tenant-specific credentials where supported, schedule synchronization workflows, process JSON, XML, and Excel-based files, validate planning data, and reconcile accepted and rejected batches. General-purpose webhooks and direct database access should not be assumed.
| Integration point | Supported by Workday Adaptive Planning? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Workday REST APIs can expose supported Workday services; the exact Adaptive Planning resources and tenant availability must be confirmed. They can support authenticated retrieval or submission of documented planning-related data. | Martini can consume documented REST endpoints, send authenticated requests, parse JSON responses, apply validation and business rules, and expose REST APIs for downstream consumers. |
| SOAP APIs | Yes | Adaptive Planning web services have historically supported XML and SOAP-style operations for data imports, exports, metadata, reporting, and related planning administration. Supported operations and versions vary by tenant. | Martini can consume SOAP services, generate or process XML payloads, transform responses, and route service faults through workflow error handling. |
| Bulk / async / batch APIs | Limited | Bulk exchange is commonly used for actuals, budgets, forecasts, metadata, reports, and planning values through files, exports, reports, or web-service operations. Exact batch behavior depends on the selected interface. | Martini can orchestrate batch requests, process large files, track source batch identifiers, validate rows, and reconcile accepted and rejected values. |
| File / attachment APIs | Limited | File-based imports and exports are common for large accounting, workforce, operational, and planning datasets. A general-purpose Adaptive Planning attachment API was not confirmed. | Martini can process JSON, XML, and Excel-based files and orchestrate file ingestion or delivery when the customer environment provides the required endpoint or transfer mechanism. |
| Authentication | Yes | Supported Workday REST APIs may use OAuth 2.0. Adaptive Planning web services may use tenant-specific API credentials and authenticated sessions, governed by Workday security permissions. | Martini can store tenant endpoints, client identifiers, secrets, passwords, tokens, and related configuration in protected environment configuration or secrets management. |
| Scheduled synchronization | Yes | Scheduled polling, report extraction, file exchange, and batch jobs are practical approaches because general-purpose webhooks for all Adaptive Planning changes were not confirmed. | Martini can trigger workflows on schedules, retrieve or process source data, apply explicit watermark and period rules, and record execution and reconciliation state. |
| Database / analytics access | Limited | Reporting and export capabilities are available, but direct SQL access to the underlying Workday Adaptive Planning SaaS database was not confirmed. | Martini can consume supported reports, exports, APIs, and files, but should not depend on direct database access to Adaptive Planning. |
| Webhooks / outbound callbacks | Not confirmed | No general-purpose webhook coverage for arbitrary changes to Accounts, Versions, Sheets, Levels, or planning values was confirmed. A Workday process may call a Martini API where supported and enabled. | Martini can expose a REST API for a supported Workday-originated callback, but event coverage and the calling process must be confirmed in the customer tenant. |
How Workday Adaptive Planning exposes data and business events
Workday REST APIs
Workday provides REST APIs for supported services, but the exact REST resources available for Adaptive Planning should be verified in the customer’s developer documentation and tenant configuration.
Martini implementation pattern
Martini implementation pattern: a workflow stores the tenant-specific endpoint and authentication configuration, calls the documented REST resource, parses JSON, validates Version, Account, Level, Dimension, and Time period values, then writes or publishes the transformed result.
Implementation sequence
Adaptive Planning SOAP web services
Adaptive Planning web services have historically provided XML and SOAP-style operations for imports, exports, metadata, reporting, and related planning operations. The customer must confirm supported service versions and operations.
Martini implementation pattern
Martini implementation pattern: a workflow constructs or consumes the documented SOAP message, handles XML namespaces and service faults, transforms the response into a canonical model, and applies controlled retry and reconciliation rules.
Implementation sequence
Batch and file exchange
Bulk planning exchange commonly uses data imports, exports, reports, files, or batch web-service operations for actuals, budgets, forecasts, metadata, and planning values. Exact formats and limits depend on the customer environment.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow retrieves or receives a file or export, validates structure and row content, processes large datasets in controlled segments, submits the supported load, and records accepted and rejected rows.
Implementation sequence
Scheduled synchronization
Because universal change-data-capture and general-purpose webhooks were not confirmed, scheduled extraction, report polling, period filters, and batch identifiers are common synchronization approaches.
Martini implementation pattern
Martini implementation pattern: a scheduler starts a workflow using a stored watermark, Version, period range, or batch identifier; the workflow retrieves only the intended scope, processes it idempotently, and advances the checkpoint only after successful reconciliation.
Implementation sequence
Martini REST API callbacks
No general-purpose Adaptive Planning webhook mechanism was confirmed. Where a Workday-originated integration process can call an external endpoint, Martini can expose a controlled REST API for that callback.
Martini implementation pattern
Martini implementation pattern: Martini authenticates the inbound request, validates the callback payload and source context, retrieves authoritative planning data when necessary, and starts an asynchronous workflow for downstream processing.
Implementation sequence
Common Workday Adaptive Planning integration patterns
Pattern 1: Load general ledger actuals
When to use this pattern
Use this pattern when finance teams need to move actuals from an ERP into Adaptive Planning for reporting, variance analysis, and forecasting. The workflow should validate financial structures before loading values and should reconcile every source batch.
Integration direction
Example Mapping
| Workday Adaptive Planning Field | Canonical Field | Target Field |
|---|---|---|
| subsidiary | companyCode | Level |
| account | accountCode | Account |
| accountingPeriod | fiscalPeriod | Time period |
| amount | actualAmount | Sheet value |
Martini implementation pattern
Martini retrieves approved actuals, maps company, Account, Level, Dimension, and Time period values, validates that target members exist, and submits a supported batch or file load. A deterministic source batch identifier supports idempotency; rejected rows are isolated and transient failures are retried with bounded backoff.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- file processing
- error handling
Pattern 2: Publish forecasts to a data platform
When to use this pattern
Use this pattern when planning and executive reporting require forecast data in a central warehouse alongside ERP, CRM, and operational information. Version and period selection should be explicit so that Actual, Budget, and Forecast values are not mixed.
Integration direction
Example Mapping
| Workday Adaptive Planning Field | Canonical Field | Target Field |
|---|---|---|
| Version | scenarioCode | scenario_code |
| Account | accountCode | account_code |
| Level | organizationCode | organization_code |
| Time period | fiscalPeriod | fiscal_period |
Martini implementation pattern
A scheduled Martini workflow retrieves a report, export, or documented API response filtered by Version and period, normalizes Dimensions and planning values into the warehouse schema, and loads Snowflake. Martini records source response or batch identifiers and prevents duplicate loads with a composite business key.
Martini capabilities used
- scheduling
- API consumption
- XML and JSON transformation
- data mapping
- workflow orchestration
- error handling
Pattern 3: Synchronize workforce planning inputs
When to use this pattern
Use this pattern when Adaptive Planning depends on workforce, organization, position, compensation, or headcount assumptions from Workday HCM. Apply security filtering and transfer only the attributes required by the planning model.
Integration direction
Example Mapping
| Workday Adaptive Planning Field | Canonical Field | Target Field |
|---|---|---|
| worker or position identifier | workforceMemberId | planningMemberId |
| organization | organizationCode | Level |
| compensation assumption | plannedCompensation | Sheet value |
| effective period | fiscalPeriod | Time period |
Martini implementation pattern
Martini retrieves permitted workforce attributes, filters sensitive data, maps organizations and positions to Levels and Dimensions, validates effective periods, and submits a supported planning import. The workflow routes permission failures and unmapped members separately from transient transport failures.
Martini capabilities used
- API consumption
- workflows
- data filtering
- data mapping
- business rules
- secrets management
- error handling
Pattern 4: Distribute approved budget values
When to use this pattern
Use this pattern when approved Budget or Forecast Versions must be shared with operational applications or reporting consumers. Version status, department or project scope, and duplicate prevention should be enforced before distribution.
Integration direction
Example Mapping
| Workday Adaptive Planning Field | Canonical Field | Target Field |
|---|---|---|
| Version | approvedScenario | budgetScenario |
| Level | departmentCode | department |
| Dimension | projectCode | project |
| planning value | approvedAmount | plannedCost |
Martini implementation pattern
Martini retrieves selected approved values through a supported report, export, REST resource, or web service, validates the scenario and period, maps the result to ServiceNow fields, and writes it using a composite key. The workflow records the source batch and target response and retries only safe transient failures.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- validation
- business rules
- idempotency
- monitoring
Applications commonly integrated with Workday Adaptive Planning
Workday Adaptive Planning can be connected with finance, workforce, operational, and data platforms to move actuals, assumptions, master data, budgets, forecasts, and reporting outputs. These relationships are integration patterns rather than confirmation of packaged Workday integrations.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Workday HCM | Synchronize workforce, organization, position, compensation, and headcount planning attributes while limiting sensitive employee data to what the planning model requires. | Workday HCM → Martini → Workday Adaptive Planning | Martini can schedule a workflow to retrieve approved workforce data, apply security filtering, map organizations and positions to Levels and Dimensions, validate planning periods, and submit a batch or file-based update to Adaptive Planning. |
| NetSuite | Transfer general ledger actuals, chart-of-accounts data, subsidiaries, and financial dimensions into planning and forecasting processes. | NetSuite → Martini → Workday Adaptive Planning | A Martini workflow can consume NetSuite data, map subsidiaries, accounts, departments, periods, and amounts to Adaptive Planning structures, validate the target model, load the batch, and record reconciliation results. |
| Salesforce | Combine bookings, pipeline, customer, and revenue information with budgets and financial forecasts. | Salesforce → Martini → Workday Adaptive Planning | Martini can retrieve selected Salesforce measures, normalize them by account, region, period, or product, apply forecast business rules, and deliver the result through a supported Adaptive Planning import, export, or web-service process. |
| SAP S/4HANA | Load general ledger actuals, cost centers, profit centers, and financial structures for budgeting and forecasting. | SAP S/4HANA → Martini → Workday Adaptive Planning | Martini can orchestrate scheduled extraction, transform SAP financial dimensions into Levels, Accounts, and Time periods, validate fiscal-calendar mappings, and process a batch or file load with error handling. |
| Oracle ERP Cloud | Synchronize actuals, accounting dimensions, journals, and financial structures with planning models. | Oracle ERP Cloud → Martini → Workday Adaptive Planning | A workflow can retrieve approved accounting data, map it to Version, Account, Level, Dimension, and Time period values, reject unmapped members, and submit or deliver the validated load to Adaptive Planning. |
| ServiceNow | Incorporate workforce, technology, project, or operational cost information into planning and forecasting, and distribute approved planning values where required. | ServiceNow → Martini → Workday Adaptive Planning | Martini can poll or receive supported ServiceNow data, transform operational costs into the Adaptive Planning model, apply Version and period rules, and route rejected values for correction. |
| Snowflake | Centralize planning data with ERP, CRM, and operational data for enterprise reporting and analytics. | Workday Adaptive Planning → Martini → Snowflake | Martini can retrieve reports, exports, or forecast batches from Adaptive Planning, normalize the data into a warehouse schema, load Snowflake, and preserve Version, period, source batch, and reconciliation metadata. |
| Anaplan | Exchange planning or comparison data where organizations operate multiple planning platforms during transition or coexistence. | Anaplan → Martini → Workday Adaptive Planning | Martini can mediate file or API exchanges, map differing Accounts, Levels, Dimensions, Versions, and periods, apply controlled overwrite or merge rules, and reconcile both planning platforms. |
How to build a Workday Adaptive Planning integration in Martini
Objective
Establish the tenant-specific Workday or Adaptive Planning endpoint and the appropriate authentication configuration before implementing data movement.
Instructions in Martini
- Confirm the tenant, environment, API or web-service interface, and supported operations
- Configure OAuth 2.0 or tenant-specific credentials as required
- Store endpoints, client secrets, passwords, and tokens in Martini environment configuration or secrets management
- Apply least-privilege permissions to the required Accounts, Levels, Versions, Sheets, Reports, and related operations
Objective
Select an execution model that matches the vendor capability and business timing rather than assuming universal change events.
Instructions in Martini
- Use a scheduled trigger for polling, report extraction, or batch exchange
- Use a supported file handoff where large planning datasets are exchanged through files
- Use a Martini API for a Workday-originated callback only when the customer confirms that process is available
- Define the Version, Time period, watermark, or batch scope
Objective
Receive or retrieve authoritative planning data through a documented interface and preserve identifiers needed for reconciliation.
Instructions in Martini
- Call the documented REST endpoint or SOAP service
- Retrieve the supported report, export, or planning file
- Capture response, job, export, or source batch identifiers
- Process large responses or files in controlled segments where practical
Objective
Coordinate the end-to-end exchange as a maintainable Martini workflow with clear stages and failure paths.
Instructions in Martini
- Separate extraction, validation, transformation, load, and reconciliation stages
- Add conditional routing for authentication, validation, transport, and business-rule failures
- Use reusable workflow logic for common planning loads
- Advance watermarks only after the target operation and reconciliation succeed
Objective
Convert source financial, workforce, or operational structures into the Adaptive Planning model or a downstream reporting schema.
Instructions in Martini
- Map Accounts, Versions, Levels, Sheets, Dimensions, and Time periods explicitly
- Normalize fiscal calendars and period identifiers
- Transform JSON, XML, Excel, or other supported structured files as required
- Externalize mappings where practical so controlled metadata changes do not require broad workflow rewrites
Objective
Enforce planning, security, data-quality, and duplicate-prevention rules before writing values.
Instructions in Martini
- Validate that Accounts, Levels, Dimensions, Versions, and periods exist
- Filter sensitive workforce or compensation data
- Use deterministic composite keys for idempotency
- Check whether the target operation appends, replaces, merges, or updates values before retrying
Common Workday Adaptive Planning data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Accounts | Represent revenue, operating expense, headcount-related, and balance-sheet planning accounts. | NetSuite, SAP S/4HANA, Oracle ERP Cloud, Snowflake | Martini validates account mappings, transforms source chart-of-accounts values, and carries account identifiers through batch reconciliation. |
| Versions | Represent Actual, Budget, Forecast, and alternative planning scenarios. | ERP platforms, Snowflake, Salesforce | Martini makes Version selection explicit, applies status and scenario rules, and prevents accidental writes to the wrong planning scenario. |
| Levels | Represent organizational and reporting structures such as companies, departments, and cost centers. | Workday HCM, NetSuite, SAP S/4HANA, Oracle ERP Cloud | Martini maps organizational hierarchies, validates target members, and routes unmapped Levels to controlled exception handling. |
| Time periods | Represent months, quarters, years, and other planning periods used for actuals and forecasts. | ERP platforms, Salesforce, Snowflake | Martini normalizes fiscal calendars, validates period identifiers, and includes period boundaries in synchronization and idempotency keys. |
| Sheets | Contain modeled, standard, or cube-style planning data. | ERP platforms, Workday HCM, Snowflake | Martini retrieves or loads supported Sheet data through documented APIs, web services, reports, exports, or files and validates the expected structure. |
| Dimensions | Segment planning data by products, regions, projects, departments, and other analytical attributes. | Salesforce, SAP S/4HANA, Oracle ERP Cloud, Snowflake | Martini maps source dimensions to Adaptive Planning members, rejects invalid combinations, and preserves dimensional context in downstream loads. |
Authentication and security considerations
Tenant-specific authentication
Authentication depends on the selected Workday or Adaptive Planning interface and tenant configuration. Supported Workday REST APIs may use OAuth 2.0, while Adaptive Planning web services may use tenant-specific API credentials and authenticated sessions.
Permissions and secrets
Use a dedicated integration identity with least-privilege access to the required Accounts, Versions, Levels, Sheets, Reports, metadata, and integration operations. Store tenant URLs, client identifiers, secrets, passwords, and tokens in protected Martini environment configuration or secrets management.
Sensitive planning data
Workforce, compensation, and financial planning data may be sensitive. Apply security filtering, avoid credentials in payloads and logs, and keep sandbox and production configuration separate.
Operational considerations for Workday Adaptive Planning integrations
Volume and pagination
Reports, exports, and planning responses may be large. Confirm pagination, response limits, file sizes, timeouts, and processing behavior for the selected interface. Prefer supported batch or file exchange for high-volume loads where appropriate.
Versions and periods
Distinguish Actual, Budget, Forecast, and alternative Versions. Validate fiscal calendars and make period selection explicit rather than assuming that identifiers match source systems.
Idempotency and reconciliation
Use a deterministic key based on tenant, Version, Account, Level, Dimensions, Time period, source system, and batch identifier. Record row counts, accepted and rejected values, response identifiers, load timestamps, and retry status.
Retries and schema changes
Separate authentication, authorization, validation, throttling, transport, and business-rule failures. Retry transient failures with bounded backoff, but do not blindly retry non-idempotent imports. Treat changes to Accounts, Levels, Dimensions, Sheets, and Versions as controlled metadata changes.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than a single API call
Workday Adaptive Planning exchanges often require extraction, validation, mapping, batch submission, reconciliation, and downstream distribution. Martini coordinates these stages in workflows rather than leaving business logic in isolated scripts.
Maintainable data transformation
Martini provides mappings, transformations, validation, conditional routing, and reusable integration logic for JSON, XML, and structured files. This supports controlled changes as planning models, fiscal calendars, and source systems evolve.
Reliable operations
Martini can schedule synchronization, preserve checkpoints and batch identifiers, handle errors, apply bounded retries, and expose APIs for controlled consumers or supported callbacks. This creates operational visibility without relying on direct access to the Workday Adaptive Planning database.
Frequently asked questions
Workday Adaptive Planning can exchange planning values, actuals, budgets, forecasts, metadata, and reports through supported Workday REST APIs, Adaptive Planning XML or SOAP-style web services, batch operations, reports, exports, and files. Scheduled synchronization is commonly used because general-purpose webhooks for all planning changes were not confirmed.
Yes. Martini can integrate with Workday Adaptive Planning through documented REST APIs, Adaptive Planning SOAP or XML web services, supported files, reports, exports, and tenant-specific authentication methods. The exact resources and operations should be confirmed in the customer’s Workday environment.
No. A dedicated Workday Adaptive Planning connector is not required. Martini can consume the vendor’s confirmed REST APIs, SOAP services, files, reports, exports, and other documented endpoints, then orchestrate workflows, mappings, validation, and reconciliation.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Workday Adaptive Planning. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Workday, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Use documented REST APIs where the required Adaptive Planning resources are available. Use Adaptive Planning SOAP or XML web services for supported planning operations, and use batch, report, export, or file exchange for larger datasets. The customer’s tenant documentation should determine the supported interface and operation.
No general-purpose webhook coverage for all Accounts, Versions, Sheets, Levels, or planning values was confirmed. Practical alternatives include scheduled polling, filtered reports or exports, file handoffs, or a Workday-originated process that calls a Martini API when supported.
A robust synchronization makes Version, Time period, Account, Level, and relevant Dimensions explicit. Martini can apply fiscal-calendar mappings, watermarks or batch identifiers, and deterministic composite keys. The workflow should also confirm whether each target operation appends, replaces, merges, or updates values.
Yes. Martini can expose a controlled REST API for downstream applications or for a supported Workday-originated callback. The API can authenticate and validate requests, start an asynchronous workflow, transform planning data, and provide a controlled boundary without exposing Workday credentials or tenant details.
Related Martini documentation
Workflows
Data
Connect Workday Adaptive Planning with Martini
Build a controlled integration between Workday Adaptive Planning and your enterprise systems using documented APIs, SOAP services, files, scheduled workflows, mappings, and secure environment configuration.