Price Setting Package 1.3.0

Owned by Ondřej Tesař
Sept 30, 2024
6 min read

There are also videos showing the main new features: Price Setting Package 1.3.0 Key Features Description

Each of the videos takes less than 3-4 minutes, so the amount of time you need to invest is not that big

 

Notes

Upgrading Projects by PlatformManager

There is a known issue: deployment is sometimes aborted when a similar PREF object already exists on the partition. As a workaround, deploy Price Setting Package only on clean partitions or remove the crashing preferences from the partition and try the deployment again.

Bugs

  • [PFPCS-1616] - Color of Corridor columns should overlay color of the row

    • Upgrade note: The default value for “NO_FINAL_PRICE” record in WarningConfig PP should be changed from “Red” to “Critical”

  • [PFPCS-1708] - PB_ country PL error on line item

  • [PFPCS-1720] - Handle unexpected error about Projection and Transaction data when using DM which doesn’t exist

    • Upgrade note: New entry has been added to WarningConfig PP

      • NO_SOURCE_TYPE

  • [PFPCS-1730] - Config validation doesn't allow for Linear and LastYear projection config.

  • [PFPCS-1737] - YTD data should be counted from the beginning of the current year to the present day

  • [PFPCS-1749] - Issues with KitEngine calculation

  • [PFPCS-1757] - Handle unexpected errors about Sales Data when Types are not supported

    • Upgrade note: New entries have been added to WarningConfig PP

      • NO_SOURCE_TABLE

      • NO_FORECAST_TYPE

  • [PFPCS-1758] - Can't get Sales Data when using Datasource to lookup

  • [PFPCS-1775] - Anchor pricing doesn't mark as dirty

  • [PFPCS-1776] - Fix reason of Competition strategy in Prices matrix when missing config for Product Competition Country Mapping

  • [PFPCS-1779] - Throw error in batchManager # performActionIfNewBatchLoaded

  • [PFPCS-1820] - Issues with Global Price/Global Decision when product is only calculated in CountryLPG

  • [PFPCS-1821] - Anchor Error - can't return result

  • [PFPCS-1827] - Incorrect PriceDecision in case strategy exception is ignored

  • [PFPCS-1836] - Base strategies should take places before Standard strategies in Prices matrix

  • [PFPCS-1857] - Issues with StrategyException when result of strategy is null or strategy is not in Prices matrix

  • [PFPCS-1865] - Fix small issues about formatting

  • [PFPCS-1874] - It throws message "Strategy Condition module has failed" if there is no Conditions defined in PP StrategyConditions

    • Upgrade note: New entry in WarningConfig PP table:

      • ERROR_LOOKING_UP_STRATEGY_CONDITIONS_DATA_PP

  • [PFPCS-1875] - Can't get Override Price when its value equals 0

  • [PFPCS-1876] - Price of Strategy(Independent Type Strategy) can't override Price of Exception strategies in FinalListPrice

  • [PFPCS-1883] - In case using both price and strategy exceptions, if exception strategy is not in the list of calculated strategies then Price Decision is not correct.

  • [PFPCS-1890] - Handle the case when the value is in the Range but can't return the result following the Rule

    • Upgrade note: New entry in WarningConfig PP table:

      • NO_SUITABLE_ROUNDING_RESULT

  • [PFPCS-1892] - Unexpected Error displays if using * in Source ID in PP DependencyConfiguration

    • Upgrade note: New entry in WarningConfig PP table:

      • INVALID_DEPENDENCY_TABLE_ID

  • [PFPCS-1906] - Competition Strategy - Exception is not thrown for dependent LPG

  • [PFPCS-1908] - Fix standard config for PSP modules and add trimming values

