Job and Repetitive Schedule Statuses

This chapter describes how discrete job and repetitive schedules statuses can be used to control production activities.

This chapter covers the following topics:

• Overview of Job and Repetitive Schedule Statuses
• Discrete Job Status Control
• Discrete Job Statuses
• Repetitive Schedule Status Control
• Repetitive Schedule Statuses
• Job and Repetitive Schedule Status Changes
• Transaction and Process Control By Status
• Business Scenarios

Overview of Job and Repetitive Schedule Statuses

Job and repetitive schedule statuses can help you manage manufacturing operations.

Job

Job statuses describe various stages the life cycle of a job and control job activities. See: Discrete Job Statuses.

Repetitive Schedule

Repetitive schedule statuses describe stages in the life cycle of a repetitive schedule and control schedule activities. See: Repetitive Schedule Statuses.

Transaction Control

Job and repetitive schedule statuses control issue, move, resource, overhead, completion, scrap, job close, period close, and purge transactions. See: Transaction Control by Status.

Status Control

Job and repetitive schedule statuses are automatically updated after certain activities. For example, the status of a job is updated to Complete when you complete all the assemblies on the job. Statuses can also be manually changed although there are some restrictions. See: Discrete Job Status Control, and Repetitive Schedule Status Control

ECO Control

Job and repetitive schedule statuses control engineering change order (ECO) implementation. See: ECO Implementation by Status.

Planning Control

Oracle planning products include supply and demands from jobs based on their status. See: Planning Control by Status.

Release Control

When you release by changing the status from Unreleased to Released - a job or schedule with a routing, the release date is automatically set and the Queue intraoperation step of the first routing operation is updated with the job or schedule quantity. You can unrelease jobs and schedules if there are no net issue, move, resource, completion, or scrap charges against them.

Hold Control

Putting jobs and schedules on hold allows you to respond to changes and to control production by temporarily preventing transactions. You can manually change jobs and repetitive schedules to On Hold. You also set the WIP Respond to Sales Order Changes parameter so that Unreleased jobs are automatically changed from Unreleased to On Hold when configuration items are unassigned in Oracle Order Management. See: Discrete Parameters.

Status Based Reporting

Job and repetitive schedule statuses control what information is displayed in various reports and inquiries. See: Reporting by Status.

Information Management

Closed jobs and Complete - No Charges and Cancelled repetitive schedules cannot be updated. Job and schedules with these statuses can be purged. You can change the status of a job or schedule so that it can be updated.

Concurrent Processing Support

When you define discrete jobs, the WIP:Define Discrete Job form profile option determines whether job bills of material and routings, if any, are created (loaded) concurrently or interactively. The status of the job tracks the progress and outcome of the concurrent load process (that is, Pending Bill Load, Pending Routing Load, Failed Bill Load, and Failed Routing Load). See: Profile Option Descriptions.

Statuses also track the progress of the job close process.

Discrete Job Status Control

You cannot update jobs with statuses of Closed, Complete - No Charges, Cancelled, or any processing status (Pending Bill Load, Pending Routing Load, Failed Bill Load, Failed Routing Load, Pending Close, and Failed Close). You can update jobs with statuses of Unreleased, Released, On Hold, or Complete although you may not be able to update all fields. The fields you can update, based on the job's status, are listed in the following tables:

Discrete Job

Status Field	Unreleased	Released	On hold	Complete
Job Name	Yes	Yes	Yes	Yes
Class	Yes	No	No	No
Status	Yes	Yes	Yes	Yes
Firm	Yes	Yes	Yes	Yes
Start Quantity	Yes	Yes	Yes	Yes
MRP Net Quantity	Yes	Yes	Yes	Yes
Start Date/Time	Yes	Yes	Yes	Yes
Completion Date/Time	Yes	Yes	Yes	Yes
Descriptive Flexfield	Yes	Yes	Yes	Yes
Attachments	Yes	Yes	Yes	Yes

Bill Information

