To take full advantage of Supplier Scheduling, inputs from Oracle Planning and Purchasing are essential.
Attention: Setting up Oracle Purchasing is a prerequisite setup step in Supplier Scheduling; setting up Oracle Planning is not.
Approved supplier list: A repository of information that associates items with suppliers sites and allows you to define attributes specific to the item/supplier site combination.
Approved purchase requisitions: Requests for the purchase of goods from a supplier that has been approved.
Approved supply agreement releases and standard purchase orders.
Receiving transactions: Receipts of goods from a supplier, returns to a supplier, and corrections associated with these transactions.
Sourcing rules: Predefined rules for determining the sources that replenish an item.
Unimplemented planned orders: Suggestions generated by the planning process to procure a specific item for specific quantity on a specific date. (Once a planned order for purchased part is implemented, it becomes a purchase requisition.)
Assigned sets: A collection of sourcing rules that is assigned to a material plan to allocate unimplemented planned orders to suppliers.
Planning Schedule
You can automatically or manually build planning schedules to communicate long-range forecast and material release information to suppliers. You can build planning schedules that include requirements for single or multiple ship-to organizations. You can also build planning schedules with buyer's authorizations to commit resources such as raw materials and labor.
Structure
The planning schedule is structured as follows:
Header: includes data such as the schedule number, forecast horizon start and end dates, supplier, supplier site code, ship-to information, schedule type, and bucket pattern.
Item Detail: includes data for each item number, such as purchase order or supply agreement number, unit of measure (UOM), current CUMs, last receipt date and quantity, and resource authorizations.
Item Detail Schedule: includes quantities for each item accumulated in predetermined date buckets that indicate the following forecast types:
Past Due: past due shipment quantities from existing supply agreement release shipments.
Release: supply agreement release shipment information and standard purchase order information excluding past due shipment quantities.
Forecast: estimates represented by unimplemented planned orders generated during MRP (Material Requirements Planning) and approved requisitions that have not yet been converted to supply agreement releases / standard purchase orders.
You can control the bucket quantities with dates for each item on the planning schedule by defining the pattern of days offset from the forecast horizon start date.
You must define the number of available buckets and the duration of time associated with each bucket. Dates are then dynamically assigned in context of the forecast horizon start date when the planning schedule is generated.
You can define bucket patterns in a combination of up to 56: Days, Weeks, Months, Quarters.
Before you confirm a schedule, you can delete items, and edit and change item schedules, if you have set up function security options. After you confirm a schedule at the header level, you can print it and electronically transmit it as an 830 transaction, if your supplier sites support EDI transactions.
Attention: You cannot modify a schedule after you confirm it.
Shipping Schedule
You can automatically or manually build shipping schedules to communicate near-term release shipment information to suppliers. The shipping schedule provides a tool for refining the requirements conveyed on the planning schedule in support of Just-In-Time (JIT) delivery. Daily buckets are typically used instead of the weekly/monthly/quarterly buckets that are preferred for the planning schedule.
Before you confirm a schedule, you can delete items, and edit and change item schedules, if you have function security. After you confirm a schedule at the header level, you can print it and electronically transmit it as an 862 transaction if your supplier sites support EDI transactions.
Attention: You cannot modify a schedule after you confirm it.
Simulation Schedules
You can build simulation schedules for personal use that can be saved or deleted when you exit the Scheduler's Workbench. Simulation schedules are unofficial schedules for personal use that contain the most current scheduled item information. You can name or number saved simulation schedules. Saved simulation schedules can be deleted at any time. You can print simulation schedules, but you cannot confirm or send them using EDI.
Comparison: Schedule Types
| Attribute | Planning Schedule | Shipping Schedule | Simulation Schedule |
|---|---|---|---|
| Purpose | Communicate long-range forecast requirements. | Communicate near term "firm" requirements; generally with a forecast planning schedule. |
|
| Generation Frequency | Weekly | Daily | On-demand |
| Planning Horizon | 4-24 months | 3-4 weeks | Any |
| Bucket Pattern | Weeks, Months, Quarters | Days | Any |
| Include multiple Ship-to Organizations | Yes | No | Yes, if you are building a planning schedule. |
| Include Resource Authorizations | Yes | No | Mo |
| EDI Transaction Set | 830 | 862 | None |
| Specify ASL attribute | Generate planning schedules | Generate shipping schedules | None |
| Able to confirm header | Yes | Yes | No |
| Schedule Type | Subtype (Type) | Description |
|---|---|---|
| Planning | Forecast All |
|
| Planning | Forecast Only |
|
| Planning | Material Release |
|
| Shipping | Release Only |
|
| Shipping | Release and Forecast |
|