Setting Up Configurator

This chapter provides overviews of configurator setup, setup prerequisites for configurator, configured item pricing, duplicate components, and media object attachments for configured items, and discusses how to:

• Set up configurator constants.

• Set up configured item segments.

• Set up cross-segment editing rules.

• Set up assembly inclusion rules.

• Set up configured tables.

Understanding Configurator Setup

You must set up the JD Edwards EnterpriseOne Configurator system before you can enter orders for configured items.

JD Edwards EnterpriseOne Configurator system setup consists of setting up:

• Configurator constants

• Configured item information

• Configured item segments

• Cross-segment editing rules

• Assembly inclusion rules

• Configured tables

• Media object attachments

Configurator constants control the JD Edwards EnterpriseOne Configurator system processing by branch/plant for the business. For example, constants control:

• Sales quote processing

• Availability checking

• Display of calculated segments

Setup for configured item information defines the format in which configured item information appears on order paperwork and the transaction type that the configured item generates, such as sales order, direct ship order, and transfer order.

Segments are the features and options of a configured item. Segments represent product characteristics such as color, material, or size. For clarification purposes, you assign numbers to each segment of the configured item. Information from the Display Order field determines the order in which you specify the segment value during order entry.

You set up cross-segment editing rules with logic statements to establish the relationship between the segment values. Use these rules to prevent invalid configurations during order entry. You can define custom error messages for a cross-segment editing rule.

Assembly inclusion rules process requested features from order entry into the specific components and routing operations that are necessary to build the configured item. Different types of assembly inclusion rules enable you to define:

• Components

• Price/cost adjustments

• Routings

• Calculated values

• Hot spot values

Assembly inclusion rules also offer advanced logic, such as algebraic expressions, smart parts, and external program references.

You can also set up tables for assembly inclusion rules to reference information that is based on segment values. You can define tables for components, prices, and calculated values. Using tables reduces the number of required rules, simplifies rule maintenance, and improves processing time.

You can attach media objects such as text, image, and OLE to configured items. Media object attachments provide additional information about the configured item, components, and configured item segment values. The information could be useful to order entry personnel.

Note. You can define segments, rules, and configured items that are specific to a branch/plant or generic across all branch/plants. A blank Branch/Plant field identifies a generic branch/plant. If you do not use the generic branch/plant, then segment, rule, and item information should be the same across branch/plants. If you define generic branch/plant segments, you must also define generic cross-segment editing and assembly inclusion rules.

Understanding Setup Prerequisites for Configurator

The JD Edwards EnterpriseOne Configurator system works with other JD Edwards EnterpriseOne systems. Before you set up the JD Edwards EnterpriseOne Configurator system, you should be familiar with these JD Edwards EnterpriseOne systems:

• JD Edwards EnterpriseOne Inventory Management

• JD Edwards EnterpriseOne Product Data Management

• JD Edwards EnterpriseOne Shop Floor Management

• JD Edwards EnterpriseOne Sales Order Management

• JD Edwards EnterpriseOne Procurement

• JD Edwards EnterpriseOne Work Order Management

• JD Edwards EnterpriseOne Engineer to Order

Note. The information that is provided here is specific to setting up the JD Edwards EnterpriseOne Configurator system. For more information regarding setting up these other systems, please refer to the respective implementation guides.

JD Edwards EnterpriseOne Inventory Management and JD Edwards EnterpriseOne Configurator

The JD Edwards EnterpriseOne Inventory Management system stores item information, sales and purchasing costs, and quantities that are available by location. The JD Edwards EnterpriseOne Inventory Management system is used to set up item information for configured items and their components, and configured subassemblies. Programs in the JD Edwards EnterpriseOne Inventory Management system define the configured item information, such as how the item is identified and stocked.

You enter Item Master information, such as item number, description, stocking type, cost, and price information, that is unique to the item across all branch/plants.

When processing Item Master Revisions, select C for configured item in the Stocking Type field.

If you want the system to automatically generate work order headers at time of order entry, then select the work order line type in the Line Type field. Select the line type for stock item if you do not need work orders.

To gather accurate costs for a configured item, select 3 in the Inventory Cost Level field, which identifies costs of the configured item at the item, branch/plant, location, and lot levels. Because configured items are specific and unique in their configuration, they must be set to this level of cost detail to obtain an accurate cost for configured components and the configured end-item.

The Configurator Costing Method field can also be used to indicate how the cost is calculated for a configured item on purchase orders only.

You have several options for pricing a configured item. You accomplish this pricing by selecting a value in the Kit/Configurator Pricing Method field. Select from these pricing methods:

• Total the list prices of components to determine the configured item price.

• Use the list price of the configured item.

• Use assembly inclusion pricing rules to determine the price.

• Total the discounted price of components.

Base prices can be established in the system for components and configured items. Advanced pricing can be used with any price method code. You can also use price adjustment, or X assembly inclusion rules, to affect the price for the configured item, regardless of the price method that you chose.

Because configured items have the same item number in the Item Master (for example, the forklift is item 6000), the system requires additional information to stock the configured item in inventory. This information enables the system to differentiate one configuration from another. Thus, configured items must be lot controlled. Configured items also need to be stocked in a specific location. Using lot and location control identifies each configured item as unique.

You can have lot numbers automatically assigned to configured items by setting a value in the Lot Process Type field. Instead of turning on lot control, the system can be set up to assign the lot and location automatically during work order completions (by way of the processing options), or the lot and location can be manually entered (at completions). The method that is used to assign lot and location information to a configured item is a business process that you must determine.

In the Item Master program, you can define the level lead time for the configured item on the Additional System Information form. The system uses this value to calculate the start dates for work orders by using fixed lead times. The start dates on a work order header are usually back-scheduled, based on the request date of the order (such as a sales order). Because each configured item is unique and difficult to plan for in the planning system, this field is used to schedule the configured item work orders accurately.

After you enter generic item information, you can enter Item Branch (P41026) information that is unique to an item for a specific branch/plant.

You can define the stocking type, line type, lot process type, and location at the branch/plant level for the configured item, configured subassemblies, and components.

JD Edwards EnterpriseOne Product Data Management and JD Edwards EnterpriseOne Configurator

The JD Edwards EnterpriseOne Product Data Management system enables you to organize and maintain information about each item that you manufacture. The JD Edwards EnterpriseOne Configurator system further defines the relationship between items and how they can be manufactured.

Although you do not need to create a bill of material for a configured item, you can create a bill of material for the manufactured components for the configured item. Use assembly inclusion rules to define component relationships for configured items. The system adds configured components to sales orders and work orders, based on these rules.

During setup, consider creating modular bills of material that group common parts for a specific feature or option. For example, a car might have an interior trim package with two choices: standard and deluxe. Each choice includes specific parts and might represent two different modular bills.

Although planning bills of material are not required for the JD Edwards EnterpriseOne Configurator system, you can use them to help manage demand for specific features and options.

