Dependency Mapping Mechanism
- Jana Volencová (Deactivated)
Here you will find an example of Cost mapping with all different dependency mapping types.
Example 1
Select Dependency
When creating a PL/PG with Price Setting Package, there is an input named Parent Level Name to select the dependency.
The selected dependency is Global. It will then search in DependencyConfiguration PP for the corresponding record.
Dependency Level Name | Depends On | Source Type | Source… | Dimension | Currency | Is Complete | ISO Code | Sales Org |
|---|---|---|---|---|---|---|---|---|
Global | Independent | * | * | Area | USD | No | GG | SO00 |
With “Lookup” Mapping Type
In DependencyMappingConfig PP set the following:
Name | Dependency Field | Type | Mapping Source Field |
|---|---|---|---|
Cost | DependencyLevelName | Lookup | DependencyLevelName |
Type is set to Lookup to indicate the mapping type.
Dependency Field points to DependencyLevelName. In the Select Dependency step, the selected dependency is Global, and in DependencyConfiguration PP, the corresponding row has the DependencyLevelName field = Global. Therefore, the dependency value will be Global.
Mapping Source Field points to DependencyLevelName, it will search in the Data Source table for rows that have DependencyLevelName field value equaling to the dependency value (Global in this case).
The source table is defined in PriceSettingConfig PP:
Key | Condition | Type | Source | Source Table | Source Field | Source Field 2 |
|---|---|---|---|---|---|---|
Cost | * | Lookup | PX | CostData | Cost | Currency |
It will search the PX CostData table for records that have DependencyLevelName field equaling to Global and get a value from the column referred in the Source Field as cost value (Cost field).
With “Table” Mapping Type
In DependencyMappingConfig PP set the following:
Name | Dependency Field | Type |
|---|---|---|
Cost | DependencyLevelName | Table |
Type is set to Table to indicate the mapping type.
Dependency Field points to DependencyLevelName. In the Select The Dependency step, the selected dependency is Global, and in DependencyConfiguration PP, the corresponding row has the DependencyLevelName field = Global. Therefore, the dependency value will be Global.
The source table is defined in PriceSettingConfig PP:
Key | Condition | Type | Source | Source Table | Source Field | Source Field 2 |
|---|---|---|---|---|---|---|
Cost | * | Lookup | PX | <<DependencyPreference>>CostData | Cost | Currency |
It will search the the PX Global CostData table for records and get a value from the column referred in the Source Field as cost value (Cost field).
With “None” Mapping Type
If you would like to search the PX CostData table and get a value from the column referred in the Source Field as cost value (Cost field).
Providing we have the source table defined in PP PriceSettingConfig this way
Key | Condition | Type | Source | Source Table | Source Field | Source Field 2 |
|---|---|---|---|---|---|---|
Cost | * | Lookup | PX | CostData | Cost | Currency |
then in table, set the Type to None, in the following way:
Name | Dependency Field | Type |
|---|---|---|
Cost |
| None |
Example 2
Example of dependency mapping of the “Lookup” type.
