Implementing Planned Orders
You can easily load suggested planned orders into Oracle Work in Process or Oracle Purchasing from the Planner Workbench to create discrete jobs and purchase requisitions.
However, you cannot release kanban items. These items have the item attribute Release Time Fence set to Do Not Release (Kanban) in Oracle Inventory. The planning process will generate planned orders against these items, but you will not be able to release them into purchasing or work in process.
Note: You can specify that planned orders be automatically released as WIP jobs or purchase requisitions. See: Auto-release Planned Orders.
The order type depends upon the Make or Buy item attribute. If an item is defined as Make, but can be purchased, you can implement it as a purchase requisition or a discrete job. In addition, Supply Chain Planning users can determine the Make/Buy item attribute with sourcing rules and bills of distribution. For more information, refer to Sourcing Rules and Bills of Distribution.
You can load discrete jobs as firmed and/or released and can view current discrete job information.
To implement a single planned order:
2. Optionally, override the default job class or requisition load group by opening the Preferences window from the Special Menu.
3. Check Release in the item row.
4. In the Implement As column, select:
Discrete Job: Only if the Build in WIP item attribute is Yes. This excludes the WIP:View Only Released ECOs profile option. This is the default when the Make or Buy item attribute is Make.
None: Do not implement the planned order. This is the default when the planned order has been fully implemented.
Purchase Requisition: Only if the Purchasable item attribute is Yes. This is the default when the Make or Buy item attribute is Buy.
Attention: You can automatically create releases at the same time you create requisitions. Set the profile PO:Release During ReqImport to create releases each time you run the Requisition Import process. Releases for all blanket-sourced, approved requisitions are automatically created (and optionally approved).
The Req Import program will be run specific to the operating unit tied with your responsibility. You may need to run Req Import for different operating units base on your needs,
5. Optionally, choose Implement to override the default values or to firm the implemented order.
Attention: You cannot modify the implemented quantity from the Implement Property Sheet. Navigate to the Supply/Demand window to change the implemented quantity.
The schedule group, build sequence, alternate BOM, alternate routing, and demand class can only be updated for planned orders being implemented as discrete jobs or discrete jobs being rescheduled. The schedule group has a list of values which lists all schedule groups from WIP for the organization in the supply record. The build sequence is a number and can only be updated when schedule group is entered.
6. Optionally specify line, alternate BOM, designator and alternate routing designator.
7. If you are using Project MRP, optionally specify project and task. For a purchase requisition, source organization, source supplier, or source supplier site, implement a discrete job as firm by setting the firm flag.
11. Review summary information based on new orders, new schedules, new requisitions, and changes to existing data.
13. Choose Save and Proceed from the Action menu to save your changes and prepare the window for the entry of the next record.
To implement all planned orders and reschedules:
1. Navigate to the Supply/Demand window.
2. Choose Select All for Release, or check Release for each planned order.
See Also
Supply and Demand Fields
Implementing Repetitive Schedules
Creating Firm Planned Orders
Implementing Planned Orders as Firm Jobs
How Purchase Requisitions are Created
Rescheduling Scheduled Receipts
Online Planner
Net Change Replan
Auto-release Planned Orders
Defining Your Display Preferences
Special Menu
