10 Set Up Assembly Inclusion Rules

This chapter contains these topics:

Section 10.1, "Set Up Assembly Inclusion Rules,"
Section 10.2, "Defining Assembly Inclusion Rules,"
Section 10.3, "Locating Assembly Inclusion Rules."

10.1 Set Up Assembly Inclusion Rules

You must set up assembly inclusion rules that process requested options and features from sales order entry into the specific components, operations, and calculated values that are necessary to build and price the configured item.

There are five types of assembly inclusion rules:

Rule	Description
Component Part (P) Rules	Define the component parts to include on the sales order and work order parts list. You also define multi-level configured items with these rules. For example, if segment 10 equals 6000 and segment 30 is greater than or equal to 10, then use part F170, else use part F175.
Work Order Component Part (Q) Rules	Define the components to include on the work order parts list. The Process Work Orders program attaches the parts list. For example, if segment 10 equals standard, then include part R100 and part R105.
Pricing (X) Rules	Define the price/cost adjustment. The system processes X rules independently based on the kit pricing method you have selected. You should not set up cost adjustments when using work order-generated line types. For example, if segment 40 equals CUS, then adjust the price by $650.00.
Routing (R) Rules	Define the work order routing and routing operations. The Process Work Orders program attaches work order routings. You must first define the routings on Enter/Change Routing before you define routing rules. For example, if segment 40 equals STD, then use the routing for standard paint. Otherwise, use the routing for custom paint.
Calculation (C) Rules	Define the mathematical calculation for a configured item's calculated segments. You must first define the segment as calculated on Configured Item Segments.

10.1.1 Logic Statements

For each assembly inclusion rule, you can define an "if/then/else" logic statement for many conditions. The following assembly inclusion rule illustrates:

If Segment 10 equals 6000, and segment 30 is greater than 10, then include part F170, else include part F175.

You can use the following conditions:

If
Then
Else
And
Or

10.1.2 Advanced Assembly Inclusion Rules

For an assembly inclusion rule, you can define advanced assembly inclusion rules to:

Expand the derived calculation formula
Define smart parts
Reference external fields
Reference external programs
Reference a table

Derived Calculations

For each rule type, you can define calculations for a specific segment to determine the following:

Rule	Calculation
Calculation (C) Rules	The value for a calculated segment
Routing (R) Rules	Run or machine hours multiplier for a routing or routing step
Pricing (X) Rules	Price multiplier
Component (P and Q) Rules	Quantity multiplier (similar to quantity per assembly)

For each calculation, the following functions are available:

Segment referencing
Algebraic expressions
Trigonometric functions
Exponential/logarithmic functions
A substring function to select a subset of values from a segment
A concatenate function to combine values from two segments
References to fields from other files
Segment definition with a custom-written external program

You can define a derived calculation on either Assembly Inclusion Rules or Advanced Rules.

Understanding Smart Parts

For quantity rules (P rules and Q rules), you can build "smart part" numbers from the segment values that you entered on the sales order. The simplest form of a smart part is that the answer to a segment question is a part number. The system calculates smart parts in a similar manner to derived calculation string-related operations.

Referencing External Fields

As you define a derived calculation, you can include field values on External Files Reference. For example, a pricing assembly inclusion rule for FORKLIFT-A uses a field reference to retrieve a base price from the Base Price table (F4106).

Referencing External Programs

You can reference an external custom program for special calculations. This is useful if the calculation requires several steps or requires more characters than available.

Multi-Level Processing

If a configured item includes multiple levels, the system processes each component down the item hierarchy before processing across. This process determines the order in which segments appear during sales order entry.

For example, in the following configured item, forms appear during sales order entry in the order A, B, C, D, E:

Figure 10-1 Multi-Level Processing Configuration

Description of "Figure 10-1 Multi-Level Processing Configuration"

Consider multi-level processing before you set up your rules, so that the system references segments for previously entered values. Use P type assembly inclusion rules to define your multi-level configured items. If you use configured items as components within multi-level configured items, ensure that the configured component items are unique.

Referencing Table Names

You can use advanced rules to reference a table that returns calculated segment values, prices, and parts to the assembly inclusion rules.

Reference	Description
Referencing segments	For both Q and P rules, you can reference upper and lower level segments from assembly inclusion rules, tables and derived calculations.

Also:

10.2 Defining Assembly Inclusion Rules

Navigation

From Configurator (G32), enter 29

