Sales Price Page Dropdown Codes

Disclaimer: This is unofficial, community-created documentation for Epicor Prophet 21 APIs. It is not affiliated with, endorsed by, or supported by Epicor Software Corporation. All product names, trademarks, and registered trademarks are property of their respective owners. Use at your own risk.

Overview

When working with the SalesPricePage window via the Interactive API, dropdown fields require specific display values (not codes). This document provides the mappings discovered through API testing.

Important: P21's code tables (code_p21) may not be accessible via OData in all environments. These values were discovered by testing the Interactive API directly.

Note: Code mappings may vary between P21 versions and configurations. Always verify codes in your specific environment.

Field Order Requirements

When creating or modifying price pages, fields must be set in a specific order. Setting fields out of order can cause validation failures or incorrect data.

Required Field Order for Page Creation

price_page_type_cd - Set page type FIRST (e.g., "Supplier / Product Group")
company_id - Required BEFORE product_group_id
product_group_id or discount_group_id - Depends on page type
supplier_id
description
pricing_method_cd - Use display value "Source"
source_price_cd - Use display value "Supplier List Price"
effective_date / expiration_date
Switch to VALUES tab
calculation_method_cd - Use display value "Multiplier"
calculation_value1 (and additional break values if needed)

Example: Creating a Price Page

# Step 1: Set page type FIRST - this determines available fields
await window.change_data("FORM", "price_page_type_cd",
                         "Supplier / Product Group", datawindow_name="form")

# Step 2: Set company_id BEFORE product_group_id
await window.change_data("FORM", "company_id", "ACME", datawindow_name="form")

# Step 3: Set product group
await window.change_data("FORM", "product_group_id", "HVAC", datawindow_name="form")

# Step 4: Set supplier
await window.change_data("FORM", "supplier_id", "10050", datawindow_name="form")

# Step 5: Set description
await window.change_data("FORM", "description", "P2-L5-10050-HVAC-WHOLESALE",
                         datawindow_name="form")

# Step 6-7: Set pricing method and source
await window.change_data("FORM", "pricing_method_cd", "Source", datawindow_name="form")
await window.change_data("FORM", "source_price_cd", "Supplier List Price",
                         datawindow_name="form")

# Step 8: Set dates
await window.change_data("FORM", "effective_date", "2025-01-01", datawindow_name="form")
await window.change_data("FORM", "expiration_date", "2030-12-31", datawindow_name="form")

# Step 9: Switch to VALUES tab
await window.select_tab("VALUES")

# Step 10-11: Set calculation method and value
await window.change_data("VALUES", "calculation_method_cd", "Multiplier",
                         datawindow_name="values")
await window.change_data("VALUES", "calculation_value1", "0.85", datawindow_name="values")

# Save
result = await window.save_data()

Why Order Matters

Setting product_group_id before price_page_type_cd will fail validation
Setting product_group_id before company_id may cause lookup errors
The VALUES tab fields are only available after FORM tab fields are set
Some fields become read-only after others are set

Calculation Method (VALUES Tab)

The calculation_method_cd field on the VALUES tab controls how pricing calculations are applied.

Code	Display Value	Description
211	Multiplier	Multiply by value (most common)
228	Difference	Subtract value from source price
229	Mark Up	Add markup percentage to cost
230	Percentage	Apply as percentage
1292	Fixed Price	Use fixed price value

Usage Example:

# Correct - use display value
window.change_data("VALUES", "calculation_method_cd", "Mark Up", datawindow_name="values")

# Incorrect - do not use code
window.change_data("VALUES", "calculation_method_cd", "229", datawindow_name="values")

Price Page Type (FORM Tab)

The price_page_type_cd field determines the page type.

Code	Display Value	Key Field
210	Customer	`customer_id`
211	Customer / Item	`customer_id` + `item_id`
213	Supplier / Discount Group	`discount_group_id`
214	Supplier / Product Group	`product_group_id`
215	Supplier / Discount Group (alt)	`discount_group_id`

Note: Type 213 ("Supplier / Discount Group") uses discount_group_id instead of product_group_id. The field order changes slightly for this type - see Discount Group Pages below.

Pricing Method (FORM Tab)

The pricing_method_cd field controls how the source price is used.

Code	Display Value
220	Value
221	Source
222	Order

Note: Some P21 environments may show different display values (e.g., "Margin", "Fixed"). The codes above were verified in a working implementation. Always test in your environment.

Source Price (FORM Tab)

