Create a pricing context variable

  • Release version: Washingtondc
  • Updated May 2, 2024
  • 2 minutes to read
  • Create custom context variables to represent product or non-product characteristics that pricing administrators can use to apply various pricing features, such as pricing adjustments, in Pricing Management.

    Before you begin

    Before creating a pricing context variable, review the context variables available in the Context Variables [sn_csm_ctxrul_mgt_context_variable] table to verify whether you need a new one. This table identifies the system-defined variables provided with Pricing Management and also any custom pricing variables that have been created. For example, the system-defined context variables provided for non-product attributes include: Account, Shipping Country, Shipping City, Shipping State, Shipping Zip, Billing Country, Billing City, Billing State, Billing Zip, and Transaction Date.

    Role required: admin

    About this task

    As an administrator, you can create custom context variables for items such as non-product characteristics, that your pricing administrators can use in pricing matrixes to control pricing features. For example, your pricing administrator might want to define pricing adjustments based on sales segment, but sales segment isn’t a system-defined context variable included with Pricing Management.

    You create the variable name and define the variable type, so that the variable can be used in a decision rule for a pricing matrix. After you create the variable, you must also map the context variable to the transaction entity, such as quote or order, from which the system retrieves the context.

    Procedure

    1. In the CSM Configurable Workspace, select the List Lists tab. view.
    2. Navigate to Context Rule Management > Context Variables.
    3. In the Context Variables list, select New.
    4. On the form, fill in the fields.
      Table 1. Context Variable form
      Field Description
      Type Context variable type. Choose the type of field for the variable. For example, the choice list field type lets your user select from a pre-defined list of choices.

      For more information on the different field types, see Field types.

      Label Name of the context variable, for example, sales segment.
      Column name ID of the context variable for which the context variable type is created. The system assigns this name automatically based on the Label name entered, for example sales_segment.
      Code System-generated alphanumeric number based on the label name.
      Context type Option that indicates from where the context is retrieved. Select one of the following:
      • Transaction Header: Context is fetched from the header record for a transaction, such as an opportunity, quote, or sales order.
      • Transaction Line: Context is fetched from the line record for an opportunity, quote, or sales order transaction.
      Application Name of the application scope. The default scope is Global.
      Active Option that indicates the context variable is available for use in pricing matrices.
    5. Select Save.
      The tab (related list) for the Type that you selected in Step 4 and the Variable Mapping tab are displayed.
    6. Depending on the Type you selected, create the values for the type, then select Save.
      For example, in Step 4, if you selected the Choice type, select New in the Choices tab and define the choices.

    What to do next

    Map the custom context variable to a transaction entity.