## JD Edwards EnterpriseOne Configurator Preface

This preface discusses:

- JD Edwards EnterpriseOne products.

- JD Edwards EnterpriseOne application fundamentals.

- Common fields used in this implementation guide.

### JD Edwards EnterpriseOne Products

This implementation guide refers to these JD Edwards EnterpriseOne products from Oracle:

- JD Edwards EnterpriseOne Inventory Management

- JD Edwards EnterpriseOne Sales Order Management

- JD Edwards EnterpriseOne Procurement and Subcontract Management

- JD Edwards EnterpriseOne Manufacturing - Shop Floor

- JD Edwards EnterpriseOne Manufacturing - PDM

- JD Edwards EnterpriseOne Requirements Planning

- JD Edwards EnterpriseOne Manufacturing - ETO Foundation

- JD Edwards EnterpriseOne Quality Management

- JD Edwards EnterpriseOne Work Order Management

- JD Edwards EnterpriseOne Advanced Pricing

### JD Edwards EnterpriseOne Application Fundamentals

Additional, essential information describing the setup and design of the system resides in a companion volume of documentation called JD Edwards EnterpriseOne Inventory Management 9.0 Implementation Guide.

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne minimum technical requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the cross-reference material in the Program Documentation at http://oracle.com/contracts/index.html for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.

See JD Edwards EnterpriseOne Inventory Management Preface.

### About This Documentation

A companion Guide called About This Documentation contains general information, including:

- Related documentation, common page elements, and typographical conventions for guides.

- Information about using guides and managing the documentation library.

- Information on the International Organization for Standardization (ISO) country and currency codes used within documentation.

- A glossary of useful JD Edwards EnterpriseOne terms that are used in documentation.

See Also

About This Documentation Preface

Using Implementation Guides

Managing the Online Library and Implementation Guides

ISO Country and Currency Codes

Glossary of JD Edwards EnterpriseOne Terms

### Common Fields Used in This Implementation Guide

