Understanding Assembly Inclusion Rules
Assembly inclusion rules translate the requested values from order entry into the specific components, routing operations, user display information, and calculated values that are necessary to build, cost, and price the configured item. Assembly inclusion rules also offer advanced logic, such as algebraic expressions, smart parts, and external program references.
The six types of assembly inclusion rules include:
Rule |
Description |
|---|---|
Component Part (P) Rules |
Define the component parts to include on the sales order and work order parts list. Define the transaction type and supplier number to support the generation of various order types for configured items and components of configured items. You also define multilevel configured items with P type rules. For example, if segment 10 equals 6000 and segment 30 is greater than or equal to 10, then use part F170 or else use part F175. Note: You must have at least one P assembly inclusion rule for the JD Edwards EnterpriseOne Configurator system to function. |
Work Order Component Part (Q) Rules |
Define the components to include on the work order parts list. The Order Processing program (R31410) attaches the parts list. For example, if segment 10 equals standard, then include part R100 and part R105. |
Calculation (C) Rules |
Define the mathematical calculation for the calculated segments for a configured item. You must first define the segment as calculated on Configured Item Segments. You can use a calculated segment value in derived calculations for other rules. |
Hot Spot (H) Rules |
Define information and messages about a configured item that are processed for display purposes only. This information appears on the order entry form in a Hot Spot field. H rules are calculated similar to C rules. However, the results do not affect the configuration identifier. |
Pricing (X) Rules |
Define the price and cost adjustments. The system processes X rules independently, based on the kit/configurator pricing method that you selected. Typically, you should not set up cost adjustments when you use work-order-generated line types. X rule cost adjustments affect only the sales order. Order Processing (R31410) recalculates the cost without the X rule. For example, if segment 40 equals CUS, then adjust the price by 650.00 USD. The Line Type for X rules should be one that has the Inventory Interface set to N. You must also be certain that the Edit Item Master for the Non-Stock Item option does not have a check mark on the Line Type Constants Revisions. This situation prevents the Item Number Invalid error at order entry. Based on whether the Price Rollup field is activated, adjustments are either reflected in the price of the parent item or entered in a new extended sales order detail line. Based-on effectivity dates defined on the Configured Item Information form are used in conjunction with the effective from and through dates of X rules 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. See Understanding Configured Item Pricing and Costing Using Based-on Effectivity Dates. |
Routing (R) Rules |
Define the work order routing and routing operations. The Order Processing program (R31410) attaches work order routings. You must first define the routings on Work With Routing Master (P3003) before you define routing rules. For example, if segment 40 equals STD, then use the routing for standard paint or else use the routing for custom paint. |
You review assembly inclusion rule information to help you maintain these rules. Rules and tables can be very complex. Using inquiry programs can help you identify segments and components within the many rules and tables that you might set up. You can determine the effect of component changes, such as shortages and substitutions, and determine the effect of changes on valid segment values. For example, if a vendor discontinues a paint color, you can determine how many configurations are affected.