The source_price_cd field determines the base price source.

Code	Display Value	Notes
200	Supplier List Price	Use with Multiplier (211) calculation method
201	Replacement Cost	Also known as "Primary Supplier Cost". Use with Mark Up (229)
202	Average Cost

Source Price and Calculation Method Pairing

Using the wrong combination of source price and calculation method produces incorrect pricing. Follow these pairings:

Calculation Method	Recommended Source Price	Why
Multiplier (211)	Supplier List Price (200)	Multiplier applies a factor to list price
Mark Up (229)	Replacement Cost / Primary Supplier Cost (201)	Mark up adds margin above cost

Important: Source Price code 201 is labeled "Replacement Cost" in the dropdown but represents the Primary Supplier Cost in P21's pricing engine. This distinction matters when building pricing logic.

Cost Type (COSTS Tab)

Code	Display Value
220	Value
221	Source
222	Order

Commission Cost Calculation Method (COSTS Tab)

The commission_cost_calc_method_cd on the COSTS tab (different from VALUES tab).

Code	Display Value
211	Multiplier
212	Difference
213	Mark Up
214	Percentage

Note: These codes differ from the VALUES tab calculation_method_cd codes.

Discovery Method

These codes were discovered by:

Opening the SalesPricePage window via Interactive API
Setting each dropdown to different display values
Reading the resulting code from window state
Verifying against live database records

# Example discovery code
window = api.open_window(service_name="SalesPricePage")
window.change_data("FORM", "price_page_uid", "45556", datawindow_name="form")
window.select_tab("VALUES")

# Try setting a display value
result = window.change_data("VALUES", "calculation_method_cd", "Mark Up", datawindow_name="values")

# Read back the code from window state
state = window.get_state()
# Extract calculation_method_cd from state['Data']

Price Breaks (Quantity-Based Pricing)

Price pages support up to 15 calculation values and 14 break quantities for quantity-based pricing.

Fields

Field	Purpose
`calculation_value1`	Base price (applies to quantity 1+)
`calculation_value2` - `calculation_value15`	Applied at corresponding break quantity
`break1` - `break14`	Quantity thresholds for each price level

Example: Setting Up Price Breaks

# Base multiplier: 0.85 for qty 1+
await window.change_data("VALUES", "calculation_value1", "0.85", datawindow_name="values")

# Price break at qty 6: 0.82 multiplier
await window.change_data("VALUES", "break1", "6", datawindow_name="values")
await window.change_data("VALUES", "calculation_value2", "0.82", datawindow_name="values")

# Price break at qty 25: 0.78 multiplier
await window.change_data("VALUES", "break2", "25", datawindow_name="values")
await window.change_data("VALUES", "calculation_value3", "0.78", datawindow_name="values")

# Price break at qty 100: 0.75 multiplier
await window.change_data("VALUES", "break3", "100", datawindow_name="values")
await window.change_data("VALUES", "calculation_value4", "0.75", datawindow_name="values")

Mapping

Quantity Range	Calculation Value
1 to (break1-1)	`calculation_value1`
break1 to (break2-1)	`calculation_value2`
break2 to (break3-1)	`calculation_value3`
...	...

Notes

calculation_value1 is always the base price (qty 1+)
break1 corresponds to calculation_value2 (not calculation_value1)
Unused break/value fields should be 0 or null
Maximum 14 break points (15 price levels including base)

Discount Group Pages (Type 213)

Discount group pages use discount_group_id instead of product_group_id. The field order differs from the standard product group page creation sequence.

Field Order for Type 213

price_page_type_cd - Set to "Supplier / Discount Group"
company_id - Required before discount_group_id
discount_group_id - Replaces product_group_id
supplier_id
description
pricing_method_cd - "Source"
source_price_cd - "Supplier List Price"
effective_date / expiration_date
Switch to VALUES tab
calculation_method_cd and values

Example: Creating a Discount Group Page

# Step 1: Set page type to Discount Group
await window.change_data("FORM", "price_page_type_cd",
                         "Supplier / Discount Group", datawindow_name="form")

# Step 2: Company ID first
await window.change_data("FORM", "company_id", "ACME", datawindow_name="form")

# Step 3: Discount group (NOT product_group_id)
await window.change_data("FORM", "discount_group_id", "DG001", datawindow_name="form")

# Step 4: Supplier
await window.change_data("FORM", "supplier_id", "10050", datawindow_name="form")

# Steps 5-11: Same as product group pages...

