Understanding Configured Item Pricing and Costing Using Based-on Effectivity Dates

You define price and cost information for configured items and components of configured items during item setup. Assembly inclusion rules for price and cost, X rules, further define price and cost adjustments at order entry time. The validation of X rules is based on a user-defined date which is also called the based-on date. The based-on date is defined separately for the sales orders, purchase orders, and work orders of a configured item.

The based-on date codes are setup at the item level on the Configured Item Information form (W3291A). Configured item information must exist before an order is entered for a configured item. The based-on date setting of the parent configured item is inherited by the child configured items.

The following table illustrates the selections for X rule based-on dates:

Based-on Date	Sales Order	Purchase Order	Work Order
Requested Date (Default)	X	X	X
Transaction/Order Date	X	X	X
Scheduled Pick Date	X
Price Effective Date	X	X
System Date	X	X	X
Promised Delivery Date		X
Original Promised Date		X
Planned Effective Date			X
Start Date			X

During assembly inclusion rule setup, effective from and through dates are entered for each rule. The effective from and through dates are then used in conjunction with the based-on date set up on the Configured Item Information form to determine which rules are valid at order entry. All X rules that are effective are applied to the order to calculate price and cost.

For example, a configured item is setup to use the order date as the sales order based-on date and requested date as the work order based-on date. If a sales order is entered for the item on August 15th, with a requested date of October 15th, the system searches for X assembly inclusion rules that are effective on August 15th. Valid X rules apply price adjustments to the sales order. If a work order is entered for the configured item, October 15th is used to validate X rules and apply cost adjustments to the work order

The based-on effectivity date functionality in the JD Edwards EnterpriseOne Configurator system is similar to the functionality in JD Edwards EnterpriseOne Advanced Pricing. JD Edwards EnterpriseOne Advanced Pricing enables the user to specify one or many dates, such as order and required, to use to include price adjustments. The based-on date code of Price Effective Date is used to sync with JD Edwards EnterpriseOne Advanced Pricing so that the system uses the same date as JD Edwards EnterpriseOne Advanced Pricing when validating X rules. This applies to both sales and purchase orders.

See Defining Configured Item Information.

See Understanding Configured Item Price and Cost Adjustments Using Based-on Effectivity Dates.