Understanding Configured Item Price and Cost Adjustments Using Based-on Effectivity Dates
When you enter an order for a configured item and trigger validation of the configuration, the system calculates price and cost adjustments. During configuration validation, the JD Edwards EnterpriseOne Configurator system reads the based-on date code from the Configured Item Information (F3290) table.
The JD Edwards EnterpriseOne Configurator system then retrieves the date corresponding to the based-on date code of the parent configured item from the JD Edwards EnterpriseOne Sales Order Management, JD Edwards EnterpriseOne Work Order Processing, or JD Edwards EnterpriseOne Procurement systems for the order type of the original order. The value is retrieved and stored in the configurator data cache for use in processing. This date is the X rule based-on date.
The JD Edwards EnterpriseOne Configurator system retrieves the X rule based-on date from the configurator data cache and validates each X rule setup in the Assembly Inclusion Rules (F3293) table. The system compares the X rule based-on date to the effective from and through dates of the X assembly inclusion rules.
If valid X assembly inclusion rules are found, the system applies the rules to calculate the price and cost of the configured item order. Once the validated X rules are processed, the system inserts a new record or updates an existing record in the Sales Order Detail File (F4211), Work Order Master (F4801), or Purchase Order Detail (F4311) table.
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.
If the X rule based-on date cannot be retrieved or a blank date is returned, the system uses the requested date to process the X assembly inclusion rules. The based-on date setting of the parent configured item is inherited by the child configured items.
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.
During sales order entry, the Price Effective Date field may display a price but you can override the value. For purchase orders, only cost adjustments from X rules are applied to the order.
See Understanding Configured Item Pricing and Costing Using Based-on Effectivity Dates.