![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Previous | Next | Contents | Index | Glossary | Library |
Released | The schedule is available for production and can be transacted against. When a schedule is changed to this status and a routing exists, the total number of assemblies to be built are moved to the Queue intraoperation step of the first routing operation. |
You can change schedules to this status as you define them. | |
Unreleased | The schedule is not released for transaction activity. You can update but cannot transact against it. |
You can change a schedule's status to Unreleased if it is not the only open schedule on a line, if there are no net issue, move, resource, completion, or scrap charges associated with the schedule, and if there are no purchase orders or purchase requisitions linked to it. | |
Complete | The schedule is completed but accepting transactions and charges. |
The schedule is automatically updated to this status when the number of completed assemblies equals the total quantity of the schedule and there are no subsequent schedules for the assembly on the production line. If there is a subsequent schedule with a status of Unreleased within the autorelease days time fence, or a schedule with a status of Released, Complete, or On Hold, then the status of the current schedule changes to Complete-No Charges. If there is no subsequent schedule that meets this requirement, the status of the current schedule changes to Complete. This keeps the current schedule active, so that you can transact any unused or excess material and perform delayed resource and material transactions. | |
You can manually assign this status only when you update the schedule, not when you define it. | |
Complete-No Charges | The schedule is completed and accepting no further activity. You cannot update or transact against it. |
The schedule is updated to this status when the number of completed assemblies equals the total quantity of the schedule and another schedule of this assembly on this line is available. If there is a subsequent schedule with a status of Unreleased and within the autorelease days time fence, or a schedule with a status of Released, Complete, or On Hold, the status of the current schedule changes to Complete-No Charges. If there is no subsequent schedule that meets this requirement, the status of the current schedule changes to Complete. This keeps the current schedule active so that you can transact unused or excess material and perform delayed resource and material transactions. Any excess material in the schedule is automatically rolled forward, that is, it is issued to the following schedule. | |
You can manually assign this status only when you update the schedule. If you are changing to this status manually, and there are subsequent schedules, you can choose to roll forward excess material, or you can leave it in the current schedule and write it off as a variance. | |
On Hold | You can update the schedule but cannot transact against it. You can assign this status to a schedule when you define it. |
Cancelled | The schedule was cancelled before completion. You cannot update the schedule or transact against it, but you can change its status. You can assign this status only when you update the schedule. |
You can return all remaining material back to inventory before you cancel the schedule or roll it forward to the next available schedule for the repetitive assembly on the line. The next schedule must have a status of Unreleased and be within the autorelease days time fence or have a status of Released, Complete, or On Hold. If there is no such schedule, or if you choose not to roll forward to the next schedule, the excess material is recognized as a variance at period close. |
Pending-mass loaded | Schedule implemented from the Open Job/Schedule Interface or Planner Workbench in Oracle Master Scheduling/MRP and Supply Chain Planning. You can update pending repetitive schedules as if they were unreleased schedules but cannot transact against. You can update schedules with this status to Unreleased, Released, or On Hold when you decide to implement a repetitive schedule. |
Repetitive Schedule Status Control
Mass Changing Repetitive Schedule Statuses
Defining Repetitive Schedules Manually
Previous | Next | Contents | Index | Glossary | Library |