Getting Started with SAP IBP New Harmonized Planning Area (SAPIBP2)

Harmonized Planning Area: Solution Information

The solution offered with the 2508 release in SAP IBP is the Harmonized Planning Area (HPA) where only one planning area will be used for Mid-long term planning with time-series buckets, and short-mid term planning with orders, using the same data model (attributes, master data types, key figures, planning levels, time profile, etc.). The new sample planning area will be called I_SAPIBP2 (The “I” denotes use of name spaces in the planning area.) Here, the “harmonized” master data model will be used by all IBP modules, including order-based supply, time-series supply, inventory, S&OP and demand.

Related Links:

Webinar Harmonized Planning area 2508-PDFWebinar Harmonized Planning area 2508-RecordingIBP 2508 What’s New Introducing I_SAPIBP2The data model and supported functionality can be viewed here I_SAPIBP2 Online Help

SAPIBP2 Technical Pre-requisites:

HANA Cloud

Customers that are not on HANA Cloud 2.0 must request a tenant migration prior to starting with SAPIBP2 (HPA)

For details refer to SAP Note 3217536 IBP: Upgrade to HANA Cloud – Overview for customers and partners

Real Time Integration (RTI)

RTI is mandatory for Order-Based Planning (OBP).

For those customers who do not have RTI installed yet, start with the Central RTI note: 3110007 – IBP Real-time Integration: Information/Restrictions. The note contains all the information that you need to start with the implementation including the current restrictions as well as the technical prerequisite within the notes.

Note: Please ensure that the prerequisites mentioned in the note are met!

To start with the RTI setup we strongly recommend to use :

The setup-check list (link in the note)We strongly recommend to use CIAS (Cloud Integration Automation Service) to setup the connection between IBP, the cloud connector and your ECC (link to CIAS in the note). This will reduce the time for the setup significantly, specially for the part with the BTP connector.

To use RTI with your ECC, check SAP note 3106619 – SAP IBP Real-time integration – Notes for installation.

It contains for each SAP ERP or SAP S/4 HANA the required service packs or – if not applicable – the notes that must be installed.PLEASE NOTE: to use the RTI functionality for a certain IBP version you MUST install ALL notes of the previous version as well in the given sequence. After the installation of the service packs or the notes there are additional notes with corrections, bug fixes etc.Do also check all notes related to the SNOTE tool and install any fixes.Plan for sufficient time and resources (experienced analyst or developer with ABAP workbench and SNOTE experience).

RTI FAQ with links to webinars: FAQs: SAP IBP Real-Time Integration and Transition from SDI

Further information:

Usage of CIAS to setup RTI efficiently:

Configuring RTI Connectivity with Cloud Integration Automation Service (CIAS) | SAP Help PortalFast track your SAP IBP Real time integration jour… – SAP CommunityExtending Efficiency: Automating IBP RTI Connectiv… – SAP Community

Important note: All the projects that are starting with time series planning and eventually want to get to order based planning, we strongly advise getting started with RTI early so that the integration infrastructure doesn’t have to change at a later point in the project.

Restrictions 2640432 – Details on Restrictions for SAP IBP Order-Based Planning – SAP for Me

Integration Strategy: RTI, CI, CIDS:

RTI is the recommended and future-proof integration technology for both order-based and time series planning in HPA, advising early adoption to ensure consistent master data flows and minimize future architectural changes.While CIDS will continue to be supported existing customers, new development and investment are shifting toward CI. CIDS will be removed from the IBP product bundle in 2026, but current users can continue using it for their existing processes. Recommended use of CI (Cloud Integration) and the development of custom integration flows (iflows), with the recommendation to leverage existing reusable iflows where possible and supplement with CIDS as needed until future releases provide more comprehensive coverage.

Frequently Asked Questions (FAQ):

S. No

Question

Answered by EAC Team

DC (XPC) is not yet HANA Cloud ready.

Work is being done around this and there will soon be an update.

If a key figure in HPA is using the new UoM conversion – do we need to pass the UoM to the CI-DS for extraction?

when using the new UoM conversion the planning area must contain the conversion attributes. The new UoM conversion generates automatically the calculations. To CI-DS the calculation view contains in the metadata the attribute I_UOMTOID. This can be set for filtering on a specific UoM

