## Oracle's JD Edwards EnterpriseOne Product Costing and Manufacturing Accounting 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 General Accounting.

- JD Edwards EnterpriseOne Inventory Management.

- JD Edwards EnterpriseOne Management - Shop Floor.

- JD Edwards EnterpriseOne Manufacturing - ETO Foundation.

- JD Edwards EnterpriseOne Manufacturing - PDM.

- JD Edwards EnterpriseOne Payroll.

- JD Edwards EnterpriseOne Requirements Planning.

- JD Edwards EnterpriseOne Sales Order Management.

### 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 Also

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

Co (company) | Enter a code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany transactions. Note. You can use company 00000 for default values such as dates and automatic accounting instructions (AAIs). You cannot use company 00000 for transaction entries.
Cost Method | Enter the cost method on which to base costing errors (that is, 01, 02, . . .). If you leave this field blank , cost method 07 (standard) will be used.
Do Ty (document type) | Specify a user-defined code (UDC) (00/DT) that identifies the origin and purpose of the transaction. The system reserves several prefixes for document types, such as vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are: P: Accounts payable documents R: Accounts receivable documents T: Time and Pay documents I: Inventory documents O: Purchase order documents S: Sales order documents
Or Ty (order type) | Specify a UDC (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. The JD Edwards EnterpriseOne system from Oracle has reserved document type codes for vouchers, invoices, receipts, and timesheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) These document types are defined by the JD Edwards EnterpriseOne system and should not be changed: P: Accounts Payable documents. R: Accounts Receivable documents. T: Payroll documents. I: Inventory documents. O: Purchase Order Processing documents. J: General Accounting/Joint Interest Billing documents. S: Sales Order Processing documents.
Setup Labor | Specify a rate that the system uses with the Setup Labor Hours of the associated routing to calculate the standard setup labor cost.
Work Center | Specify 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.