Specify a start date for this scheduled order. For new orders, the default is blank. However, you cannot leave this field blank; otherwise, an error displays. Enter any date that is before or after the system date and earlier than or the same as the header end date.

The start date defaults to the Line Start Effective field if it is after the system date. If it is earlier than or on the system date, the system date defaults to the Line Start Effective field.

If you change the header start date and line items already exist on the scheduled order, you must specify a start date that is earlier than the line start dates.

See Effective Dates.

Specify an end date for this scheduled order or leave blank. If you specify a date, the date must be later than or the same as the header start effective date. If blank, the order is open. The date you enter here defaults to the line End Effective field.

You can close a scheduled order by assigning a date that is earlier than the system date. When you do:

Although the system warns you that the order lines are inactive, you can still change information on the order. You cannot add new lines though.

Enter the number of zero schedules the system generates for a supplier when an order is active but no demand exists. A zero schedule is a one-line schedule for zero quantities that suppliers still receive and process until some agreed-upon point in time when the customer stops sending the zero-quantity schedules. You can enter a zero so that the system never creates a zero schedule.

The system uses the Zero Schedules field to determine if the maximum number of zero schedules has been generated for a scheduled order line before creating a new zero schedule in Schedule Update From MRP (5.5.3.1). The system stops generating zero schedules for the combined supplier, order, and line when it reaches the number you specify.

This field defaults from the same-named field in Supplier Schedule Control (5.5.1.24).

This field sets the default for the line. See Fixed Price.

Enter a value identifying the revision level of this order. Use revision numbers to identify the most current copy of a document. When an order is initially created, revision defaults to zero.

Each time the order changes, you can manually increase the revision number by 1; however, there are no restrictions on incrementing numbers. A new copy of the document can be printed listing the current information along with the revision number.

When you access an existing order, the system prompts you to specify whether you are making an order revision change when you attempt to leave the header frame. You can specify No and continue accessing the order. If you specify Yes, you must enter a new revision level in the Order Revision field.

The system automatically sets the Print PO field to Yes when you modify the revision level.

Specify the date the revision level is effective. The default is blank.

Specify the daybook set that will be used to number supplier invoices that originate from this scheduled order. The default daybook set is copied from the supplier record in Supplier Data Maintenance (2.3.1), but you can overwrite it with a new value.

See User Guide: Financials for more information on daybook sets.

Enter the discount table for this order. You cannot leave this field blank if you set Schedule Discount Table Req to Yes in Purchasing Control.

The system uses the current date for price list Start and Expire Date comparisons.

For scheduled orders, Price List—in PO Shipper Receipt and Purchase Order Receipts—automatically phases in prices as they become effective when Fixed Prices is set to No on the scheduled order being received.

If a price list exists at the time of receipt and Fixed Price is set to No on the order line, the system uses price list logic to determine the price to post. If no price list exists, the system posts the amount in Purchase Cost.

Create a price list with the item number of the line item, a blank product line, unit-of-measure the same as the stocking unit-of-measure for the item, currency equal to the supplier's, and an amount type of P (price), D (discount), or M (mark-up). Discount tables entered in this field must be created through Supplier Price List Maintenance. Price tables (type L) are not considered for scheduled orders.

This field determines the effect on inventory, planning, and cost accounting when the item is received in a purchase order. Type defaults from Memo Order Type in Item-Site Inventory Data Maintenance (1.4.16), if defined for the order line site; otherwise, it defaults from Item Master Maintenance (1.4.1).

Blank: This line item is received into inventory. When the receipt is processed, inventory balances are increased and a general ledger (GL) transaction debits the Inventory account. Inventory items are considered supply by MRP.

Non-blank: This item does not affect inventory and does not create an Inventory GL transaction. For a non-inventory item, type defaults to M (memo). Memo items are expensed or capitalized upon receipt, depending on the Purchases account for the item. Memo items have no effect on MRP.