From Configurator Setup (G3241), choose Assembly Inclusion Rules

Defining assembly inclusion rules consists of the following tasks:

Defining unconditional rules
Defining conditional rules
Defining values
Defining ranges
Setting up advanced rules (optional)
Copying rules (optional)

To define unconditional rules

Before you define conditional rules, you can define unconditional rules to include parts, adjustments, calculated values, or routing steps regardless of the values in segment questions.

On Assembly Inclusion

Figure 10-2 Assembly Inclusion screen

Description of "Figure 10-2 Assembly Inclusion screen"

Complete the following fields:
- Branch/Plant
- Rule Type
- Configured Item
Complete the following field with an asterisk:
- And/Or
Complete the following fields:
- Item
- Line Type

To define conditional rules

On Assembly Inclusion

Complete the following fields:
- Branch/Plant
- Rule Type
- Configured Item
- If
- Bracket
- Segment
- Relationship
- Values
- Bracket
- Then
- Item
- Operation Sequence
- Line Type
Access More Details.

Figure 10-3 Assembly Inclusion (Details) screen

Description of "Figure 10-3 Assembly Inclusion (Details) screen"
Complete the following fields:
- Quantity
- Effective From
- Component Branch
- Effective Thru
Complete the following optional fields:
- Segment Item
- Segment Branch
- Issue Type Code
- Price Rollup
- Derived Calculation

Field	Explanation
Branch/Plant	A number that identifies a branch, plant, work center, or business unit. Form-specific information You can define a generic or blank branch/plant for assembly inclusion rules and then use the rules for all branch/plants.
Rule Type	Designates the type of included components: C – Calculation P – Part List Q – Work Order Component R – Route Sheet X – Price/Cost Adjustment
Configured Item	A number that the system assigns to an item. It can be in short, long, or 3rd item number format. Form-specific information Header: The configured item number for which assembly inclusion rules are being defined. Detail: For P rules, this item is included in the parts list. For R rules, the routing for this item is copied.
And/Or Selection	A code that determines whether compound data selection logic is based on an A = AND condition or an O = OR condition. Form-specific information For configuration management, you can include parts, prices, costs, or routings with the configured item. Additional values include: I – If E – Else * – Then For example: I – Seg 1 = A * – Part B E – Part C E – Part D If Seg 1 is A, include part B. If Seg 1 is not A, include part C and part D.
Price	The price charged for the unit of measure in the adjoining field. Use these fields, for example, if your primary unit of measure is EA (each), but you typically use a list price per box.
Cost	A user-defined cost the system uses based on information that you supply, which includes the name of the costing method and the method of calculation.
Op Seq	In routings, this number is used to sequence 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 number 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 for the item. The Shop Floor Control system uses this field in the backflush/preflush by operation process. In engineering change orders, this number is used to sequence the assembly steps for the engineering change. Skip To fields allow 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. Form-specific information For R rules, this value defines which routing step should be added to the configured item's work order routing. For P and Q rules, this value controls the consumption of material during backflush or super backflush transactions.
Item Number - Unknown Format Entered	The item number entered which can be in any of the three formats (short, long, or 3rd item number). Form-specific information The configured item number of the segment in the Assembly Inclusion Rule. Use this number to reference a previously selected segment.
Price Roll Up Flag	Determines whether the price/cost is rolled up into the parent item. The extended price/cost will be zero if the flag is set to roll up to the parent. Y or 1 - Roll up price or cost to parent. N or 0 - Separate price/cost add-on.
Effective From	A date that indicates one of the following: When a component part goes into effect on a bill of material When a routing step goes into effect as a sequence on the routing for an item When a rate schedule is in effect The default is the current system date. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Control, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
Thru	A date that indicates one of the following: When a component part is no longer in effect on a bill of material When a routing step is no longer in effect as a sequence on the routing for an item When a rate schedule is no longer active The default is December 31 of the default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Control, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
Comp Branch	A secondary or higher level business unit. Sometimes used to reference a branch or plant with several departments or jobs subordinate to it. Branch/Plant - (MMCU) Dept A - (MCU) Dept B - (MCU) Job 123 - (MCU)
Issue Type Code	A code that defines how the system issues each component in the bill of material from stock. In shop floor control, it indicates how the system issues a part to a work order. Valid codes are: I – Manual issue (default) F – Floor stock (no issue) B – Backflush (when part is reported as complete) P – Preflush (when parts list is generated) U – Super backflush (at pay-point operation) S – Sub-contract 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 a different code on the bill of material and work order parts list. The bill of material code overrides the branch/plant value.
Print Part	This field will determine if the Configurator part should print on the sales order and work order. The flag will be used in the Pick Slip, Invoice Print, Bill of Lading, and Print Parts List. Y – Print on sales and work order N – Do not print on sales and work order 2 – Print on sales order only 3 – Print on work order only You can also use 1 for Y and 0 for N.
Derived Calculation	Defines an algebraic formula that calculates the quantity, price, hours or a value associated with a rule. For example: Segment References S3 indicates segment 3. S3=Piston= indicates segment 3 in item Piston. Trigonometric and Logarithmic Functions SIN(20) indicates the sine of 20. COS(S3) indicates the cosine of segment 3. TAN(S4) indicates the tangent of segment 4. ARC(S) indicates the arctangent of segment 3. LOG indicates log to base 10. LN indicates natural log. 2**5 indicates an exponent, 2 to the fifth power. Substring SUBSTR(S10,1,4) indicates that the substring from segment 10 starts at the first position of the string and includes the first 4 positions. Concatenations CONCAT(S3,S4) combines the values of segments 3 and 4. External Fields To specify external fields from external files. use & followed by the field name. For example, &T2AMTU(WD) indicates an amount field on the Item Supplemental Database table, and the WD data type. External Programs To define an external program for the calculation, enter the name of the external program and EXTVAR in the Derived Calculations field. Smart Parts PS4 indicates a smart part number P2000 when the value of segment 4 is 2000.
Quantity - Standard Required Quantity	The number of units to which the system applies the transaction.

