Pricing API calls updated to include future prices

If you use these API calls to receive requests for and return pricing data to integrated applications, you can now include future prices set up for products in PD Future Price/Cost Change Setup:
  • sxapiOEPricing
  • sxapiOEPricingMultiple

The API calls were updated to allow passing a futuredate=mm/dd/yy value in the Extra Data List input parameter.

These business rules can be enabled in SA Business Rule Setup to use the future date to return future price data:
  • AllowFuturePrice

    Select Yes for the Rule Value to allow API requests for a future price. If this business rule is not enabled, future prices are not calculated and returned in the API call, regardless if a future date is provided in the request.

  • AllowFuturePriceCost

    Select Yes for the Rule Value to return an API request for a future price or cost from PD Future Price/Cost Change Setup.

  • AllowFuturePriceCostSeq

    Select Yes for the Rule Value to use PD Future Price/Cost Change Setup records to calculate prices or costs in date sequence. If there is both a global and warehouse-specific future price record with the same effective date, the warehouse-specific record is used.

Future prices are set up for products in PD Future Price/Cost Change Setup and assigned an Effective Date. If a future date is passed in either of the API calls, it is verified against records in PD Future Price/Cost Change Setup with an Effective Date on or before the future date to determine the future cost. The process for determining the future price is similar to the logic applied when you run PD Administrator Future Price/Cost Report to update prices and costs on Product Warehouse Product Setup records.

Future price requests cannot be made for these records:
  • Rebate prices
  • Nonstock products
  • Catalog products
  • Build-on-demand kits
  • Tally product
  • Value Add product