Configured Item | Enter a number that identifies a configured item.
Cfg Item Alias (configured item alias) | Enter a value from UDC 32/CI that specifies a particular instance of a configured item that is referenced in the rule. The Cfg Item Alias field on the assembly inclusion rule form provides the ability to reference a specific occurrence of an included item. This is not a required field. The Cfg Item Alias field is for use with duplicate components. If you do not use this field with duplicate components then the system processes duplicate components based on the first duplicate item value that is stored in cache. Important! You should use the Cfg Item Alias field to ensure that the correct duplicate item is used in a configuration. A configured item alias may be assigned to an item using an assembly inclusion rule. The system verifies that the configured item alias has not been assigned to another item in the assembly inclusion rules. This prevents two components on any rule from being assigned the same configured item alias. Once the configured item alias is assigned in an assembly inclusion rule, then the Configured Item Alias Left and Configured Item Alias Right fields in the cross-segment editing and assembly inclusion rules can be set to reference a configured item alias. The system verifies that the configured item alias is assigned to the item in the rule.
Configured Item Alias Left and Configured Item Alias Right | Enter a value from UDC 32/CI that specifies a particular instance of a configured item that is referenced in the left or right side of the condition. The Configured Item Alias Left and Configured Item Alias Right fields on the cross-segment editing and assembly inclusion rule forms provide the ability to reference a specific occurrence of an included item. This is not a required field. The Configured Item Alias Left and Configured Item Alias Right fields are for use with duplicate components. If you do not use these fields with duplicate components then the system processes duplicate components based on the first duplicate item value that is stored in cache. Important! It is recommended that you use the Configured Item Alias Left and Configured Item Alias Right fields to ensure that the correct duplicate item is used in a configuration.
Derived Calculation | Enter an algebraic formula that specifies the quantity, price, hours, or a value associated with a rule. These examples illustrate the syntax for possible derived calculations: 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(S3) 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 Specifies the fields from non-configurator tables that you want the system to access as part of a calculation. Use the ampersand character followed by the field name. For example, &T2AMTU(WD) indicates an amount field in the Item Supplemental Database table, and the WD data type. External Programs Specifies that a program external to the JD Edwards EnterpriseOne system from Oracle is to be used for the calculation. Enter the name of the external program and EXTVAR in the Derived Calculations field. Smart Parts 'P'S4 indicates a smart part number P2000 when the value of segment 4 is 2000.
Description | Enter the name of the feature or option that is associated with the segment number.
Effective From, Effective From Date, Effective Thru (effective through) and Effective Thru Date (effective through date) | Enter dates that indicate when a rule takes effect or is no longer active in the JD Edwards EnterpriseOne Configurator system from Oracle. The dates determine whether the system processes the rule during configuration validation of the order. These dates apply to cross-segment editing and assembly inclusion rules.
External Program | Enter the name of the external program that will be providing values for external variables.
Line Type | Enter a code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interacts, such as JD Edwards EnterpriseOne General Ledger from Oracle, JD Edwards EnterpriseOne Job Cost from Oracle, JD Edwards EnterpriseOne Accounts Payable from Oracle, JD Edwards EnterpriseOne Accounts Receivable from Oracle, and JD Edwards EnterpriseOne Inventory Management from Oracle. It also specifies the conditions under which a line prints on reports, and it is included in calculations. Codes include: S: Stock item J: Job cost N: Nonstock item F: Freight T: Text information M: Miscellaneous charges and credits W: Work order
Op (operator, operand, and and/or selection) | Enter a code that determines whether compound data selection logic is based on an A = AND condition or an O = OR condition. 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 equals A, include part B. If Seg 1 does not equal A, include part C and part D.
Product Code and User Code | Enter a code that identifies the table that contains user-defined codes. The table is also referred to as a UDC type. If you define a calculated segment, you do not need to enter a user-defined code.
Rel (relationship) | Enter a code that identifies the operands in Boolean logic. You can specify any of these codes: CE: Can be equal to EQ: Equal to LT: Less than LE: Less than or equal to GT: Greater than GE: Greater than or equal to NE: Not equal to NL: Not less than NG: Not greater than
Rule Table and 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 user-defined code 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 statement: If the color segment value is red, then use item number Red Component on the configured item sales order and work order parts list. You can create a configured table for any rule type except R (routing) rules.
Segment Branch and Segment Branch/Plant | Specify the branch/plant of the item in the Segment Item field. Enter a business unit, which is an accounting entity required for management reporting. It can be a profit center, department, warehouse location, job, project, work center, branch/plant, and so forth. This business unit is from the business unit entered on the header of a sales/purchase order for reporting purposes. This data is always right justified on entry (for example, CO123 would appear as _______CO123). A security mechanism has been provided to inhibit users from entering or locating business units outside the scope of their authority.
Segment Description | Enter the name of the feature or option that is associated with the segment number. This field is automatically populated, based on information from the Configured Item, Branch/Plant, Segment Number, and Segment Item fields. You can enter specific values for the segments that are included in a configured item. Segment values are separated by a special character, called the segment delimiter. For the JD Edwards EnterpriseOne Configurator system, this is the name of the feature or option that is associated with the segment number.
Segment Item | Reference a previously selected segment from a different configuration level.
Segment Number and Seg Num (segment number) | Enter a number that establishes the sequence in which the segments were defined in the system. Segment numbers are user-defined. Cross-segment editing rules reference the segment numbers to ensure that the set of values defines a valid configuration. Assembly inclusion rules reference segment numbers and their associated values to define prices, component parts, routing, and calculated values for configured items.
Smart Part | Enter a formula that calculates the part number associated with a rule. A smart part formula consists of a literal value (constant) and a segment answer (variable). The literal value must be in single quotes. For example: The part number consists of the literal 'P' and the value of segment 4. If the smart part calculation and the value of Segment 4 is 2000, then the smart part would be P2000. To reference segments that have already been entered on a different level, specify the item number of that level with the segment number. For example, the notation for Segment 4 of Piston is: Derived Calculation S4=Piston= SUBSTR(S4,2,3) where 2 is the beginning position and 3 is the length of the substring. To combine two fields, use the concatenation function. For example, CONCAT(S3,S1) which will combine the values of Segment 3 and 1 into one field.
Trans Type (transaction type) | Enter a value from UDC 32/DE that specifies the type of transaction that the component of a configured item should generate. If the conditions for the transaction, processing options, and branch/plant are not correct for the transaction type, then the system does not generate the transaction. You use the Trans Type field in combination with the Write Attached Detail Line field on the Assembly Inclusion Edit Group Revisions form. Values are: 0: Sales Order 1: Direct Ship 2: Transfer 3: Inter Branch/Company 4: Purchase Order Note. If you select the direct ship or purchase order transaction type, you must enter a supplier number in the Supplier Number field for the component item. This field works only with a P type rule. When the value of the Trans Type field is 4 (purchase order), the system validates both the stocking type and line type of the component item. Items with a stocking type of phantom or a line type set to generate a purchase order or work order are not supported.
( (bracket selection beginning) and ) (bracket selection ending) | Enter a collection of open and closed brackets to group conditional configurator rules. For example, to define the condition (Seg 1 = A OR Seg 2 = B) AND Seg 3 = C, use the brackets: (Seg 1 = A O Seg 2 = B) A Seg 3 = C