Defining Assembly Inclusion Rule Logic
Access the Assembly Inclusion Edit Group Revisions form.
For each assembly inclusion rule, you define unconditional and conditional rules using Boolean logic. Before you define conditional rules, define unconditional rules to include parts, price adjustments, cost adjustments, calculated values, display values, or routing steps—regardless of the segment values.
To reference a segment from another level in the configured item:
Complete the Op field.
Complete the Segment Item Left, Segment Branch Left, Configured Item Alias Left, Segment Item Right, Segment Branch Right, and Configured Item Alias Right fields.
Continue to enter the remaining rule information.
- Rule Type
Enter a value that identifies whether the resulting value of the assembly inclusion rule is a part number, price, routing operation, or calculated value. Values are:
P: Part List
Q: Work Order Component
C: Calculation
H: Hot Spot
X: Price/Cost Adjustment
R: Route Sheet
- Parent Sgmt (parent segment)
Enter a number that the system uses to reference the answer to the question. Segment numbers are user-defined.
Cross-segment editing rules reference the segment numbers to ensure that the set of values defines a valid configuration.
Assembly inclusion rules reference segment numbers and their associated values to define prices, component parts, routing, and calculated values for configured items.
If this segment number is used in assembly inclusion rules or cross-segment editing rules, then this is the segment used for the left side of the condition.
- Values
Enter an answer that is valid for the segment and rule relationship. You can enter a specific UDC value or one of these values:
*VALUES: Provides multiple values lists for you to use in the logic rule. You can enter up to 45 values.
If you enter *VALUES and press Tab to move out of the field, the system calls the Configured Item Rule Range or Values program (P32921), which enables you to revise values. Values are:
*BLANK: Uses a blank value in the logic rule.
*ZERO: Searches for amounts that are equal to zero as part of the logic rule.
*RANGE: Uses a range of values (for example, 1 to 50) in the logic rule. You enter the range of values. The first value in the range must be less than the second value.
If you enter *RANGE and press Tab to move out of the field, the system calls the Configured Item Rule Range or Values program (P32921), which enables you to revise ranges.
*ALL: Uses all values in the logic rule.
For Dynamic Configurator Only
Note: The following values do not impact assembly inclusion rules.The following values are valid only in the Cross Segment Editing program (P3292) when the Rules Processing option on the Configured Item Information form is set to Dynamic to enable dynamic configuration:
*REQ: The system changes the Required To Be attribute (ATRQ) of the defined segment to Required. You may use *REQ standalone to display all valid UDC values in the combo box. Alternatively, you may use *REQ in conjunction with *VALUES to limit the list of valid UDC values that are displayed in the combo box.
*OPT: The system changes the Required To Be attribute (ATRQ) of the defined segment to Optional. You may use *OPT standalone to display all valid UDC values in the combo box. Alternatively, you may use *OPT in conjunction with *VALUES to limit the list of valid UDC values that are displayed in the combo box.
- Child Sgmt (child segment)
Enter a number that the system uses to reference the answer to the question. Segment numbers are user-defined.
Cross-segment editing rules reference the segment numbers to ensure that the set of values defines a valid configuration.
Assembly inclusion rules reference segment numbers and their associated values to define prices, component parts, routing, and calculated values for configured items.
If this segment number is used in assembly inclusion rules or cross-segment editing rules, then this is the segment used for the right side of the condition.
- Item Number
Enter a number that the system assigns to an item. It can be in short, long, or third-item number format.
- Component Branch
Enter a secondary or lower-level business unit. The system uses the value that you enter to indicate that a branch or plant contains several subordinate departments or jobs. For example, assume that the component branch is named MMCU.
The structure of MMCU might be:
Branch/Plant - (MMCU)
Dept A - (MCU)
Dept B - (MCU)
Job 123 - (MCU)
- Cfg Item Alias (configured item alias)
Enter a value from UDC 32/CI that specifies a particular instance of a configured item that is referenced in the rule.
The Cfg Item Alias field on the assembly inclusion rule form provides the ability to reference a specific occurrence of an included item. This is not a required field. The Cfg Item Alias field is for use with duplicate components. If you do not use this field with duplicate components then the system processes duplicate components based on the first duplicate item value that is stored in cache.
Important: You should use the Cfg Item Alias field to ensure that the correct duplicate item is used in a configuration.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.
- Print Part
Enter a UDC (32/PF) that indicates whether the system prints the Configurator part on the sales order and work order. The system uses the value that you enter in this field to affect programs such as Print Pick Slips (R42520), Print Invoices (R42565), Bill of Lading (R42530), and parts list on Work Order Print (R31415). Values are:
0: Do not print the Configurator part on the sales order or the work order.
1: Both the sales order and the work order.
2: Sales order only.
3: Work order only.
- Quantity
Enter the number of units that the system applies to the transaction.
- U/M (unit of measure)
Enter a UDC (00/UM) that identifies the unit of measure for an amount or quantity. For example, it can represent a barrel, box, cubic meter, liter, hour, and so on.
- Operation Seq No. (operation sequence number)
Enter a number that is used to indicate an order of succession.
In routing instructions, this is a number that sequences the fabrication or assembly steps in the manufacture of an item. You can track costs and charge time by operation.
In bills of material, this is a number that designates the routing step in the fabrication or assembly process that requires a specified component part. You define the operation sequence after you create the routing instructions for the item. The JD Edwards EnterpriseOne Shop Floor Management system uses this number in the backflush/preflush by operation process.
In engineering change orders, this is a number that sequences the assembly steps for the engineering change.
For repetitive manufacturing, this is a number that identifies the sequence in which an item is scheduled to be produced.
Skip To fields enable you to enter an operation sequence that you want to begin the display of information.
You can use decimals to add steps between existing steps. For example, use 12.5 to add a step between steps 12 and 13.
- Issue Type
Enter a code that indicates how the system issues each component in the bill of material from stock. In JD Edwards EnterpriseOne Shop Floor Management, it indicates how the system issues a part to a work order. Values are:
I: Manual issue
F: Floor stock (there is no issue)
B: Backflush (when the part is reported as complete)
P: Preflush (when the parts list is generated)
U: Super backflush (at the pay-point operation)
S: Subcontract item (send to supplier)
Blank: Shippable end item
You can issue a component in more than one way within a specific branch/plant by using different codes on the bill of material and the work order parts list. The bill of material code overrides the branch/plant value.
- Line Type
Enter a code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as JD Edwards EnterpriseOne General Ledger, JD Edwards EnterpriseOne Job Cost, JD Edwards EnterpriseOne Accounts Payable, JD Edwards EnterpriseOne Accounts Receivable, and JD Edwards EnterpriseOne Inventory Management. It also specifies the conditions under which a line prints on reports, and it is included in calculations. Codes include:
S: Stock item
J: Job cost
N: Nonstock item
F: Freight
T: Text information
M: Miscellaneous charges and credits
W: Work order
- Write Attached Detail Line
Enter a value from UDC 32/WA that specifies whether the component line generates a detail line to indicate that the component is going to be shipped. Values are:
0: Do not create.
1: Create.
This field works only with a P type rule. If it is set appropriately, details are written to the sales order and cost is also rolled up to the sales order. This field does not work with purchase orders as components of a purchase order do not generate detail lines.
Turn the detail lines off whenever possible so that the lines are not processed.
- Trans Type (transaction type)
Enter a value from UDC 32/DE that specifies the type of transaction that the component of a configured item should generate. If the conditions for the transaction, processing options, and branch/plant are not correct for the transaction type, then the system does not generate the transaction. You use the Trans Type field in combination with the Write Attached Detail Line field on the Assembly Inclusion Edit Group Revisions form. Values are:
0: Sales Order
1: Direct Ship
2: Transfer
3: Inter Branch/Company
4: Purchase Order
Note: If you select the direct ship or purchase order transaction type, you must enter a supplier number in the Supplier Number field for the component item.This field works only with a P type rule.
When the value of the Trans Type field is 4 (purchase order), the system validates both the stocking type and line type of the component item. Items with a stocking type of phantom or a line type set to generate a purchase order or work order are not supported.
- Supplier Number
Enter a number that identifies an entry in the JD Edwards EnterpriseOne Address Book system for a supplier.
If you select a value of 1 (direct ship) or 4 (purchase order) in the Trans Type field, you must enter a supplier number for the component item.
If no value is entered in the Supplier Number field on the Assembly Inclusion Edit Group Revisions form, the system retrieves the supplier number from the Item/Branch Plant Info form and populates it as the default value.
This field works only with a P type rule. It is display only for Q rules.
- Segment Item Left
Enter a number that represents the item number of the parent configured item for the segment referenced in the left side of the condition. Use this field to reference a previously chosen segment from a different configuration level.
- Segment Branch Left
Enter the branch/plant associated with the configured item that contains the segment number referenced in the left side of the condition. Use this value to reference a previously selected segment from a different configuration level, and to reference the branch/plant of the item in the Segment Item Left field.
- Configured Item Alias Left
Enter a value from UDC 32/CI that specifies a particular instance of a configured item that is referenced in the left side of the condition.
The Configured Item Alias Left field on the cross-segment editing and assembly inclusion rule forms provides the ability to reference a specific occurrence of an included item. This is not a required field. The Configured Item Alias Left field is for use with duplicate components. If you do not use this field with duplicate components then the system processes duplicate components based on the first duplicate item value that is stored in cache.
Important: It is recommended that you use the Configured Item Alias Left field to ensure that the correct duplicate item is used in a configuration.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 field 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.
- Segment Item Right
Enter a number that represents the item number of the parent configured item for the segment referenced in the right side of the condition. Use this field to reference a previously chosen segment from a different configuration level.
- Segment Branch Right
Enter the branch/plant associated with the configured item that contains the segment number referenced in the right side of the condition. Use this value to reference a previously selected segment from a different configuration level, and to reference the branch/plant of the item in the Segment Item Right field.
- Configured Item Alias Right
Enter a value from UDC 32/CI that specifies a particular instance of a configured item that is referenced in the right side of the condition.
The Configured Item Alias Right field on the cross-segment editing and assembly inclusion rule forms provides the ability to reference a specific occurrence of an included item. This is not a required field. The Configured Item Alias Right field is for use with duplicate components. If you do not use this field with duplicate components then the system processes duplicate components based on the first duplicate item value that is stored in cache.
Important: You should use the Configured Item Alias Right field to ensure that the correct duplicate item is used in a configuration.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 Right field 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.
- Unit Price
Enter the price that is charged for the unit of measure in the adjoining field. Use these fields, for example, if the primary unit of measure is EA (each), but you typically use a list price per box.
- Unit Cost
Enter a user-defined cost that the system uses based on information that you supply, which includes the name of the costing method and the method of calculation.
- Price Rollup
Enter a UDC (32/PP) that indicates whether the price or cost of an add-on is included in the price or cost of the parent configured item. Values are:
0: Separate the price or cost of the add-on.
1: Include the price or cost of the add-on in the price or cost of the parent item. When you select this value, the extended price or cost is zero.
- Rule Number
Displays the number that indicates the order in which rules were entered in the system for a particular configured item. It also indicates the order in which rules are processed by the system.
- Seq No. (sequence number)
Displays the sequence number for lines in an edit group of cross-segment editing rules or assembly inclusion rules. It is assigned to lines within a rule based on the order in which that line of the rule was entered for a configured item. You can insert a line within a rule to assign a new sequence number.
The sequence number also indicates the order in which each line within a rule will be processed.