Status Field	Unreleased	Released	On hold	Complete
Reference	Yes	No	No	No
Alternate	Yes	No	No	No
Revision	Yes	No	No	No
Revision Date	Yes	No	No	No
Supply Type	Yes	No	No	No

Routing Information

Status Field	Unreleased	Released	On hold	Complete
Reference (for non-standard jobs)	Yes	No	No	No
Alternate	Yes	No	No	No
Revision	Yes	No	No	No
Revision Date	Yes	No	No	No
Completion Subinventory	Yes	Yes	Yes	Yes
Completion Locator	Yes	Yes	Yes	Yes

More Information

Status Field	Unreleased	Released	On hold	Complete
Demand Class	Yes	Yes	Yes	Yes
Lot Number	Yes	Yes	Yes	Yes
Description	Yes	Yes	Yes	Yes

Schedule Group, Project

Status Field	Unreleased	Released	On hold	Complete
Schedule Group	Yes	Yes	Yes	Yes
Build Sequence	Yes	Yes	Yes	Yes
Line	Yes	Yes	Yes	Yes
Project	Yes	Yes	Yes	Yes
Task	Yes	Yes	Yes	Yes

Sales Order

Status Field	Unreleased	Released	On hold	Complete
Quantity Allocated	Yes	Yes	Yes	No

Related Topics

Overview of Job and Repetitive Schedule Statuses

Overview of Changing Discrete Jobs

Defining Discrete Jobs Manually

Discrete Job Statuses

Discrete Job Statuses

Discrete job statuses describe the various stages in the life cycle of a job and control the activities that you can perform on it.

User Controlled Statuses

You can manually change user-controlled statuses. For example, you can change a job's status to Released to initiate the production cycle. Some user-controlled statuses are automatically changed based on other events. For example, when you complete a job, its status is changed to Complete.

Variable	Description
Released	The job is available for production and can be transacted against. When a job is changed to this status, the date released is automatically set to the current date and, if a routing exists, the job quantity is moved to the Queue intraoperation step of the first routing operation. You can change jobs to this status as you define them.
Unreleased	The job is not released for transaction activity. You can update but cannot transact against it. You can assign a status of Unreleased if there are no net issue, move, resource, completion, or scrap charges associated with the job and no purchase orders or purchase requisitions linked to the job.
Complete	The job is completed but accepting transactions and charges. Jobs are automatically updated to this status when the quantity completed into inventory equals the job quantity. You can manually assign this status only when you update the job, not when you define it.
Complete-No Charges	The job is complete and accepting no further activity. You cannot update or transact against it, but you can change its status to Complete. You can assign this status only when you update the job.
On Hold	You can update the job but cannot transact against it. You can assign this status to a job when you define it.
Cancelled	The job was cancelled before completion. You cannot update the job or transact against it, but you can change its status. You can assign this status only when you update the job.
Closed	The job is closed and accepting no further activity. Job are automatically updated to this status upon successful completion of the job close process. You can change jobs with this status to another status if the accounting period that the job was completed in is still open and if your functional security setup permits.

Processing Statuses

Some job statuses are automatically updated by a process. For example, if you have the WIP:Define Discrete Job Form profile option set to concurrent definition, the job status is used to track the progress of the bill of material and routing load process. When you close a job, its status is used to track the progress of the concurrent close process.