Is CIDS supported with IBP2508?

CI is strategic and advisable for long run. Existing customers may continue to use CI-DS. For HPA projects, we advise using RTI as the primary integration mechanism for master data (and orders, stocks, etc), so it is consistent between TSP and OBP.

Do I have to integrate on one hand via CIDS and in parallel via RTI and all the developments we did in the in the back end system to enrich the data. Do I have then to implement everything again?

In case you want to use through all the processes the same data and you have the corresponding data in your S4 system, the then the recommendation is definitely to use RTI so that you get then the master data synchronized between all applications from one single point. There are extensions available so you can extend RTI up to a certain point.

How do I raise a customer Influence request for IBP?

With a valid S-User you can raise this here.

How do objects in IBPSAP7F relate to objects in HPA.

Will be shared soon.

Is this now an RTI periodic job?

S/4 -> IBP = real time IBP ->S/4 = depending on your requirement, it can be real-time or as batch job (system settings)

Which notes do I have to implement?

3106619 – SAP IBP Real-time integration – Notes for installation – SAP for Me. Read & implement it from top down

RTI outbound integration – is it possible to differentiate STRs? eg: deployment STRs vs DRP STR

Yes, PReq and STR can be differentiated when selecting, but not between normal STR and Deployment STR

Recommendation of implementing Supply and Response and IO in one planning area with HPA?

The recommendation is context specific, so “it depends”. There are three scenarios. (1) Most customers group IO with supply due to technical alignment on network master data. But some IBP customers view IO as part of the demand consensus business process (combining forecasting and risk/safety management), so they either (2) group IO with demand or (3) keep it in a separate PA.

Do existing customer have to pay additionally for CI-DS license if they want to continue?

No change for existing customers. New customers that get their system beyond Q1/2026 will not receive a CIDS Org as a bundle with IBP but must license CI additionally.

Is SAP CI different from BTP-Integration Suite (Cloud Platform Integration) ? or is it the new name for the same tool? If it is the same, are there many pre-delivered IBP flows which can be configured in the ‘design’ tab of the Integration Suite environment?

SAP BTP Integration Suite is the umbrella offering, and CI is one of its core services. CI is part of the BTP integration suite, and we do have iFlows. But at the moment, the pre-delivered iFlows is pretty limited. We are working on more flows.

Is ‘segmentation’ in S/4 mandatory to use CBP in IBP or is ‘classification’ in S/4 sufficient?

Officially released is the segmentation only. For other classes, you may need to implement some BADI. But please note that CBP is not in the MVP (Minimum Viable Product) for HPA. IBP CBP and order-based shelf life planning is planned for inclusion in I_SAPIBP2 in the February release 2602. (Depending of course on successful QA.)

if there is any functionality planned in the roadmap that would allow for selective export of specific planning area objects—such as key figures, planning levels —to a higher system in the landscape, rather than exporting the entire planning area configuration

Nothing on the roadmap as such.

Is there an ability to trigger CI jobs directly from IBP or can they only be triggered/scheduled directly in CI?

As of today, only via CI directly. But that is a roadmap item and currently planned for early next year (but legal disclaimer, changes can come at any point in time)

Planned Independent Requirements (Forecast) please – is it going to be part of the CFM1 selection screen as other transactional data types? This would help to enable proper FC consumption and its synchronization between S4 and OBP.

No, forecast is not coming over via RTI

CBP is not part of EAC program?

For CBP restrictions, please check as well on

2640432 – Details on Restrictions for SAP IBP Order-Based Planning – SAP for Me –> search for “Characteristic Based Planning (CBP)”

and 3422877 – Prerequisites and Restriction with Characteristic Based Planning (CBP) in response and su…

especially
“In the backend:

1)You have implemented all notes relevant for CBP, see (SAP Note 3435209 – Characteristic Based Planning (CBP) and E2E integration support with backend processes)

2)You either use
a)segmentation in S/4HANA
b)batch classification for stock only and/or implement RTI BAdI on backend side (from ERP EHP4 or S/4HANA)
“

But you can still proceed, because you can add CBP functionality later, does not need to be used from the very beginning