S: Subcontract. This line item is for a subcontract operation. A work order number, lot ID, and operation are specified on the order and on the receipt. When the receipt is processed, work order operation status is updated and a GL transaction debits the WIP account from the work order.

B: Blanket. This line item is for a blanket order. The system sets the line type to B in Blanket Order Maintenance, and you cannot change it. You cannot specify B on any other type of order.

Supplier schedules are designed to track the ongoing agreement between supplier and customer for inventory or subcontract items. Therefore, Type codes in Supplier Scheduled Order Maintenance (5.5.1.13) are typically blank (inventory) or subcontract.

Enter the code representing the revision level of the item. This field is validated against predefined values entered in Generalized Codes Maintenance (36.2.13) for field pod_rev. This field defaults from the Revision field in Item-Site Planning Maintenance (1.4.17). If no revision exists there, it defaults from the Revision field in Item Master Maintenance (1.4.1).

Do not confuse the header order revision with the line item revision. Order revision indicates whether changes have been made to the scheduled order; it has no default. Item revision indicates changes have been made to the engineering version of the item; the level defaults from either Item-Site Planning Maintenance (1.4.17) or Item Master Maintenance (1.4.1).

When you copy a schedule line from another schedule line, the new schedule line inherits the source item revision level and date.

When you export schedule information using the following programs, the item revision level and item revision date from the schedule are included in the information:

Specify the date the item revision level is effective. The default is blank.

Indicate whether a price lookup should occur at scheduled order receipt or, if you use Evaluated Receipts Settlement (ERS), whether the ERS Processor determines a new invoice cost for the line item when creating an invoice. The difference between the extended cost entered on the PO and the extended cost determined by the ERS Processor for the supplier invoice is posted to the AP Variance account.

Yes: The system does not look up prices during scheduled order receipt and the ERS processor does not determine a new invoice for the line item when creating a supplier invoice.

No: The system looks up prices during scheduled order receipt and copies the value of this field to the receiver. If you use ERS, the ERS processor determines a new invoice cost for the line item when creating a supplier invoice.

The quantity for scheduled order lines typically comes from planning, shipping, or required schedules. For this reason, scheduled order lines typically have a 0 (zero) quantity. Since scheduled orders typically do not have an order quantity to determine a price, PO costs on scheduled orders are not affected; therefore, this field has no effect for scheduled orders when you run Purchase Order Cost Update (5.19). During receipt, the system does, however, look up new prices for scheduled order lines with a discount table and updates the PO cost based on the quantity that you receive.

Enter the work order ID or cumulative order ID associated with a subcontract item. If you use the Advanced Repetitive module, you can leave this field blank. The system validates this field when the order type is S and automatically updates the ID when it creates a cumulative ID in Advanced Repetitive transactions.

Specify the operation code for the operation that the subcontractor performs. If you use the Advanced Repetitive module, you can leave this field blank. The system validates this field when the order type is S and automatically updates the operation field when it creates a cumulative ID in Advanced Repetitive (18.22) transactions.

Specify the number of days inside the schedule update time fence for scheduled release calculations. These days should not exceed the number specified in Schedule Days.

Quantities and dates within this period are not changed by Schedule Update from MRP (5.5.3.1). Set Firm Days to zero to eliminate the update time fence. Do this when all requirements are released as planned so that the schedule update replans all dates and quantities.

See Effect of Firm Days for more details.

Specify the number of days of discrete dates and quantities to appear on printed or transmitted releases and on reports and inquiries, including intraday quantities and times. See Schedule Bucketing for details.

Specify the number of weekly bucketed quantities to appear on printed or transmitted releases and on reports and inquiries following any Schedule Days dates and quantities. Each quantity represents the total requirement for the Monday through Sunday week. Bucketing is for print and reporting purposes only. Internally, the system stores all requirements by discrete dates and quantities.

Specify the number of monthly bucketed quantities to appear on printed or transmitted releases and on reports and inquiries following weekly buckets and discrete dates and quantities. Each quantity represents the entire month’s requirements from the first Monday up to the first Monday of the following month.

Raw and fabrication authorization commitments are made to give suppliers some protection against sudden and unforeseen reductions in demand.

This field is normally blank. Specify a value for suppliers who do not ship or take responsibility for shipping, but from whom you pick up or schedule the pickup of orders. Entering a value in Transport Days converts all order dates from receipt dates to shipment dates.

Schedule Update from MRP uses this value to set shipment dates based on delivery dates (delivery date – transport days). It then checks the supplier’s calendar, if one exists, to verify that the shipment date is a workday for the supplier. If not, the update back-schedules to the next supplier workday.

All reports and inquiries check this field to verify whether to print or display delivery dates or shipment dates. When this value is positive, the system uses shipment dates.

Enter the number of calendar days early that the MRP required date will be adjusted. Schedule Update from MRP creates schedule dates from MRP requirement dates this many days early. Specifying these early days provides a safeguard when deliveries may be late.

Specify the item number by which the supplier identifies this item. The default is blank. Both your item number and the supplier item number display on reports and inquiries, print on order documents, and display during order receipt functions. This helps receiving clerks who receive packing lists that show only supplier item numbers.

Optionally enter the item number of the container in which the item will be delivered. The value must be a valid item number defined in Item Master Maintenance (1.4.1).

Enter a code for the routine ship or delivery pattern, the days of the week or month when deliveries are required.

Schedule Update from MRP uses ship/delivery patterns to calculate actual supplier schedule required dates. MRP generates quantities, but the quantities are not divided into buckets as they are in customer schedules. MRP may shift quantities to earlier dates, if necessary, as defined by the ship/delivery pattern code.

You can use ship/delivery pattern codes for both planning and shipping schedules. You would ordinarily use pattern codes only for planning schedules that use bucketed quantities frequently.

SDP codes support both the Organization for Data Exchange by Teletransmission in Europe (ODETTE) and the Automotive Industry Action Group (AIAG) ship/delivery patterns. They are translated to the appropriate industry-standard codes during EDI conversion and transmission.

Enter the maximum quantity to be received before warning messages display when you access the order line. If greater than 0 (zero), all maintenance, inquiry, and update programs display warning messages when the cumulative quantity received is equal to or exceeds this quantity.

Enter the multiple in which orders for this item are shipped. This is similar to Order Multiple in the item master. It displays here because the standard shipment multiple for an item can vary among suppliers. Schedule Update from MRP rounds order quantities up to this multiple.

Order Multiple should generally be blank in the item master for items that are referenced on scheduled orders, since both values are applied to orders during different planning functions (MRP and Schedule Update from MRP).

Enter the date on which this order began to accumulate quantities. This may or may not be the date on which the order was created in your database.

When a line item is first scheduled, the cumulative receipt quantity is zero and the cumulative start date is set to the active start date of the schedule. As receipts are processed, the system updates the cumulative receipt quantity.

Sometimes cumulative receipt quantities must be adjusted manually, usually as dictated by policy. For example, you may reset them to zero at the start of your new fiscal year using Cum Received Reset to Zero (5.5.5.14). The affected cumulative start dates are then changed to that date.

See Resetting Cumulative Quantities for details.

You can also adjust cumulative receipts manually to reflect returned or defective items or losses due to theft using Cumulative Received Maintenance (5.5.5.13). For example, when defective items are returned to the supplier, you may want to process a return and credit without decreasing cumulative quantity.

See Cumulative Received Maintenance for details.

Enter the start effective date of this order line item or accept the default. The default is the:

The date cannot be blank and must within the range specified by the header.

Enter the end effective date of this order line item, leave blank, or accept the default header End Effective date. If blank, there is no expiration for this line item. If you enter a date, it must be:

The system displays a warning if you change the end effective date and firm scheduled quantities exist outside of the date.

The end effective date displays on reports and inquiries.