You can define all possible routings for the configured item and define assembly inclusion rules to select which routing to attach to the work order. The routing assembly inclusion rule enables you to specify a complete routing or specific routing operations to attach to a configured item work order. You do not need to enter a routing for the configured item unless you also enter a routing inclusion rule.

JD Edwards EnterpriseOne Shop Floor Management and JD Edwards EnterpriseOne Configurator

The JD Edwards EnterpriseOne Shop Floor Management system enables you to control the flow of materials inside the plant by managing and tracking manufacturing work orders. It provides an effective way to maintain and communicate information that the system requires to complete production requests.

The JD Edwards EnterpriseOne Configurator system integrates with JD Edwards EnterpriseOne Shop Floor Management to manage the work orders for configured items. Before you can process work orders for configured items, you must enter business-specific information in Shop Floor programs within the JD Edwards EnterpriseOne Manufacturing system from Oracle.

The system enables you to generate work order headers at the time of sales order entry. You must ensure that JD Edwards EnterpriseOne Sales Order Management is set up so that the interface exists with the JD Edwards EnterpriseOne Work Order and JD Edwards EnterpriseOne Shop Floor Management systems to support these order types.

The system also enables you to enter work orders for configured items directly through the Manufacturing Work Order Processing program (P48013). This step gives enables you to generate work orders for configured items that you might want to prebuild or stock in inventory to better meet the demands of the business.

After the work orders are created, they move through the JD Edwards EnterpriseOne Shop Floor Management system using Order Processing (R31410) and other shop floor programs as dictated by business processes.

JD Edwards EnterpriseOne Sales Order Management and JD Edwards EnterpriseOne Configurator

The JD Edwards EnterpriseOne Sales Order Management system controls all aspects of processing sales orders. The JD Edwards EnterpriseOne Configurator system works with the JD Edwards EnterpriseOne Sales Order Management system to adapt the way that you enter and process sales orders for configured items.

Besides regular sales orders, the JD Edwards EnterpriseOne Sales Order Management system also supports sales quotes, credit, transfer, direct ship, interbranch, and combination orders for configured items.

Before you can enter orders for configured items, you must enter business-specific information in the JD Edwards EnterpriseOne Sales Order Management programs within the JD Edwards EnterpriseOne Distribution system from Oracle.

You must set up order line types and document types (order types) for the system to use. The order line type tells the system how to process each detail line that you enter for a specific order type (for instance, T is a text line). The document type identifies the origin and purpose of the transaction (for instance, SO is a sales order). The order activity rules are then set up by combination of an order type and a line type. The order activity rules define the specific steps in the order processing cycle for the business.

You set up new line types to generate work orders (in addition to sales orders) for configured items during sales order entry.

A typical sales order cycle includes sales order entry, packing, shipping, and invoicing. For a work-order-generated line type and sales order document type, you can add to the cycle steps for creating the work order parts lists and completing work orders for configured items. Optionally, both of these manufacturing processes can update associated sales order activity.

A work-order-generated line type and sales quote document type are typically used for entering sales quotes for configured items. However, additional system setup prohibits the creation of associated work order headers when a quote order is generated.

A credit order line type and credit order document type are used for entering credit orders for configured items. Because credit orders facilitate receiving product back from a customer, the system must be set up so that the configured item can be put back into inventory.

The appropriate line types, document types, and order activity rules should be set up to support transfer, direct ship, interbranch, and combination orders for configured items. You must also ensure that the Procurement system is set up so that the interface exists with the JD Edwards EnterpriseOne Sales Order Management system to support these order types.

JD Edwards EnterpriseOne Procurement and JD Edwards EnterpriseOne Configurator

The JD Edwards EnterpriseOne Procurement system controls all aspects of purchasing activities. The JD Edwards EnterpriseOne Configurator system works with the JD Edwards EnterpriseOne Procurement system to adapt the way that you enter and process purchase orders for configured items.

Besides regular purchase orders, the JD Edwards EnterpriseOne Procurement system also supports purchase orders that are created at the time of sales order entry for transfer, direct ship, and combination orders for configured items.

Before you can enter purchase orders for configured items, you must enter business-specific information in the JD Edwards EnterpriseOne Procurement programs within the JD Edwards EnterpriseOne Distribution system.

You must set up order line types and document types (order types) for the system to use. The order line type tells the system how to process each detail line that you enter for a specific order type (for instance, T is a text line). The document type identifies the origin and purpose of the transaction (for instance, OP is a purchase order). The order activity rules are then set up by combination of an order type and a line type. The order activity rules define the specific steps in the order processing cycle.

You set up a line type for configured items and a document type for the purchase order.

You also set up order activity rules to define the specific steps in the purchase order processing cycle. A typical purchase order cycle includes purchase order entry, printing and communicating the order, and receiving goods or services.

The appropriate line types, document types, and order activity rules should be set up to support transfer, direct ship, and combination orders for configured items. You must also ensure that the JD Edwards EnterpriseOne Sales Order Management system is set up so that the interface exists with the JD Edwards EnterpriseOne Procurement system to support these order types.

JD Edwards EnterpriseOne Work Orders and JD Edwards EnterpriseOne Configurator

The JD Edwards EnterpriseOne Work Order Management system controls the processing of work orders. The JD Edwards EnterpriseOne Configurator system works with the JD Edwards EnterpriseOne Work Order Management system to adapt the way that you enter and process work orders for configured items.

Before you can enter work orders for configured items, you must enter business-specific information in the work order programs within the JD Edwards EnterpriseOne Manufacturing system.

The JD Edwards EnterpriseOne Work Order Management system is specifically designed to handle small, short-term tasks that are part of a major project. It is also designed for quick setup, simple cost accounting, and basic scheduling for projects that can be completed quickly.

Generating a work order is the activity that starts the process of completing a task. The work order identifies the work that needs to be done, and the information that is collected captures the history of the work that is performed.

The system enables you to enter work orders for configured items directly through the work order entry process. This process enables you to generate work orders for configured items that you might want to prebuild or stock in inventory to better meet the demands of the business.

To enter work orders for configured items, the Manufacturing Work Order Processing program (P48013) and processing options must be set up appropriately.

After the work orders are created, they move through the JD Edwards EnterpriseOne Shop Floor Management system by way of Order Processing (R31410) and other shop floor programs as dictated by the business processes. Thus, you must ensure that the JD Edwards EnterpriseOne Shop Floor Management system is set up.

The system also enables you to generate work order headers at the time of sales order entry. You must ensure that the JD Edwards EnterpriseOne Sales Order Management system is set up so that the interface can support the order types in the JD Edwards EnterpriseOne Work Order Management and JD Edwards EnterpriseOne Shop Floor Management systems.

JD Edwards EnterpriseOne Engineer to Order and JD Edwards EnterpriseOne Configurator

The JD Edwards EnterpriseOne Engineer to Order (ETO) system controls all aspects of project management, primarily in an engineer-to-order (ETO) environment. The JD Edwards EnterpriseOne Configurator system works with the ETO system to adapt the way that you enter and process various order types for configured items which are part of a project.

The JD Edwards EnterpriseOne ETO system supports sales orders, purchase orders, and work orders for configured items.

