## JD Edwards EnterpriseOne Product Data Management 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 Procurement and Subcontract Management.

- JD Edwards EnterpriseOne Production and Distribution Planning.

- JD Edwards EnterpriseOne Product Costing and Manufacturing Accounting.

- JD Edwards EnterpriseOne Sales Order Management.

- JD Edwards EnterpriseOne Manufacturing - Shop Floor.

- JD Edwards EnterpriseOne Requirements Planning.

### JD Edwards EnterpriseOne Application Fundamentals

Additional, essential information describing the setup and design of your system appears 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

Effective From | Enter a date that indicates: 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 the JD Edwards EnterpriseOne Product Costing system from Oracle, JD Edwards EnterpriseOne Shop Floor Management system from Oracle, and JD Edwards EnterpriseOne Capacity Planning system from Oracle. Material Requirements Planning (MRP) in the JD Edwards EnterpriseOne Requirements Planning system from Oracle 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.
Effective Thru (effective through) | Enter a date that indicates: 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 the JD Edwards EnterpriseOne Product Costing system , JD Edwards EnterpriseOne Shop Floor Management system, and JD Edwards EnterpriseOne Capacity Planning system. MRP in the JD Edwards EnterpriseOne 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.
Frm Grd (from grade) | Enter a user-defined code (UDC) (40/LG) that indicates the minimum grade that is acceptable for an item. The system displays a warning message if you try to purchase or issue items with grades that do not meet the minimum grade acceptable. The system does not allow you to sell items with grades that do not meet the minimum acceptable level.
From Potency | Enter a number that indicates the minimum potency or percentage of active ingredients acceptable for an item. The system displays a warning message if you try to purchase or issue items that do not meet the minimum acceptable potency. The system does not allow you to sell items that do not meet the minimum acceptable potency.
Group No. (group number) | Displays a number used to combine similar records.
Item Number | Enter an item number. It can be in short, long, or third item number format.
Job Type | Enter a UDC (07/G) that defines the jobs within the organization. You can associate pay and benefit information with a job type and apply that information to the employees who are linked to that job type.
Leadtime Offset | Enter the number of days that a part is needed before or after the start date of a manufacturing work order. The system adds the lead time offset days for the part to the start date of the work order to determine the actual date that the part is required. To indicate that a part is needed prior to the work order start date, enter the days as a negative number. To indicate how many days after the work order start date that the part is required, enter a positive number.
Line/Cell | Enter a number that defines a production line or cell. Detailed work center operations can be defined inside the line or cell.
Ln Ty (line type) | Displays a code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as JD Edwards EnterpriseOne General Ledger 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.
Move Hours | Enter the planned hours that are required to move the order from this operation to the next operation in the same work center. If the Routing Master values are blank, the system retrieves the default value from the work order routing. However, the system uses these values only for backscheduling variable leadtime items.
Next Oper (next operation) | Enter the operation number with which the current operation can be simultaneously processed.
Oper Seq# (operation sequence number) | Displays a number used to indicate an order of succession. In routing instructions, a number that sequences the fabrication or assembly steps in the manufacture of an item. You can track costs and charge time by operation. In bills of material, a number that designates the routing step in the fabrication or assembly process that requires a specified component part. You define the operation sequence after you create the routing instructions for the item. The JD Edwards EnterpriseOne Shop Floor Management system uses this number in the backflush/preflush by operation process. In engineering change orders, a number that sequences the assembly steps for the engineering change. For repetitive manufacturing, a number that identifies the sequence in which an item is scheduled to be produced. Skip To fields enable you to enter an operation sequence that you want to begin the display of information. You can use decimals to add steps between existing steps. For example, use 12.5 to add a step between steps 12 and 13.
Percent Scrap | Enter the percentage of unusable component material that is created during the manufacture of a particular parent item. During Distribution Requirements Planning (DRP), Master Production Schedule (MPS), and MRP generation, the system increases gross requirements for the component item to compensate for the loss. Enter percentages as whole numbers, for example, 5 percent as 5.0. Note. Inventory shrink and scrap are compounded to calculate the total loss in the manufacture of a particular item. Accurate shrink and scrap factors support more accurate planning calculations.
Quantity | Enter the number of units that the system applies to the transaction.
Queue Hours | Enter the total hours that an order is expected to be in queue at work centers and moving between work centers. The system stores this value in the Item Branch table. You can calculate this value using the Leadtime Rollup program or you can enter it manually. When you run the Leadtime Rollup program, the system overrides manual entries and populates the table with calculated values.
Record Type | Enter the default note type that will be printed. If left blank, note type A will be used.
Run Labor | Enter the standard hours of labor that you expect to incur in the normal production of this item. The run labor hours in the Routing Master table are the total hours that it takes the specified crew size to complete the operation. The hours are multiplied by the crew size during shop floor release and product costing.
Run Machine | Enter the standard machine hours that you expect to incur in the normal production of this item.
Setup Labor | Enter the standard setup hours that you expect to incur in the normal completion of this item. This value is not affected by crew size.
Substitute Item | Enter the item number that the system uses as a substitute if the original item is not available. It can be in short, long, or third item number format.
Thr Grd (through grade) | Enter a UDC (40/LG) that indicates the maximum grade that is acceptable for an item. The system displays a warning message if you try to purchase or issue items with grades that exceed the maximum grade acceptable. The system does not allow you to sell items with grades that exceed the maximum grade acceptable. Use only grade or potency, not both.
Thru Potency (through potency) | Enter a number that indicates the maximum potency or percentage of active ingredients that is acceptable for an item. The system displays a warning message if you try to purchase or issue items that have a potency that exceeds the maximum potency acceptable. The system does not allow you to sell items that have a potency that exceeds the maximum potency acceptable.
Time Basis | Enter a UDC (30/TB) that indicates how machine or labor hours are expressed for a product. Time basis codes identify the time basis or rate to be used for machine or labor hours entered for every routing step. For example, 25 hours per 1,000 pieces or 15 hours per 10,000 pieces. You can maintain the time basis codes in Time Basis Codes. The system uses the values in the Description-2 field on the User Defined Codes form for costing and scheduling calculations. The description is what the code represents, but is not used in calculations.
Work Center | Displays an alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority.
Yield % (yield percent) | Enter the planned output yield percent for a step. The Planned Yield Update program uses this value to update the cumulative percent in the routing and the operation scrap percent in the bill of material. Materials Requirements Planning uses the step scrap percent and the existing component scrap percent to plan component demand.