## JD Edwards EnterpriseOne Procurement 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 Accounts Payable.

- JD Edwards EnterpriseOne Address Book.

- JD Edwards EnterpriseOne Advanced Pricing.

- JD Edwards EnterpriseOne Bulk Stock Inventory.

- JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange.

- JD Edwards EnterpriseOne General Ledger.

- JD Edwards EnterpriseOne Inventory Management.

- JD Edwards EnterpriseOne Project Costing.

- JD Edwards EnterpriseOne Procurement and Subcontract Management.

- JD Edwards EnterpriseOne Manufacturing - PDM.

- JD Edwards EnterpriseOne Quality Management.

- JD Edwards EnterpriseOne Requirements Planning.

- JD Edwards EnterpriseOne Requisition Self Service.

- JD Edwards EnterpriseOne Transportation Management.

- JD Edwards EnterpriseOne Warehouse Management.

- JD Edwards EnterpriseOne Project and Government Contract Accounting.

### 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 Financial Management Application Fundamentals 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 Financial Management Application Fundamentals 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

Approval Route Code | Enter a code that determines to whom an order is routed for approval.
Branch/Plant | Enter 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.
Buyer | Enter the address book number that identifies who is responsible for setting up and maintaining the correct stocking levels for each inventory item.
Discount Factor | Enter the factor that the system applies to the unit price of an inventory item to determine the net price. The system retrieves this value from the inventory pricing rules if you have assigned a rule to this item. The pricing rule setup determines if the system multiplies the unit price by this value or adds to or deducts from the unit price.
Evaluated Receipts | Enter a code that indicates if an order is eligible for the evaluated receipt settlement process. An evaluated receipt settlement indicates that you have an agreement with the supplier to create vouchers based on the items that you receive. You use the Evaluated Receipt Settlement (R43800) procedure to create vouchers from receipt records. As a result, the supplier does not send you invoices and you can bypass the Voucher Match procedure. Values are: N: Not eligible for evaluated receipt settlement processing. Y: Eligible for evaluated receipt settlement processing. I : Receipt transaction is in process. T: Eligible for evaluated receipt settlement processing. However, a tolerance error occurred during the receipt process. R: Eligible for evaluated receipt settlement processing. However, the receipt is currently in the receipt routing process. V: A voucher has been created for the receipt transaction using the evaluated receipt settlement process.
Extended Cost | Enter a value that is equal to the number of units multiplied by the unit price.
Freight Handling Code | Enter a code that exists in the Freight Handling Code (42/FR) UDC that indicates the method by which supplier shipments are delivered. For example, the supplier could deliver to the dock, or you could pick up the shipment at the supplier's dock. You can also use these codes to indicate who has responsibility for freight charges. For example, you can have a code indicating that the customer legally takes possession of goods as soon as they leave the supplier warehouse and is responsible for transportation charges to the destination.
G/L Category and G/L Offset (general ledger category and general ledger offset) | Enter a value from the G/L Posting Code (41/9) UDC that identifies the general ledger offset that system uses when it searches for the account to which it posts the transaction. If you do not want to specify a class code, enter **** (four asterisks) in this field. You can use automatic accounting instructions (AAIs) to predefine classes of automatic offset accounts for the JD Edwards EnterpriseOne Inventory Management system from Oracle, JD Edwards EnterpriseOne Procurement system from Oracle, and JD Edwards EnterpriseOne Sales Order Management system from Oracle. You might assign general ledger class codes as follows: IN20: Direct ship orders IN60: Transfer orders IN80: Stock sales The system can generate accounting entries based upon a single transaction. For example, a single sale of a stock item can trigger the generation of accounting entries similar to: Sales-Stock (Debit) xxxxx.xx Accounts Receivable Stock Sales (Credit) xxxxx.xx Posting Category: IN80 Stock Inventory (Debit) xxxxx.xx Stock COGS (Credit) xxxxx.xx The system uses the class code and the document type to find the AAI.
Hold Code | Enter a code that exists in the Hold Codes (42/HC) UDC that identifies why an order is on hold.
Item Price Group | Enter a code that exists in the Item Price Groups (40/PI) UDC that identifies an inventory price group for an item. Inventory price groups have unique pricing structures that direct the system to incorporate discounts or markups on items on sales and purchase orders. The discounts or markups are based on the quantity, monetary amount, or weight of the item ordered. When you assign a price group to an item, the item takes on the same pricing structure defined for the inventory price group. You must assign an inventory price group to the supplier or customer, as well as to the item, for the system to interactively calculate discounts and markups on sales orders and purchase orders.
Landed Cost Rule | Enter a code that exists in the Landed Cost Rule (41/P5) UDC that indicates the landed cost rule for an item. The landed cost rule determines purchasing costs that exceed the actual price of an item, such as broker fees or commissions. You set up landed cost rules on the Landed Cost Revisions form.
Last Status | Enter a code that exists in the Activity/Status Codes (40/AT) UDC that indicates the last step in the processing cycle that this order line has successfully completed.
Ledger Type | Enter a code that exists in the Ledger Types (09/LT) UDC that specifies the type of ledger, such as AA (Actual Amounts), BA (Budget Amount), or AU (Actual Units). You can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.
Line Type | Enter a code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as Oracle's JD Edwards EnterpriseOne General Ledger, Oracle's JD Edwards EnterpriseOne Job Cost, Oracle's JD Edwards EnterpriseOne Accounts Payable, Oracle's JD Edwards EnterpriseOne Accounts Receivable, and JD Edwards EnterpriseOne Inventory Management. It also specifies the conditions under which a line prints on reports, and it is included in calculations. Values are: S: Stock item J: Job cost N: Nonstock item F: Freight T: Text information M: Miscellaneous charges and credits W: Work order
Next Status | Enter a code that exists in the Activity/Status Codes (40/AT) UDC that indicates the next step in the order flow of the line type.
Order Type | Enter a code that exists in the Document Type (00/DT) UDC that identifies the type of document. This code also indicates the origin of the transaction. There are reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) These document types are predefined 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 Ledger/Joint Interest Billing documents. S: Sales Order Processing documents.
Pricing Rule | Enter a code that exists in the Item Price Groups (40/PI) UDC to classify inventory by pricing rules. Typically, these categories correspond to the major sections in the inventory price book. You can set up as many detail categories as you need. You can use a single code for sales, purchasing, order/basket, and contract pricing. If you set up a contract rule, it must equal the short number for the item under contract.
Print Message | Enter a value from the Print Messages (40/PM) UDC to specify with print message to use. Examples of text used in messages are engineering specifications, hours of operation during holiday periods, and special delivery instructions.
Subledger | Enter a code that identifies a detailed, auxiliary account within a general ledger account. A subledger can be an equipment item number or an address book number. If you enter a subledger, you must also specify the subledger type.
Supplier | Enter the name or number that identifies an address book record. You can use this field to enter and locate information. If you enter a value other than the address book number (AN8), such as the long address or tax ID, you must precede it with the special character that is defined in the Address Book constants. When the system locates the record, it returns the address book number into the field.
Tax Explanation Code | Enter a code that exists in the Tax Explanation Codes (00/EX) UDC that controls the algorithm that the system uses to calculate tax and general ledger distribution amounts. The system uses the tax explanation code in conjunction with the tax rate area and tax rules to determine how the tax is calculated. Each transaction pay item can be defined with a different tax explanation code.
Tax Rate/Area | Enter a code that identifies a tax or geographic area that has common tax rates and tax authorities. The system validates the code you enter against the Tax Areas table (F4008). The system uses the tax rate area in conjunction with the tax explanation code and tax rules to calculate tax and general ledger distribution amounts when you create an invoice or voucher.
Unit Cost | Enter the price charged for the unit of measure in the adjoining field. Use these fields, for example, if the primary unit of measure is EA (each), but you typically use a list price per box.