In Price Flexibility Package you can configure multiple monitors. Each monitor can have its own:

• Price Grid Mapping (which PG product with detected changes is monitored)

• Observable Attributes (which changes of a product will trigger a LifeCycle Monitor)

• Dependency Level

Dependency Levels require most attention. They are responsible for multi-level fallback. Each piece of data can be duplicated for each Dependency Level to simulate, for example, different costs of production among countries. However, “Plus” in “Cost Plus” strategy might be different per vendor, not per country. Because of that, we can keep data on different Dependency Level. The lookup will be performed for more and more generic levels, until data is found.

Hierarchy used will be from DependencyConfiguration PP if PSP is deployed, or PF_DependencyConfiguration PP if no PSP is deployed.

Please note that, unlike in PSP, users do not need to use Dependency Mapping. Then the configuration should be left empty.

Restrictions of Multiple Monitor Instances

Currently, these are downsides of using this feature:

• Price Flexibility Package → Price Setting Package integration is supported for only 1 monitor instance.

• ‘Needs Recalculate’ flag (which is an optimization trick) is utilized properly for only 1 monitor instance.

Fallback Rules

Fallbacks follow these rules:

• Check if the current dependency level is complete.

  • If yes, abort the algorithm.

• Look up the master dependency level.

  • If the master dependency level does not exist, add empty mapping data as a possible fallback and abort the algorithm.

  • If the master dependency level is not in the HQ relationship with the current level, add a master as a possible fallback.

• Repeat with the master dependency level as the current dependency level.

Example without the isComplete flags:

Open

Example with the isComplete flags:

Open