Understanding Advanced Pricing Constants

Set up system constants to determine which functions to perform. For example, if you have several branch/plants and use different units of measure for the items in each branch/plant, you can set a system constant to automatically convert units of measure by branch. System constants apply to all branch/plants. You cannot customize system constants for each branch/plant.

For Advanced Pricing, the system constants define how the system retrieves price adjustments for sales orders and purchase orders. When you set up base prices and adjustments, you can use various units of measure and effective date ranges. The system retrieves the unit cost for a purchase order detail line based on either the transaction unit of measure, the purchasing unit of measure, or the primary unit of measure. Additionally, you can retrieve the price based on specific dates in the order process. For example, you can base the sales price on the date that the item is shipped versus the date that the order is entered in the system.

The system uses pricing constants to control which JD Edwards EnterpriseOne system— Sales Order Management, Procurement, or both—uses JD Edwards EnterpriseOne Advanced Pricing. Additionally, you can assign the special characters in the price formulas for sales or purchase order adjustments. You can also specify other controls, such as using the sold to address book number to retrieve direct price adjustments, applying pricing approvals, or use promotional pricing. You can set the Sales Pricing on Override Price, Procurement Pricing on Override Price, or both options to override the price and perform manual price adjustments and view the price history records. To increase system performance, you can activate the Accelerated Pricing Resolution Engine.

Like system constants, pricing constants apply to all branch/plants. You cannot customize the settings for each branch/plant.