Variable	Description
Pending Bill Load	The concurrent process is loading the bill of material for the job. You cannot update the job nor transact against it. For non-standard discrete jobs, this is applicable only if you specified a bill reference.
Pending Routing Load	The bill of material load was successful and the concurrent process is now loading the routing for the job. You cannot update the job nor transact against it. For non-standard discrete jobs, this option is applicable only if you specified a routing reference.
Failed Bill Load	The concurrent process was unable to load the bill of material for the job. The load may have failed for a number of reasons. For example, the job start date may be outside the last open accounting period at the time of job creation. You can close the failed job with the Close Discrete Jobs window and open another job for the assembly. Or you can resubmit the job once you change the status to Unreleased, Released, or On Hold. For non-standard discrete jobs, this option is applicable only if you specified a bill reference.
Failed Routing Load	The concurrent process was unable to load the routing for the job. The load may have failed for a number of reasons. For example, the job start or completion date may be outside the organization workday calendar at the time of job creation. You can close the failed job and open another job for the assembly, or you can resubmit the job after changing its status to Unreleased, Released, or On Hold. For non-standard discrete jobs, this option is available only if you specified a routing reference.
Pending Close	The concurrent process is closing the job. You cannot transact against or update it. If the close process terminates abnormally, you can change the status of the job and resubmit it.
Failed Close	The concurrent process was unable to close the job. The close may have failed for a number of reasons. For example, there may be pending transactions against the job. You must fix the problems before you can close the job. You cannot transact against it.

Related Topics

Overview of Job and Repetitive Schedule Statuses

Discrete Job Status Control

Mass Changing Discrete Job Statuses

Overview of Discrete Job Close

Defining Discrete Jobs Manually

Repetitive Schedule Status Control

You cannot update repetitive schedules with user controlled statuses of Cancelled, Complete - No Charges or with the Pending - Mass Loaded processing status. You can update repetitive schedules with statuses of Unreleased, Released, On Hold, or Complete although you may not be able to update all fields. The fields you can update, based on the schedule's status, are listed in the following table:

Status and Quantity Information

Status Field	Unreleased	Released	On hold	Complete
Line	Yes	Yes	Yes	Yes
Assembly	Yes	Yes	Yes	Yes
Status	Yes	Yes	Yes	Yes
Daily Quantity	Yes	Yes	Yes	Yes
Days	Yes	Yes	Yes	Yes
Total Quantity	Yes	Yes	Yes	Yes
Descriptive Flexfield	Yes	Yes	Yes	Yes

Scheduling Information

Status Field	Unreleased	Released	On hold	Complete
First Unit Start Date	Yes	Yes	Yes	Yes
Last Unit Start Date	Yes	Yes	Yes	Yes
First Unit Completion Date	Yes	Yes	Yes	Yes
Last Unit Completion Date	Yes	Yes	Yes	Yes

Bill and Routing Information

Status Field	Unreleased	Released	On hold	Complete
Bill Revision	Yes	No	No	No
Bill Revision Date	Yes	No	No	No
Routing Revision	Yes	No	No	No
Routing Revision Date	Yes	No	No	No

Planning Information and Description

Status Field	Unreleased	Released	On hold	Complete
Firm	Yes	Yes	Yes	Yes
Demand Class	Yes	Yes	Yes	Yes
Description	Yes	Yes	Yes	Yes
Descriptive Flexfield	Yes	Yes	Yes	Yes

Related Topics

Overview of Job and Repetitive Schedule Statuses

Overview of Repetitive Manufacturing

Overview of Changing Repetitive Schedules

Defining Repetitive Schedules Manually

Repetitive Schedule Statuses

Repetitive Schedule Statuses

Repetitive schedule statuses describe the various stages the life cycle of a repetitive schedule and control the activities that you can perform on it.

User Controlled Statuses

You can manually change user-controlled statuses. For example, you can change a repetitive schedule's status to Released to initiate the production cycle. Some user-controlled statuses are automatically updated based on other events. For example, when you complete all the assemblies on a schedule, its status is changed to Complete or Complete-No Charges.

Variable	Description
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.

Processing Status

There is one repetitive schedule status this is automatically updated by a process.

Variable	Description
Pending-mass loaded	Schedule implemented from the Open Job/Schedule Interface or Planner Workbench in Oracle planning products. 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.

Related Topics

Overview of Job and Repetitive Schedule Statuses

Repetitive Schedule Status Control

Mass Changing Repetitive Schedule Statuses

Defining Repetitive Schedules Manually

Job and Repetitive Schedule Status Changes

