An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit can 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.
Business unit security might prevent you from viewing information about business units for which you have no authority.
A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher, or journal entry.
If you use the Next Numbers by Company/Fiscal Year feature, the Automatic Next Numbers program (X0010) uses the document company to retrieve the correct next number for that company.
If two or more original documents have the same document number and document type, you can use the document company to locate the desired document.
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 asterisk (*) distinguishes it from other entries (as defined in JD Edwards EnterpriseOne Foundation - Address Book constants), when you type *TOTAL into the field, the system returns 4100.
Customer PO (customer purchase order)
An alphanumeric value used as a cross-reference or secondary reference number. Typically, this is the customer number, supplier number, or job number.
A value from UDC 00/DT (Document Type - All Documents) that identifies the origin and purpose of the document. Enter the document type to use as the default value, or select it from the Select User Define Codes form. For example, you can specify the default document type associated with the purchase order for a subcontract routing.
Effective Date, Effective From, and Eff Date From (effective date from)
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 date on which a component part goes into effect on a bill of material
The date on which a routing step goes into effect as a sequence on the routing for an item
The date on which a rate schedule becomes effective
The default date is the current system date. You can enter future effective dates to plan 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, the JD Edwards EnterpriseOne Shop Floor Management system from Oracle, and the 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, and not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
Expiration Date, Effective Thru, and Eff Date Thru (effective date through)
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.
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
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 that you enter.
A forecasting method used to calculate the detail forecast for a specific item. Forecast type is also used to summarize forecasts in the system. For planning bills, the forecast type is used to create forecasts for components when you explode planning bills.
Item Number and 2nd Item Number
A number that identifies the item. The system provides three separate item numbers and 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-digit, user defined, alphanumeric item number.
3rd Item Number
Another 25-digit, 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, bar codes, customer numbers, or supplier numbers.
A value from UDC 40/AT that determines the last step in the processing cycle that has been successfully completed for this order line.
A number that identifies multiple occurrences, such as line numbers on a purchase order or other document. Generally, the system assigns this number, but in some cases you can override it.
Line Type and Ln Ty (line type)
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, the JD Edwards EnterpriseOne Job Cost system from Oracle, the JD Edwards EnterpriseOne Accounts Payable system from Oracle, the JD Edwards EnterpriseOne Accounts Receivable system from Oracle, and the 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
Lot/SN, Lot/Serial Number, and Lot Serial Number
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics.
A user-defined code (system 40/type AT) that indicates the next step in the order flow of the line type.
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.
A date that identifies when the order was entered into the system. This date determines which effective level the system uses for inventory pricing.
A number that identifies the original document. This can be an invoice number, work order number, sales order number, journal entry number, and so on.
If you use the employee number format for time entry, the system displays the Employee Number field instead of the Order Number field.
A user-defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. JD Edwards has 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.)
The following document types are defined by JD Edwards and you should not change them:
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
A date that identifies the date that the work order or engineering change order is planned to be completed.
An item associated with a production number for managing the supply and demand for a customer order.
You enable production number control by item or by item branch/plant by using the Production Number Controlled option.
An alphanumeric value that provides the ability to associate supply transactions to a demand transaction. The production number is a system generated 30-digit alphanumeric value. The system generates a production number based on user-defined segments and segment values. The system concatenates the production number short to the system-generated production number to maintain a unique identifier.
The production number can also be a user input value that is different from the system generated value. If the user inputs a value for the production number, then the system does not concatenate the production number short to the production number.
A production number is generated or entered at the time of sales order entry or forecast entry. Material requirements planning (MRP) populates all messages generated from this demand with the production number. All transactions associated with the production number can be managed through the Production Number Workbench program (P34403).
A number that provides a unique identifier during production number generation. The production number short is a 10-digit next number that is setup in system 34 of the Next Numbers program (P0002).
To maintain a unique identifier, the system concatenates the production number short to the system-generated production number.
A number that identifies an engineer-to-order project in the system. You set up the project in the Add/Revise Project program (P31P011).
A date that represents the promised shipment date for either a sales order or purchase order. The Supply and Demand Programs use this date to calculate Available to Promise information. This value can be automatically calculated during sales order entry. This date represents the day that the item can be shipped from the warehouse.
A value that represents the quantity of units affected by this transaction. This value can be the number of units that the customer ordered.
A date that represents the date that an item is scheduled to arrive or that an action is scheduled for completion.
A number that identifies 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.
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.
A number that identifies the start date for the order. You can enter this date manually, or have the system calculate it using a backscheduling routine. The routine starts with the required date and offsets the total leadtime to calculate the appropriate start date.
A user-defined code (00/SS) that describes the status of a work order, rate schedule, or engineering change order. Any status change from 90 through 99 triggers the system to automatically update the completion date.
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or location.
A number that identifies a task in an engineer-to-order project in the system. You set up the project tasks in the Project Workbench program (P31P001).
A value from the user-defined code (UDC) 00/DT that identifies the type of document. This code also indicates the origin of the transaction. The system has 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 defined by the 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
ET: Engineer to Order