## JD Edwards EnterpriseOne Sales Order 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 Accounts Receivable.

- JD Edwards EnterpriseOne Bulk Stock Inventory

- JD Edwards EnterpriseOne Foundation – Address Book.

- JD Edwards EnterpriseOne Configurator.

- JD Edwards EnterpriseOne General Accounting

- JD Edwards EnterpriseOne General Ledger.

- JD Edwards EnterpriseOne Inventory Management.

- JD Edwards EnterpriseOne Procurement Management

- JD Edwards EnterpriseOne Requirements Planning.

- JD Edwards EnterpriseOne Sales Order Management.

- JD Edwards EnterpriseOne Transportation Management.

- JD Edwards EnterpriseOne Warehouse Management.

### JD Edwards EnterpriseOne Application Fundamentals

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

Customer Number and Customer | Enter a number that identifies an entry in JD Edwards EnterpriseOne Foundation - Address Book, such as employee, applicant, participant, customer, supplier, tenant, or location. You can use this number to locate and enter information about the address book record. 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 JD Edwards EnterpriseOne Foundation - Address Book constants. When the system locates the record, it returns the address book number to the field. For example, if address book number 4100 (Total Solutions) has a long address TOTAL and an * distinguishes it from other entries (as defined in JD Edwards EnterpriseOne Foundation - Address Book constants), you could type *TOTAL into the field, and the system would return 4100.
Customer PO (customer purchase order) | Enter the number of the purchase order that you want to use as a cross-reference or secondary reference number.
Cust Price Group, Customer Price Grp, and Customer Group (customer price group) | Enter a value from UDC 40/PC to identify the pricing group associated with this customer or supplier. For sales orders, you assign a pricing group to a customer on the Customer Billing Instructions form. Groups typically contain customers with common pricing characteristics, such as retailers, wholesalers, and so forth. For purchase orders, you assign a pricing group to a supplier on the Supplier Billing Instructions form.
Effective Date, Effective From, and Eff Date From(effective date from) | Enter a date that indicates when the address, item, transaction, or record becomes active. The meaning of this field differs, depending on the program. For example, the effective date can represent any of these dates: The date on which a change of address becomes effective. The date on which a lease becomes effective. The date on which a price becomes effective. The date on which the currency exchange rate becomes effective. The date on which a tax rate becomes effective. The default date is the current system date. You can enter future effective dates to plan for upcoming changes.
Expiration Date, Effective Thru, and Eff Date Thru(effective date through) | Enter a date that indicates when the address, item, transaction, or record is no longer in effect. The meaning of this field differs, depending on the program. The default date is December 31 of the default year that is defined in the data dictionary for the Century Change Year field.
Item Number | Enter a number that identifies the item. The system provides three separate item numbers plus an extensive cross-reference capability to alternative item numbers. The three types of item numbers are: Item Number (short) An 8-digit, computer-assigned item number. 2nd Item Number A 25-character, user-defined, alphanumeric item number. 3rd Item Number Another 25-character, user-defined, alphanumeric item number. In addition to these three basic item numbers, the system provides an extensive cross-reference search capability. You can define numerous cross-references to alternative part numbers. For example, you can define substitute item numbers, replacements, promotional items, bar codes, customer numbers, or supplier numbers.
Item Price Group, Item Price Grp, and Item Group | Enter a value from UDC 40/PI to identify 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, dollar 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 adjustment definition or the item, for the system to interactively calculate discounts and markups on sales orders and purchase orders based on an item group.
Last Status | Review the value from UDC 40/AT to determine the last step in the processing cycle that has been successfully completed for this order line.
Line Type and Ln Ty | Enter a code to control how the system processes lines on a transaction. This value controls transaction interfaces with the JD Edwards EnterpriseOne General Ledger system from Oracle, JD Edwards EnterpriseOne Job Cost system from Oracle, JD Edwards EnterpriseOne Accounts Payable system from Oracle, JD Edwards EnterpriseOne Accounts Receivable system from Oracle, and JD Edwards EnterpriseOne Inventory Management system from Oracle. The line type also specifies the conditions under which a line prints on reports, and is included in calculations. Some common codes are: S: Stock item. J: Job cost. N: Non-stock item. F: Freight. T: Text information. M: Miscellaneous charges and credits. W: Work order.
Location | Enter the area in the warehouse where you ship or receive inventory. The format of the location is user-defined and you enter the location format for each branch/plant. A location format comprises elements and, optionally, a separator character. The total length of all elements in this field, including separators, cannot exceed 20 characters.
Lot Number and Lot/Serial | Enter a number that identifies the lot or serial number. A lot is a group of items with similar characteristics.
Order Company | Enter a number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a sales order, and so on). If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (P0010) uses the order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order type, the order company lets you locate the desired document. If you use the regular Next Numbers facility, the system does not use the order company to assign a next number. In this case, you do not use the order company to locate the document.
Order Date | Review the field to determine the date that the order is entered into the system. This date determines which effective level the system uses for inventory pricing.
Payment Instrument | Enter a value from UDC 00/PY that specifies how payments are made by the customer. For example, C for check or T for electronic funds transfer.
Payment Terms, Pymt Terms, and Default Payment Terms | Enter a code that specifies the terms of payment, including the percentage of discount available if the invoice is paid by the discount due date. Use a blank code to indicate the most frequently used payment term. You define each type of payment term on the Payment Terms Revisions form. Examples of payment terms include: Blank: Net 15. 001: 1/10 net 30. 002: 2/10 net 30. 003: Due on the 10th day of every month. 006: Due upon receipt. The payment terms code prints on customer invoices.
Quantity Ordered | Enter the number of units that the customer ordered.
Requested Date | Enter the date that the customer requested for delivery. The requested date is the date that the item should arrive at the customer location.
Requested Time | Enter the time requested for delivery. Enter the time using the 24-hour time format (HHMMSS). For example, enter 6:00 a.m. as 060000, and enter 7:00 p.m. as 190000.
Revision Number | Review the field to determine the number of times this order has been modified. You can locate a specific change order number to review the fields that were modified. The system uses this field only if you activate the audit logging feature in the Sales Order Entry programs (P4210 and P42101) processing options and you do not bypass audit logging in the customer billing instructions for the customer on the sales order.
Ship To | Enter the address number of the location to which you want to ship this order. The address book provides default values for customer address, including street, city, state, zip code, and country.
Sold To | Enter a number that identifies an entry in the JD Edwards EnterpriseOne Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or location. The sold to customer address identifies the customer entity to whom the goods are sold.
Tax Area/Code, Tax Area, and 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.
Tax Certificate No. (tax certificate number) | Enter the number that tax authorities issue to tax-exempt individuals and companies to identify their tax-exempt status.
UoM and UM (unit of measure) | Enter a value from UDC 00/UM to specify the measurement used to define the quantity of an inventory item. For example, CS (case) or BX (box).
Unit Price | Review or enter the list or base price to be charged for one unit of an item. If you do not set up prices in the Item Base Price File table (F4106), you must manually enter the price on the sales order.