Statuses describe the various stages in the life cycle of a job or repetitive schedule. Statuses are either user or processing controlled. Processing controlled statuses are updated based on the progress and outcome of concurrent processes. User controlled statuses can be updated by the user or are changed based on events such as job or schedule completion.

Some status changes are allowed while others are not. Some status changes are conditional. For example, you cannot change jobs and schedules from Released to Unreleased if there are net issue, move, resource, completion, or scrap charges associated with them. You also cannot unclose a job that is linked to a sales order or that was closed in a now closed accounting period.

Change To USER status From USER Status	Unreleased	Released	Complete	Complete-No Charges	On Hold	Cancelled	Closed
Unreleased	N/A	Yes	Yes	No	Yes	Yes	Yes
Released	Cond	N/A	Yes	No	Yes	Yes	Yes
Complete	Cond	Yes	N/A	Yes	Yes	Yes	Yes
Complete - No Charges (DIS)	No	No	Yes	N/A	No	No	Yes
Complete - No charges (REP)	No	No	No	N/A	No	No	N/A
On Hold (DIS)	Cond	Yes	Yes	No	N/A	Yes	Yes
On Hold (REP)	Cond	Yes	Yes	No	N/A	Yes	Yes
Cancelled (REP)	No	No	No	No	No	N/A	N/A
Cancelled (DIS)	Cond	Yes	Yes	Yes	Yes	N/A	Yes
Pending - Mass Loaded (REP)	Yes	Yes	Yes	No	Yes	Yes	N/A
Pending Bill Load (DIS)	No	No	No	No	No	No	No
Failed Bill Load (DIS)	Yes	Yes	No	No	Yes	No	Yes
Pending Routing Load (DIS)	No	No	No	No	No	No	No
Failed Routing Load (DIS)	Yes	Yes	No	No	Yes	No	Yes
Pending Close (DIS)	Cond	Yes	Yes	Yes	Yes	Yes	Yes
Failed Close (DIS)	Yes	Yes	Yes	No	Yes	Yes	Yes
Closed (DIS)	Yes	Yes	Yes	No	No	No	N/A

Related Topics

Overview of Discrete Job Close

Discrete Job Statuses

Repetitive Schedule Statuses

Changing Discrete Jobs

Changing Repetitive Schedules

Mass Changing Discrete Job Statuses

Mass Changing Repetitive Schedule Statuses

Transaction and Process Control By Status

Statuses control what transactions can be performed on discrete jobs and repetitive schedules. Discrete job statuses also help you control whether you can close and purge jobs. Statuses can also be used to control ECO implementation and the MRP planning process.

Transaction Control By Status

Material, Move, and Resource Transactions

You can perform issue, completion, move, scrap, and resource transactions for jobs and schedules with Released or Complete statuses. Backflush transactions and overhead charges are indirectly controlled by status since their source move or completion transactions are directly controlled by status.

Cost Update Transactions

Cost update transactions are created for standard discrete jobs and non-standard asset jobs with the following statuses: Unreleased, Released, Complete, Complete-No Charges, and On Hold.

Period Close Transactions

When you close an accounting period, accounting transactions for repetitive schedules with statuses of Released, Complete, Complete-No Charges, and On Hold or just Complete and Complete-No Charges depending on how you set the WIP Recognize Period Variances Parameter - are automatically created.

When you close an accounting period, accounting transactions for non-standard expense jobs with statuses of Unreleased, Released, Complete, Complete-No Charges, and On Hold are also automatically created.

Job Close Transactions

You can close jobs of any status except jobs that are Closed, Pending Close, Pending Bill Load, and Pending Routing Load.

Purge Transactions

You can purge jobs that were closed in a now closed period. You can also purge repetitive schedules that were changed to statuses of Complete-No Charges and Cancelled in closed periods.

Related Topics

Discrete Job Statuses

Repetitive Schedule Statuses

Overview of Discrete Job Purge

Overview of Repetitive Schedule Purge

Job and Repetitive Schedule Status Changes

Period Close, Oracle Cost Management User's Guide

ECO Implementation By Status

