Hello, SAP Community members! 

If you have worked with the Partitioning in SAP Profitability and Performance Management On-Premise, you already know how powerful it is. The ability to split a large dataset into ranges and run your processing functions package by package is, in many models, the difference between a job that completes in minutes and one that ties up your system for hours. The idea is elegant: define your ranges once at design time, and the engine does the rest. 

For SAP Profitability and Performance Management Cloud Standard Model customers, this raises a natural question: does the Cloud Partitioning give me the same control I had On-Premise, including the ability to determine ranges dynamically at runtime rather than locking them in at design time? With the introduction of Dynamic Packaging Type, the answer is yes. 

The Dynamic Packaging Type in SAP Profitability and Performance Management Cloud Standard Model follows the same principle as its On-Premise counterpart: ranges are no longer pre-defined as inner nodes but are determined at runtime from the input data of the function where partitioning is applied. For background on the On-Premise partitioning and packaging setup, see the SAP Help Portal documentation.

Meet the Dynamic Packaging Type in Partitioning

The Dynamic Packaging Type is found in the Partitioning within the General Entities. This is a new packaging option that brings a fundamentally different approach to how processing operations are split across data ranges at runtime. Until now, only Static packaging was available in SAP Profitability and Performance Management Cloud Standard Model; you define your ranges as inner nodes at design time, and those ranges are fixed for every run. 

One key structural difference worth knowing upfront: with Dynamic Packaging, you no longer define range nodes inside the Partitioning at all. Any range nodes previously defined inside a Static Packaging are removed when you switch to Dynamic. The ranges are built fresh at runtime, derived from the input function entries of the function where dynamic partitioning is applied.

Configuring the Partitioning: Packaging Type

Expand the Partitioning in your model. The Properties panel now includes the new field placed directly after Run Mode. 

Packaging Type: Determining How Ranges Are Defined 

This is the central new field introduced by this enhancement. 

Packaging Type (dropdown, mandatory): Determines whether ranges are defined at design time or derived at runtime. 

The dropdown offers two values: 

• Static 
• Dynamic 

Static preserves the existing behavior — ranges are defined as inner nodes inside the Partitioning at design time, exactly as before. 

Dynamic is the new Packaging Type introduced by this enhancement. Unlike Static, where ranges are locked in at design time, Dynamic determines partition ranges at runtime — derived automatically from the input function entries of the function where dynamic partitioning is applied. Note that switching an existing Partitioning from Static to Dynamic removes any range nodes previously defined inside it. 

The default value for Packaging Type is Static. Existing Partitioning built without this field are treated as Static automatically. No migration of existing configurations is required. 

Packaging Field: Defining the Field for Dynamic Range Creation 

Another mandatory companion to Packaging Type, present for both Static and Dynamic configurations. 

Packaging Field (dropdown, mandatory): Defines which field values are used to create the partition ranges at runtime.

Note: The field previously labeled Field in the Partitioning has been renamed to Packaging Field. This rename applies to all Partitioning, both Static and Dynamic configurations. 

Before You Begin

Before configuring a Dynamic Packaging Type, keep the following constraints in mind: 

• Range Levels and Destinations are not supported for Dynamic Packaging Type. These features are only available with Static packaging. 
• For Dynamic Packaging Type, the following Run Mode values are not displayed in the dropdown when Dynamic is selected: PPBP, PPDP, SPXP, SUXP. 
• For a given Packaging Field, you can define multiple Partitioning as long as each has a different Run Mode or Packaging Type setting.

How It Works

To help illustrate, here is a complete end-to-end walkthrough of configuring and running a Partitioning with Dynamic Packaging Type. 

1. Open your model in the Modeling environment and locate the Partitioning you want to configure (or create a new one from the Palette). 
2. Open the Properties panel. Locate the Packaging Type field, placed directly after Run Mode. 
3. Set Packaging Type to Dynamic.  
4. Set Packaging Field to the field whose values will drive range creation at runtime. Confirm that this field exists as an input to the function where dynamic partitioning will be applied. 
   Note that PPBP, PPDP, SPXP, and SUXP Run Mode values will not be displayed in the Run Mode dropdown when Dynamic Packaging Type is selected.
   
5. Save the Partitioning configuration. 
6. Execute your process. At runtime, the system reads the distinct values of the Packaging Field from the input function entries and constructs the partition ranges dynamically before processing begins. 
7. Check the Application Monitor to confirm the run completed and to see how many package instances were created. In our example, if the input function contains entries for four customers, the engine creates four partition ranges at runtime and processes each as a separate package instance. 

This is the complete end-to-end flow: the Packaging Type field drives whether ranges come from design-time nodes or runtime data, the Packaging Field identifies the dimension that structures those runtime ranges, and the engine handles range creation automatically before execution begins. See SAP Help related to Partitioning and Range Setup for further details. 

Wrapping Up

The Dynamic Packaging Type removes a configuration step that, for many models, was also a maintenance burden: keeping design-time range nodes synchronized with the actual data in your system. Whether you work with a cost center hierarchy that changes frequently and you want packaging to always reflect the current structure, a profit center landscape that varies by version and requires a different set of ranges for each scenario, or a model where the right partition boundaries simply cannot be known until the data arrives at runtime, Dynamic Packaging Type gives you a clean, supported way to let the data define its own partitions. 

We are eager to hear from you. Which datasets in your models are you thinking of migrating from Static to Dynamic packaging? Have you encountered situations where design-time range maintenance was a limiting factor in your partitioning strategy? Share your thoughts in the comments below and stay tuned for further enhancements to the Partitioning in SAP Profitability and Performance Management Cloud Standard Model. 

As always, feel free to reach out via the SAP Profitability and Performance Management Community if you have questions. 

Related Resources 

• Partitioning and Range Setup – SAP Help Portal (SAP Profitability and Performance Management Cloud Standard Model) 
• Different Run Modes – SAP Help Portal (SAP Profitability and Performance Management Cloud Standard Model) 
• Partitioning and Packaging Setup – SAP Profitability and Performance Management On-Premise 

Source link