You are here:
Troubleshoot Penny Perfect Pricing
Diagnose and resolve the common reasons an order doesn't price as expected.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions in Manufacturing Cloud, Automotive Cloud, and Consumer Goods Cloud, with required add-ons. |
| User Permissions Needed | |
|---|---|
| To troubleshoot pricing configurations and data pipelines | Manage Advanced Pricing AND View Setup and Configuration |
| To review data pipelines and error logs | Manage Data Pipelines |
No Price Returned or Zero Price Calculated
Possible Causes
- No matching condition record exists in the External Pricing Key Value Consolidated View object for any evaluated Search Strategy Step.
- The External Pricing Key Value Consolidation job hasn't run, is still in progress, or failed.
- Key Type field attribute mappings don't match the condition master data imported from the ERP system.
- The Internal Organization Unit on the Pricing Specification doesn't match the Internal Organization Unit value on the imported External Pricing Key Value records.
- The validity date range (Valid From / Valid To) on condition records doesn't cover the order pricing date.
- Valid From or Valid To was left blank on the condition record — both fields must be populated when importing condition data.
Diagnosis
- Open the priced Order record and inspect the Pricing Details tab to see which Search Strategy Steps were evaluated.
- Verify that consolidated condition records exist for the expected merge keys:
- From Setup, enter Expression Sets in the Quick Find box, and select Expression Sets.
- Open the External Pricing Key Value Consolidated Views tab.
- Filter by Internal Organization Unit and External Pricing Specification, and search for records matching the order account and product attributes.
- Verify that the External Pricing Key Value Consolidation job
completed successfully:
- From Setup, in the Quick Find box, enter Data Processing Engines, and select Data Processing Engines.
- Check the execution status and error logs for External Pricing Key Value Consolidation.
- Confirm that Key Type attribute definitions match your ERP condition table structure.
Resolution
- Import missing condition master data into the External Pricing Key Value object, and re-run the External Pricing Key Value Consolidation job.
- Add a generic fallback step to your Search Strategy (such as base product price without customer specificity).
- Update validity dates (Valid From / Valid To) on affected condition records.
- Reconfigure Pricing Key Type field mappings to match the imported condition data.
Pricing Performance or Timeouts
Possible Causes
- The order exceeds the supported limit of 1,000 line items per transaction.
- The External Pricing Key Value Consolidated View table exceeds 40 million rows per sales organization.
- The Calculation Schema contains an excessive number of calculation steps.
Diagnosis
- Check the line item count on the Order record.
- Check the number of calculation steps configured in the order's Pricing Calculation Schema.
- Check APEX CPU time and heap allocation in Developer Console debug logs during price calculation.
Resolution
- Split orders with more than 1,000 line items into multiple smaller orders.
- Archive or delete expired pricing condition records (Valid To in the past) to reduce consolidated view row counts.
- Streamline the Calculation Schema by consolidating or removing unnecessary calculation steps.
- Contact Salesforce Support if calculation performance issues persist after optimizing data size.
External Pricing Key Value Consolidation Job Fails
Possible Causes
- Mapped Key Type attributes are missing or misconfigured in expression set metadata.
- Required fields contain null values in External Pricing Key Value records.
- Data Processing Engine (DPE) runtime limits or execution errors occurred.
Diagnosis
- Review DPE execution logs:
- From Setup, in the Quick Find box, enter Data Processing Engines, and select Data Processing Engines.
- Select External Pricing Key Value Consolidation and view the Execution History related list.
- Open the failed job record to inspect the detailed error message.
- Verify data completeness in External Pricing Key Value and External Pricing Key Value Tier staging tables.
Resolution
- Correct field attribute mappings in the Pricing Key Type Expression Set Builder, save, and activate.
- Clean and re-import staging data to ensure all required fields are populated.
- Re-run the External Pricing Key Value Consolidation job definition.
Did this article solve your issue?
Let us know so we can improve!