You must ensure that the appropriate systems (such as JD Edwards EnterpriseOne Sales Order Management, JD Edwards EnterpriseOne Procurement, and JD Edwards EnterpriseOne Work Order Management) are set up for integration with JD Edwards EnterpriseOne ETO and JD Edwards EnterpriseOne Configurator.

Understanding Configured Item Pricing

The first step in pricing configured items is to set the Kit/Configurator Pricing Method field on the Item Master Revisions form. The kit/configurator pricing method is used to specify how the system determines the sales price of a kit or configured item. The price method code determines whether to price components or parent items.

This table describes the types of method codes that are used:

Note. If the Item Base Price table (F4106) is used for pricing the configured item and the X assembly inclusion rule contains & BPUPRC in the Derived Calculation field to pull the base price, the price is doubled on the order. If table F4106 is used to pull the base price, the X assembly inclusion rules should be used only for other price adjustments, such as shipping or freight charges.

After you define the Kit/Configurator Pricing Method on the Item Master Revisions form, you must define base prices for the components and the configured item in the F4106 table. The system uses the base price to price the item. If you define special pricing or discounts for the item, the system bases the calculation of the discounted price on the base price.

Use base pricing to define prices for:

• An item or group of items.

• A specific time period.

• Different units of measure.

• Different currencies.

Use pricing groups to group items or customers with similar characteristics. This method streamlines the processes of entering and maintaining base prices.

Advanced pricing can also be used with any price method code. Advanced pricing supports placing a new line item on the sales order, such as a line item for free goods.

You can use price adjustment, or X assembly inclusion rules, to affect the price for the configured item, regardless of the price method that you selected. X rules work with base and advanced pricing as well.

Understanding Duplicate Components

You can add multiple instances of a configured component item to a configured parent item. Each new instance of the component can be configured uniquely or be an exact copy of an instance of the component that you previously configured. You can use a single part number to represent the various configurations of a component item, thus reducing the number of part numbers that you must manage.

To include multiple instances of a configured component item in a parent item, you add the appropriate P-type assembly inclusion rules to the parent item. You can include multiple instances of the configured component item within the configured parent item with unconditional or conditional rules.

Whether multiple instances of the configured component item are included as part of the default configuration (using unconditional rules) or as part of a subsequent configuration (using conditional rules), each instance can be configured differently, but have the same part number. Using a single part number enables you to set up all of the associated segments, assembly inclusion rules, and cross-segment editing rules for a single item, and then create various configurations for that item.

The system uses a sequence ID to help identify duplicate components in a configuration. The sequence ID is a next number type sequence ID. The IDs are assigned sequentially. This sequence ID facilitates multiple instances of a configured component item in a configured parent item, each having a unique segment value.

Currently, you can refer to an upper-level configured item in cross-segment editing rules, assembly inclusion rules, and derived calculations. The JD Edwards EnterpriseOne Configurator system correctly processes the rules, based on the upper-level configured item segment selection. With the introduction of duplicate components, referring to an upper-level duplicate configured item adds complexity because no ability to identify the sequence ID of the referred duplicate component currently exists. Thus, when processing rules where the duplicate configured items have different segment values, the system encounters difficulty identifying which duplicate component segment value to use. Therefore, the system must make an assumption to resolve this issue. When the referred upper-level configured item is a duplicate component, the system processes rules that are based on the first duplicate item value that is stored in cache. Cache is evaluated from the top down so that the first component that it finds will be used.

Example: Duplicate Components

The cabinet can be configured with two or three drawers, depending on the height of the cabinet:

• * body (unconditionally add a configurable cabinet body to the configuration).

• * drawer (unconditionally add a configurable drawer to the configuration).

• * drawer (unconditionally add a configurable drawer to the configuration).

• I height = 36 * drawer (if the height of the cabinet is 36 inches, add a third configurable drawer to the configuration).

Each instance of the drawer in this example can be configured differently but have the same part number.

Understanding Media Object Attachments for Configured Items

You can attach media objects to configured Item Master records, segments, and user-defined codes (UDCs) to use within the JD Edwards EnterpriseOne Configurator system. This feature of the system enables you to include a visual cue of configured items, configured item segments, and UDC values, which can be used for segment answers within order entry. Media objects can be photos, graphics, files, or text documents, including information that might initially exist on a paper document.

Note. The media object is attached to the Item Master through the Internal Attachment Row menu, not to the Item Branch/Plant.

The media objects that you define appear on the Configure Item form at order entry. As you select a configured item from the Attribute Filter option, the media object displays the image from the Item Master for the related configured item number. The segment or segment-answer user-defined code displays the media object when a row is selected.

The display of media objects at order entry is controlled by the processing options for the Configured Item Revisions program (P3210). The Media Object Display processing option controls whether an attached media object is displayed on the form during order entry. The Media Object Display Order processing option specifies the order in which media objects appear on the form if more than one media object type is attached to a configured item, configured segment, or user-defined code segment value.

Setting Up Configurator Constants

This section provides an overview of configurator constants and discusses how to define configurator constants.

Understanding Configurator Constants

Use configurator constants to control the JD Edwards EnterpriseOne Configurator system processing for the branch/plants. For each branch/plant, you can:

• Define the configured segment (string) delimiter.

• Define whether the calculated segments appear during order entry.

• Indicate the configurator error character.

• Verify parent availability during sales order entry.

• Determine whether the sales quote cost will include manufacturing labor and overhead.

• Define which stocked line type to use if the system finds a matching configuration in stock during sales order entry.

• Indicate sales quote document types.

The system stores configurator constants in the Configurator Constants table (F3209).

Form Used to Set Up Configurator Constants

Defining Configurator Constants

Access the Configurator Constants Revision form.

Configurator constants are defined by branch/plant.

Setting Up Configured Item Segments

This section provides overviews of configured item segments and common attributes, lists prerequisites, and discusses how to:

• Define configured item information.

• Define a configured item segment.

• Set up user-defined segment values.

• Copy configured items.

• Locate configured item segment information.

• Print configured items.

Understanding Configured Item Segments

To begin using the JD Edwards EnterpriseOne Configurator system, you must define configured item information and the segments of each configured item.

Configured item information defines the format in which configured item information appears on order paperwork and the transaction type that the configured item generates, such as sales order, direct ship order, and transfer order.

Segments are the features and options of a configured item. Both cross-segment editing rules and assembly inclusion rules use segments within logic statements. Segments represent product characteristics such as color, material, and size. Segments define the choices that are available within a specific feature or option by using UDCs, ranges of values, or calculations. For clarification purposes, you assign numbers to each segment of the configured item. Information from the Display Order field determines the order in which you specify the segment value during order entry.

When adding new segments to a configured item, enter them at the end of the list of existing segments. This process keeps the configuration information in order, which is important if you will be using the Check Availability functionality.

You assign segments for a configured item in a numeric sequence.

Item 6000 (forklift) contains these segments:

• 10 Forklift Rating

• 20 Power Type

• 30 Boom Height