What are the efforts/estimates to move from CIDS to CI?

there is no automatic tool for migration from CI-DS to CI. Therefore you would need to start over. The target is that we replace most of the data flow with RTI. And you dont need to replace a CI-DS flow for e.g. Sales History, you can just copy and re-map it to the new planning area. As existing customer, you still have the license for CI-DS. If you WANT to create new CI flows, you can still use the same source in S/4 which potentially uses the addon. So for an experienced person it should take a couple of hours for a flow.

We are planning to use RTI as much as possible but we have a few additional attributes at Product and Location Product master data level, currently these attributes are maintained in a Custom table, if we integrate these with RTI BADI then how can trigger a change pointer when an attribute value is updated in the Custom table

Support document link on the same will be shared soon.

Given that we will focus only on S&OP processes for the moment, and that their S/4HANA system (2023 FPS1) will only be upgraded to a higher release in 2026, is it technically feasible and supported to implement RTI inbound integration in the meantime by applying only the HPA-relevant notes below, without upgrading to the latest FPS (staying on S/4 2023 FPS1) or applying all other required SAP Notes manually ?

Need to apply all the notes that are listed in the central sub notes. So you start basically at your current release and you need to upgrade at least to the point where HPA was introduced, simply applying the nodes that are HPA relevant. (https://me.sap.com/notes/3106619/E)

What is your suggestion either to go with CI or CIDS, along with RTI between S4 and IBP, Considering we already have CIDS between IBP and BW/BI. And which integration is preferable between Datasphere and IBP

Datasphere is a cloud solution, and there you should go with CI.

[Data models]

Will the OKF always remain on that granularity of “Sales Order new”, “Sales order released” , “Sales order confirmed” etc. – for Supply planning for example it is sufficient to have the “Sales orders (all open)” as an aggregate if you run weekly buckets for example.

OKF aggregate single order from the backend tables on order level to planning level of the KF they are working on, that would be e.g. all all requested Sales Order on level i_DayProdLocDemand

You may not need that details for Supply Planning, but in order-based planning we need the differentiation whether a sales order is requested, or confirmed, or confirmed in time, or confirmed late etc.

“Sales Order new” or “Sales order released” dont exist

Is there a list of Cached Key figures. On key figure is there a property that indicates that it is a cached KF.

All order key figure in i_SAPIBP2 are OKF key figures, and they have a different symbol:

Is there a possibility to get a more detailed roadmap of the features that will become available in the future? Examples are custom attributes in the priority manager, fixed setup times etc.

On Custom attributes: currently these customer attributes cannot be used in the demand prioritization. It’s a coming feature. No fixed schedule for this, but this will be delivered soon.

It’s something with respect to extensibility of OBP data structures.

Is there a plan to support non-time based UoM for production resources?

There are possibilities to use other UOMS in S4 but you need to do some additional customizations that are not so common and there must be also BADI implemented and so on. If anymore use cases are identified, please feel free to open a customer influence request on this so that we can then get a broader overview.

Validity of the transportation lane– when will this feature be available?

Supported by IO. In supply planning, plan is to make it available in next 2 releases.

Regarding the triggering of CI jobs through IBP. Is that still on target for 2602?

Yes, the application job is on target for 2602

when we copy HPA, we can only create a new version from the version we have in sample planning area

So my question is how will it work in the future? Let’s imagine in the current version of HPA 2511 we have our developments, our new key figures, new calculations or whatever you must data types and then in February we want to update or refresh.

Our version with the new changes that you guys from SAP are going to implement probably in the next release. What is the suggestion from SAP then? How do we make sure that the new changes from the new version of HPA are incorporated into our version but our developments are not lost?

Unfortunately at the moment we do not have a lifecycle management in place that for example semi automatically updates the content of existing planning areas. However, there is currently a manual process to do so but at the moment this is more into the product direction feature.

prefix for attribute descriptions like location ID 2, location description 2 still remain after copying planning area to latest version in the same development system.

Suggestion was to raise a ticket so that development team can look into it.

Can we integrate characteristics or custom fields for batches to OBP ? now as far as I see in the current BAdi structure, it’s not possible to enhance existing structures, let’s say with the custom fields. So will it part of the future releases?

OSS note raised. Team to get back with a solution

Scheduling agreements capability in future releases. How will the merge to the latest versions of HPA to standard planning area

Manually merge of keyfigures is the only way currently. Compare planning area application in IBP offers enhanced UI to help identify any changes done in the PA

Is custom BAdi development for any master data (not part of standard RTI model) possible through RTI integration?

custom BAdi enhancements are possible, but only for attributes on existing master data types. For complete new additional master data types, I’m afraid I think this is not possible. They behave more like time series master data, so you would need to integrate them through CI

Integration of CI scheduling with application job templates

On Roadmap for 2602

CI is also supported with on premise or is it still on the cloud?

it is available for S/4 HANA on Premise as well, there is a need for a Cloud Connector.

How much adjustments will be needed to adapt our existing RTI BAdI implementations for 7F to work with HPA. We’ve already made enhancements for 7F, but are unsure how different HPA will be—especially considering changes in master data types—and whether significant rework will be required.

If you use only the OBP functionality in HPA, generally no adaptation needed in the RTI BAdIs.
The RTI BadIs were enhanced with additional attributes to cover the additional use cases for the other IBP application (TS-supply, inventory…)

for HPA we will need to enhance or to develop new BAdis apart of those that we already developed for RTI.

There are no new BadIs – only compatible enhancements in the existing BAdIs

Roadmap for Substitutions? Product substitution and component substitution

probably in middle of next year.

how can we control the dataflow in the RTI because SAP7F and HPA have different master data models for production. Do we need to use two different logical systems in S/4 to connect to both planning areas in IBP?

For every target planning area in IBP (SAP7F, HPA) an sperate “RTI connectivity” is needed. With this 2 different destinations in ERP (S/4) are available. Every destination is connected through the integration profile to a dedicated planning area.

In every RTI Badi (methods outbound = ERP->IBP) the destination is available as an input parameter. This means that you can decide within the BAdI implementation, to what planning area you’re integrating.

Watch this space for more updates! 😊

This blog has been created for the sole purpose of helping customers looking to implement the new Harmonized Planning Area (HPA) in their IBP landscape. It contains all the technical pre-requisites with links, important tips and FAQs to help you kick-start with your HPA adoption journey. Harmonized Planning Area: Solution InformationThe solution offered with the 2508 release in SAP IBP is the Harmonized Planning Area (HPA) where only one planning area will be used for Mid-long term planning with time-series buckets, and short-mid term planning with orders, using the same data model (attributes, master data types, key figures, planning levels, time profile, etc.). The new sample planning area will be called I_SAPIBP2 (The “I” denotes use of name spaces in the planning area.) Here, the “harmonized” master data model will be used by all IBP modules, including order-based supply, time-series supply, inventory, S&OP and demand.Related Links:Webinar Harmonized Planning area 2508-PDFWebinar Harmonized Planning area 2508-RecordingIBP 2508 What’s New Introducing I_SAPIBP2The data model and supported functionality can be viewed here I_SAPIBP2 Online HelpSAPIBP2 Technical Pre-requisites:HANA CloudCustomers that are not on HANA Cloud 2.0 must request a tenant migration prior to starting with SAPIBP2 (HPA)For details refer to SAP Note 3217536 IBP: Upgrade to HANA Cloud – Overview for customers and partners Real Time Integration (RTI)RTI is mandatory for Order-Based Planning (OBP).For those customers who do not have RTI installed yet, start with the Central RTI note: 3110007 – IBP Real-time Integration: Information/Restrictions. The note contains all the information that you need to start with the implementation including the current restrictions as well as the technical prerequisite within the notes.Note: Please ensure that the prerequisites mentioned in the note are met!To start with the RTI setup we strongly recommend to use :The setup-check list (link in the note)We strongly recommend to use CIAS (Cloud Integration Automation Service) to setup the connection between IBP, the cloud connector and your ECC (link to CIAS in the note). This will reduce the time for the setup significantly, specially for the part with the BTP connector.To use RTI with your ECC, check SAP note 3106619 – SAP IBP Real-time integration – Notes for installation.It contains for each SAP ERP or SAP S/4 HANA the required service packs or – if not applicable – the notes that must be installed.PLEASE NOTE: to use the RTI functionality for a certain IBP version you MUST install ALL notes of the previous version as well in the given sequence. After the installation of the service packs or the notes there are additional notes with corrections, bug fixes etc.Do also check all notes related to the SNOTE tool and install any fixes.Plan for sufficient time and resources (experienced analyst or developer with ABAP workbench and SNOTE experience).RTI FAQ with links to webinars: FAQs: SAP IBP Real-Time Integration and Transition from SDIFurther information:Usage of CIAS to setup RTI efficiently:Configuring RTI Connectivity with Cloud Integration Automation Service (CIAS) | SAP Help PortalFast track your SAP IBP Real time integration jour… – SAP CommunityExtending Efficiency: Automating IBP RTI Connectiv… – SAP CommunityImportant note: All the projects that are starting with time series planning and eventually want to get to order based planning, we strongly advise getting started with RTI early so that the integration infrastructure doesn’t have to change at a later point in the project.Restrictions 2640432 – Details on Restrictions for SAP IBP Order-Based Planning – SAP for Me Integration Strategy: RTI, CI, CIDS:RTI is the recommended and future-proof integration technology for both order-based and time series planning in HPA, advising early adoption to ensure consistent master data flows and minimize future architectural changes.While CIDS will continue to be supported existing customers, new development and investment are shifting toward CI. CIDS will be removed from the IBP product bundle in 2026, but current users can continue using it for their existing processes. Recommended use of CI (Cloud Integration) and the development of custom integration flows (iflows), with the recommendation to leverage existing reusable iflows where possible and supplement with CIDS as needed until future releases provide more comprehensive coverage.Frequently Asked Questions (FAQ): S. NoQuestionAnswered by EAC Team1DC (XPC) is not yet HANA Cloud ready.Work is being done around this and there will soon be an update.2If a key figure in HPA is using the new UoM conversion – do we need to pass the UoM to the CI-DS for extraction?when using the new UoM conversion the planning area must contain the conversion attributes. The new UoM conversion generates automatically the calculations. To CI-DS the calculation view contains in the metadata the attribute I_UOMTOID. This can be set for filtering on a specific UoM3Is CIDS supported with IBP2508? CI is strategic and advisable for long run. Existing customers may continue to use CI-DS. For HPA projects, we advise using RTI as the primary integration mechanism for master data (and orders, stocks, etc), so it is consistent between TSP and OBP.4Do I have to integrate on one hand via CIDS and in parallel via RTI and all the developments we did in the in the back end system to enrich the data. Do I have then to implement everything again?In case you want to use through all the processes the same data and you have the corresponding data in your S4 system, the then the recommendation is definitely to use RTI so that you get then the master data synchronized between all applications from one single point. There are extensions available so you can extend RTI up to a certain point.5How do I raise a customer Influence request for IBP?With a valid S-User you can raise this here.6How do objects in IBPSAP7F relate to objects in HPA. Will be shared soon.7Is this now an RTI periodic job?S/4 -> IBP = real time IBP ->S/4 = depending on your requirement, it can be real-time or as batch job (system settings)8Which notes do I have to implement?3106619 – SAP IBP Real-time integration – Notes for installation – SAP for Me. Read & implement it from top down9RTI outbound integration – is it possible to differentiate STRs? eg: deployment STRs vs DRP STR Yes, PReq and STR can be differentiated when selecting, but not between normal STR and Deployment STR10Recommendation of implementing Supply and Response and IO in one planning area with HPA?The recommendation is context specific, so “it depends”. There are three scenarios. (1) Most customers group IO with supply due to technical alignment on network master data. But some IBP customers view IO as part of the demand consensus business process (combining forecasting and risk/safety management), so they either (2) group IO with demand or (3) keep it in a separate PA.11Do existing customer have to pay additionally for CI-DS license if they want to continue?No change for existing customers. New customers that get their system beyond Q1/2026 will not receive a CIDS Org as a bundle with IBP but must license CI additionally.12Is SAP CI different from BTP-Integration Suite (Cloud Platform Integration) ? or is it the new name for the same tool? If it is the same, are there many pre-delivered IBP flows which can be configured in the ‘design’ tab of the Integration Suite environment? SAP BTP Integration Suite is the umbrella offering, and CI is one of its core services. CI is part of the BTP integration suite, and we do have iFlows. But at the moment, the pre-delivered iFlows is pretty limited. We are working on more flows.13Is ‘segmentation’ in S/4 mandatory to use CBP in IBP or is ‘classification’ in S/4 sufficient? Officially released is the segmentation only. For other classes, you may need to implement some BADI. But please note that CBP is not in the MVP (Minimum Viable Product) for HPA. IBP CBP and order-based shelf life planning is planned for inclusion in I_SAPIBP2 in the February release 2602. (Depending of course on successful QA.)14if there is any functionality planned in the roadmap that would allow for selective export of specific planning area objects—such as key figures, planning levels —to a higher system in the landscape, rather than exporting the entire planning area configurationNothing on the roadmap as such.15Is there an ability to trigger CI jobs directly from IBP or can they only be triggered/scheduled directly in CI?As of today, only via CI directly. But that is a roadmap item and currently planned for early next year (but legal disclaimer, changes can come at any point in time)16Planned Independent Requirements (Forecast) please – is it going to be part of the CFM1 selection screen as other transactional data types? This would help to enable proper FC consumption and its synchronization between S4 and OBP.No, forecast is not coming over via RTI17CBP is not part of EAC program?For CBP restrictions, please check as well on 2640432 – Details on Restrictions for SAP IBP Order-Based Planning – SAP for Me –> search for “Characteristic Based Planning (CBP)”and 3422877 – Prerequisites and Restriction with Characteristic Based Planning (CBP) in response and su… especially “In the backend: 1)You have implemented all notes relevant for CBP, see (SAP Note 3435209 – Characteristic Based Planning (CBP) and E2E integration support with backend processes)2)You either use a)segmentation in S/4HANAb)batch classification for stock only and/or implement RTI BAdI on backend side (from ERP EHP4 or S/4HANA) “But you can still proceed, because you can add CBP functionality later, does not need to be used from the very beginning18What are the efforts/estimates to move from CIDS to CI?there is no automatic tool for migration from CI-DS to CI. Therefore you would need to start over. The target is that we replace most of the data flow with RTI. And you dont need to replace a CI-DS flow for e.g. Sales History, you can just copy and re-map it to the new planning area. As existing customer, you still have the license for CI-DS. If you WANT to create new CI flows, you can still use the same source in S/4 which potentially uses the addon. So for an experienced person it should take a couple of hours for a flow.19We are planning to use RTI as much as possible but we have a few additional attributes at Product and Location Product master data level, currently these attributes are maintained in a Custom table, if we integrate these with RTI BADI then how can trigger a change pointer when an attribute value is updated in the Custom table Support document link on the same will be shared soon.20Given that we will focus only on S&OP processes for the moment, and that their S/4HANA system (2023 FPS1) will only be upgraded to a higher release in 2026, is it technically feasible and supported to implement RTI inbound integration in the meantime by applying only the HPA-relevant notes below, without upgrading to the latest FPS (staying on S/4 2023 FPS1) or applying all other required SAP Notes manually ?Need to apply all the notes that are listed in the central sub notes. So you start basically at your current release and you need to upgrade at least to the point where HPA was introduced, simply applying the nodes that are HPA relevant. (https://me.sap.com/notes/3106619/E)21What is your suggestion either to go with CI or CIDS, along with RTI between S4 and IBP, Considering we already have CIDS between IBP and BW/BI. And which integration is preferable between Datasphere and IBPDatasphere is a cloud solution, and there you should go with CI.22[Data models] Will the OKF always remain on that granularity of “Sales Order new”, “Sales order released” , “Sales order confirmed” etc. – for Supply planning for example it is sufficient to have the “Sales orders (all open)” as an aggregate if you run weekly buckets for example.OKF aggregate single order from the backend tables on order level to planning level of the KF they are working on, that would be e.g. all all requested Sales Order on level i_DayProdLocDemandYou may not need that details for Supply Planning, but in order-based planning we need the differentiation whether a sales order is requested, or confirmed, or confirmed in time, or confirmed late etc. ”Sales Order new” or “Sales order released” dont exist23Is there a list of Cached Key figures. On key figure is there a property that indicates that it is a cached KF.All order key figure in i_SAPIBP2 are OKF key figures, and they have a different symbol: 24Is there a possibility to get a more detailed roadmap of the features that will become available in the future? Examples are custom attributes in the priority manager, fixed setup times etc.On Custom attributes: currently these customer attributes cannot be used in the demand prioritization. It’s a coming feature. No fixed schedule for this, but this will be delivered soon.It’s something with respect to extensibility of OBP data structures.25Is there a plan to support non-time based UoM for production resources?There are possibilities to use other UOMS in S4 but you need to do some additional customizations that are not so common and there must be also BADI implemented and so on. If anymore use cases are identified, please feel free to open a customer influence request on this so that we can then get a broader overview.26Validity of the transportation lane– when will this feature be available?Supported by IO. In supply planning, plan is to make it available in next 2 releases.27Regarding the triggering of CI jobs through IBP. Is that still on target for 2602?Yes, the application job is on target for 260228when we copy HPA, we can only create a new version from the version we have in sample planning areaSo my question is how will it work in the future? Let’s imagine in the current version of HPA 2511 we have our developments, our new key figures, new calculations or whatever you must data types and then in February we want to update or refresh.Our version with the new changes that you guys from SAP are going to implement probably in the next release. What is the suggestion from SAP then? How do we make sure that the new changes from the new version of HPA are incorporated into our version but our developments are not lost?Unfortunately at the moment we do not have a lifecycle management in place that for example semi automatically updates the content of existing planning areas. However, there is currently a manual process to do so but at the moment this is more into the product direction feature.29prefix for attribute descriptions like location ID 2, location description 2 still remain after copying planning area to latest version in the same development system.Suggestion was to raise a ticket so that development team can look into it.30Can we integrate characteristics or custom fields for batches to OBP ? now as far as I see in the current BAdi structure, it’s not possible to enhance existing structures, let’s say with the custom fields. So will it part of the future releases?OSS note raised. Team to get back with a solution31Scheduling agreements capability in future releases. How will the merge to the latest versions of HPA to standard planning areaManually merge of keyfigures is the only way currently. Compare planning area application in IBP offers enhanced UI to help identify any changes done in the PA32Is custom BAdi development for any master data (not part of standard RTI model) possible through RTI integration?custom BAdi enhancements are possible, but only for attributes on existing master data types. For complete new additional master data types, I’m afraid I think this is not possible. They behave more like time series master data, so you would need to integrate them through CI33Integration of CI scheduling with application job templatesOn Roadmap for 260234CI is also supported with on premise or is it still on the cloud?it is available for S/4 HANA on Premise as well, there is a need for a Cloud Connector.35How much adjustments will be needed to adapt our existing RTI BAdI implementations for 7F to work with HPA. We’ve already made enhancements for 7F, but are unsure how different HPA will be—especially considering changes in master data types—and whether significant rework will be required.If you use only the OBP functionality in HPA, generally no adaptation needed in the RTI BAdIs.The RTI BadIs were enhanced with additional attributes to cover the additional use cases for the other IBP application (TS-supply, inventory…)36for HPA we will need to enhance or to develop new BAdis apart of those that we already developed for RTI.There are no new BadIs – only compatible enhancements in the existing BAdIs37Roadmap for Substitutions? Product substitution and component substitutionprobably in middle of next year.38how can we control the dataflow in the RTI because SAP7F and HPA have different master data models for production. Do we need to use two different logical systems in S/4 to connect to both planning areas in IBP?For every target planning area in IBP (SAP7F, HPA) an sperate “RTI connectivity” is needed. With this 2 different destinations in ERP (S/4) are available. Every destination is connected through the integration profile to a dedicated planning area.In every RTI Badi (methods outbound = ERP->IBP) the destination is available as an input parameter. This means that you can decide within the BAdI implementation, to what planning area you’re integrating.Watch this space for more updates! 😊 Read More Technology Blog Posts by SAP articles

#SAP

#SAPTechnologyblog