DependencyConfiguration PP

Company Parameter DependencyConfiguration defines:

  • All Pricing Levels used for price setting

  • Dimension of Pricing Levels

  • Relations (dependencies) between the Pricing Levels

  • Properties (preferences) of each Pricing Level which can be used when looking up data in tables

This is one of the core tables whose content is uploaded during the accelerator installation process.

Field Name

Description

Data Type

Example

Field Name

Description

Data Type

Example

Dependency Level Name

Name of this Pricing Level. Unique ID, it should represent name of the pricing environment.

Text value defined by  business user

Germany

Depends On

The pricing level can depend on another level.

Here is the name of another Pricing/Dependency Level from this table, on which it depends.

Text, with allowed values:

  • "Independent" – for independent level

  • <name of another dependency level listed in this table> – for dependent levels

Global

Dimension

Name of dimension where the level belongs (for details on dependencies see Pricing Levels).

Text

  • empty – used for independent level

  • <name of dimension> – this dimension name will be the same for all pricing levels from the same dimension

Country

Warehouse

Currency

Currency Code used for calculations of prices on this pricing level. If we read prices from the parent price list and currencies differ, the accelerator will perform a currency conversion.

Text

EUR

IsComplete

Flag indicating if all data is supposed to be filled/available at this point when doing data lookups on this level or dependent levels.

  • "Yes" – Fallback hierarchy will be stopped at this point.

  • "No" – When looking up data, and they are not found on this level, we continue to "fall back” to higher levels to find the data.

Boolean, with allowed values:

  • Yes

  • No (default)

No

Preference #01-27

Custom parameters, used in mapping the dependency level to the appropriate rows of a given source table. The mapping is managed via the DependencyMappingConfig PP table.  Currently, only one field can be used to map at a time (see also Dependency Mapping Mechanism).

 

ISO Code

SalesOrg

Example: 

image-20240726-124209.png