• 35 Interior

• 40 Paint

• 50 Propane Tank

• 60 Calculated Counterweight

• 65 Additional fork (spare)

You can define three types of segments:

• Required: During order entry, you must provide this required information. The system performs edit checking against a UDC table of values, a range of values, or numeric validation.

• Optional: During order entry, this information is optional. The system performs edit checking against a UDC table of values, a range of values, or numeric validation.

• Calculated: During order entry, the system calculates the value for this segment. You define the calculation with a C (calculation) assembly inclusion rule. Calculated segments do not need a UDC or range of values defined. Calculated segments can be numeric or alphanumeric.

  Note. The segment information for a configured item should be the same across branch/plants to enable transfers to other branches.

During order entry, you can enter a value for each segment. The system restricts this value, using one of these:

• Numeric or alphabetic checking.

• Range checking.

• A UDC table that contains all values.

You can define multilevel configured items with no limit on the number of levels. In addition, no limits exist on the number of segments per level. You use assembly inclusion rules to define item levels and associated work orders.

You use segments to define cross-segment editing rules that ensure valid configurations. During order entry, the system verifies the combination of features and options to ensure that the item can be manufactured. You also use segments to define assembly inclusion rules that determine configuration-specific prices, components, calculated values, and routing steps.

Note. The segments can be set up so that a value from a C (calculated) assembly inclusion rule populates the answer field for a non-C segment (a required or optional segment).

Understanding Common Attributes

A common attribute in the JD Edwards EnterpriseOne Configurator system is a trait or characteristic that is shared by several segments in a configured item. You can set up and define a common attribute in Common Attributes UDC table (32/CA). You then attach the common attribute to a particular segment using the Common Attribute field in Configured Item Segments (P3291).

Note. If using common attribute functionality, set the Common Attribute Display and Common Attribute Display Scope processing options on the Processing tab for the Configured Item Revisions program (P3210).

You enter the value for the common attribute at order entry. When the value is entered in the Attribute Value field on the Configurator Common Attributes form, the value automatically fills the answer field for all of the segments that are associated with that common attribute. This process makes order entry input easier, reduces order entry time, and also reduces potentially costly order entry errors.

Example: Common Attributes

The furniture industry often uses common attributes. In a configuration for a sofa, a common attribute might be Color. The Color common attribute is associated with the segments for the sofa frame, bottom sofa cushions, sofa arm covers, and decorative pillows. After the customer picks a color, that value can be entered in the attribute field on the common attribute form. The color is then applied as the answer to all segments that are associated with that particular common attribute.

Prerequisites

Before you enter configured item segments, you must:

• Verify that the stocking type for a configured item is C (configured).

• Set the Kit/Configurator Pricing Method on Item Master Revisions.

• Verify that the manufactured configured components have bills of material.

• Create routings for the configured item and for the components that are manufactured.

See Entering Item Master Information.

See Setting Up Bills of Material.

See Creating Routing Instructions.

Forms Used to Set Up Configured Item Segments

Defining Configured Item Information

Access the Configured Item Information form.

Print Components	Enter a code that specifies whether the system prints configured item information on the order paperwork. On a sales order, the system prints the pick slip and the invoice. On a work order, the system prints the parts list. Values are: 0: Do not print. 1: Print.
Text String	Enter a code that indicates whether the configured text string format or a user-defined format appears on the sales order (pick slip and invoice print) and work order (print parts list). You define the user-defined format for each segment. You can print the segment number, description, value, or value description in the user-defined format. Values are: 1: Configured text string. 0: User-defined format.
Display Item	Enter a code that indicates whether the system prints the configured item number. If selected, the item number will print before the segment value information either in the text string format or the user-defined format. Values are: 1: Print. 0: Do not print.

Defining a Configured Item Segment

Access the Configured Item Segments Revision form.

Note. You cannot delete a configured item segment if cross-segment editing or assembly inclusion rules exist for that configured item.

To control the printing of configured item information on sales orders, purchase orders, and work orders, complete these fields.

Setting Up User-Defined Segment Values

Access the User Defined Codes form.

Create a UDC table of segment values for a noncalculated segment. The UDC table that the segment references presents the choices that are available within that particular feature or option.

Note. You can use codes 55 through 59 for the UDC types. When you set up custom UDC tables for use with the JD Edwards EnterpriseOne Configurator system, you should use these system codes so that the custom UDCs are not overwritten during a software upgrade.

Note. If you associate a required segment with a UDC table, you must select a value from the table. If you associate an optional segment with a UDC table, do not enter a value or enter a value from the UDC table.

Copying Configured Items

Access the Copy Configured Item form.

Note. When you copy a configured item, you can copy any attribute from the original item. However, you cannot copy from one rule type to another. For example, if the original item was set up with a P assembly inclusion rule, you cannot copy it to a Q assembly inclusion rule.

Locating Configured Item Segment Information

Access the Segment UDC Where Used form.

For the UDC table that you specify, you can locate all configured items and segments that reference the table. This is useful for reviewing the effect of table changes on configured items.

Printing Configured Items

Select Print Segments from the Form menu on the Configured Item Segments Revision form.

Print a hard copy of the configured item segments. Use the hard copy to verify the accuracy of the configured item segment setup.

Note. On the Work with Batch Versions form, copy the version XJDE0001 that is delivered with the software to create another version of the program that you can modify.

Setting Up Cross-Segment Editing Rules

This section provides overviews of Boolean logic, cross-segment editing rule logic, and error messages and discusses how to:

• Define a cross-segment logic statement.

• Define values for cross-segment logic statements.

• Define ranges for cross-segment logic statements.

• Copy a cross-segment editing rule.

• Set up custom error messages.

• Review cross-segment editing information.

• Print cross-segment editing rules.

Understanding Boolean Logic

Boolean logic is based on the binary number system, so it uses the bit system of 1 or 0 (true or false). Boolean logic uses statements that are written in an algebraic format to derive deductions using algebraic operations. The statements define the relationships between sets of ideas or objects. Boolean statements produce precision and control. The logic uses English words to make the statements more intuitive. However, it is not always simple or easy.

Boolean logic uses words that are called operators to determine whether the value of a statement is either true or false. Boolean operators are conjunctions that are used with terms and phrases to create precise conditional statements. Although the most common operators are AND and OR, different systems use various symbols for the Boolean logic operators.

Nesting

Nesting is the method of combining Boolean operators in a logical order when more than one Boolean operator is used in a statement. Parentheses are used to effectively sequence the operators and group variables. The parentheses offer substantial control in limiting and ordering the relationship between the variables.

Note. Complex nesting requires additional processing time.

When writing a nested Boolean logic statement using the operator OR, you must enclose the terms in parentheses. For example:

(Gas or Propane) and (08 or 10)

Conditional Logic

In its simplest form, a conditional statement is an IF-THEN statement and consists of two parts:

• Hypothesis: The hypothesis is preceded by an IF.

• Conclusion: The conclusion can be preceded by a THEN.

The IF-THEN statement is typically formatted as like this:

IF condition, THEN statement.

IF is the beginning of the IF-THEN statement, and THEN identifies what actions should be taken if the condition in the IF statement is met. For example:

If the power type is not propane, then no propane tank (should be selected).

Multiple Variables

If you use nesting, the condition and statement portions of the IF-THEN statement can be compound (several variables). For example:

If the forklift rating is 6000 pounds and the power type is propane, then the propane tank must be 50 pounds.

Conditional Statement with Else

The IF-THEN-ELSE statement is also used. The ELSE portion of the statement identifies what actions should be taken if the condition in the IF statement is not met.

The IF-THEN-ELSE statement is typically formatted as like this:

IF condition, THEN statement (ELSE statement).

For example:

If the paint color is standard, then select part number S-200 or else select part number C-100.

Understanding Cross-Segment Editing Rule Logic

The JD Edwards EnterpriseOne Configurator system uses cross-segment editing rules 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, or else segment 30 must be less than or equal to 10.

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 by the validate configuration function 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 calculation functionality. 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.

Note. No limit exists on the nesting of cross-segment editing rules. However, nesting does have an impact on system performance. The deeper the rules are nested, the slower the processing time.

Understanding Error Messages

As you enter an order, error messages appear for invalid combinations that are defined by cross-segment editing rules.

These error messages might appear:

• Hard error message: For an invalid combination with a required condition, a hard error message appears. To proceed, you must correct the problem by changing segment values.

• Soft error message: For an invalid combination with an optional condition, a soft error message appears. You can either correct the segment value, or override the error message and continue configuring the item.

The two types of messages are:

• A system-generated message.

  When an error occurs, the system automatically generates an error message. System-generated error messages contain the cross-segment editing rule (Boolean logic) that has been violated. The system displays calculated segment values in cross-segment editing rule error messages. For example:

  IF Power Type {Seg 020} is not equal to PROPANE, THEN Propane Tank {Seg 050} should be equal to *BLANK. Power Type {Seg 020} is BATTERY. Propane Tank {Seg 050} is 50(Lb)TK.

• A custom or user-defined message.

  You can create error messages for cross-segment editing rules that contain specific or custom information. Custom error messages could include more detail or simplify the content to make the error message easier to understand. For example, a 6000 LB capacity forklift requires a gas or propane engine.

  You set up customer error messages by using the media object functionality that you access from the Cross Segment Edit Group Revision form.

You have three options for controlling which error messages appear during order entry. You can display only the system message (cross-segment editing rule), only the custom message, or both the cross-segment editing rule and the custom message. You must select a value from UDC 32/CM in the Custom Message field on the Cross Segment Edit Group Revision form.

Important! You should not add the custom message to the first sequence of the cross-segment editing rule. The custom message must be attached to the conclusion portion of a Boolean statement such as would follow the operators then, and, or, and else. If a message is attached to any other sequence of the rule, it does not appear when the error occurs.

Forms Used to Set Up Cross-Segment Editing Rules

Defining a Cross-Segment Logic Statement

Access the Cross Segment Edit Group Revision form.

Important! You can reference upper-level items in a cross-segment editing rule by using the Segment Item and Segment Branch fields. When writing the rule, you must first enter information in the Segment Item field before entering the segment number in the Segment Number field. This process tells the system from which configured item to retrieve segment information for the cross-segment editing rule.

Defining Values for Cross-Segment Logic Statements

Access the Values Revision form.

Values

Enter a list of valid answers to the configurator feature and option questions that appear during order entry. When you define cross-segment editing rules, you compare the segment answers to values to determine invalid configurations. When you define assembly inclusion rules, you create unique configurations by comparing the segment answers to values to assign parts, prices, calculated values, or routing steps.

Defining Ranges for Cross-Segment Logic Statements

Access the Range Revision form.

From Range and To Range

Enter the starting value or the ending value of a range of numbers. In the JD Edwards EnterpriseOne Configurator system, the *Range variable is used in the Values field that is associated with the cross-segment editing rules and assembly inclusion rules. The *Range values represent answers to the segment that is referenced by the rule. You can use a UDC table to act as a filter to narrow the possible values that the logic statement will return. When you are using a range of values, the entire range of values from the lower limit to the upper limit is acceptable. The answer cannot be limited to, for instance, even numbers, two decimal places, 1/4", and so on. Any value within the range of values is a valid answer.

Copying a Cross-Segment Editing Rule

Access the Work with Cross Segment Editing Rules form.

To save time during setup, you can copy a cross-segment editing rule from one configured item to another:

1. On the Work with Cross Segment Editing Rules form, complete the Branch/Plant and Configured Item fields, and click Find to locate a configured item.

2. Select a record, and select Insert Edit Group and then Insert Before or Insert After from the Row menu.

3. On Cross Segment Edit Group Revision, select a blank line, and then select Copy from the Row menu.

4. On Rules Copy Window - Cross Segment Editing Rules, locate the configured item from which you want to copy a rule.

5. Select a record or several records, and click Select.

6. On the Cross Segment Edit Group Revision form, modify the rule as required, and select OK.

Setting Up Custom Error Messages

Access the Cross Segment Edit Group Revision form.

1. Complete the Custom Message field with the appropriate value.

   Note. You should not add the custom message to the first sequence of the cross-segment editing rule. The custom message must be attached to the conclusion portion of a Boolean statement such as would follow the operators then, and, or, and else. If a message is attached to any other sequence of the rule, it does not appear when the error occurs.

2. From the Row menu, select Custom Message.

3. On Media Object Viewer, select Text.

Reviewing Cross-Segment Editing Information

Access the Cross Segment Where Used Inquiry form.

Review cross-segment editing information to help you maintain the rules. For the item number and segment that you specify, you can review rule logic and segment values.

Printing Cross-Segment Editing Rules

Select Print Rules from the Form menu on the Work with Cross Segment Editing Rules form.

This report provides a hard copy of cross-segment editing rules. Use the hard copy to verify the accuracy of cross-segment editing rule setup.

Setting Up Assembly Inclusion Rules

This section provides overviews of assembly inclusion rules, assembly inclusion rule logic, advanced assembly inclusion rules, derived calculations, external program references, configured tables, smart parts, and hot spot assembly inclusion rules and discusses how to:

• Define codes for hot spots.

• Set processing options for Assembly Inclusion Rules (P3293).

• Define assembly inclusion rule logic.

• Define advanced assembly inclusion rules.

• Copy assembly inclusion rules.

• Test derived calculations.

• Print assembly inclusion rules.

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 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:

Important! You must have at least one P assembly inclusion rule for the JD Edwards EnterpriseOne Configurator system to function.

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.

Business Case: Assembly Inclusion Rules

When sales orders are created, all of the detail information appears on the sales order. In most cases, the customer does not need all of the information, and it crowds the sales order. Also, some detailed information is not appropriate for the customer to see. Only pertinent lines should be printed on the customer sales order.