10.2.1 What You Should Know About

Topic	Description
Price rollup	During sales order entry processing of pricing rules, the system compares the line type of the configured item on the sales order to "true" x rule line types. If the line types match, the price adjustment is reflected in the configured parent's unit price. If the line types are different, the price rollup field is used to determine if the price adjustment is reflected in the parent's unit price.
Revising lines	You can use the insert line option and the delete line option to revise the assembly inclusion rules.
Assembly inclusion rule processing	During sales order entry, the system processes each assembly inclusion rule independently by rule type from top to bottom in the following order: C rules Cross-segment editing rules P rules Q rules (if necessary) R rules (if necessary) X rules

To define values

On Assembly Inclusion

Complete the following field with *VALUE:
- Value
The system prompts you to work with *VALUE entries on Value Selection.

Figure 10-4 Value Selection screen

Description of "Figure 10-4 Value Selection screen"
On Value Selection, complete the following field:
- Value

10.2.2 What You Should Know About

Topic	Description
Revising *VALUE	To revise existing VALUE entries, place the cursor on VALUE and choose the Range/Values function.

To define ranges

On Assembly Inclusion

Complete the following field with *RANGE:
- Value
The system prompts you for all new and changed rules containing a *RANGE.

Figure 10-5 Value Selection (*RANGE) screen

Description of "Figure 10-5 Value Selection (*RANGE) screen"
On Value Selection, complete the following fields:
- From Range
- To Range

10.2.3 What You Should Know About

Topic	Description
Revising *RANGE	To revise existing RANGE entries, place the cursor on RANGE and choose the Range/Values function.

To set up advanced rules

On Assembly Inclusion Rules

Access Advanced Rule Functions.

Figure 10-6 Advanced Rule Functions screen

Description of "Figure 10-6 Advanced Rule Functions screen"
On Advanced Rule Functions, complete one or more of the following fields:
- Derived Calculation
- External Program
- Table Name
- Smart Part

To copy rules

On Assembly Inclusion

On a blank line, access Rules Copy Window.

Figure 10-7 Rules Copy Window screen

Description of "Figure 10-7 Rules Copy Window screen"
On Rules Copy Window, locate the configured item from which you want to copy a rule.
Do one of the following:
- To select a line, choose the Select Value option.
- To select the complete rule, choose the Select Group option.

10.2.4 Processing Options

Section 23.5, "Assembly Inclusion Rules (P3293)."

10.3 Locating Assembly Inclusion Rules

You review assembly inclusion rule information to help you maintain these rules. You can determine the effect of component changes such as shortages and substitutions, and determine the effect of changes to valid segment values. For example, if a vendor discontinues a paint color, you can determine how many configurations will be affected.

Locating assembly inclusion rules consists of the following tasks: