## JD Edwards EnterpriseOne Demand Scheduling 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:

- JD Edwards EnterpriseOne Accounts Receivable

- JD Edwards EnterpriseOne Demand Scheduling Execution

- JD Edwards EnterpriseOne EDI (Electronic Data Interchange)

- JD Edwards EnterpriseOne Inventory Management

- JD Edwards EnterpriseOne Sales Order Management

- JD Edwards EnterpriseOne Transportation Management

- JD Edwards EnterpriseOne Warehouse Management

Note. This implementation guide documents only form elements that require additional explanation. If a form element is not documented with the process or task in which it is used, then it either requires no additional explanation or is documented with the common fields for the section, chapter, or implementation guide.

### JD Edwards EnterpriseOne Application Fundamentals

The JD Edwards EnterpriseOne Demand Scheduling Execution 9.0 Implementation Guide provides you with implementation and processing information for the JD Edwards EnterpriseOne Demand Scheduling Execution solution. However, additional, essential information describing the setup and design of the system resides in companion documentation. The companion documentation consists of important topics that apply to many or all JD Edwards EnterpriseOne products lines. The companion volume for Demand Scheduling is:

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.

JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide.

See Also

JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide

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

A/B Firm and A/B Plan | Select this option to determine whether you can adjust the demand by modifying either the quantity that you have already shipped (also known as ahead amount) or the quantity that you need to ship (also known as behind amount) in relation to the customer's requirements. If you activate this option, then you can adjust the demand before you create the sales order.
Authorization to Meet Competition Number | The Authorization to Meet Competition Number is transmitted and extracted for the ASN.
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.
Card Number | The card number is an OEM assigned value that further describes the part number
Contract | Enter a unique number assigned by the company to identify a particular contract. A contract is defined as a legally enforceable promise and must include these factors: an offer, an acceptance, consideration, legality of subject matter, capacity of parties to execute, and more. You may wish to assign some significance to the contract number (such as. a contract type code, state, year, and so forth). A contract may have multiple supplements (field GSUP) to record addendums or changes.
Delivery Batch/Batch Lot Number | The Delivery Batch Number is used to identify items that are required to be packaged together. It is not returned on the ASN or the MPL; although, it will be on the delivery batch label.
Demand Type | Enter a code that specifies whether the demand is firm or planned. The demand type is used to determine how the system processes demand.
Engineering Tag | A number that identifies the initial production part (IPP) tag being returned on an advance ship notice (ASN). Companies typically use the IPP tag to indicate that a new part is being shipped because of an engineering change, a new supplier, and so on. The tag number is generated outside the supplier's system and input for the ASN preferably through scanning. The supplier associates the IPP tag with the serial number for a specific carton and attaches the tag to the first shipment of changed parts.
Engineering Tag Reason Code | A code that identifies the reason associated with an initial production part (IPP) tag being returned on an advance ship notice (ASN). Companies typically use the IPP tag to indicate that a new part is being shipped because of an engineering change, a new supplier, and so on.
Item Revision Level Qualifier | The qualifier for Item Revision Levels as follows: EC - Delta - Supplier must ship to this level BE - Latest revision on books, ship this or newer (GPCS)
Job Number | The lot number or job number that represents a group of sequence numbers and which uniquely identifies a job. The system uses the job number for production sequencing.
Job Sequence Number | The sequence number sent in from the OEM and that the system uses for production sequencing. Production sequencing is the process of indicating the order in which goods are unloaded from the truck.
Line Number | The line number that you assign when originating an EDI transaction. This number can represent an order line number (applicable for any order type), an invoice pay item, a journal entry line number, and so forth.
Off Line Date | The date most of the OEM vehicles are expected to be produced. The off line date determines the first part of the rotation number or sequence number.
Processed (Y/N) (processed (yes/no)) | Select this option to indicate whether a record has been successfully processed. Depending on the program, the system updates the EDSP field in a table with one of these values: Blank: The record has not been processed. 1: The record has been successfully processed. In order to run the EDI Inbound Demand Edit/Update batch program (R47171), you must specify 1.
Product Type | OEM reference number for third-party vendors for kanban orders.
Program ID (program identification) | The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T: The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so forth. For example, the value P in the number P4210 indicates that the object is a program. SS: The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is Sales Order Processing. XXX: The remaining characters of the number are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates the Sales Order Entry program.
Pull Signal | Enter a code that might represent a DON (Delivery Order Number), RAN (Release Accounting Number), or KANBAN number to trigger replenishment of material. Some customers use pull-based manufacturing practices to signal line-side replenishment of material.
Record Sequence | Enter an identifier that is used to assign the relative position within the header or detail information of an EDI transaction (for example, H01, H02, D01, and so forth).
Reference Number | A number that identifies a demand entity.
Requirement Type | Enter a code from the EDI transaction set/message that indicates the type of demand being received. The requirement type is typically defined via OEM requirement type of firm or plan.
Route | Enter a code that represents a sequence of points at which goods are collected on the assembly line.
Route Suffix | The suffix from the EDI transaction set/message that identifies the sequence of points where goods are collected.
Routing Date | The routing date is transmitted for eKanban orders and populated to the third-party data collection vendor and printed on the UCC/B10 label.
Routing Order Sequence Number | The routing order sequence number is transmitted for eKanban orders and populated to the third-party data collection vendor and printed on the UCC/B10 label.
Routing Time | The routing time is transmitted for eKanban orders and populated to the third-party data collection vendor and printed on the UCC/B10 label.
SCAC | A unique four-character code assigned to the carrier.
Send/Receive Indicator | Enter an indicator that identifies a specific transaction set can be sent, received, or both. Values are: S: Send R: Receive B: Both
Sold To | Enter a user-defined 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.
Transaction Set | Enter a qualifier that the system uses to identify a specific type of EDI transaction.
Transaction Set Purpose | Enter a code that identifies the purpose of the transaction set. Refer to UDC 47/PU. The 1st character of the 2nd description in that table controls how the transaction is processed. Refer to ANSI X.12 Data Item 353.