Use the Assembly Inclusion Rule application in the JD Edwards EnterpriseOne Configurator system to adapt the sales order. Use P assembly inclusion rules to add parts to the sales order and work order parts list, and use Q assembly inclusion rules to add parts to the work order parts list only. These assembly inclusion rules enable you to adapt the sales order and work order parts list to communicate the appropriate information.

Understanding Assembly Inclusion Rule Logic

For each assembly inclusion rule, you can define a logic statement for many conditions. This statement can determine which parts to include or how to price an item. The logic is similar to that used in cross-segment editing rules. The main difference is that assembly inclusion rules logic statements can be either conditional or unconditional.

An unconditional statement is identified by an asterisk (a then condition) in the And/Or Selection field. Use unconditional rules when you want to apply the same rule, regardless of the segment answers. You must define unconditional rules before you define conditional rules. All unconditional rules must be grouped together in the first rule (rule number one). Unconditional rules are used, for example, when a part is always included as a component or when a price adjustment is always performed.

Conditional rules use Boolean logic to control or condition an action, based on segment answers. You can also use and/or operators to create conditional rules that are compound statements of logic. This P assembly inclusion rule is an example of a compound logic statement: If Segment 10 equals 6000, and segment 30 is greater than 10, then include part F170, else include part F175.

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, 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 by the calculation function at order entry. You can change the rule number when setting up assembly inclusion rules by using the Insert Before and Insert After options on the Row menu on the Work with Assembly Inclusion 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 calculation processing. You can change the sequence number by using the Insert Before and Insert After options on the Row menu on the Assembly Inclusion Edit Group Revisions form.

Note. No limit exists on the nesting of assembly inclusion rules. However, nesting does have an impact on system performance. The deeper the rules are nested, the slower the processing time.

Calculation Processing

During order entry, the validate configuration feature verifies JD Edwards EnterpriseOne Configurator processes level-by-level in this order:

• Segment agreement

  System processing includes UDC validation, range checking, alpha versus numeric checking, length checking, and required versus optional checking.

• C assembly inclusion rules

  The system processes C rules first because the calculated segment answer might be required to validate the configuration. The calculated segment answer might also be needed to perform additional calculations for the configured item.

• Cross-segment editing rules

  The system validates the configuration before processing the remaining rules.

• P assembly inclusion rules

• Q assembly inclusion rules, as needed

  The system processes Q assembly inclusion rules during Sales Quotes (P4210) (to establish cost) and Order Processing (R31410) (to create the parts list and establish cost), depending upon system setup.

• R assembly inclusion rules, as needed

  The system processes R assembly inclusion rules during Sales Quotes (P4210) (to establish cost) and Order Processing (R31410) (to create the routing and establish cost), depending upon system setup.

• X assembly inclusion rules

• H assembly inclusion rules

Required Fields for Assembly Inclusion Rules

This table lists the information that you have to supply in addition to common fields for each rule in the Assembly Inclusion Rules program:

Understanding Advanced Assembly Inclusion Rules

In addition to the logic statements, you can set up optional advanced assembly-inclusion-rule functionality. You set up advanced assembly inclusion rules on either the Assembly Inclusion Edit Group Revisions form or the Advanced Rule Functions form.

Advanced assembly-inclusion-rule features vary, according to the type of assembly inclusion rule that you set up, as illustrated in the table:

Understanding Derived Calculations

For each rule type, you can define calculations that refer to the values of one or more segments. You can define a derived calculation on either the Assembly Inclusion Edit Group Revisions form or the Advanced Rule Functions form.

Segment References

You can reference any segment within a formula. To reference a segment within the same configured item, enter S and the segment number.

For example, S3 indicates segment three.

To reference a segment from a different configured item, enter S, the segment number, and the configured item name. Enclose the item name within equal signs.

For example, S3=Piston= indicates segment three of item Piston.

Algebraic Formulas

Use algebraic formulas to combine different mathematical operations with these operators: +, -, ×, and ÷. You can embed calculations by enclosing them in parentheses. You might want to embed segment numbers in the formula to include segment values as part of the calculation.

For example, this formula calculates the counterweight that is necessary to keep the forklift from tipping over when its boom is fully extended with a full load:

Derived Calculation: S10 ÷ (4 × COS(2 × S30 × 3.1416 ÷ 360 × 2 × 3.1416))

Trigonometric and Logarithmic Functions

You can use trigonometric and logarithmic functions independently or as part of a complex formula.

These trigonometric functions are available (values expressed in radians):

These logarithmic functions are available:

This function is available:

Substrings

You can use the SUBSTR (substring) function to include a portion of a larger string of characters in a formula.

To calculate a substring, you must provide these references:

• The segment from which you want to take the substring.

• The starting position within the string where you want to begin referencing values.

• The length of the string that you want to reference.

For example, if segment 10 is 400012, then these expressions are true:

Concatenations

You can use the CONCAT (concatenate) function to combine the values of two different segments. For example:

External Field References

You can reference fields that are external to the JD Edwards EnterpriseOne Configurator system to use in derived calculations.

Using the External Files Reference program, you select a field from these tables:

After you reference a field value, the information appears in the Derived Calculation field, preceded by an ampersand (&). The ampersand is then followed by the table identifier and then the field alias. You can use the field independently or within a complex expression.

You can also include field values through External Files Reference. For example, a pricing assembly inclusion rule for item 6000 (forklift) uses a field reference to retrieve a base price from the F4106 table. The formula & BPUPRC appears in the Derived Calculation field, where BP is the table identifier for the F4106 table and UPRC is the alias for price.

The system uses the component item number and branch from the rule to retrieve the appropriate tables. It also uses the Address Book number to retrieve data from the address book or billing instructions tables.

To reference a supplemental database field, you must also specify the data type. Enter the data type after the field, in this way:

When you reference the unit of measure in table F41002, you must specify the unit of measure in the same manner.

Understanding External Program References

You can use a program that is external to the software to define a calculation. You refer to an external custom business function for special calculations that are particularly complex or involved.

For R, P, and Q rules, the external business function refers to the component number, component branch, and sold-to number. For H, C, or X rules, the external business function refers to the configured item number, branch/plant, and sold-to number.

Several setups must be completed before an external business function can be called. A business function object must be created for the external program. This business function object must then be added to the Object Librarian.

The Function Use processing option value for the Assembly Inclusion Rules program (P3293) must be equal to the Object Use value on the Object Librarian for the function being called.

You must enter EXTVAR in the Derived Calculation field on the Assembly Inclusion Edit Group Revisions form. Enter the name of the external business function to be called in the External Program field.

After the system runs the external function, it places the results in EXTVAR, a 30-character variable in the inclusion rule.

The external business function can also access and use the values of previously entered segments that are sorted in cache. The system passes the B3200000 data structure to the external business function.

Understanding Configured Tables

You can set up configured tables to simplify assembly inclusion rules. Although they take time to set up, tables reduce the number of rules and reduce processing time. Each table uses an assembly inclusion rule to reference return calculated segment values, prices, parts, and display information to the sales or work order.

See Setting Up Configured Tables.

Understanding Smart Parts

