Harmonized Planning Area

The idea behind the harmonized planning area (HPA) concerns mid-long-term supply demand and inventory planning with time series buckets (which is what is enabled now with the sample planning area, SAPIBP1, from a technical perspective), also including short—and mid-term supply planning with orders. What is currently supported with two planning areas in customers' implementation can now be done in one planning area (with the technical name SAPIBP2) and with at least one proposed default integration technology.

Several innovations are involved, starting with the new aligned data model. This is key to planning, as every application will understand it, and every function will support it.

The application mapping is on top of the aligned data model. The redesigned mapping layer is an abstraction layer for decoupling the applications from the data model.

The applications were enabled to access the aligned data model. New engine APIs will be introduced in the HPA's backend. Huge investments have also been made in heuristics and optimizers to support this new data model.

Since there will be many improvements in information exchange capabilities between applications (for example, dedicated functions to translate data from time series data into order data), process enablement for complicated real-world planning will provide the most value to the customers.

The first shipment of this planning area was for release 2508. With it, the focus is on integrating as many features as possible from the existing functionality of SAPIBP1 (time series) and SAP7F (order-based) into the new planning area, SAPIBP2. With the release 2508, the prerequisites for all future developments on SAPIBP2 were established, ensuring that future requirements are anticipated, existing prohibitive dependencies are resolved (decoupling principle), and local functions are consolidated as much as possible into one function (reuse principle).

The aligned data model is future-ready. Since multiple applications use the same data model, requirements are addressed ahead of time, and the model is shipped aligned even though not all applications have consumed it (there might be different timelines for different applications).

The planning area SAPIBP2 is the visible artifact for the aligned data model. In that planning area, the namespace concept is introduced. The new SAP namespace I_ applies to master data types, planning levels, attributes, and key figures. Time profiles remain the same as today. The customer namespace will be without the underscore.

In summary, the value of the aligned data model comes from:

• TCO Reduction
  • Only one set of master data for all applications
  • No redundant data and corresponding synchronization issues
  • Easier setup of UOM conversion
• Content Protection

  No unintended overwrites or issues for Customer Content by SAP or Partner (same for Partner Content)

The configured data model was achieved with SAP7F. Its value lies in enabling greater extensibility to better meet requirements and serving as a basis for future enhancements.

Application Mapping is an abstraction layer between configured data model and static application interfaces. It allows consumption by all applications that have been decoupled from planning areas. This central application mapping replaces all existing mappings.

The value to the customer is ease (one Fiori app) and flexibility. The customer can combine different applications in the same planning area. The customer can also decide to decouple due to their business process, such as using different calendars. Remapping the standard SAP business meaning to a different attribute (possibly custom attribute) for application A and another for application B is easy.

Application mapping incorporates validation checks based on the application requirements related to data type, length, etc., to provide better model/data quality.

Application mapping enables the usage of different key figures in different versions.

Additionally, visibility is improved. The customer can see explicitly what kind of information the application uses from a planning area with thousands of artifacts.

As the structural differences between different models were removed, the value of consistency was realized. Consistency ensures that all applications use the same data model in the same way, or at least in a compatible way. The same mapping UI is available across all applications, making it easier for users to consume and maintain.

The RTI-integrated master data is available for time series-based planning. Order data is read-only for time series-based planning.

The value to the customer is in the ability to choose the integration pattern independently from the planning application they want to implement.

This element will largely enable customers to combine applications into combined business planning processes.

The resolution of barriers, the elimination of technical mismatches in the planning processes, and the enablement of new cross-application planning processes (including integration) generate significant value.

The following enablers can be noted:

• Enabled Information Exchange between Applications

  All planning area objects in the component CORE ensure the same understanding by all apps that share content

  • Direct exchange without the need to copy key figures for technical reasons
  • Same information used for multiple applications (a break-out via Application Mapping is possible)
• Respect for Horizons
  • No planning or consideration of input data beyond the end of the planning horizon
  • Consideration of input data in the frozen horizon, but no creation of data
• Respect the scope of planning

  If the scope of planning is a subset of the supply chain, then no creation of data beyond the defined subset

• Consider Confirmed Input Data As-is

  Confirmed Input Data must not be recalculated to eliminate subsequent errors in planning results

• Support Calculated Key Figures as Input

  All Time Series Planning Algorithms will be able to read calculated key figures as input (including Order Key Figures)

• Function to Create Orders from Key Figure Values

  Time Series Planning results can be transformed into orders

  • To be used as input for order-based planning
  • To be integrated into S/4 SAPHANA using RTI