Understanding Cross-Segment Editing Rule Logic
The JD Edwards EnterpriseOne Configurator system uses cross-segment editing rules (CSERs) to ensure feature and option compatibility during order entry. These rules establish the relationships among the configured item segments with Boolean logic statements. During order entry, the cross-segment editing rules validate that the feature and option values that you select create a valid product configuration. This validation enables you to avoid invalid combinations of segments and prevent invalid orders. Error messages about invalid configurations appear based on segment information from the order and cross-segment editing rules.
For each cross-segment editing rule, you can define an if/then/else logic statement for many conditions. For example, a forklift might require a different value for segment 30 (boom height), depending on the value of segment 10 (lift rating). This cross-segment editing rule illustrates this situation:
If segment 10 equals 6000, then segment 30 must equal 12, else segment 30 must be less than or equal to 10.
See Understanding Boolean Logic.
Each phrase of the conditional logic statement is a separate record (written on a separate line).
The system automatically separates rules by highlighting them with different colors.
The system automatically assigns a rule number that is based on the order in which each rule is entered into the system. The rule number is the order in which the rules will be processed at order entry. You can change the rule number when setting up cross-segment editing rules by using the Insert Before and Insert After options on the Row menu on the Work with Cross Segment Editing Rules form.
The system automatically assigns a sequence number to each line within a rule, based on the order in which each line of each rule is entered into the system. The sequence number is the order in which each line within a rule will be processed during rules processing. You can change the sequence number by using the Insert Before and Insert After options on the Row menu on the Cross Segment Edit Group Revision form.
The system enables you to perform multi-level referencing for non-dynamic and dynamic rules processing. You can perform upward and downward referencing to access values from segments on various levels of the configured item.
The system supports upward referencing only within cross-segment editing rules for single pass rules processing. Single pass rules processing does not support downward referencing. Upward referencing for single pass rules processing has no limitations.
The system also enables you to perform segment to segment comparisons. For example, if segment 10 is greater than segment 20. You can perform comparison across levels as well. For example, if segment 10 (of item 6000 in branch/plant M30) is greater than segment 20 (of item 6100 in branch/plant M30).
You use the Segment Item Left, Segment Branch Left, Configured Item Alias Left, Segment Item Right, Segment Branch Right, and Configured Item Alias Right fields in cross-segment editing rules.
A configured item alias may be assigned to an item using an assembly inclusion rule. The system verifies that the configured item alias has not been assigned to another item in the assembly inclusion rules. This prevents two components on any rule from being assigned the same configured item alias.
Once the configured item alias is assigned in an assembly inclusion rule, then the Configured Item Alias Left and Configured Item Alias Right fields in the cross-segment editing and assembly inclusion rules can be set to reference a configured item alias. The system verifies that the configured item alias is assigned to the item in the rule.
When dynamic configuration is enabled and UDC values are used for segments, cross-segment editing rules affect the values listed for a segment during order entry. When a segment answer is changed, all allowed values for other segments are updated to include only valid values based on the processed cross-segment editing rules. If there are no valid values left for a segment after the cross-segment editing rules are processed, then the system removes the segment from the configuration.