Oracle Engineering automatically implements engineering change orders (ECOs) with Release, Schedule, and Implement statuses for jobs with statuses of Unreleased and schedules with statuses of Unreleased, Released, and On Hold. You can optionally choose to implement Open status ECOs using the WIP:Exclude ECOs profile option. See: Work in Process Profile Options, and ECO Statuses in the Engineering User's Guide.

Note: Oracle Engineering does not implement ECOs on non-standard discrete jobs.

Unreleased Standard Discrete Jobs and Repetitive Schedules

When an ECO is implemented in Oracle Engineering, the system automatically regenerates the bills of material for unreleased jobs and schedules to reflect the impact of the ECO.

Released, Complete, or On Hold Repetitive Schedules

The impact of an ECO implementation on Released, Complete, or On Hold repetitive schedules depends on whether repetitive assemblies have been moved beyond the Queue intraoperation step of the first routing operation.

See Overview of Engineering Change Orders and Defining Engineering Change Orders in the Engineering User's Guide.

Planning Control by Status

Oracle planning products includes the assembly supply and component demand of jobs with statuses of Unreleased, Released, Complete, and On Hold. Because planning uses different planning algorithms for repetitive manufacturing, repetitive statuses do not impact how repetitive schedule supply and demand is viewed.

Related Topics

Overview of Material Requirements Planning, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide

Overview of the Planner Workbench, Oracle Advanced Planning Implementation and User's Guide

Reporting by Status

Job and repetitive schedule statuses determine what information is listed on reports. For example, if a job has a status of Closed, Compete-No Charges, or Cancelled, information about that job and its component requirements is not listed on the Discrete Job Shortage Report since shortages on jobs with these statuses do not need to be filled.

You can view discrete job and repetitive schedule information regardless of status. For example, you could view the component material requirements for a closed job using the View Discrete Jobs window.

Status Report	Unreleased	Released	Complete	Complete No Charges	On Hold	Cancelled	Closed	Pending Mass Loaded (Rep)
Discrete Job Data Report	Yes	Yes	Yes	Yes	Yes	Yes	Yes	N/A
Discrete Dispatch Report	Opt	Yes	Yes	No	Yes	No	No	N/A
Discrete Job Listing Report	Yes	Yes	Yes	Yes	Yes	Yes	Yes	N/A
Discrete Job Pick List Report	Yes	Yes	Yes	No	Yes	No	No	N/A
Discrete Job Routing Sheet	Yes	Yes	Yes	No	Yes	No	No	N/A
Discrete Job Shortage Report	Yes	Yes	Yes	No	Yes	No	No	N/A
Discrete Job Value Report	Yes	Yes	Yes	Yes	Yes	Yes	Yes	N/A
Expense Job Value Report	No	Yes	Yes	Yes	Yes	Yes	Yes	N/A
Job Lot Composition Report	Yes	Yes	Yes	Yes	Yes	Yes	Yes	N/A
Move Transaction Report	No	Yes	Yes	Yes	Yes	Yes	Yes	N/A
Repetitive Line Report	Yes	Yes	Yes	No	Yes	No	N/A	Yes
Repetitive Pick List Report	Yes	Yes	Yes	No	Yes	No	N/A	N/A
Repetitive Routing Sheet	Yes	Yes	Yes	No	Yes	No	N/A	N/A
Repetitive Schedule Data Report	Yes	Yes	Yes	Yes	Yes	Yes	N/A	Yes
Repetitive Schedule Shortage Report	Yes	Yes	Yes	No	Yes	No	N/A	N/A
Repetitive Value Report	No	Yes	Yes	Yes	Yes	Yes	N/A	N/A
Resource Performance Report	No	Yes	Yes	Yes	Yes	Yes	Yes	N/A
Resource Transaction Report	No	Yes	Yes	Yes	Yes	Yes	Yes	N/A
WIP Account Distribution Report	No	Yes	Yes	Yes	Yes	Yes	Yes	N/A
WIP Account Summary Report	Yes	Yes	Yes	Yes	Yes	Yes	Yes	N/A
WIP Location Report	No	Yes	Yes	Yes	Yes	Yes	No	N/A
WIP Outside Processing Report	No	Yes	Yes	Yes	Yes	Yes	No	N/A
WIP Offsetting Account Report	Yes	Yes	Yes	Yes	Yes	Yes	Yes	N/A
WIP Value Report	No	Yes	Yes	Yes	Yes	Yes	No	N/A