Stories

  • [PFPCS-1324] - Make Anchor/Kit Pricing engines input fields parameterized

  • [PFPCS-1674] - Definition of relevant Competitors

    • Upgrade notes:

      • New entry in WarningConfig PP:

        • ERROR_LOOKING_UP_RELEVANT_COMPETITION_DATA_PP

      • New PP table introduced:

        • Name: RelevantCompetitionData

        • Type/Value: MATRIX/MATRIX3

        • Keys: Product Dimensions (Standard config: Business Unit/Product Group/Product Class)

        • Attributes: Relevant Competitor, Competitor#01, Competitor#02, … , Competitor#29

  • [PFPCS-1711] - Enhance competition Strategy

  • [PFPCS-1759] - Introduce Minimum Margin Price to the Pricing Logic

    • Upgrade notes:

      • New entries in WarningConfig PP:

        • ARITHMETIC_EXCEPTION

        • NO_MIN_MARGIN_PRICE

      • Every configuration row in StrategyDefinition PP that uses CompetitionEngine needs additional input parameter, so COMPETITION_PRICES must be changed to COMPETITION_PRICES,MINIMUM_MARGIN_PRICE in Strategy Calculation Parameters column.

  • [PFPCS-1514] - Price Setting: Global/Local level naming

    • Upgrade notes:

      • Change name CountryInformation PP to DependencyConfiguration and do following changes:

        • Change Value Type of this table to MATRIX4

        • Rename fields as follows (label in brackets):

          • key1 → DependencyLevelName (Dependency Level Name)

          • key2 → DependsOn (Depends On)

          • key3 → SourceType (Source Type)

          • key4 → SourceId (Source ID)

          • attribute1 → Dimension (Dimension)

          • attribute2 → Currency (Currency)

          • attribute3 → Preference1 (ISO Code)

          • attribute4 → Preference2 (SalesOrg)

          • attribute5-30 → Preference3-28 (Preference #3-#28) - Only if you intend to use other fields for dependency mapping (old country mapping) purposes

        • Reconfigure dependencies.

          • Old “Global” country should have “Independent” flag in “Depends On” column.

          • Old countries should have “Global” in “Depends On” column

          • Old countries should have PG or PL in “Source Type” column and proper ID of “Global” independent PG/PL

      • Change name CountryMappingConfig PP to DependencyMappingConfig and do following changes:

        • Wherever “Country Field” has Name value, change it to DependencyLevelName

        • In “Name” column, change all Country Mapping strings into Dependency Mapping, eg. Cost Country Mapping → Cost Dependency Mapping

        • Rename fields as follows (label in brackets):

          • attribute1 → DependencyField (Dependency Field)

      • Rename all autogenerated parameters:

        • *CountryAdjustment → *DependencyLevelAdjustment

      • Rename keys in WarningConfig PP:

        • COUNTRY_ADJUSTMENT_IS_ZERO → DEPENDENCY_ADJUSTMENT_IS_ZERO

        • ERROR_GETTING_GLOBAL_PRICES_FROM_GLOBAL_ITEM → ERROR_GETTING_INDEPENDENT_LEVEL_PRICES_FROM_INDEPENDENT_LEVEL_ITEM

        • ERROR_LOOKING_UP_COUNTRY_ADJUSTMENT → ERROR_LOOKING_UP_DEPENDENCY_ADJUSTMENT

        • NO_COUNTRY → NO_DEPENDENCY_LEVEL_NAME

        • NO_COUNTRY_ADJUSTMENT → NO_DEPENDENCY_ADJUSTMENT

        • NO_GLOBAL_DECISION → NO_INDEPENDENT_LEVEL_DECISION

        • NO_GLOBAL_ITEM → NO_INDEPENDENT_LEVEL_ITEM

        • NO_GLOBAL_PRICE → NO_INDEPENDENT_LEVEL_PRICE

        • NO_INPUT_FOR_GLOBAL_ADJUSTED_PRICE → NO_INPUT_FOR_INDEPENDENT_LEVEL_ADJUSTED_PRICE

        • NO_INPUT_FOR_GLOBAL_PRICE_PRIORITY → NO_INPUT_FOR_INDEPENDENT_LEVEL_PRICE_PRIORITY

      • Make adjustments in PriceSettingConfig PP:

        • Remove:

          • Row with “Price Orientation” key

          • Row with “Global Price” key

        • Change values:

          • Change all keys:

            • Global Manual Override Allowance → Independent Manual Override Allowance

            • Local Manual Override Allowance → Dependent Manual Override Allowance

          • Change all Conditions:

            • Global → Independent

            • Local → Dependent

          • Change all sourceTables if Table type country mapping was used and this placeholder is somewhere in this PP’s source table column:

            • <<Country>> → <<DependencyPreference>>

        • Make adjustments in StrategyDefinition PP:

          • Rename (label in brackets):

            • attribute4 → Independent Level Only (Independent Level Only)

            • attribute5 → Independent Level Priority (Independent Level Priority)

          • Change values:

            • Global → Independent in Level column

            • Local→ Dependent in Level column

            • all references to COUNTRY_INFORMATION_VALUES → DEPENDENCY_INFORMATION_VALUES in StrategyCalculationParameters column

          • Change allowed values:

            • Global → Independent in Level column

            • Local→ Dependent in Level column

        • Make adjustments in StrategySelection PP:

          • Rename:

            • Prioritize Global Price → Prioritize Independent Level Price

        • Make adjustments in PricingExceptions PP (if used):

          • Rename (label in brackets):

            • key2 -> DependencyLevelName (Dependency Level Name)

        • Make adjustments to default PXes (only if used - labels in brackets):

          • Rename in DiscountGroups PX

            • attribute1 → DependencyLevelName (DependencyLevelName)

          • Rename in ListPrices PX

            • attribute1 → DependencyLevelName (DependencyLevelName)

          • Rename in ProductCosts PX

            • attribute3 → DependencyLevelName (DependencyLevelName)

          • Rename in PromotionPrices PX

            • attribute4 → DependencyLevelName (DependencyLevelName)

          • Rename in RecommendedRetailPrices PX

            • attribute4 → DependencyLevelName (DependencyLevelName)

        • Reconfigure/Recreate all PLs/LPGs that use either GlobalPriceListLogic or CountryPriceListLogic

          • Logic names changed:

            • GlobalPriceListLogic → IndependentPriceListLogic

            • CountryPriceListLogic → DependentPriceListLogic

          • Gathering input changed, proper values must be selected during first configuration

        • Remove unnecessary objects:

          • GlobalPriceListLogic CL

          • CountryPriceListLogic CL

  • [PFPCS-1545] - Price Setting: Add conditions to price strategies

    • Upgrade notes:

      • New entry in WarningConfig PP:

        • ISSUE_EXECUTING_STRATEGY_CONDITION

      • New PP table introduced:

        • Name: StrategyConditions

        • Type/Value: MATRIX/MATRIX

        • Key: Order

        • Attributes: Condition, Rule, CheckException

        • Example:

  • [PFPCS-1498] - Round up / round down feature

    • Upgrade notes:

      • New entry in DependencyMappingConfig

        • Rounding Dependency Mapping

      • New entry in WarningConfig PP:

        • NO_ROUNDING_RULE

      • New module added to AP:

        • PSP_ROUNDING_RULES_MODULE

      • New entry in PriceSettingConfig, standard config below:

        • Key: Rounding Rules

        • Condition: *

        • Type: Lookup

        • Source: PP

        • Source Table: RoundingRule

        • Source Field: RoundingRule

        • Source Field 2 : RoundingMode

      • New PP table introduced:

        • Name: RoundingRulesConfig

        • Type/Value: MATRIX/MATRIX2 (when using Table Dependency Mapping), MATRIX/MATRIX3 (when using Lookup Dependency Mapping)

        • Keys: From, To, Dependency Mapping (in case of Lookup)

        • Attributes: Rounding Rule, Rounding Mode

        • Warning: Empty RoundingRulesConfig is currently not supported. To turn off rounding, the module should be turned off or one entry with the rounding mode “NO_ROUNDING” should be created.

        • Example:

  • [PFPCS-1515] - Enable to create Qty Breakdown Pricelist

    • Upgrade notes:

      • New entries in WarningConfigPP:

        • ERROR_LOOKING_UP_VOLUME_EXCEPTION

        • ERROR_PARSING_VOLUME_DISCOUNTS

        • NO_INPUT_FOR_VOLUME_DISCOUNT

      • New PP tables introduced:

        • VolumeBreakdown

          • Name: {DependencyLevelName}VolumeBreakdown

          • Type/Value: MATRIX/MATRIX3

          • Keys: Product Dimensions (Standard config: Business Unit/Product Group/Product Class)

          • Attributes: Volume #01, Discount #01, Volume #02, Discount #02, … , Volume #15, Discount #15

        • VolumeExceptions

          • Name: VolumeBreakdownExceptions

          • Type/Value: MATRIX/MATRIX2

          • Keys: SKU, Dependency Level Name

          • Attributes: Volume #01, Discount #01, Volume #02, Discount #02, … , Volume #15, Discount #15

        • Examples:

  • [PFPCS-1165] - Wrap pricing logic inside manager - make price calculations centralized

    • Upgrade notes:

      • Entries removed from WarningConfig PP:

        • ERROR_LOOKING_UP_BASE_STRATEGIES

        • ERROR_LOOKING_UP_PRICE_STRATEGIES

        • NO_INPUT_FOR_COUNTRY_ADJUSTED_PRICE

        • NO_INPUT_FOR_GLOBAL_PRICE

        • NO_INPUT_FOR_GLOBAL_DECISION

        • NO_PRICE_IN_PRICE_SELECTOR

        • NO_STRATEGY_DEFINITION_PP

        • NO_STRATEGY_IN_PRICE_SELECTOR

        • NO_PX_ROWS_FOR_PRICE_LOOKUP

      • New entries added to WarningConfig PP:

        • ERROR_LOOKING_UP_STRATEGIES

  • [PFPCS-1698] - Rename Projection to Forecast in configuration

    • Upgrade notes:

      • Changes in PriceSettingConfig

        • “Projection” keys are changed to “Forecast”

      • Changes in DependencyMappingConfig

        • “Projection Dependency Mapping” changed to “Forecast Dependency Mapping”

  • [PFPCS-1703] - PM/PSP v1.3.0: Move all elements into definition directory