Depending on the item numbering scheme and the need for reducing assembly inclusion rules, you can set up smart parts, or special item numbers, to derive defined variable segments. Using smart parts is a simplified version of using assembly inclusion rules.

For example, a manufacturer might have 100 different paint options for a configured item. Rather than set up 100 different assembly inclusion rules to account for variations in paint color, the manufacturer might want to set up special item numbers, or smart parts, to keep track of the different paint values. These smart parts combine the segment item and the paint color into one item number, as defined in the smart part field on the Advanced Rule Functions form.

Smart parts work with P and Q rules. You can build smart part numbers by using the segment values from order entry. The system calculates smart parts in a similar manner to derived calculations. However, the resulting smart part is an alphanumeric string. You must define item numbers that are the result of smart part calculations in the Item Master (F4101) and Item Branch File (F4102) tables.

Smart part formulas can define short, second, or third item numbers. Smart parts use the part numbering symbol conventions that are defined in the branch/plant constants. For example, if the smart part formula uses the symbol to identify the third part number, the system places the third part number on the sales order and work order detail line.

You can build a smart part number by using these functions:

Business Case: Advanced Assembly Inclusion Rules

A business has special calculations to run when a new order is created.

Use the Advanced Assembly Inclusion Rule features in the JD Edwards EnterpriseOne Configurator system to enable order entry to take advantage of segment referencing, algebraic formulas, trigonometric and logarithmic functions, substrings, concatenations, external field references, external business function references, configured tables, and smart parts. This feature enables you to perform calculations when you validate product configuration. Thus, calculated values are available to order entry personnel and the customer.

Understanding Hot Spot Assembly Inclusion Rules

Hot spots are used to provide visual information during order entry. Allowing certain kinds of information to appear during the order entry process can improve the overall effectiveness for the user. Hot spot information enables you to view either predefined (hard-coded) values or user-defined calculated values. Hot spots are for display purposes only.

The hot spot information is available after the successful (no errors) calculation process has been run. The initial hot spot selection values are displayed, based on the processing option settings for the Configured Item Revisions program (P3210). You then can dynamically change the hot spot display. Click a hot spot button and select a different hot spot to display from the UDC 32/HS table.

The UDC contains a list of all valid hot spot entries. It also contains a numeric reference to the hot spot, a description, and an indication of whether the hot spot is hard-coded. Hard-coded entries are not changeable and are numbered descending from 999. Examples of hard-coded hot spot entries include price (as defined by the order entry mode), cost (as defined by the order entry mode), and weight.

Hard-Coded Hot Spots

Hard-coded hot spots are predefined and cannot be changed. These hot spots are numbered descending from 999.

Note. Prices do not include blanket discounting from the JD Edwards EnterpriseOne Advanced Pricing system from Oracle.

Hot Spot Assembly Inclusion Rule Definitions

Before you can define H (Hot Spot), assembly inclusion rules, you must define the hot spot UDC value in UDC table 32/HS.

User-defined hot spots are determined by using the H assembly inclusion rule. The hot spot rules function similarly to a calculation (C) assembly inclusion rule. This process means that the power of the derived calculation, external program interfaces, and more can be leveraged. Configured tables are also supported for the H rule type.

Hot spots (H rules) are processed in the same way as calculated values (C rules). This means that if the configuration validation fails, the displayed value is the customer-defined error character as defined in the Configurator Constants. The H rule differs from a C rule in that processing is done last for the parent item. In addition, anything from any level can be referenced.

The values from UDC 32/HS are used by the F3293 Evaluate AIR business function (B3200460) to process the hot spot (H Rule) as numeric or nonnumeric. If the result of the rule matches the Numeric Y/N definition, then it is rounded, based on the UDC definition. The second description for UDC 32/HS enables you to enter an edit code that is used to scrub the result before it appears on the form. The edit codes are standard programming edit codes.

Note. If a hot spot is defined in UDC 32/HS but a corresponding H assembly inclusion rule has not been defined, the hot spot displays a value of zero on the Configured Item Revisions form at order entry.

Forms Used to Set Up Assembly Inclusion Rules

Defining Codes for Hot Spots

Access the User Defined Codes form.

You must define UDCs for hot spots in UDC table 32/HS. After you define the hot spot, you can define an assembly inclusion rule with a corresponding calculation.

If the column named Description 02 does not appear in the UDC table, change the setup of UDC 32/HS:

1. Select Code Types from the Form menu on the Work With User Defined Codes form.

2. Type HS in the Code Types QBE (query by example) line and click Find.

3. Click Select to get to the User Defined Code Types form.

4. Type Y in the 2nd Line (Y/N) (second line) field.

   This step displays the second description field in the initial UDC table.

5. Verify that the Numeric (Y/N) field is set to Y.

6. Click OK and then Close.

7. Click Add when the Description 02 column appears in the table on the Work With User Defined Codes form.

Setting Processing Options for Assembly Inclusion Rules (P3293)

These processing options control default processing for the Assembly Inclusion Rules program.

Defaults

These processing options control default rule types.

Edits

This processing option controls validation against external programs.

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, calculated values, display values, or routing steps—regardless of the segment values.

Note. All unconditional rules must be grouped together in the first rule (rule number one).

To reference a segment from another level in the configured item:

1. Complete the Op field.

2. Complete the Segment Item and Segment Branch/Plant fields.

3. Continue to enter the remaining rule information.

Note. If the rule is not written in this order when referencing a segment from another level in the configured item, you will either get the incorrect segment reference or an error message.

Defining Advanced Assembly Inclusion Rules

Access the Advanced Rule Functions form.

Copying Assembly Inclusion Rules

Access the Assembly Inclusion Edit Group Revisions form.

To copy an assembly inclusion rule:

1. Select a blank line.

2. Select Copy from the Row menu.

3. Locate the configured item from which you want to copy a rule on the Rules Copy Window - Assembly Inclusion Rules form.

4. Select one or more lines, and click Select.

5. Modify as required on the Assembly Inclusion Edit Group Revisions form.

Testing Derived Calculations

Access the Derived Calculations form.

Note. The Assembly Inclusion Rule Tester tests the derived calculation for any of the six assembly inclusion rules. The derived calculation to be tested appears at the top of the form. The segments that relate to the derived calculation appear in the middle of the form.

Printing Assembly Inclusion Rules

Select Print Rules from the Form menu on the Work with Assembly Inclusion Rules form.

Print a hard copy of assembly inclusion rules to verify the assembly inclusion rule setup.

Setting Up Configured Tables

This section provides an overview of configured table setup and discusses how to:

• Define table name for a configured table.

• Set processing options for Configured Table Definition (P3281).

• Define table definitions with dimensions for configured tables.

• Set processing options for Table/Item Cross Reference (P3282).

• Define the configured table/configured item cross reference.

• Define table return segment values for a C table.

• Set processing options for Configured Table Values (P3283).

• Define values for configured tables.

• Link assembly inclusion rules and configured tables.

• Copy a configured table.

• Review a configured table.

• Print configured rule table values.

Understanding Configured Table Setup

