Supply Chain Management Blogs by SAP
Expand your SAP SCM knowledge and stay informed about supply chain management technology and solutions with blog posts by SAP. Follow and stay connected.
cancel
Showing results for 
Search instead for 
Did you mean: 
MichaelMack
Advisor
Advisor
979

A guide to the key considerations and strategies for connecting SAP IBP with non-SAP backend systems 

Introduction 

In today's complex business landscape, organizations often rely on multiple systems to manage their operations. To achieve companywide operational planning, it is essential to connect SAP Integrated Business Planning (IBP) with SAP and non-SAP backends. In this blog post, we'll explore the key considerations and strategies for integrating IBP with non-SAP systems. 

Integration Approaches 

Key Architecture Considerations 

To integrate IBP with non-SAP backends, consider: 

  • When integrating IBP with non-SAP backends, it's crucial to consider the requirements for operational planning, the inputs and outputs, and the time horizon for data transmission.  
  • What is the data volume and frequency?  
  • Long term picture: how does the final architecture look like? Is it a temporary solution until backends are moving to SAP? 

What are some key inputs and outputs for operational planning? 

  • Master data: This is the data that defines the structure and characteristics of the planning objects, such as products, locations, location products, resources, transportation lanes and attributes. Master data is typically integrated to IBP as input data. 
  • Key figures: This is the data that represents the quantitative values of the planning objects in time bucketed granularity, such as demand forecast, inventory targets, capacity and costs. Key figures are in- and output of operational planning. 
  • Orders and stock: This is the data that reflects the actual and planned transactions of customer orders, inventory batches, production executions, stock transfers, and planned orders. It also includes details like input and output nodes, source of supply information, and order types. Orders and stock are in- and output of operational planning, depending on the implementation scope. 

What integration approaches are possible? 

There are two main options for integrating IBP with non-SAP backends: 

  1. API based Integration: This method uses OData-compliant APIs to enable real-time data interchange between IBP and other systems. OData is a standard protocol for accessing and manipulating data from various sources. OData can be consumed by various development, business intelligence, data integration, mobile and web development, and data visualization tools. 
  2. Middleware Solutions: This method uses a software layer, such as SAP Cloud Integration (SAP CI) or SAP Cloud Integration for Data Services (SAP CI-DS), to connect IBP with non-SAP backends. Middleware solutions can handle data transformation, routing, and orchestration, and offer a user-friendly interface for integration. 

How can you integrate all inputs and outputs with non-SAP backends for operational planning in SAP IBP?  

  • Master data and key figures: There are 2 options: IBP OData services or using a middleware like SAP Cloud Integration (SAP CI) or SAP Cloud Integration for Data Services (SAP CI-DS). 
    1. You can use available SAP CI/ SAP CI-DS Integration content for IBP, change the data source/target and adjust mapping for a ETL type integration.
    2. OData services are  
  • Orders and stock can be integrated by IBP OData services only. All IBP Order OData APIs follow the same design pattern and allow fast and consistent, bidirectional data integration to Baseline and Planning Versions in SAP IBP. 
    There are currently APIs available for Stock and Purchasing document types.  
    • Stock – in and outbound integration of all available Stock types in SAP IBP. 
      more details
    • Purchasing Documents - in and outbound integration of all available purchasing related documents: Stock transfer and Purchase Requisitions and Orders, Subcontracting Purchase Requisitions and Orders (including subcontracting components), Inbound and Outbound Deliveries.  
      more details  
    • APIs for Production and Sales Order documents are planned on the roadmap. Find here more details:  

Conclusion 

IBP can work with non-SAP backends to enable smooth operational planning, as it lets organizations use the best of both worlds: the powerful planning features of IBP, and the easy and open link to the existing source systems. By doing so, they can achieve end-to-end visibility and collaboration across their supply chain network, and ultimately, lower shortages.