Installation Prerequisites (Price Setting)

Before you start installing Price Setting Package, you need to meet the following requirements:

• Get access to PlatformManager and the target partition, as described in common accelerator installation prerequisites.

• Find out your Product Hierarchy/Segmentation – see Product Segmentation (Price Setting). You will need it in one of the deployment steps. You can define the product segmentation for all of the features at once, and then also individually per feature (see Product Segmentation per Feature), if needed.
  This setting directly influences the structure of tables created during installation. It is important to do a proper research of the required product segmentation before installation, because re-configuration after installation requires that you to go through a special manual process.

• Make sure the target partition has the following bare minimum data tables and fields:

  • Product Master table with configured fields for attributes which will be used for the Product Segmentation.

    • Data rows available (you need at least 1 row to be able to create a price list after installation).

• Review the Mandatory Data (Price Setting) article to understand which data and tables you will need depending on your required use cases. This is not necessary for the installation itself, but for the configuration afterwards.

• Prepare a CSV file with Dependency Configuration – see . This file will be required in one of the deployment steps.
  This setting directly influences the structure of tables created during installation.

  Examine your customer data and requirements before you fill in this configuration because any re-configuration requires that you go through some manual steps. You can find frequently needed procedures in .

  You will need to upload this configuration as a CSV file. It is recommended that you have attributeIds in the first line of the file as headers, so that PlatformManager can automatically map it with the proper fields. Otherwise, manual mapping might be required. The file will be stored in the table, so you can import all the information that this table accepts.

  • Here is an example of a dummy business CSV file with dependencies. Your “Preference” fields will most likely be different from this example.

    DependencyLevelName,DependsOn,SourceType,SourceId,Dimension,Currency,IsComplete,Preference1_IsoCode,Preference2_SalesOrg Global,Independent,*,*,,EUR,No,GL,SO20 Germany,Global,*,*,Country,EUR,No,DE,SO24 United Kingdom,Global,*,*,Country,GBP,No,UK,SO30 United States of America,Global,*,*,Country,USD,No,US,SO26

  • The only mandatory fields for installation are:

    • DependencyLevelName

    • DependsOn

    • Dimension

    • Currency

    • SourceType – Since you do not have any price lists yet, place a star “*” symbol here.

    • SourceId – Since you do not have any price lists yet, place a star “*” symbol here.

  • The rest of the fields (i.e. IsComplete and the various “Preferences”) can be set up later during configuration of the package.