OData Queries for Both Page Types

When querying price pages, check both product_group_id and discount_group_id:

# Get ALL active pages for a supplier (both types)
params = {
    "$filter": (
        f"supplier_id eq {supplier_id} "
        f"and row_status_flag eq 704 "
        f"and (product_group_id ne null or discount_group_id ne null)"
    ),
    "$select": (
        "price_page_uid,description,price_page_type_cd,"
        "product_group_id,discount_group_id,supplier_id"
    ),
}

Dollar-Based Price Breaks

In addition to quantity-based breaks (documented above), price pages support dollar-based breaks where break values represent total order value rather than unit quantities.

Configuration Fields

Dollar-based breaks require additional fields on the VALUES tab:

Field	Display Value	Code	Purpose
`totaling_method_cd`	Discount Group	217	Group items by discount group for break calculation
`totaling_basis_cd`	Supplier List Price	200	Use supplier list price as the dollar total basis

Example: Dollar-Based Breaks

# Switch to VALUES tab
await window.select_tab("VALUES")

# Set calculation method
await window.change_data("VALUES", "calculation_method_cd", "Multiplier",
                         datawindow_name="values")

# Configure dollar-based totaling
await window.change_data("VALUES", "totaling_method_cd", "Discount Group",
                         datawindow_name="values")
await window.change_data("VALUES", "totaling_basis_cd", "Supplier List Price",
                         datawindow_name="values")

# Set dollar-based breaks (total order value thresholds)
# $0-$4,999: 0.85 multiplier
await window.change_data("VALUES", "calculation_value1", "0.85",
                         datawindow_name="values")

# $5,000-$9,999: 0.82 multiplier
await window.change_data("VALUES", "break1", "5000", datawindow_name="values")
await window.change_data("VALUES", "calculation_value2", "0.82",
                         datawindow_name="values")

# $10,000-$14,999: 0.78 multiplier
await window.change_data("VALUES", "break2", "10000", datawindow_name="values")
await window.change_data("VALUES", "calculation_value3", "0.78",
                         datawindow_name="values")

# $15,000-$19,999: 0.75 multiplier
await window.change_data("VALUES", "break3", "15000", datawindow_name="values")
await window.change_data("VALUES", "calculation_value4", "0.75",
                         datawindow_name="values")

# $20,000+: 0.72 multiplier
await window.change_data("VALUES", "break4", "20000", datawindow_name="values")
await window.change_data("VALUES", "calculation_value5", "0.72",
                         datawindow_name="values")

Quantity vs Dollar Breaks Comparison

Aspect	Quantity Breaks	Dollar Breaks
Break values represent	Unit quantities	Total order value ($)
`totaling_method_cd`	Not set (default)	"Discount Group" (217)
`totaling_basis_cd`	Not set (default)	"Supplier List Price" (200)
Typical use case	Volume discounts per SKU	Order-level discounts
Break example	6 units, 25 units, 100 units	$5K, $10K, $15K, $20K

COSTS Tab Configuration

The COSTS tab is a separate tab on the SalesPricePage window that controls commission cost calculation. This determines how cost is calculated for commission purposes, separate from the selling price configured on the VALUES tab.

Accessing the COSTS Tab

# Switch to COSTS tab
await window.select_tab("COSTS")

# Set commission cost calculation method
await window.change_data("COSTS", "commission_cost_calc_method_cd", "Multiplier",
                         datawindow_name="costs")

# Set commission cost value (1.01 = pass-through costing with 1% margin)
await window.change_data("COSTS", "commission_cost_value1", "1.01",
                         datawindow_name="costs")

Common Pattern: Pass-Through Costing

For pages where commission cost should simply pass through at cost:

await window.select_tab("COSTS")
await window.change_data("COSTS", "commission_cost_calc_method_cd", "Multiplier",
                         datawindow_name="costs")
await window.change_data("COSTS", "commission_cost_value1", "1.01",
                         datawindow_name="costs")

Commission Cost Codes (Different from VALUES Tab)

The COSTS tab uses different code numbers than the VALUES tab for calculation methods:

Tab	Code	Display Value
VALUES	211	Multiplier
VALUES	228	Difference
VALUES	229	Mark Up
VALUES	230	Percentage
COSTS	211	Multiplier
COSTS	212	Difference
COSTS	213	Mark Up
COSTS	214	Percentage

Warning: Do not assume codes are the same across tabs. "Difference" is 228 on VALUES but 212 on COSTS.