What’s New in SAP IBP 2605
Release Brief
Sneak Preview · May 2025

What’s New in
SAP IBP 2605

The 2605 release is measured rather than monumental — but beneath the surface it delivers meaningful progress in supply planning flexibility, integration openness, and AI-assisted decision-making.

Release2605
PublishedMay 2025
DomainSupply Chain Planning
AuthorSmartCons · SAP Practice
01

Integration Developments

oData APIs & Real-Time Integration

oData API — Key Figure & Master Data Extract/Load

SAP IBP 2605 formalises direct integration into the SAPIBP2 planning area via a set of oData APIs. For consultants and architects managing hybrid landscapes, this is a welcome shift toward standardisation — replacing bespoke integration patterns with sanctioned, documented endpoints.

Provided oData Endpoints
  • /IBP/PLANNING_DATA_API_SRV
  • /IBP/MASTER_DATA_API_SRV
  • /IBP/EXTRACT_ODATA_SRV

These APIs open significant flexibility for organisations exchanging data with third-party systems, data lakes, or custom analytics platforms — without relying solely on SAP-native middleware.

Real-Time Integration — Outbound Pegging Data

SAP IBP can now export pegging information from Order Based Planning areas to SAP ECC or S/4HANA. Activation requires setting global parameter RTI_OUTBOUND_PEGGING_EXTRACTION to YES.

Implementation Note

Downstream systems such as ECC or S/4HANA do not natively recognise pegging data — it must be handled, stored, and reported separately. However, this integration bridges planning to execution and can meaningfully support order confirmation and ATP processes.

02

Supply Planning Enhancements

VMI · Sources of Supply · Telescopic

VMI — Vendor Managed Inventory Planning

The headline feature of this release for supply planning practitioners. SAP has extended Order Based Planning to natively support VMI processes — enabling organisations to plan VMI locations and output VMI Sales Orders to downstream systems.

This capability is exclusive to Order Based Planning (SAPIBP2). Time-series planning remains unsupported, meaning mid-to-long-term VMI replenishment will still require workarounds in the interim.

Multiple Validity Periods for Sources of Supply

A long-overdue enhancement: IBP now supports validity periods for Sources of Supply. SAPIBP2 covers both PDS and Transportation Lane validity, while SAP7F supports PDS validity only.

SAPIBP2
PDS + Transport Lane validity
SAP7F
PDS validity only

Previously, customers were forced into workarounds to manage source-of-supply validity in Order Based Planning. This brings the system in line with standard supply chain practice and reduces custom configuration overhead.

Telescopic Planning — Now Available for SAPIBP2

Telescopic planning — which allows different granularity across different time horizons — is now available for SAPIBP2. Previously accessible only in SAPIBP1 and SAP7(F), this closes a meaningful capability gap for customers on the newer planning area.

Customers can now plan at weekly granularity in the near term and monthly in the extended horizon — within the same planning run and area.

03

AI Capabilities

Safety Stock · Working Capital Insights

Financial Impact Insights — AI-Assisted Inventory Optimisation

A small but meaningful addition to the AI-assisted inventory optimisation module. Users can now view working capital insights correlated with changes in AI-recommended safety stock levels — providing a financial lens alongside the operational recommendation.

This creates a clearer business case for safety stock decisions — bridging supply chain planning and finance stakeholders, a recurring friction point in large-scale IBP implementations.

04

General Announcements

CI-DS Sunset · RTI Direction

CI-DS — No Longer Available for New Clients

SAP has announced that CI-DS (Cloud Integration for Data Services) will no longer be available to new IBP clients. Going forward, any organisation procuring SAP IBP licenses must adopt Real-Time Integration (RTI) as the foundational integration layer alongside CI.

Advisory

Existing clients on CI-DS should evaluate their integration roadmap in light of this deprecation signal. New implementations should architect around RTI from day one to avoid costly rework.

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top