.png)
SAP Integrated Business Planning Integration Guide
Connect SAP Integrated Business Planning with enterprise applications through OData APIs, selected SOAP services, file exchange, and scheduled integration workflows.
SAP Integrated Business Planning integration options at a glance
SAP Integrated Business Planning primarily integrates through OData services for selected master data, planning data, and key-figure operations. Selected scenarios also support SOAP web services, file-based imports and exports, application jobs, and batch or bulk-oriented processing. Authentication is configured through SAP communication systems, communication users, and communication arrangements, with OAuth 2.0, Basic Authentication, or client certificates available depending on the service. A general-purpose webhook mechanism was not confirmed, so scheduled polling and SAP integration services are important alternatives. Martini can consume these APIs, process files, schedule workflows, map planning models, validate data, and manage retries and reconciliation.
| Integration point | Supported by SAP Integrated Business Planning? | Common use cases | How Martini supports it |
|---|---|---|---|
| OData and REST-style APIs | Yes | Read and update selected master data, planning data, and key figures, with filtering by planning area, planning level, time period, version, or other supported dimensions. | Martini can consume SAP IBP OData endpoints, construct filtered requests, process JSON or XML responses where supported, map fields, and expose APIs for downstream consumers. |
| SOAP APIs | Limited | Selected SAP IBP communication scenarios provide SOAP web services for integration processes that are not covered by the relevant OData service. | Martini can consume a documented WSDL, construct XML requests, apply configured authentication, and handle SOAP faults. Availability must be verified per service. |
| Bulk, batch, and asynchronous processing | Limited | Bulk file loads, application jobs, and API batch or bulk operations support large master-data and planning-data exchanges in selected scenarios. | Martini can partition workloads, coordinate scheduled batches, checkpoint progress, and retry failed pages or batches without repeating completed work. |
| File import and export | Limited | CSV or other SAP-supported file formats can be used for selected master-data and planning-data imports and exports through configured SAP integration flows or file services. | Martini can process files, validate structure and required fields, transform rows into SAP IBP payloads, and route rejected files or records for review. |
| Scheduled synchronization | Yes | Scheduled polling, application jobs, and SAP integration services can coordinate recurring synchronization where general-purpose change events are not available. | Martini scheduler-triggered workflows can retrieve incremental windows, process partitions, write checkpoints, and coordinate downstream publication. |
| Authentication and communication arrangements | Yes | SAP communication systems, communication users, and communication arrangements define endpoints, scopes, permissions, and supported OAuth 2.0, Basic Authentication, or certificate-based access. | Martini can keep tenant URLs, credentials, tokens, and certificates in protected environment configuration or secrets management and apply them to API workflows. |
| Webhooks and outbound callbacks | Not confirmed | A general-purpose webhook mechanism for all SAP IBP planning, master-data, or key-figure changes was not confirmed. | Martini should use scheduled APIs, application jobs, files, or documented SAP integration services rather than assume webhook coverage. |
| Direct database access | No | Direct access to the SAP-managed SAP IBP database is not expected; planning and analytical data should be accessed through supported APIs and integration services. | Martini can consume supported SAP interfaces or load data into an accessible enterprise database, but it should not connect directly to the managed IBP database. |
How SAP Integrated Business Planning exposes data and business events
SAP IBP OData APIs
SAP IBP primarily exposes OData services for selected master data, planning data, key figures, and integration scenarios. Supported filters and write operations depend on the activated communication scenario and tenant configuration.
Martini implementation pattern
Martini implementation pattern: Martini calls the configured OData endpoint with the required authentication, filters and pagination, converts the response into an internal model, applies business rules, and writes or publishes the result. For writes, the workflow records request context and SAP responses for reconciliation.
Implementation sequence
SAP IBP SOAP services
Selected SAP IBP integration scenarios provide SOAP web services. SOAP availability, operations, WSDLs, and authentication requirements are interface-specific and should be confirmed before implementation.
Martini implementation pattern
Martini implementation pattern: Martini consumes the relevant WSDL or configured SOAP contract, creates XML requests, applies the tenant's authentication configuration, and handles SOAP faults separately from transport failures.
Implementation sequence
SAP IBP file exchange
SAP IBP supports file-based import and export for selected data-exchange scenarios. File formats, delimiters, required fields, validation rules, and transfer services depend on the configured flow.
Martini implementation pattern
Martini implementation pattern: Martini receives or retrieves the supported file, validates its structure and encoding, maps rows into SAP IBP objects or target-system models, and records file and batch identifiers for replay.
Implementation sequence
Scheduled SAP IBP synchronization
A general-purpose webhook mechanism for SAP IBP changes was not confirmed. Recurring synchronization is therefore commonly implemented with scheduled API polling, application jobs, file exchange, or SAP integration services.
Martini implementation pattern
Martini implementation pattern: A scheduler-triggered workflow retrieves a bounded time window or planning partition, uses a durable cursor, transforms the result, and retries transient failures without reprocessing completed partitions.
Implementation sequence
Common SAP Integrated Business Planning integration patterns
Pattern 1: Load ERP master data into SAP IBP
When to use this pattern
Use this pattern when SAP S/4HANA or SAP ECC is the source of products, locations, customers, resources, or other planning attributes. It supports controlled initial loads and recurring incremental synchronization.
Integration direction
Example Mapping
| SAP Integrated Business Planning Field | Canonical Field | Target Field |
|---|---|---|
| Product ID | product.externalId | Master Data Object product |
| Plant or Location | location.externalId | Master Data Object location |
| Base Unit of Measure | product.unitOfMeasure | Planning attribute unit |
Martini implementation pattern
A scheduled Martini workflow extracts a bounded set of ERP data, normalizes identifiers and units, validates required planning attributes, partitions the load, and submits it through the configured OData, SOAP, or file interface. Failed partitions are retried and rejected records are retained for reconciliation.
Martini capabilities used
- workflows
- scheduled triggers
- API consumption
- file processing
- data mapping
- business rules
- error handling
Pattern 2: Publish SAP IBP planning data to analytics
When to use this pattern
Use this pattern when approved forecasts, supply plans, scenarios, or key figures must be combined with operational and financial data in SAP Analytics Cloud or SAP Datasphere.
Integration direction
Example Mapping
| SAP Integrated Business Planning Field | Canonical Field | Target Field |
|---|---|---|
| Key Figure | planning.metric | Analytics measure |
| Time Period | planning.period | Calendar period |
| Version | planning.scenario | Scenario identifier |
Martini implementation pattern
Martini retrieves planning data by planning area, version, period, or other supported dimensions, maps SAP planning semantics into the analytical model, applies approval and publication rules, and delivers the result through the target interface. Counts and key totals are reconciled before publication.
Martini capabilities used
- API consumption
- pagination
- data mapping
- business rules
- workflow orchestration
- reconciliation
- error handling
Pattern 3: Transfer demand signals from Salesforce to SAP IBP
When to use this pattern
Use this pattern when approved opportunity, account, product, or pipeline information is used as an input to demand planning. The exact mapping depends on the customer's planning model and SAP IBP configuration.
Integration direction
Example Mapping
| SAP Integrated Business Planning Field | Canonical Field | Target Field |
|---|---|---|
| Product | demand.product | Planning master-data product |
| Close Date | demand.period | Time Profile period |
| Opportunity Amount | demand.quantity | Key Figure value |
Martini implementation pattern
Martini retrieves eligible Salesforce data, resolves product and account identifiers, converts dates and quantities into SAP planning periods and units, applies eligibility and approval rules, and writes supported planning inputs. The workflow records the source reference to make retries idempotent.
Martini capabilities used
- API consumption
- data mapping
- transformations
- validation
- business rules
- idempotency
- retry handling
Pattern 4: Coordinate procurement inputs with SAP Ariba
When to use this pattern
Use this pattern when procurement, supplier, or supply-related information must be coordinated with SAP IBP. It is suitable for API or file-based transfers where rejected or incomplete loads require operational follow-up.
Integration direction
Example Mapping
| SAP Integrated Business Planning Field | Canonical Field | Target Field |
|---|---|---|
| Supplier ID | supplier.externalId | Planning supplier attribute |
| Material or Product | supply.product | Master Data Object product |
| Requested Quantity | supply.quantity | Supply-related Key Figure |
Martini implementation pattern
Martini orchestrates the source extraction, validates supplier and product references, transforms quantities and periods, submits the configured SAP IBP load, and routes validation failures to an exception workflow. Batch identifiers and source counts support replay and reconciliation.
Martini capabilities used
- workflows
- API consumption
- file processing
- mapping
- validation
- conditional routing
- error handling
Applications commonly integrated with SAP Integrated Business Planning
SAP Integrated Business Planning commonly participates in SAP-centered planning architectures and can also exchange planning inputs or outputs with selected non-SAP applications. The exact direction, object coverage, and interface depend on the tenant configuration, planning areas, communication arrangements, and customer planning model.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Exchange products, locations, inventory, sales, supply, and execution data with the planning environment. | SAP S/4HANA → Martini → SAP Integrated Business Planning | Schedule a Martini workflow to retrieve or receive source data, map it to SAP IBP master data or planning levels, validate units and periods, submit it through the selected OData, SOAP, or file interface, and reconcile accepted and rejected records. |
| SAP ECC | Provide legacy ERP master and transactional data to SAP IBP and return selected planning results. | SAP ECC → Martini → SAP Integrated Business Planning | Use scheduled API or file-based extraction, transform SAP ECC structures into the configured SAP IBP model, partition large loads, and persist batch checkpoints for replay. |
| SAP Analytics Cloud | Present forecasts, scenarios, approved plans, and key figures in analytical and planning dashboards. | SAP Integrated Business Planning → Martini → SAP Analytics Cloud | Retrieve approved planning data from SAP IBP, normalize key figures and time dimensions, apply publication rules, and deliver the result through the target application's supported API or file interface. |
| SAP Datasphere | Combine SAP IBP planning data with ERP, finance, and other enterprise data sources. | SAP Integrated Business Planning → Martini → SAP Datasphere | Extract partitioned planning data, preserve SAP identifiers and planning dimensions, transform it into the enterprise analytical model, and load it through the configured target interface with reconciliation totals. |
| SAP Ariba | Coordinate procurement, supplier, and supply-related information with supply planning. | SAP Ariba → Martini → SAP Integrated Business Planning | Orchestrate API or file transfers, validate supplier and planning attributes, route incomplete loads to an exception process, and reconcile submitted and rejected data. |
| SAP SuccessFactors | Provide workforce or organizational planning inputs where they are relevant to broader supply-chain planning. | SAP SuccessFactors → Martini → SAP Integrated Business Planning | Use a controlled scheduled workflow to retrieve approved workforce inputs, map organizational dimensions to the configured planning model, and apply tenant-specific validation before submission. |
| Salesforce | Use sales pipeline, account, product, or opportunity information as demand-planning inputs and return approved planning information to sales operations. | Salesforce → Martini → SAP Integrated Business Planning | Retrieve selected commercial data, apply product and time-bucket mappings, validate demand eligibility, write supported planning inputs to SAP IBP, and expose approved outputs to Salesforce through its supported API. |
| Kinaxis RapidResponse | Exchange planning data when SAP IBP coexists with another supply-chain planning platform or during a migration. | SAP Integrated Business Planning → Martini → Kinaxis RapidResponse | Create a canonical planning model in Martini, transform key figures and planning dimensions in both directions, coordinate batch boundaries, and use reconciliation workflows to identify differences. |
How to build a SAP Integrated Business Planning integration in Martini
Objective
Establish the SAP IBP communication arrangement and Martini environment configuration before implementing business flows.
Instructions in Martini
- Confirm the SAP IBP tenant, communication scenario, endpoint, and technical user
- Configure OAuth 2.0, Basic Authentication, or client certificate access as required
- Store credentials, client identifiers, certificates, and tenant URLs in protected environment configuration
- Verify permissions for planning areas, master data, key figures, and required operations
Objective
Select a trigger that matches the availability of the SAP IBP interface and the required synchronization latency.
Instructions in Martini
- Use a scheduler for polling and recurring planning exchanges
- Use a workflow or API entry point for controlled inbound requests
- Use file processing or SAP application jobs for supported bulk scenarios
- Do not assume a general-purpose SAP IBP webhook trigger
Objective
Read or receive bounded SAP IBP data while avoiding unbounded requests and preserving replay information.
Instructions in Martini
- Use OData filters, pagination, and time or planning partitions
- Retrieve data through the documented SOAP operation where applicable
- Validate file structure before processing exports or imports
- Persist cursors, request identifiers, file identifiers, and batch boundaries
Objective
Coordinate extraction, transformation, validation, target writes, and operational outcomes in one maintainable Martini workflow.
Instructions in Martini
- Separate transport, transformation, validation, and persistence stages
- Use reusable workflow logic for common SAP authentication and response handling
- Apply controlled concurrency around SAP quotas and planning windows
- Route rejected records and technical failures to distinct handling paths
Objective
Translate SAP planning semantics into the target system while preserving identifiers and dimensions.
Instructions in Martini
- Map planning areas, planning levels, master data, key figures, versions, and time profiles explicitly
- Normalize units of measure, currencies, calendars, periods, nulls, and zeros
- Use canonical fields where multiple applications exchange the same planning concept
- Validate required attributes before submitting a load
Objective
Protect planning integrity by applying approval, eligibility, deduplication, and reconciliation rules before writes.
Instructions in Martini
- Define authoritative sources and incremental cursors
- Use deterministic business keys or batch identifiers for idempotency
- Prevent writes to unintended versions or planning areas
- Compare source, submitted, accepted, and rejected counts
Common SAP Integrated Business Planning data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Planning Areas | Define planning models, planning levels, key figures, attributes, and time-related configuration. | SAP S/4HANA, SAP ECC, SAP Analytics Cloud, SAP Datasphere | Martini treats planning-area configuration as integration metadata, validates the active model, and uses it to control mappings and workflow parameters. |
| Master Data Objects | Represent products, locations, customers, resources, and other configured planning attributes. | SAP S/4HANA, SAP ECC, SAP Ariba, Salesforce | Martini extracts or receives master data, maps business keys and attributes, validates required values, and performs supported create or update operations. |
| Key Figures | Store demand, supply, inventory, capacity, forecast, and other measurable planning values. | SAP Analytics Cloud, SAP Datasphere, SAP S/4HANA, Salesforce | Martini maps units, currencies, periods, versions, and planning levels, then writes or publishes values through the relevant configured interface. |
| Planning Data | Represent time-series or other planning values associated with key figures, planning levels, master data, versions, and periods. | SAP S/4HANA, SAP Analytics Cloud, SAP Datasphere, Kinaxis RapidResponse | Martini partitions large extracts, transforms planning dimensions, checkpoints batches, and reconciles source, submitted, accepted, and rejected totals. |
| Time Profiles | Define planning time periods and calendar structures used by planning areas and key figures. | SAP S/4HANA, SAP Analytics Cloud, SAP Datasphere | Martini validates period and calendar mappings and prevents data loads when source periods do not align with the configured profile. |
| Versions | Separate baseline plans, statistical forecasts, and what-if planning scenarios. | SAP Analytics Cloud, SAP Datasphere, SAP S/4HANA | Martini carries version identifiers through mappings, applies publication rules, and prevents accidental writes to an unintended scenario. |
Authentication and security considerations
Communication arrangements and technical users
SAP IBP access is governed by communication systems, communication users, communication arrangements, scopes, and tenant permissions. The available endpoint and authentication method depend on the selected service and configuration.
Authentication and secrets
- Use OAuth 2.0, Basic Authentication, or client certificates only where supported by the SAP scenario.
- Store tenant URLs, credentials, client identifiers, tokens, and certificates in Martini environment configuration or secrets management.
- Assign technical users only the permissions required for the relevant planning areas, objects, and operations.
- Do not log access tokens, private keys, or complete planning payloads containing sensitive business data.
Operational considerations for SAP Integrated Business Planning integrations
Volume and throttling
Use pagination, bounded filters, time windows, and planning-area or planning-level partitions. Confirm SAP IBP and SAP integration-service quotas, control concurrency, and avoid large extracts during critical planning windows.
Reliability and reconciliation
- Use deterministic business keys, upsert behavior where supported, and batch identifiers to prevent duplicates.
- Retry transient HTTP, transport, and service failures with controlled backoff.
- Handle OData errors, SOAP faults, validation errors, rejected records, and partial batch failures separately.
- Persist cursors, rejected payloads, SAP error details, and source-to-target counts for replay and reconciliation.
Configuration and testing
Planning areas, attributes, key figures, time profiles, versions, planning levels, and communication arrangements are configuration-dependent. Use representative test data, contract tests, and environment-specific configuration before promotion.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration instead of isolated scripts
Martini provides a maintainable workflow layer around SAP IBP APIs, SOAP services, scheduled jobs, and files. It can coordinate retrieval, transformation, validation, target writes, retries, and reconciliation without embedding the entire integration in a one-off script.
Stable contracts and reusable logic
Martini can expose APIs that shield downstream systems from tenant-specific SAP configuration, while reusable workflows centralize authentication, pagination, mapping, and error handling.
Operational control
- Apply business rules consistently across SAP and non-SAP applications.
- Checkpoint large planning exchanges and replay failed partitions.
- Separate technical failures from rejected business records.
- Monitor workflow outcomes and preserve operational context for support teams.
Frequently asked questions
SAP Integrated Business Planning can be integrated through OData services, selected SOAP web services, file-based imports and exports, application jobs, and SAP integration services. OData is the primary API approach for many master-data and planning-data scenarios, while the exact interface depends on the tenant's communication arrangements and activated planning configuration.
Yes. Martini can consume SAP IBP OData or REST-style APIs, selected SOAP services, and supported files; schedule synchronization workflows; map planning objects; expose APIs; and implement validation, retry, and reconciliation logic. A dedicated SAP IBP Martini connector was not confirmed.
No. A dedicated connector is not required. Martini can use SAP IBP's confirmed native integration mechanisms, including OData APIs, selected SOAP services, file exchange, scheduled processing, and SAP communication authentication patterns.
Lonti does not charge an additional per-connector or per-vendor fee to integrate SAP Integrated Business Planning. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from SAP, SAP Integration Suite, cloud infrastructure, or other third-party services depending on subscriptions, usage, and deployment model.
Use the interface specified by the relevant SAP IBP communication scenario. OData is the primary API style for many master-data and planning-data operations. SOAP or file-based processing may be more appropriate for selected scenarios, bulk exchanges, or SAP-supported integration flows.
A general-purpose webhook mechanism covering all SAP IBP planning, master-data, or key-figure changes was not confirmed. Integrations should generally use scheduled API polling, application jobs, file exchange, or SAP integration services unless a specific scenario documents an outbound callback.
Large exchanges should use pagination, filters, time windows, planning-area or planning-level partitioning, incremental cursors, and supported batch or file processes. Martini can checkpoint completed partitions, retry failed pages, and reconcile source, submitted, accepted, and rejected totals.
Yes. Martini can expose a controlled API that validates and transforms requests, applies business rules, invokes the appropriate SAP IBP OData or SOAP service, and returns a stable contract to downstream applications. This can reduce direct coupling to tenant-specific SAP configuration.
Related Martini documentation
SAP APIs
Workflows
Plan your SAP Integrated Business Planning integration
Use Martini to design secure, scheduled, and maintainable SAP Integrated Business Planning workflows across APIs, SOAP services, files, and enterprise applications.