Business Requirements

When a new dependency level is required:

Decide:
- Is this going to be a “Virtual Dependency Level” (used only as a fallback for other dependency levels which are lower in hierarchy) or a standard one?
- Is this going be “Parent” or “Dependent on already existing dependency” Level?
  - If Dependent, should it be in master relation or HQ relation?
- Is this is going be “Complete Dependency Level” (no fallback to more general Dependency Levels, nor general fallback)?
Prepare data for Dependency Level (or agree to utilize a fallback to some of them).
Prepare Hierarchical Config for Dependency Level (or agree to utilize a fallback to some of them).

New Dependency Level Check List

Add a new entry to Dependency Configuration. All values will come from business requirements described above.
- Remember to enter PL/PG ID of Master Dependency Level, not just Dependency Level just being added.
- Remember that Preferences are used for Dependency Mapping DependencyMappingConfig PP. PSP does not support different Dependency Mapping per Dependency Level, so it needs to be similar to data entered for other Dependency Levels.
Run bootstrapping, according to this guide: Change Product Segmentation
Enter data in newly created Hierarchical tables (if needed, fallback might be utilized if Dependency Level is not complete – a general fallback is always utilized). List of all Hierarchical tables: Hierarchical Lookups.
Enter data for each Data Lookup (if needed, fallback/general fallback might be utilized if Dependency Level is not complete). List of all Data Lookups: Data Lookups
Create a new PL/PG, according to the second part of this section: Install Price Setting Accelerator | Configuration and Price List/Grid Creation

Go to Pricefx Processes > Price Setting Accelerator Configuration Wizard.
Select Core Elements module and click Configure selected module.
Select Configure Dependency Level.
Select an action.
1. Add new dependency level
2. Edit dependency level
3. Delete dependency level