Note: Reports that are printed with processes, such as importing and purging jobs and schedules, are not included in the above table.

Related Topics

Viewing Discrete Job Information

Discrete Job Statuses

Repetitive Schedule Statuses

Business Scenarios

The following business cases illustrate how statuses can be used to manage manufacturing production.

Production Start

You are ready to define jobs. However, you do not want to kit and assemble these jobs until you have confirmed material availability and production capacity.

In this case, you can begin by defining your jobs with a status of Unreleased. Once you are certain that everything is ready, you can change the status of the jobs to Released and print your shop paperwork. See: Changing Discrete Job, Mass Changing Discrete Job Statuses, Discrete Shop Packet, and Discrete Job Dispatch Report.

To identify which jobs to kit, the stockroom staff can run a report for all jobs with a status of Released. See: Discrete Job Listing Report.

To identify which assemblies to build, the shop floor staff can run a report that lists assemblies with quantities in the Queue intraoperation step of the first routing operation. See: WIP Location Report.

Production Stop

You need to stop a group of jobs temporarily because a quality problem has developed. You also need to stop a job that is building a configure-to-order item because the customer has just changed the configuration.

In the first instance, stopping production on the group of jobs makes it possible for you to address the quality problem. In the second instance, stopping production allows you to evaluate how the customer's change affects material requirements and operations. You can temporarily stop production on the jobs involved by changing their statuses to On Hold. See: Changing Discrete Jobs and Mass Changing Discrete Job Statuses.

Jobs can be defined in sequential order using the automatic sequence generator. Sequentially ordered jobs are easier to query and mass change than non-sequential jobs.

Once the quality problem is resolved and the impact of the changes to the configure-to-order job have been determined, you can change the statuses of the jobs from On Hold to Unreleased or Released.

Close Discrete Jobs

You are preparing to close your accounting period and must review all jobs that can be closed. You can find and view all Complete, Complete-No Charges, and Cancelled jobs using the View Discrete Jobs window. Using this window, you can also check the disposition of component materials and the status of shop floor operations. See: Viewing Discrete Job Information.

If all the jobs are in order, you can view job costs either on-line or using reports. See: Viewing WIP Value Summaries, Oracle Cost Management User's Guide and Discrete Job Value Report.

Once you are satisfied that your job cost information is correct, you can close your jobs individually or as a group based on their status. See: Overview of Discrete Job Close.

Repetitive Schedule First In - First Out Sequencing

You have implemented an ECO on a repetitive schedule in production, and the schedule has automatically split into two repetitive schedules. The first schedule uses the original bill of material and the second uses the new bill with the ECO. See: ECO Implementation by Status.

Because of the production rates and lead times being used, the schedule split results in having the same assembly with two different bills on the same line at the same time. Since the first in-first out allocations are used when two schedules are released on the line at the same time, you must maintain first in-first out order when moving assemblies. Unfortunately several of the assemblies with the original bill are being may be held for repair at a Reject intraoperation step and assemblies using the new bill are beginning to pass them. This could result in the lose of physical first in-first out (FIFO) flow and improper backflushing.

To correct this problem you must separate the assemblies by changing the status of the first schedule to On Hold. This freezes the first schedule removing it from the FIFO algorithm. Later, when the rejected assemblies are ready to go, you can change the status on the first schedule to Released so that assemblies on the first schedule take precedence in the FIFO algorithm. See: Defining Repetitive Schedules Manually.

Related Topics

Discrete Job Statuses

Repetitive Schedule Statuses

Job and Repetitive Schedule Status Changes