A configured rules table is a collection of data that you define for a configured item. During order processing, assembly inclusion rules can refer to tables to retrieve component parts, calculated segment values, price adjustments, or display information.

You can use tables to reduce the number of assembly inclusion rules that are required when segment answers vary greatly. The table type should be the same as the assembly inclusion rule type that refers to it.

Setting up tables adds time to the setup process. However, tables can dramatically reduce the number of assembly inclusion rules and their complexity, thus improving processing time and simplifying setup.

When you enter an order for a configured item, you select answers for the segments that are defined for the item. For example, for a forklift, you might select a value of 4000 for segment 10 (Lift Rating) and a value of PROPANE for segment 20 (Power type).

Depending on the values that you define for each segment, you can specify the information that returns to the order. You must define the values for each segment as a key to the table.

You can define tables that correspond to the matching assembly inclusion rule types:

Note. No table corresponds to the assembly inclusion rule for routing.

Because only one value can be returned for H and X tables, the system limits setup options when you specify the return dimensions for these table types.

Because a table might contain many segments (keys) and values, you must decide how the table information appears before you can review table information.

Note. The tables that are used for rules processing within the JD Edwards EnterpriseOne Configurator system are not UDCs.

As you work with table information, you can speed data entry by setting a processing option for copying rows of data.

You also can define effectivity dates for the table.

When creating C tables that return multiple values, you must define destination segment numbers during the Table/Item Cross Reference step. The Table Return Segment Values form automatically appears when you are entering a C table.

Table Definitions with Dimensions for Configured Tables

To create a configured table, you must define the table type and dimensions. The dimensions refer to the number of segments that are used as keys to the table and the number of values that the table returns to the configured item. The maximum number of keys to the table is 20. The maximum number of return values is 99,999.

Tables can have these dimensions:

• One segment and one return.

• One segment and multiple returns.

• Multiple segments and one return.

• Multiple segments and multiple returns.

You should have an idea of what you want the table to do prior to defining its dimensions. A one-segment, one-return table is particularly helpful when you want to define price, cost, hot spot values, or other specific information.

You might create a one-segment, multiple return table when one segment can return multiple information consistently. Many component item numbers might be related to a specific segment answer. For example, a paper manufacturer might configure a certain size of letterhead to return a correspondingly sized envelope and response card.

You might create a multiple-segment, multiple return table when using P or Q tables. P and Q tables are based on P and Q assembly inclusion rules, which return parts to the sales or work order.

Note. When working with tables with multiple segments and multiple returns, remember that the form displays segment information in columns and values in rows.

Understanding How to Link Assembly Inclusion Rules and Configured Tables

After you define table values, you must provide access to the table so that the part number, calculated value, price adjustment, or display information is retrieved to the order. The table is linked to the corresponding assembly inclusion rule. The table can be accessed through either unconditional or conditional rules. During order processing, the assembly inclusion rule causes the table to be read and the values are brought back to the order.

Forms Used to Set Up Configured Tables

Defining Table Name for a Configured Table

Access the User Defined Codes form.

Setting Processing Options for Configured Table Definition (P3281)

These processing options control default processing for the Configured Table Definition program.

Data Defaults

These processing options control default values that the system uses when you run this program.

Defining Table Definitions with Dimensions for Configured Tables

Access the Rule Table Definition Revisions form.

Rules Table Name	Enter the name of a collection of data that you set up to minimize the number of assembly inclusion rules that you need for a configured item. You must define rule table names in UDC table 32/TN. A rule table can be accessed by 1 to 20 keys and can return up to 99 values. When you reference a rule table in an assembly inclusion rule, the system uses the rule keys to retrieve the values that are associated with the rule table. For example, if you defined segment 10 to be the color of an item, you could set the table to retrieve item Red Component when the customer enters Red for segment 10. In this example, the table would be: Item Color: Value Red: Red Component The table would include the following instruction: If the color segment value is red, then use item number Red Component on the configured item sales order and work order parts list.
C Table - Calculated Values, P Table - SO Parts List, Q Table - WO Parts List, X Table - Price Adjustments, and H Table - Hot Spots	Enter a value that identifies the type of rule table. Values are: P: Part list (on sales order and work order) Q: Work order component (on work order only) C: Calculated values H: Hot Spot X: Price/Cost adjustment
Number of Segments	Enter how many keys (segments) are used to access the table. Key values must be on the current level or a previous level of the configured item. The maximum is 20 keys.
Number of Table Values	Enter how many values the system returns from the rules table when a match is found on the table keys. If you enter more than one return value for a C (calculated) rule, you must indicate the segment numbers to return the values to. With H and X tables, the Number of Table Values field is automatically populated with 1.

Setting Processing Options for Table/Item Cross Reference (P3282)

This processing option controls default processing for the Table/Item Cross Reference program.

Defaults

This processing option controls default values that the system uses when you run the Table/Item Cross Reference program.

Defining the Configured Table/Configured Item Cross Reference

Access the Configured Item Cross Reference Revision form.

Note. Multiple configured items can refer to a single table, and a single configured item can refer to multiple tables.

You can enter an item *ALL to define a generic cross-reference for all configured items. If you use *ALL, you must use the same segment numbers for all configured items.

Defining Table Return Segment Values for a C Table

Access the Configured Item/Rules Table Return Segment Values form.

Setting Processing Options for Configured Table Values (P3283)

These processing options control default processing for the Configured Table Values program.

Defaults

This processing option controls the default value that the system uses when you run the Configured Table Values program

Processing

This processing option controls whether you can copy from a row.

Defining Values for Configured Tables

Access the Configured Table Value Revision form.

Segment Value 1 and Segment Value 2

Complete as many segment value fields as you defined on the Rule Table Definition Revisions form when you defined dimensions for the table. The names of the segment value fields are defined when you create the table/item cross reference. Each time that you enter a value for a segment and the associated item number, a new blank row appears.

Note. As you work with table information, you can speed data entry by setting a processing option for copying rows of data. You can use one of two methods to copy rows. The first method is to select a row, and then select Copy row from the Row menu. You can then change the row data as necessary for the table. The second method is to enter 1 in the C field of the row that you want to copy. After you complete the fields in a row and press the Enter key, that row is copied into the next row. When you no longer want to automatically copy a row or if you need to make changes, clear the C field.

Linking Assembly Inclusion Rules and Configured Tables

Access the Advanced Rule Functions form.

Copying a Configured Table

Access the Copy Table form.

Table Definition

Select to copy the table definition that is the basic data describing a table. The Copy button is selected from the Table Definition form, so the table definition is always copied. The other pieces of table data are selectable, allowing you to copy only the table definition if need be.

Reviewing a Configured Table

Access the Work with Rules Table Detail form.

Select a component item by branch/plant to retrieve rules table detail. Select whether you want to view the data by value or by component.

Printing Configured Rule Table Values

Select Configurator Setup (G3241), Configured Rules Table Values.

Print a hard copy of configured table information to verify the accuracy of the configured table keys and return values. Review the table segments and values for the table name and table type that you specify.