WIP Setup

When you log on to the oracle WIP for the first time , you get the below error message

So the first setup that you need to do is the WIP parameter setup. Including the WIP parameter there are 12 steps to set up Work in Process, three of which are required. All of the steps are visually depicted on the Work in Process Setup Flowchart


WIP parameters

You can use WIP parameters to define modes of operation and to assign default values for various work in process functions. You can only define one set of WIP parameters per organization.
1. Discrete

Default Discrete Class 
Determines which accounting class is used as the default for a Standard Discrete Job.
NOTE: Must be entered after WIP Acctg Classes are setup, while rest of WIP parameters must be entered before you can enter WIP Acctg classes.

Default Lot Number Type
Determines how lot numbers are assigned to discrete jobs.
    Job Name – job lot numbers are based on job name
    Based on Inventory Rules – Job lot numbers are based on the lot number rules you defined in Oracle Inventory.

Respond to Sales Order Changes
Determines whether and how the system responds to changes to configure-to-order (CTO) sales orders and their related discrete jobs.  IF a configured item is de-linked from a Sales Order or sales order line placed on hold, you have following options:
   Never    Work Order not placed on hold
   Always    Work Order always placed on hold
   When linked 1 to 1    Work Order placed on hold if it is the only work order reserved to that sales order


2. Repetitive

Recognize Period Variances
Determines which repetitive schedule variances are posted to GL when an accounting period is closed.
    All Schedules    Post variances for ALL repetitive schedules
    Cancelled & Complete-No Charges Only  Post variances for repetitive schedules with statuses of Cancelled
                or Complete-No Charges
Autorelease Days
Determines the time period within which the system automatically releases the next unreleased schedule after you complete a repetitive schedule.

3. Move Transaction Tab


Require Scrap Account
    Determines whether a scrap account is required when you move scrap assemblies into and out of the Scrap intra-operation step of an operation.
    Clicked on – System debits/credits the applicable account and job.
    Clicked off – Cost of scrap remains on the job until job or period close, at which time it is written off as a variance.
 
Allow Creation of New Operations
    Determines whether you can or cannot add an operation to a discrete job WIP routing during a move transaction.  i.e.  Add an operation to track unexpected rework.
 
Allow Moves Over No Move Shop Floor Statuses
    Determines whether moves are disallowed if an intra-operation step has a No Move Shop Floor Status.
 
4. Material Tab
Supply Sub inventory
Determines which supply sub-inventory is used as a default when backflushing Operation Pull and Assembly Pull components IF defaults are not defined at the BOM component level or the inventory item level.

Supply Locator

Determines default locator used with Supply Sub inventory default if the Supply Sub inventory is Locator controlled.

Lot Selection Method

Determines how lot controlled Operation Pull and Assembly Pull components are selected during backflush transactions.
Expiration Date : Backflush lots selected based on expiration date using FIFO Or Receipt date using FIFO (uses receipt date if the lot is not under shelf life control)
Manual : Backflush lots must be manually selected
Receipt Date : Backflush lots selected based on inventory receipt date using

Lot Verification
Determines how lots selected are verified during backflush transactions
All :     Verifies automatically selected lots were the ones consumed by the Assemblies
Exceptions Only :  Verifies that manually selected lots were the ones consumed by the Assemblies

Release Backflush Components

Determines whether operation pull and assembly pull supply type components are used in the Component Pick release process.

5. Intraoperation Tab
 

Determines which intra-operation steps are enabled in your WIP routing operations.
Queue
  • Assemblies in the Queue intraoperation step of an operation are waiting for you to perform work on them. 
  • Queue is the default intraoperation step for every operation in a routing. 
  • When you release jobs, the assembly quantity is automatically loaded  into the Queue intraoperation step of the first operation.
  • You can move assemblies from the Queue intraoperation step to any other enabled intraoperation step.
  •  
Run   
  • Assemblies in the Run intraoperation step are ready to be worked   on.
  • You can move assemblies from the Run step to any other enabled  intraoperation step in the routing.
  •  
To Move
  • Assemblies in the To Move intraoperation step of an operation have  been completed and are waiting to be moved to the next operation.
  • You can move assemblies from the To Move intraoperation step to any other enabled intraoperation step in the routing.
  • Before you can use the Completion Transactions window to complete assembles from jobs and schedules with routings, you must move these assemblies into the To Move intraoperation step of the last operation. For this reason, the To Move intraoperation step is automatically enabled for all final routing operations.
  • Assemblies in the To Move step are considered complete for the operation.
Reject   
  • Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped.
  • You can move assemblies from the Reject intraoperation step to any other enabled intraoperation step in the routing.
  • Assemblies in the Reject step may not be useable, but they are considered complete for the operation because components and resources have been consumed in their production.
  •  
Scrap    
  • Assemblies in the Scrap intraoperation step are considered unusable. This step is for those assemblies you want to consider as a variance on the discrete job.
  • Oracle Master Scheduling/MRP and Oracle Supply Chain Planning does not consider assemblies in Scrap steps in the MRP planning process.
  • Assemblies in the Scrap intraoperation step are usually not useable.
  • They are considered complete for the operation because components and resources have been consumed in their production.
  • They can be recovered from scrap by moving them to another intraoperation or operation step.
6. Outside Processing Tab
Shop Floor Status for PO Move Resources
    Determines which shop floor status is assigned to the Queue intraoperation step of an outside processing operation when a discrete job is created. 

Requisition Creation Time
    Determines whether Purchase requisitions are created for OSP operations automatically or manually and when in the manufacturing process they are created.
At Job/Schedule Release -  Creates requisition when Job is released
At Operation -    Creates requisition when you move assemblies into the Queue intraoperation step of an OSP operation.
Manual - Requires manual creation of requisition

Job Roles for Notification
Production Scheduler -  Ties an employee with Production Scheduler job role to receive notification when there are no purchase orders for OSP items, when OSP assemblies have been shipped or when they will not be shipped.
Shipping Manager - Ties an employee with Shipping Manager job role to receive notification when intermediate assemblies are ready to be shipped to an OSP supplier.

Propagate Job Change to Purchasing
Sets how quantity changes are forwarded to purchasing documents, and initiates cancellation of these documents under certain conditions. Your choices are:
Automatic – Changes are passed routinely through the workflow. You can choose to have them propagated as fully automatic, or subject to approval. If this parameter is set to Automatic, the requisition and purchase order documents are cancelled if the following conditions exist: The job status is changed to Cancel, Complete No Charge, or Closed.
Manual – You must update changes directly in the purchasing documents.

1.2 WIP parameters

You can use WIP parameters to define modes of operation and to assign default values for various work in process functions. You can only define one set of WIP parameters per organization.
1. Discrete

Default Discrete Class 
Determines which accounting class is used as the default for a Standard Discrete Job.
NOTE: Must be entered after WIP Acctg Classes are setup, while rest of WIP parameters must be entered before you can enter WIP Acctg classes.

Default Lot Number Type
Determines how lot numbers are assigned to discrete jobs.
    Job Name – job lot numbers are based on job name
    Based on Inventory Rules – Job lot numbers are based on the lot number rules you defined in Oracle Inventory.

Respond to Sales Order Changes
Determines whether and how the system responds to changes to configure-to-order (CTO) sales orders and their related discrete jobs.  IF a configured item is de-linked from a Sales Order or sales order line placed on hold, you have following options:
   Never    Work Order not placed on hold
   Always    Work Order always placed on hold
   When linked 1 to 1    Work Order placed on hold if it is the only work order reserved to that sales order


2. Repetitive

Recognize Period Variances
Determines which repetitive schedule variances are posted to GL when an accounting period is closed.
    All Schedules    Post variances for ALL repetitive schedules
    Cancelled & Complete-No Charges Only  Post variances for repetitive schedules with statuses of Cancelled
                or Complete-No Charges
Autorelease Days
Determines the time period within which the system automatically releases the next unreleased schedule after you complete a repetitive schedule.

3. Move Transaction Tab


Require Scrap Account
    Clicked on – System debits/credits the applicable account and job.
    Clicked off – Cost of scrap remains on the job until job or period close, at which time it is written off as a variance.
Determines whether a scrap account is required when you use the Move Transactions window to move job and repetitive assemblies into and out of the Scrap intraoperation step of an operation. It also determines whether a scrap account is required when flow schedule assemblies are scrapped or returned from scrap through the Work Order–less Completions window. If you do not specify that a scrap account is required, it is optional.

This parameter also determines how scrap transactions are processed. If you enter a scrap account, the system debits this account and credits the job or schedule elemental accounts through the operation at which the assemblies are scrapped. If you enter a reversing scrap transaction, the system credits this account and debits the job or schedule elemental accounts through the operation at which the assemblies are returned. If you do not provide a scrap account, the cost of scrap remains in the job or schedule until job or period close and is then written off as a variance.
 
Allow Creation of New Operations
    Determines whether you can or cannot add an operation to a discrete job WIP routing during a move transaction.  i.e.  Add an operation to track unexpected rework.
 
Allow Moves Over No Move Shop Floor Statuses
    Determines whether moves are disallowed if an intra-operation step has a No Move Shop Floor Status.
Determines whether moves are disallowed if an intraoperation step that disallows moves exists at an autocharge operation and intraoperation step between the From and To operations or at intervening intraoperation step at the From and To operations if they are direct charge. If an intraoperation step that disallows moves is found, a warning message is displayed and the move is disallowed.

Direct charge operations between the From and To Operations are not considered when the system checks for no move shop floor statuses. Scrap and Reject intraoperation steps at autocharge operations are also not considered.
 
4. Material Tab
Supply Sub inventory
Determines which supply sub-inventory is used as a default when backflushing Operation Pull and Assembly Pull components IF defaults are not defined at the BOM component level or the inventory item level.

Supply Locator

Determines default locator used with Supply Sub inventory default if the Supply Sub inventory is Locator controlled.

Lot Selection Method

Determines how lot controlled Operation Pull and Assembly Pull components are selected during backflush transactions.
Expiration Date : Backflush lots selected based on expiration date using FIFO Or Receipt date using FIFO (uses receipt date if the lot is not under shelf life control)
Manual : Backflush lots must be manually selected
Receipt Date : Backflush lots selected based on inventory receipt date using

Lot Verification
Determines how lots selected are verified during backflush transactions
All :     Verifies automatically selected lots were the ones consumed by the Assemblies
Exceptions Only :  Verifies that manually selected lots were the ones consumed by the Assemblies

Release Backflush Components

Determines whether operation pull and assembly pull supply type components are used in the Component Pick release process.
Note: The Discrete Job Pick List Report does not use this parameter.

5. Intraoperation Tab
 

Determines which intra-operation steps are enabled in your WIP routing operations.
Queue
  • Assemblies in the Queue intraoperation step of an operation are waiting for you to perform work on them. 
  • Queue is the default intraoperation step for every operation in a routing. 
  • When you release jobs, the assembly quantity is automatically loaded  into the Queue intraoperation step of the first operation.
  • You can move assemblies from the Queue intraoperation step to any other enabled intraoperation step.
Run   
  • Assemblies in the Run intraoperation step are ready to be worked   on.
  • You can move assemblies from the Run step to any other enabled  intraoperation step in the routing.
To Move
  • Assemblies in the To Move intraoperation step of an operation have  been completed and are waiting to be moved to the next operation.
  • You can move assemblies from the To Move intraoperation step to any other enabled intraoperation step in the routing.
  • Before you can use the Completion Transactions window to complete assembles from jobs and schedules with routings, you must move these assemblies into the To Move intraoperation step of the last operation. For this reason, the To Move intraoperation step is automatically enabled for all final routing operations.
  • Assemblies in the To Move step are considered complete for the operation.
Reject   
  • Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped.
  • You can move assemblies from the Reject intraoperation step to any other enabled intraoperation step in the routing.
  • Assemblies in the Reject step may not be useable, but they are considered complete for the operation because components and resources have been consumed in their production.
Scrap    
  • Assemblies in the Scrap intraoperation step are considered unusable. This step is for those assemblies you want to consider as a variance on the discrete job.
  • Oracle Master Scheduling/MRP and Oracle Supply Chain Planning does not consider assemblies in Scrap steps in the MRP planning process.
  • Assemblies in the Scrap intraoperation step are usually not useable.
  • They are considered complete for the operation because components and resources have been consumed in their production.
  • They can be recovered from scrap by moving them to another intraoperation or operation step.
6. Outside Processing Tab
Shop Floor Status for PO Move Resources
    Determines which shop floor status is assigned to the Queue intraoperation step of an outside processing operation when a discrete job is created. 

Requisition Creation Time
    Determines whether Purchase requisitions are created for OSP operations automatically or manually and when in the manufacturing process they are created.
At Job/Schedule Release -  Creates requisition when Job is released
At Operation -    Creates requisition when you move assemblies into the Queue intraoperation step of an OSP operation.
Manual - Requires manual creation of requisition

Job Roles for Notification
Production Scheduler -  Ties an employee with Production Scheduler job role to receive notification when there are no purchase orders for OSP items, when OSP assemblies have been shipped or when they will not be shipped.
Shipping Manager - Ties an employee with Shipping Manager job role to receive notification when intermediate assemblies are ready to be shipped to an OSP supplier.

Propagate Job Change to Purchasing
Sets how quantity changes are forwarded to purchasing documents, and initiates cancellation of these documents under certain conditions. Your choices are:
Automatic – Changes are passed routinely through the workflow. You can choose to have them propagated as fully automatic, or subject to approval. If this parameter is set to Automatic, the requisition and purchase order documents are cancelled if the following conditions exist: The job status is changed to Cancel, Complete No Charge, or Closed.
Manual – You must update changes directly in the purchasing documents.

7. Serial Parameters
The following parameter is used to set features for serial number control tracking throughout manufacturing. Serial control includes control beginning at the routing, association of serial numbers to jobs before their production, serial based transaction entry, generation of serial numbers, and serial label printing.

Default Serialization Start Operation
Determines the job operation where tracking of the serial number begins. The values are:
Enabled: If the serialization start operation is defined on the bill of material item routing, it is copied to the job routing. If this
value is not defined on the item routing, the first operation is defaulted to be the serialization start operation on the job
routing.
Disabled: The serialization start operation on the job routing is blank.

Auto Associate Serial Numbers on Job Creation From Interface
Determines if serial numbers are automatically generated and associated with a job when a job is created through the WIP Mass Load interface. The job start quantity determines the number of serial numbers created. The values are:
Enabled: Serial numbers are automatically generated and associated with a job.
Disabled: Serial numbers are not automatically generated and associated with a job.

Default Intraoperation Step for Assembly Moves
This parameter is used for move transactions on a serialized job. It defines a default value for the intraoperation step where you are moving assemblies – the To step. Your choices are Queue, Run, To move, and null.
For example, when moving assemblies, if this value is set to:
• Queue – the default intraoperation To step for the next move transaction is the next Queue step in the routing.
• Run – the default intraoperation To step for the next move transactions is the next Run step in the routing.
• To move – the default intraoperation To step for the next move transaction is the next To move in the routing.
• Null – a default is not set, you must specify the step in your move transaction.

WIP parameters

You can use WIP parameters to define modes of operation and to assign default values for various work in process functions. You can only define one set of WIP parameters per organization.
1. Discrete

Default Discrete Class 
Determines which accounting class is used as the default for a Standard Discrete Job.
NOTE: Must be entered after WIP Acctg Classes are setup, while rest of WIP parameters must be entered before you can enter WIP Acctg classes.

Default Lot Number Type
Determines how lot numbers are assigned to discrete jobs.
    Job Name – job lot numbers are based on job name
    Based on Inventory Rules – Job lot numbers are based on the lot number rules you defined in Oracle Inventory.

Respond to Sales Order Changes
Determines whether and how the system responds to changes to configure-to-order (CTO) sales orders and their related discrete jobs.  IF a configured item is de-linked from a Sales Order or sales order line placed on hold, you have following options:
   Never    Work Order not placed on hold
   Always    Work Order always placed on hold
   When linked 1 to 1    Work Order placed on hold if it is the only work order reserved to that sales order


2. Repetitive

Recognize Period Variances
Determines which repetitive schedule variances are posted to GL when an accounting period is closed.
    All Schedules    Post variances for ALL repetitive schedules
    Cancelled & Complete-No Charges Only  Post variances for repetitive schedules with statuses of Cancelled
                or Complete-No Charges
Autorelease Days
Determines the time period within which the system automatically releases the next unreleased schedule after you complete a repetitive schedule.

3. Move Transaction Tab


Require Scrap Account
    Determines whether a scrap account is required when you move scrap assemblies into and out of the Scrap intra-operation step of an operation.
    Clicked on – System debits/credits the applicable account and job.
    Clicked off – Cost of scrap remains on the job until job or period close, at which time it is written off as a variance.
 
Allow Creation of New Operations
    Determines whether you can or cannot add an operation to a discrete job WIP routing during a move transaction.  i.e.  Add an operation to track unexpected rework.
 
Allow Moves Over No Move Shop Floor Statuses
    Determines whether moves are disallowed if an intra-operation step has a No Move Shop Floor Status.
 
4. Material Tab
Supply Sub inventory
Determines which supply sub-inventory is used as a default when backflushing Operation Pull and Assembly Pull components IF defaults are not defined at the BOM component level or the inventory item level.

Supply Locator

Determines default locator used with Supply Sub inventory default if the Supply Sub inventory is Locator controlled.

Lot Selection Method

Determines how lot controlled Operation Pull and Assembly Pull components are selected during backflush transactions.
Expiration Date : Backflush lots selected based on expiration date using FIFO Or Receipt date using FIFO (uses receipt date if the lot is not under shelf life control)
Manual : Backflush lots must be manually selected
Receipt Date : Backflush lots selected based on inventory receipt date using

Lot Verification
Determines how lots selected are verified during backflush transactions
All :     Verifies automatically selected lots were the ones consumed by the Assemblies
Exceptions Only :  Verifies that manually selected lots were the ones consumed by the Assemblies

Release Backflush Components

Determines whether operation pull and assembly pull supply type components are used in the Component Pick release process.

5. Intraoperation Tab
 

Determines which intra-operation steps are enabled in your WIP routing operations.
Queue
  • Assemblies in the Queue intraoperation step of an operation are waiting for you to perform work on them. 
  • Queue is the default intraoperation step for every operation in a routing. 
  • When you release jobs, the assembly quantity is automatically loaded  into the Queue intraoperation step of the first operation.
  • You can move assemblies from the Queue intraoperation step to any other enabled intraoperation step.
  •  
Run   
  • Assemblies in the Run intraoperation step are ready to be worked   on.
  • You can move assemblies from the Run step to any other enabled  intraoperation step in the routing.
  •  
To Move
  • Assemblies in the To Move intraoperation step of an operation have  been completed and are waiting to be moved to the next operation.
  • You can move assemblies from the To Move intraoperation step to any other enabled intraoperation step in the routing.
  • Before you can use the Completion Transactions window to complete assembles from jobs and schedules with routings, you must move these assemblies into the To Move intraoperation step of the last operation. For this reason, the To Move intraoperation step is automatically enabled for all final routing operations.
  • Assemblies in the To Move step are considered complete for the operation.
Reject   
  • Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped.
  • You can move assemblies from the Reject intraoperation step to any other enabled intraoperation step in the routing.
  • Assemblies in the Reject step may not be useable, but they are considered complete for the operation because components and resources have been consumed in their production.
  •  
Scrap    
  • Assemblies in the Scrap intraoperation step are considered unusable. This step is for those assemblies you want to consider as a variance on the discrete job.
  • Oracle Master Scheduling/MRP and Oracle Supply Chain Planning does not consider assemblies in Scrap steps in the MRP planning process.
  • Assemblies in the Scrap intraoperation step are usually not useable.
  • They are considered complete for the operation because components and resources have been consumed in their production.
  • They can be recovered from scrap by moving them to another intraoperation or operation step.
6. Outside Processing Tab
Shop Floor Status for PO Move Resources
    Determines which shop floor status is assigned to the Queue intraoperation step of an outside processing operation when a discrete job is created. 

Requisition Creation Time
    Determines whether Purchase requisitions are created for OSP operations automatically or manually and when in the manufacturing process they are created.
At Job/Schedule Release -  Creates requisition when Job is released
At Operation -    Creates requisition when you move assemblies into the Queue intraoperation step of an OSP operation.
Manual - Requires manual creation of requisition

Job Roles for Notification
Production Scheduler -  Ties an employee with Production Scheduler job role to receive notification when there are no purchase orders for OSP items, when OSP assemblies have been shipped or when they will not be shipped.
Shipping Manager - Ties an employee with Shipping Manager job role to receive notification when intermediate assemblies are ready to be shipped to an OSP supplier.

Propagate Job Change to Purchasing
Sets how quantity changes are forwarded to purchasing documents, and initiates cancellation of these documents under certain conditions. Your choices are:
Automatic – Changes are passed routinely through the workflow. You can choose to have them propagated as fully automatic, or subject to approval. If this parameter is set to Automatic, the requisition and purchase order documents are cancelled if the following conditions exist: The job status is changed to Cancel, Complete No Charge, or Closed.
Manual – You must update changes directly in the purchasing documents.

1.2 WIP parameters

You can use WIP parameters to define modes of operation and to assign default values for various work in process functions. You can only define one set of WIP parameters per organization.
1. Discrete

Default Discrete Class 
Determines which accounting class is used as the default for a Standard Discrete Job.
NOTE: Must be entered after WIP Acctg Classes are setup, while rest of WIP parameters must be entered before you can enter WIP Acctg classes.

Default Lot Number Type
Determines how lot numbers are assigned to discrete jobs.
    Job Name – job lot numbers are based on job name
    Based on Inventory Rules – Job lot numbers are based on the lot number rules you defined in Oracle Inventory.

Respond to Sales Order Changes
Determines whether and how the system responds to changes to configure-to-order (CTO) sales orders and their related discrete jobs.  IF a configured item is de-linked from a Sales Order or sales order line placed on hold, you have following options:
   Never    Work Order not placed on hold
   Always    Work Order always placed on hold
   When linked 1 to 1    Work Order placed on hold if it is the only work order reserved to that sales order


2. Repetitive

Recognize Period Variances
Determines which repetitive schedule variances are posted to GL when an accounting period is closed.
    All Schedules    Post variances for ALL repetitive schedules
    Cancelled & Complete-No Charges Only  Post variances for repetitive schedules with statuses of Cancelled
                or Complete-No Charges
Autorelease Days
Determines the time period within which the system automatically releases the next unreleased schedule after you complete a repetitive schedule.

3. Move Transaction Tab


Require Scrap Account
    Clicked on – System debits/credits the applicable account and job.
    Clicked off – Cost of scrap remains on the job until job or period close, at which time it is written off as a variance.
Determines whether a scrap account is required when you use the Move Transactions window to move job and repetitive assemblies into and out of the Scrap intraoperation step of an operation. It also determines whether a scrap account is required when flow schedule assemblies are scrapped or returned from scrap through the Work Order–less Completions window. If you do not specify that a scrap account is required, it is optional.

This parameter also determines how scrap transactions are processed. If you enter a scrap account, the system debits this account and credits the job or schedule elemental accounts through the operation at which the assemblies are scrapped. If you enter a reversing scrap transaction, the system credits this account and debits the job or schedule elemental accounts through the operation at which the assemblies are returned. If you do not provide a scrap account, the cost of scrap remains in the job or schedule until job or period close and is then written off as a variance.
 
Allow Creation of New Operations
    Determines whether you can or cannot add an operation to a discrete job WIP routing during a move transaction.  i.e.  Add an operation to track unexpected rework.
 
Allow Moves Over No Move Shop Floor Statuses
    Determines whether moves are disallowed if an intra-operation step has a No Move Shop Floor Status.
Determines whether moves are disallowed if an intraoperation step that disallows moves exists at an autocharge operation and intraoperation step between the From and To operations or at intervening intraoperation step at the From and To operations if they are direct charge. If an intraoperation step that disallows moves is found, a warning message is displayed and the move is disallowed.

Direct charge operations between the From and To Operations are not considered when the system checks for no move shop floor statuses. Scrap and Reject intraoperation steps at autocharge operations are also not considered.
 
4. Material Tab
Supply Sub inventory
Determines which supply sub-inventory is used as a default when backflushing Operation Pull and Assembly Pull components IF defaults are not defined at the BOM component level or the inventory item level.

Supply Locator

Determines default locator used with Supply Sub inventory default if the Supply Sub inventory is Locator controlled.

Lot Selection Method

Determines how lot controlled Operation Pull and Assembly Pull components are selected during backflush transactions.
Expiration Date : Backflush lots selected based on expiration date using FIFO Or Receipt date using FIFO (uses receipt date if the lot is not under shelf life control)
Manual : Backflush lots must be manually selected
Receipt Date : Backflush lots selected based on inventory receipt date using

Lot Verification
Determines how lots selected are verified during backflush transactions
All :     Verifies automatically selected lots were the ones consumed by the Assemblies
Exceptions Only :  Verifies that manually selected lots were the ones consumed by the Assemblies

Release Backflush Components

Determines whether operation pull and assembly pull supply type components are used in the Component Pick release process.
Note: The Discrete Job Pick List Report does not use this parameter.

5. Intraoperation Tab
 

Determines which intra-operation steps are enabled in your WIP routing operations.
Queue
  • Assemblies in the Queue intraoperation step of an operation are waiting for you to perform work on them. 
  • Queue is the default intraoperation step for every operation in a routing. 
  • When you release jobs, the assembly quantity is automatically loaded  into the Queue intraoperation step of the first operation.
  • You can move assemblies from the Queue intraoperation step to any other enabled intraoperation step.
Run   
  • Assemblies in the Run intraoperation step are ready to be worked   on.
  • You can move assemblies from the Run step to any other enabled  intraoperation step in the routing.
To Move
  • Assemblies in the To Move intraoperation step of an operation have  been completed and are waiting to be moved to the next operation.
  • You can move assemblies from the To Move intraoperation step to any other enabled intraoperation step in the routing.
  • Before you can use the Completion Transactions window to complete assembles from jobs and schedules with routings, you must move these assemblies into the To Move intraoperation step of the last operation. For this reason, the To Move intraoperation step is automatically enabled for all final routing operations.
  • Assemblies in the To Move step are considered complete for the operation.
Reject   
  • Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped.
  • You can move assemblies from the Reject intraoperation step to any other enabled intraoperation step in the routing.
  • Assemblies in the Reject step may not be useable, but they are considered complete for the operation because components and resources have been consumed in their production.
Scrap    
  • Assemblies in the Scrap intraoperation step are considered unusable. This step is for those assemblies you want to consider as a variance on the discrete job.
  • Oracle Master Scheduling/MRP and Oracle Supply Chain Planning does not consider assemblies in Scrap steps in the MRP planning process.
  • Assemblies in the Scrap intraoperation step are usually not useable.
  • They are considered complete for the operation because components and resources have been consumed in their production.
  • They can be recovered from scrap by moving them to another intraoperation or operation step.
6. Outside Processing Tab
Shop Floor Status for PO Move Resources
    Determines which shop floor status is assigned to the Queue intraoperation step of an outside processing operation when a discrete job is created. 

Requisition Creation Time
    Determines whether Purchase requisitions are created for OSP operations automatically or manually and when in the manufacturing process they are created.
At Job/Schedule Release -  Creates requisition when Job is released
At Operation -    Creates requisition when you move assemblies into the Queue intraoperation step of an OSP operation.
Manual - Requires manual creation of requisition

Job Roles for Notification
Production Scheduler -  Ties an employee with Production Scheduler job role to receive notification when there are no purchase orders for OSP items, when OSP assemblies have been shipped or when they will not be shipped.
Shipping Manager - Ties an employee with Shipping Manager job role to receive notification when intermediate assemblies are ready to be shipped to an OSP supplier.

Propagate Job Change to Purchasing
Sets how quantity changes are forwarded to purchasing documents, and initiates cancellation of these documents under certain conditions. Your choices are:
Automatic – Changes are passed routinely through the workflow. You can choose to have them propagated as fully automatic, or subject to approval. If this parameter is set to Automatic, the requisition and purchase order documents are cancelled if the following conditions exist: The job status is changed to Cancel, Complete No Charge, or Closed.
Manual – You must update changes directly in the purchasing documents.

7. Serial Parameters
The following parameter is used to set features for serial number control tracking throughout manufacturing. Serial control includes control beginning at the routing, association of serial numbers to jobs before their production, serial based transaction entry, generation of serial numbers, and serial label printing.

Default Serialization Start Operation
Determines the job operation where tracking of the serial number begins. The values are:
Enabled: If the serialization start operation is defined on the bill of material item routing, it is copied to the job routing. If this
value is not defined on the item routing, the first operation is defaulted to be the serialization start operation on the job
routing.
Disabled: The serialization start operation on the job routing is blank.

Auto Associate Serial Numbers on Job Creation From Interface
Determines if serial numbers are automatically generated and associated with a job when a job is created through the WIP Mass Load interface. The job start quantity determines the number of serial numbers created. The values are:
Enabled: Serial numbers are automatically generated and associated with a job.
Disabled: Serial numbers are not automatically generated and associated with a job.

Default Intraoperation Step for Assembly Moves
This parameter is used for move transactions on a serialized job. It defines a default value for the intraoperation step where you are moving assemblies – the To step. Your choices are Queue, Run, To move, and null.
For example, when moving assemblies, if this value is set to:
• Queue – the default intraoperation To step for the next move transaction is the next Queue step in the routing.
• Run – the default intraoperation To step for the next move transactions is the next Run step in the routing.
• To move – the default intraoperation To step for the next move transaction is the next To move in the routing.
• Null – a default is not set, you must specify the step in your move transaction.

WIP Accounting Classes

You can define any number of accounting classes. The valuation and variance accounts that are associated with these accounting classes determine which accounts are charged and when.


Discrete Accounting Classes
You can define accounting classes for each type of discrete production you use: standard discrete, asset non-standard discrete and expense non-standard discrete. You must assign an accounting class all your discrete jobs.

Standard Discrete
Standard discrete accounting classes can be used to group job costs. For example, if you build subassemblies and finished goods, you can define your accounting classes so that you can separately value and report the costs associated with subassembly and finishedgoods production. Standard discrete accounting classes can be automatically defaulted when you create discrete jobs.

When you define an accounting class, you must assign valuation and variance accounts to it. When you issue materials to a job that uses this accounting class, the appropriate valuation accounts are charged. When the job is closed, final costs and variances are calculated and posted to the variance and valuation accounts. When the accounting period is closed, these journal entries are automatically posted to the general ledger.

Non-Standard Discrete
Non-standard discrete accounting classes can be used to group and report various types of non-standard production costs, such as field service repair or engineering projects.
For example to track recurring expenses - machine maintenance or engineering projects - with non-standard jobs, you can define and assign an accounting class with a type of expense non-standard to these jobs. The valuation accounts carry the costs incurred on these expense jobs as an asset during the period and automatically writes them off to the variance accounts at period close.

On the other hand, if you use non-standard discrete jobs to track production costs as assets, you can define and assign an accounting class with a type of asset non-standard.
Asset non-standard discrete jobs are costed the same as standard discrete jobs. Valuation accounts are charged when material is issued to a job and final costs and variances are calculated and posted to the appropriate variance and valuation accounts when the job is closed.


WIP  Valuation Accounts
WIP accounting class valuation accounts are charged when you issue components, move assemblies, complete assemblies, and charge resources.
Material – Normally an asset account, this account tracks material costs. Under standard costing, it is debited at standard when you issue material to a job or schedule and credited at standard when you complete assemblies from a job or schedule, close a job or close and accounting period. Under average costing, this account is debited at the average cost at the time of the issue transaction and is credited when you complete assemblies from a job.

Material Overhead – Normally an asset account, this account tracks material overhead (burden) costs.
Under standard costing, it is charged/debited at standard when you issue material with material overhead to a job or schedule and relieved at standard when you complete assemblies from a job or schedule, close a job or close an accounting
period. Under average costing, this account is debited at the average cost at the time of the issue transaction.
Note: When assemblies are completed and material overhead is earned, this account is not charged/credited. Instead, the material overhead account for the completion subinventory is debited.

Resource – Normally an asset account, this account tracks resource costs. Under standard costing, it is charged/debited at standard when resources are charged to a job or schedule and relieved/credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, this account is debited and credited at the resource rate at the time the resource is charged.

Outside processing – Normally an asset account, this account tracks outside processing costs. Under standard costing it is debited at the standard or purchase order cost when you receive items for a job or schedule. It is credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, the debiting of this account is based on item receipt (just as it is under standard costing).

Overhead – An asset account to track resource or department overhead cost

WIP Variance Accounts
Variance accounts associated with Standard Discrete and Non-Standard Asset accounting classes are charged when jobs are closed. Variance accounts associated with Expense Non-Standard Discrete, and optionally Repetitive accounting classes, are charged when accounting periods are closed.

Material variance– This account tracks variances that occur when the previous level material costs charged to the job or schedule do not equal the previous level material costs that are relieved. This calculation gives you a net material usage and configuration variance.

Resource variance – Tracks variances that occur when the resource costs charged to the job do not equal resource costs relieved.

Outside Processing variance – Tracks variances that occur when OSP costs charged to the job do not equal OSP costs relieved from the job

Overhead variance– This account tracks the variances that are occur when the overhead costs charged to the job or schedule do not equal the overhead costs relieved from the job or schedule. These variances include both efficiency and method variances.

Standard Cost variance - This Variance account applies only to Standard Discrete and Asset Non–Standard.
This account is charged for the sum of all the elemental standard cost adjustments when you perform a standard cost update that impacts an active job. Cost updates are not performed for repetitive schedules or expense non–standard jobs.

Bridging – Optional –

Expense – Optional-used to accommodate European accounting  Practices

Estimated Scrap – Not applicable – requires Oracle Shop floor mgmt and applies to lot based jobs.

Repetitive Accounting Classes
Repetitive accounting classes are used to group production costs and must be assigned to each repetitive line/assembly association that is created. Every schedule for that assembly on that line uses these accounts. The accounts are charged whenever you transact against the line/assembly association. Repetitive accounting classes can be automatically defaulted when you associate repetitive assemblies with production lines.

You can analyze repetitive manufacturing costs by assembly regardless of the line on which it was manufactured by using the same accounting class for all lines that build that assembly. You can use the same class for all assemblies on a line to do line based cost reporting or you can use a different accounting class for every line/assembly association.

Lot Based Job Accounting Classes
Oracle Shop Floor Management extends work in process functionality using network routings, lot based transactions, and yield based operational costing. If you have Oracle Shop Floor Management installed, you can define accounting classes for standard production and expense non-standard jobs.

Maintenance Account Class
Maintenance accounting classes are used to group costs for work orders used in Oracle Enterprise Asset Management (eAM). For example, if you are creating work orders for plant maintenance activities, you can define your accounting classes to separately value and report the costs related to asset. Maintenance accounting classes are automatically defaulted when you create eAM work orders.

1.3 WIP Accounting Classes

You can define any number of accounting classes. The valuation and variance accounts that are associated with these accounting classes determine which accounts are charged and when.

Discrete Accounting Classes
You can define accounting classes for each type of discrete production you use: standard discrete, asset non-standard discrete and expense non-standard discrete. You must assign an accounting class all your discrete jobs.

Standard Discrete
Standard discrete accounting classes can be used to group job costs. For example, if you build subassemblies and finished goods, you can define your accounting classes so that you can separately value and report the costs associated with subassembly and finishedgoods production. Standard discrete accounting classes can be automatically defaulted when you create discrete jobs.

When you define an accounting class, you must assign valuation and variance accounts to it. When you issue materials to a job that uses this accounting class, the appropriate valuation accounts are charged. When the job is closed, final costs and variances are calculated and posted to the variance and valuation accounts. When the accounting period is closed, these journal entries are automatically posted to the general ledger. (Cost -> Valuation A/C, Variance - Variance A/Cs)

Expense Non-Standard Discrete
Non-standard discrete accounting classes can be used to group and report various types of non-standard production costs, such as field service repair or engineering projects.
For example to track recurring expenses - machine maintenance or engineering projects - with non-standard jobs, you can define and assign an accounting class with a type of expense non-standard to these jobs. The valuation accounts carry the costs incurred on these expense jobs as an asset during the period and automatically writes them off to the variance accounts at period close.

Asset non–standard Discrete

On the other hand, if you use non-standard discrete jobs to track production costs as assets, you can define and assign an accounting class with a type of asset non-standard.
Asset non-standard discrete jobs are costed the same as standard discrete jobs. Valuation accounts are charged when material is issued to a job and final costs and variances are calculated and posted to the appropriate variance and valuation accounts when the job is closed.


WIP  Valuation Accounts
WIP accounting class valuation accounts are charged when you issue components, move assemblies, complete assemblies, and charge resources.
Material – Normally an asset account, this account tracks material costs. Under standard costing, it is debited at standard when you issue material to a job or schedule and credited at standard when you complete assemblies from a job or schedule, close a job or close and accounting period. Under average costing, this account is debited at the average cost at the time of the issue transaction and is credited when you complete assemblies from a job.

Material Overhead – Normally an asset account, this account tracks material overhead (burden) costs.
Under standard costing, it is charged/debited at standard when you issue material with material overhead to a job or schedule and relieved at standard when you complete assemblies from a job or schedule, close a job or close an accounting period. Under average costing, this account is debited at the average cost at the time of the issue transaction.
Note: When assemblies are completed and material overhead is earned, this account is not charged/credited. Instead, the material overhead account for the completion subinventory is debited.

Resource – Normally an asset account, this account tracks resource costs. Under standard costing, it is charged/debited at standard when resources are charged to a job or schedule and relieved/credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, this account is debited and credited at the resource rate at the time the resource is charged.

Outside processing – Normally an asset account, this account tracks outside processing costs. Under standard costing it is debited at the standard or purchase order cost when you receive items for a job or schedule. It is credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, the debiting of this account is based on item receipt (just as it is under standard costing).

Overhead – Normally an asset account this account tracks resource or department overhead cost. Under standard costing it is debited at standard when resources are charged to a job or schedule. It is relieved at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period.

WIP Variance Accounts
Variance accounts associated with Standard Discrete and Non-Standard Asset accounting classes are charged when jobs are closed. Variance accounts associated with Expense Non-Standard Discrete, and optionally Repetitive accounting classes, are charged when accounting periods are closed.

Material variance– This account tracks variances that occur when the previous level material costs charged to the job or schedule do not equal the previous level material costs that are relieved. This calculation gives you a net material usage and configuration variance.

Resource variance – Tracks variances that occur when the resource costs charged to the job do not equal resource costs relieved.

Outside Processing variance – Tracks variances that occur when OSP costs charged to the job do not equal OSP costs relieved from the job

Overhead variance– This account tracks the variances that are occur when the overhead costs charged to the job or schedule do not equal the overhead costs relieved from the job or schedule. These variances include both efficiency and method variances.

Standard Cost variance - This Variance account applies only to Standard Discrete and Asset Non–Standard.
This account is charged for the sum of all the elemental standard cost adjustments when you perform a standard cost update that impacts an active job. Cost updates are not performed for repetitive schedules or expense non–standard jobs.

Bridging – Optional –

Expense – Optional-used to accommodate European accounting  Practices

Estimated Scrap – Not applicable – requires Oracle Shop floor mgmt and applies to lot based jobs.

Repetitive Accounting Classes
Repetitive accounting classes are used to group production costs and must be assigned to each repetitive line/assembly association that is created. Every schedule for that assembly on that line uses these accounts. The accounts are charged whenever you transact against the line/assembly association. Repetitive accounting classes can be automatically defaulted when you associate repetitive assemblies with production lines.

You can analyze repetitive manufacturing costs by assembly regardless of the line on which it was manufactured by using the same accounting class for all lines that build that assembly. You can use the same class for all assemblies on a line to do line based cost reporting or you can use a different accounting class for every line/assembly association.

Lot Based Job Accounting Classes
Oracle Shop Floor Management extends work in process functionality using network routings, lot based transactions, and yield based operational costing. If you have Oracle Shop Floor Management installed, you can define accounting classes for standard production and expense non-standard jobs.

Maintenance Account Class
Maintenance accounting classes are used to group costs for work orders used in Oracle Enterprise Asset Management (eAM). For example, if you are creating work orders for plant maintenance activities, you can define your accounting classes to separately value and report the costs related to asset. Maintenance accounting classes are automatically defaulted when you create eAM work orders.

WIP Accounting Classes

You can define any number of accounting classes. The valuation and variance accounts that are associated with these accounting classes determine which accounts are charged and when.


Discrete Accounting Classes
You can define accounting classes for each type of discrete production you use: standard discrete, asset non-standard discrete and expense non-standard discrete. You must assign an accounting class all your discrete jobs.

Standard Discrete
Standard discrete accounting classes can be used to group job costs. For example, if you build subassemblies and finished goods, you can define your accounting classes so that you can separately value and report the costs associated with subassembly and finishedgoods production. Standard discrete accounting classes can be automatically defaulted when you create discrete jobs.

When you define an accounting class, you must assign valuation and variance accounts to it. When you issue materials to a job that uses this accounting class, the appropriate valuation accounts are charged. When the job is closed, final costs and variances are calculated and posted to the variance and valuation accounts. When the accounting period is closed, these journal entries are automatically posted to the general ledger.

Non-Standard Discrete
Non-standard discrete accounting classes can be used to group and report various types of non-standard production costs, such as field service repair or engineering projects.
For example to track recurring expenses - machine maintenance or engineering projects - with non-standard jobs, you can define and assign an accounting class with a type of expense non-standard to these jobs. The valuation accounts carry the costs incurred on these expense jobs as an asset during the period and automatically writes them off to the variance accounts at period close.

On the other hand, if you use non-standard discrete jobs to track production costs as assets, you can define and assign an accounting class with a type of asset non-standard.
Asset non-standard discrete jobs are costed the same as standard discrete jobs. Valuation accounts are charged when material is issued to a job and final costs and variances are calculated and posted to the appropriate variance and valuation accounts when the job is closed.


WIP  Valuation Accounts
WIP accounting class valuation accounts are charged when you issue components, move assemblies, complete assemblies, and charge resources.
Material – Normally an asset account, this account tracks material costs. Under standard costing, it is debited at standard when you issue material to a job or schedule and credited at standard when you complete assemblies from a job or schedule, close a job or close and accounting period. Under average costing, this account is debited at the average cost at the time of the issue transaction and is credited when you complete assemblies from a job.

Material Overhead – Normally an asset account, this account tracks material overhead (burden) costs.
Under standard costing, it is charged/debited at standard when you issue material with material overhead to a job or schedule and relieved at standard when you complete assemblies from a job or schedule, close a job or close an accounting
period. Under average costing, this account is debited at the average cost at the time of the issue transaction.
Note: When assemblies are completed and material overhead is earned, this account is not charged/credited. Instead, the material overhead account for the completion subinventory is debited.

Resource – Normally an asset account, this account tracks resource costs. Under standard costing, it is charged/debited at standard when resources are charged to a job or schedule and relieved/credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, this account is debited and credited at the resource rate at the time the resource is charged.

Outside processing – Normally an asset account, this account tracks outside processing costs. Under standard costing it is debited at the standard or purchase order cost when you receive items for a job or schedule. It is credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, the debiting of this account is based on item receipt (just as it is under standard costing).

Overhead – An asset account to track resource or department overhead cost

WIP Variance Accounts
Variance accounts associated with Standard Discrete and Non-Standard Asset accounting classes are charged when jobs are closed. Variance accounts associated with Expense Non-Standard Discrete, and optionally Repetitive accounting classes, are charged when accounting periods are closed.

Material variance– This account tracks variances that occur when the previous level material costs charged to the job or schedule do not equal the previous level material costs that are relieved. This calculation gives you a net material usage and configuration variance.

Resource variance – Tracks variances that occur when the resource costs charged to the job do not equal resource costs relieved.

Outside Processing variance – Tracks variances that occur when OSP costs charged to the job do not equal OSP costs relieved from the job

Overhead variance– This account tracks the variances that are occur when the overhead costs charged to the job or schedule do not equal the overhead costs relieved from the job or schedule. These variances include both efficiency and method variances.

Standard Cost variance - This Variance account applies only to Standard Discrete and Asset Non–Standard.
This account is charged for the sum of all the elemental standard cost adjustments when you perform a standard cost update that impacts an active job. Cost updates are not performed for repetitive schedules or expense non–standard jobs.

Bridging – Optional –

Expense – Optional-used to accommodate European accounting  Practices

Estimated Scrap – Not applicable – requires Oracle Shop floor mgmt and applies to lot based jobs.

Repetitive Accounting Classes
Repetitive accounting classes are used to group production costs and must be assigned to each repetitive line/assembly association that is created. Every schedule for that assembly on that line uses these accounts. The accounts are charged whenever you transact against the line/assembly association. Repetitive accounting classes can be automatically defaulted when you associate repetitive assemblies with production lines.

You can analyze repetitive manufacturing costs by assembly regardless of the line on which it was manufactured by using the same accounting class for all lines that build that assembly. You can use the same class for all assemblies on a line to do line based cost reporting or you can use a different accounting class for every line/assembly association.

Lot Based Job Accounting Classes
Oracle Shop Floor Management extends work in process functionality using network routings, lot based transactions, and yield based operational costing. If you have Oracle Shop Floor Management installed, you can define accounting classes for standard production and expense non-standard jobs.

Maintenance Account Class
Maintenance accounting classes are used to group costs for work orders used in Oracle Enterprise Asset Management (eAM). For example, if you are creating work orders for plant maintenance activities, you can define your accounting classes to separately value and report the costs related to asset. Maintenance accounting classes are automatically defaulted when you create eAM work orders.

1.3 WIP Accounting Classes

You can define any number of accounting classes. The valuation and variance accounts that are associated with these accounting classes determine which accounts are charged and when.

Discrete Accounting Classes
You can define accounting classes for each type of discrete production you use: standard discrete, asset non-standard discrete and expense non-standard discrete. You must assign an accounting class all your discrete jobs.

Standard Discrete
Standard discrete accounting classes can be used to group job costs. For example, if you build subassemblies and finished goods, you can define your accounting classes so that you can separately value and report the costs associated with subassembly and finishedgoods production. Standard discrete accounting classes can be automatically defaulted when you create discrete jobs.

When you define an accounting class, you must assign valuation and variance accounts to it. When you issue materials to a job that uses this accounting class, the appropriate valuation accounts are charged. When the job is closed, final costs and variances are calculated and posted to the variance and valuation accounts. When the accounting period is closed, these journal entries are automatically posted to the general ledger. (Cost -> Valuation A/C, Variance - Variance A/Cs)

Expense Non-Standard Discrete
Non-standard discrete accounting classes can be used to group and report various types of non-standard production costs, such as field service repair or engineering projects.
For example to track recurring expenses - machine maintenance or engineering projects - with non-standard jobs, you can define and assign an accounting class with a type of expense non-standard to these jobs. The valuation accounts carry the costs incurred on these expense jobs as an asset during the period and automatically writes them off to the variance accounts at period close.

Asset non–standard Discrete

On the other hand, if you use non-standard discrete jobs to track production costs as assets, you can define and assign an accounting class with a type of asset non-standard.
Asset non-standard discrete jobs are costed the same as standard discrete jobs. Valuation accounts are charged when material is issued to a job and final costs and variances are calculated and posted to the appropriate variance and valuation accounts when the job is closed.


WIP  Valuation Accounts
WIP accounting class valuation accounts are charged when you issue components, move assemblies, complete assemblies, and charge resources.
Material – Normally an asset account, this account tracks material costs. Under standard costing, it is debited at standard when you issue material to a job or schedule and credited at standard when you complete assemblies from a job or schedule, close a job or close and accounting period. Under average costing, this account is debited at the average cost at the time of the issue transaction and is credited when you complete assemblies from a job.

Material Overhead – Normally an asset account, this account tracks material overhead (burden) costs.
Under standard costing, it is charged/debited at standard when you issue material with material overhead to a job or schedule and relieved at standard when you complete assemblies from a job or schedule, close a job or close an accounting period. Under average costing, this account is debited at the average cost at the time of the issue transaction.
Note: When assemblies are completed and material overhead is earned, this account is not charged/credited. Instead, the material overhead account for the completion subinventory is debited.

Resource – Normally an asset account, this account tracks resource costs. Under standard costing, it is charged/debited at standard when resources are charged to a job or schedule and relieved/credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, this account is debited and credited at the resource rate at the time the resource is charged.

Outside processing – Normally an asset account, this account tracks outside processing costs. Under standard costing it is debited at the standard or purchase order cost when you receive items for a job or schedule. It is credited at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period. Under average costing, the debiting of this account is based on item receipt (just as it is under standard costing).

Overhead – Normally an asset account this account tracks resource or department overhead cost. Under standard costing it is debited at standard when resources are charged to a job or schedule. It is relieved at standard when you complete assemblies from a job or schedule, close a job, or close an accounting period.

WIP Variance Accounts
Variance accounts associated with Standard Discrete and Non-Standard Asset accounting classes are charged when jobs are closed. Variance accounts associated with Expense Non-Standard Discrete, and optionally Repetitive accounting classes, are charged when accounting periods are closed.

Material variance– This account tracks variances that occur when the previous level material costs charged to the job or schedule do not equal the previous level material costs that are relieved. This calculation gives you a net material usage and configuration variance.

Resource variance – Tracks variances that occur when the resource costs charged to the job do not equal resource costs relieved.

Outside Processing variance – Tracks variances that occur when OSP costs charged to the job do not equal OSP costs relieved from the job

Overhead variance– This account tracks the variances that are occur when the overhead costs charged to the job or schedule do not equal the overhead costs relieved from the job or schedule. These variances include both efficiency and method variances.

Standard Cost variance - This Variance account applies only to Standard Discrete and Asset Non–Standard.
This account is charged for the sum of all the elemental standard cost adjustments when you perform a standard cost update that impacts an active job. Cost updates are not performed for repetitive schedules or expense non–standard jobs.

Bridging – Optional –

Expense – Optional-used to accommodate European accounting  Practices

Estimated Scrap – Not applicable – requires Oracle Shop floor mgmt and applies to lot based jobs.

Repetitive Accounting Classes
Repetitive accounting classes are used to group production costs and must be assigned to each repetitive line/assembly association that is created. Every schedule for that assembly on that line uses these accounts. The accounts are charged whenever you transact against the line/assembly association. Repetitive accounting classes can be automatically defaulted when you associate repetitive assemblies with production lines.

You can analyze repetitive manufacturing costs by assembly regardless of the line on which it was manufactured by using the same accounting class for all lines that build that assembly. You can use the same class for all assemblies on a line to do line based cost reporting or you can use a different accounting class for every line/assembly association.

Lot Based Job Accounting Classes
Oracle Shop Floor Management extends work in process functionality using network routings, lot based transactions, and yield based operational costing. If you have Oracle Shop Floor Management installed, you can define accounting classes for standard production and expense non-standard jobs.

Maintenance Account Class
Maintenance accounting classes are used to group costs for work orders used in Oracle Enterprise Asset Management (eAM). For example, if you are creating work orders for plant maintenance activities, you can define your accounting classes to separately value and report the costs related to asset. Maintenance accounting classes are automatically defaulted when you create eAM work orders.

WIP Supply Types


WHAT: Used to Control how component materials are:
  • supplied to Discrete Jobs
  • planned in Oracle Master Scheduling/MRP and Supply Chain Planning
  • costed in Oracle Cost Management
HOW: Assign Supply Types
  • to items defined in Oracle Inventory
  • to components when creating BOM’s
  •  
WIP Supply Types:
    Assembly Pull
-    Components issued to job when completing assemblies
-    Pulled from the supply subinventory assigned to the component
-    If a Non-Standard Job, you have an assembly referenced for that job

    Operation Pull
-    Components issued to job when completing backflush operations
-    Pulled from the supply subinventory assigned to the component
-    CanNOT assign to an assembly without a routing

    Push
-    Issued manually to jobs as required
-    Can specify the subinventory from which to issue push components

   Phantom
-    Assigned to BOM component subassemblies and items in Oracle BOM
-    Components of Phantom subassemblies used as if tied directly to the parent assembly
-    Do not appear on WIP jobs,  as subassemblies they lose their identity and become a collection of their components on the WIP job
-    When rolling up assembly costs, normally only the material cost under the phantom is rolled up to the parent, not the phantom routing costs.  NOTE: Two switches can be set that impacts leadtime and cost rollups.

    Bulk
-    Can be viewed and displayed on reports
-    Shows Shop Floor requirement but not transacted/backflushed
-    Often used for inexpensive items that are expensed at receipt
-    Can manually issue specific bulk components to a discrete job if desired.

    Supplier
-    Supplier component requirements can be included on bills of material. Requirements for supplier components are created when you define discrete jobs and repetitive schedules in Work in Process.
-  Supplier component requirements can be viewed and are displayed on reports. They provide information on the component materials that your suppliers provide but neednot be transacted.
-  Supplier components are notbackflushednor do they default when issuing all components for an assembly. You can, however, manually issue specific supplier components to discrete jobs and repetitive schedules.

1.1 WIP Supply Types


WHAT: Used to Control how component materials are:
  • supplied to Discrete Jobs
  • planned in Oracle Master Scheduling/MRP and Supply Chain Planning
  • costed in Oracle Cost Management
HOW: Assign Supply Types
  • to items defined in Oracle Inventory
  • to components when creating BOM’s
  •  
WIP Supply Types:
    Assembly Pull
-    Components issued to job when completing assemblies
-    Pulled from the supply subinventory assigned to the component
-    If a Non-Standard Job, you have an assembly referenced for that job

    Operation Pull
-    Components issued to job when completing backflush operations
-    Pulled from the supply subinventory assigned to the component
-    CanNOT assign to an assembly without a routing

    Push
-    Issued manually to jobs as required
-    Can specify the subinventory from which to issue push components 
-    Use 'WIP component issue' from material transaction form to issue the material

   Phantom
-    Assigned to BOM component subassemblies and items in Oracle BOM
-    Components of Phantom subassemblies used as if tied directly to the parent assembly
-    Do not appear on WIP jobs,  as subassemblies they lose their identity and become a collection of their components on the WIP job
-    When rolling up assembly costs, normally only the material cost under the phantom is rolled up to the parent, not the phantom routing costs.  NOTE: Two switches can be set that impacts leadtime and cost rollups.

    Bulk
-    Can be viewed and displayed on reports
-    Shows Shop Floor requirement but not transacted/backflushed
-    Often used for inexpensive items that are expensed at receipt
-    Can manually issue specific bulk components to a discrete job if desired.

    Supplier
-    Supplier component requirements can be included on bills of material. Requirements for supplier components are created when you define discrete jobs and repetitive schedules in Work in Process.
-  Supplier component requirements can be viewed and are displayed on reports. They provide information on the component materials that your suppliers provide but neednot be transacted.
-  Supplier components are notbackflushednor do they default when issuing all components for an assembly. You can, however, manually issue specific supplier components to discrete jobs and repetitive schedules.

WIP Supply Types


WHAT: Used to Control how component materials are:
  • supplied to Discrete Jobs
  • planned in Oracle Master Scheduling/MRP and Supply Chain Planning
  • costed in Oracle Cost Management
HOW: Assign Supply Types
  • to items defined in Oracle Inventory
  • to components when creating BOM’s
  •  
WIP Supply Types:
    Assembly Pull
-    Components issued to job when completing assemblies
-    Pulled from the supply subinventory assigned to the component
-    If a Non-Standard Job, you have an assembly referenced for that job

    Operation Pull
-    Components issued to job when completing backflush operations
-    Pulled from the supply subinventory assigned to the component
-    CanNOT assign to an assembly without a routing

    Push
-    Issued manually to jobs as required
-    Can specify the subinventory from which to issue push components

   Phantom
-    Assigned to BOM component subassemblies and items in Oracle BOM
-    Components of Phantom subassemblies used as if tied directly to the parent assembly
-    Do not appear on WIP jobs,  as subassemblies they lose their identity and become a collection of their components on the WIP job
-    When rolling up assembly costs, normally only the material cost under the phantom is rolled up to the parent, not the phantom routing costs.  NOTE: Two switches can be set that impacts leadtime and cost rollups.

    Bulk
-    Can be viewed and displayed on reports
-    Shows Shop Floor requirement but not transacted/backflushed
-    Often used for inexpensive items that are expensed at receipt
-    Can manually issue specific bulk components to a discrete job if desired.

    Supplier
-    Supplier component requirements can be included on bills of material. Requirements for supplier components are created when you define discrete jobs and repetitive schedules in Work in Process.
-  Supplier component requirements can be viewed and are displayed on reports. They provide information on the component materials that your suppliers provide but neednot be transacted.
-  Supplier components are notbackflushednor do they default when issuing all components for an assembly. You can, however, manually issue specific supplier components to discrete jobs and repetitive schedules.

1.1 WIP Supply Types


WHAT: Used to Control how component materials are:
  • supplied to Discrete Jobs
  • planned in Oracle Master Scheduling/MRP and Supply Chain Planning
  • costed in Oracle Cost Management
HOW: Assign Supply Types
  • to items defined in Oracle Inventory
  • to components when creating BOM’s
  •  
WIP Supply Types:
    Assembly Pull
-    Components issued to job when completing assemblies
-    Pulled from the supply subinventory assigned to the component
-    If a Non-Standard Job, you have an assembly referenced for that job

    Operation Pull
-    Components issued to job when completing backflush operations
-    Pulled from the supply subinventory assigned to the component
-    CanNOT assign to an assembly without a routing

    Push
-    Issued manually to jobs as required
-    Can specify the subinventory from which to issue push components 
-    Use 'WIP component issue' from material transaction form to issue the material

   Phantom
-    Assigned to BOM component subassemblies and items in Oracle BOM
-    Components of Phantom subassemblies used as if tied directly to the parent assembly
-    Do not appear on WIP jobs,  as subassemblies they lose their identity and become a collection of their components on the WIP job
-    When rolling up assembly costs, normally only the material cost under the phantom is rolled up to the parent, not the phantom routing costs.  NOTE: Two switches can be set that impacts leadtime and cost rollups.

    Bulk
-    Can be viewed and displayed on reports
-    Shows Shop Floor requirement but not transacted/backflushed
-    Often used for inexpensive items that are expensed at receipt
-    Can manually issue specific bulk components to a discrete job if desired.

    Supplier
-    Supplier component requirements can be included on bills of material. Requirements for supplier components are created when you define discrete jobs and repetitive schedules in Work in Process.
-  Supplier component requirements can be viewed and are displayed on reports. They provide information on the component materials that your suppliers provide but neednot be transacted.
-  Supplier components are notbackflushednor do they default when issuing all components for an assembly. You can, however, manually issue specific supplier components to discrete jobs and repetitive schedules.

WIP Fundas

Try to understand the screenshots shown in the attched PPT.

Shop Floor Statuses

Shop floor statuses can be used to control shop floor movement transactions. You can define as many shop floor statuses as are required. Shop floor statuses can be assigned to the intraoperation steps of work in process routing operations. When assigned to an intraoperation step of an operation that is associated with a particular repetitive line and assembly, the status applies to all repetitive schedules building that assembly on that line.

Usage
You can control move transactions by assigning Shop Floor Statuses to intraoperation steps on the work in process routing. For example you may want to create a “Hold for Quality Check” status that can be assigned to an intraoperation stepbefore moving to the next assembly step.

Defining Shop Floor Statuses
(N) WIP > Move Transactions > Shop Floor Statuses > Shop Floor Statuses

 
1. Enter an alphanumeric Status name.
For example, enter WIPHold to signify that shop floor assemblies are on WIP hold or, QAHold to signify that the shop floor assemblies are on quality assurance hold.

2. Enter a Status description.
Descriptions can be used to identify shop floor statuses on standard reports. They can be up to 240 characters of alpha numeric text.

3. Uncheck Allow Moves so that you can use this status to control move transactions. Allow Moves defaults to checked.

Assign Shop Floor Statuses
Shop floor statuses can be attached to WIP jobs in Assign Shop Floor Statuses form

2.3 Shop Floor Statuses

Shop floor statuses can be used to control shop floor movement transactions. You can define as many shop floor statuses as are required. Shop floor statuses can be assigned to the intraoperation steps of work in process routing operations. When assigned to an intraoperation step of an operation that is associated with a particular repetitive line and assembly, the status applies to all repetitive schedules building that assembly on that line.

Usage
You can control move transactions by assigning Shop Floor Statuses to intraoperation steps on the work in process routing. For example you may want to create a “Hold for Quality Check” status that can be assigned to an intraoperation stepbefore moving to the next assembly step.

Defining Shop Floor Statuses
(N) WIP > Move Transactions > Shop Floor Statuses > Shop Floor Statuses

 
1. Enter an alphanumeric Status name.
For example, enter WIPHold to signify that shop floor assemblies are on WIP hold or, QAHold to signify that the shop floor assemblies are on quality assurance hold.

2. Enter a Status description.
Descriptions can be used to identify shop floor statuses on standard reports. They can be up to 240 characters of alpha numeric text.

3. Uncheck Allow Moves so that you can use this status to control move transactions. Allow Moves defaults to checked.

Assign Shop Floor Statuses
Shop floor statuses can be attached to WIP jobs in Assign Shop Floor Statuses form

Shop Floor Statuses

Shop floor statuses can be used to control shop floor movement transactions. You can define as many shop floor statuses as are required. Shop floor statuses can be assigned to the intraoperation steps of work in process routing operations. When assigned to an intraoperation step of an operation that is associated with a particular repetitive line and assembly, the status applies to all repetitive schedules building that assembly on that line.

Usage
You can control move transactions by assigning Shop Floor Statuses to intraoperation steps on the work in process routing. For example you may want to create a “Hold for Quality Check” status that can be assigned to an intraoperation stepbefore moving to the next assembly step.

Defining Shop Floor Statuses
(N) WIP > Move Transactions > Shop Floor Statuses > Shop Floor Statuses

 
1. Enter an alphanumeric Status name.
For example, enter WIPHold to signify that shop floor assemblies are on WIP hold or, QAHold to signify that the shop floor assemblies are on quality assurance hold.

2. Enter a Status description.
Descriptions can be used to identify shop floor statuses on standard reports. They can be up to 240 characters of alpha numeric text.

3. Uncheck Allow Moves so that you can use this status to control move transactions. Allow Moves defaults to checked.

Assign Shop Floor Statuses
Shop floor statuses can be attached to WIP jobs in Assign Shop Floor Statuses form

2.3 Shop Floor Statuses

Shop floor statuses can be used to control shop floor movement transactions. You can define as many shop floor statuses as are required. Shop floor statuses can be assigned to the intraoperation steps of work in process routing operations. When assigned to an intraoperation step of an operation that is associated with a particular repetitive line and assembly, the status applies to all repetitive schedules building that assembly on that line.

Usage
You can control move transactions by assigning Shop Floor Statuses to intraoperation steps on the work in process routing. For example you may want to create a “Hold for Quality Check” status that can be assigned to an intraoperation stepbefore moving to the next assembly step.

Defining Shop Floor Statuses
(N) WIP > Move Transactions > Shop Floor Statuses > Shop Floor Statuses

 
1. Enter an alphanumeric Status name.
For example, enter WIPHold to signify that shop floor assemblies are on WIP hold or, QAHold to signify that the shop floor assemblies are on quality assurance hold.

2. Enter a Status description.
Descriptions can be used to identify shop floor statuses on standard reports. They can be up to 240 characters of alpha numeric text.

3. Uncheck Allow Moves so that you can use this status to control move transactions. Allow Moves defaults to checked.

Assign Shop Floor Statuses
Shop floor statuses can be attached to WIP jobs in Assign Shop Floor Statuses form

Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

2.1 Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

2.2 Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

2.1 Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

2.2 Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

2.1 Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

2.2 Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. You can assign schedule groups as you define and update jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

 
 
Build Sequencing
You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.
Schedule Groups
You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign that schedule group to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure.

Build Sequence
You can sequence jobs within a schedule group. For example, you can use sequences to prioritize, by customer, all jobs on a specific production line. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading.

Defining Labor Rates

You can add, delete, and update the effective date of the hourly labor rates for person–type resources (employees). You also can define multiple hourly labor rates for the same employee, as long as each rate has a different effective date.

If you use actual costing, the hourly labor rate rather than the standard rate is used to compute the actual cost of person–type resources charged to discrete jobs and repetitive schedules. You can enter an employee number when performing a person–type resource transaction in the Resource Transactions window or the Resource Transaction Open  Interface process. The employee’s most current hourly labor rate is used to compute the actual cost of the transaction.

 
You can define multiple hourly labor rates for the same employee as long as they have different effective dates. You can define a labor rate to the smallest currency denomination. For example, you can define a US dollar rate to the penny. You can only update or delete future labor rates.

2.4 Defining Labor Rates

You can add, delete, and update the effective date of the hourly labor rates for person–type resources (employees). You also can define multiple hourly labor rates for the same employee, as long as each rate has a different effective date.

If you use actual costing, the hourly labor rate rather than the standard rate is used to compute the actual cost of person–type resources charged to discrete jobs and repetitive schedules. You can enter an employee number when performing a person–type resource transaction in the Resource Transactions window or the Resource Transaction Open  Interface process. The employee’s most current hourly labor rate is used to compute the actual cost of the transaction.

 
You can define multiple hourly labor rates for the same employee as long as they have different effective dates. You can define a labor rate to the smallest currency denomination. For example, you can define a US dollar rate to the penny. You can only update or delete future labor rates.

Defining Labor Rates

You can add, delete, and update the effective date of the hourly labor rates for person–type resources (employees). You also can define multiple hourly labor rates for the same employee, as long as each rate has a different effective date.

If you use actual costing, the hourly labor rate rather than the standard rate is used to compute the actual cost of person–type resources charged to discrete jobs and repetitive schedules. You can enter an employee number when performing a person–type resource transaction in the Resource Transactions window or the Resource Transaction Open  Interface process. The employee’s most current hourly labor rate is used to compute the actual cost of the transaction.

 
You can define multiple hourly labor rates for the same employee as long as they have different effective dates. You can define a labor rate to the smallest currency denomination. For example, you can define a US dollar rate to the penny. You can only update or delete future labor rates.

2.4 Defining Labor Rates

You can add, delete, and update the effective date of the hourly labor rates for person–type resources (employees). You also can define multiple hourly labor rates for the same employee, as long as each rate has a different effective date.

If you use actual costing, the hourly labor rate rather than the standard rate is used to compute the actual cost of person–type resources charged to discrete jobs and repetitive schedules. You can enter an employee number when performing a person–type resource transaction in the Resource Transactions window or the Resource Transaction Open  Interface process. The employee’s most current hourly labor rate is used to compute the actual cost of the transaction.

 
You can define multiple hourly labor rates for the same employee as long as they have different effective dates. You can define a labor rate to the smallest currency denomination. For example, you can define a US dollar rate to the penny. You can only update or delete future labor rates.

Defining Production Lines

A production line describes a unique set of operations, departments, and/or manufacturing cells that produce one or more of your products.
  • You can associate production lines with repetitive assemblies, discrete jobs, flow routings, schedules, and work order-less completions.
  • You can define and update production lines. But you cannot delete production lines.
     
After deifing a production line, we can attach it to a JOB in schedule group, project tab.

 

2.1 Defining Production Lines

A production line describes a unique set of operations, departments, and/or manufacturing cells that produce one or more of your products.
  • You can associate production lines with repetitive assemblies, discrete jobs, flow routings, schedules, and work order-less completions.
  • You can define and update production lines. But you cannot delete production lines.
     
After deifing a production line, we can attach it to a JOB in schedule group, project tab.

 

Defining Production Lines

A production line describes a unique set of operations, departments, and/or manufacturing cells that produce one or more of your products.
  • You can associate production lines with repetitive assemblies, discrete jobs, flow routings, schedules, and work order-less completions.
  • You can define and update production lines. But you cannot delete production lines.
     
After deifing a production line, we can attach it to a JOB in schedule group, project tab.

 

2.1 Defining Production Lines

A production line describes a unique set of operations, departments, and/or manufacturing cells that produce one or more of your products.
  • You can associate production lines with repetitive assemblies, discrete jobs, flow routings, schedules, and work order-less completions.
  • You can define and update production lines. But you cannot delete production lines.
     
After deifing a production line, we can attach it to a JOB in schedule group, project tab.

 

Discrete Manufacturing

You can use Oracle Work in Process to produce assemblies in discrete batches, also known as discrete jobs.

Standard Versus Non–Standard Jobs
Standard discrete jobs control the material, resources, and operations required to build an assembly and collect its manufacturing cost. Non–standard discrete jobs control material and collect costs for miscellaneous manufacturing activity. They may or may not build an assembly. This type of activity can include rework, field service repair, upgrade, disassembly, maintenance, engineering prototypes, and other projects.

Discrete Versus Lot Based Jobs
A discrete job is a production order for the manufacture of a specific (discrete) quantity of an assembly, using a specific standard routing and operations. If you have Oracle Shop Floor Management installed, you can use lot based jobs in your manufacturing. A lot based job follows a network routing. Network routings provide flexibility in choosing the next operation which, in turn, determines the series of operations the job moves through.




1. Create Jobs
2. Issue Componets (Material and MOH)
3. Move transaction (Resource and OH)
4. Complete Jobs
5. Close Jobs

WIP Transactions

As shown in the below fig. in WIP we mainly do three types of transactions

  • 1. Component  Issue - Material transaction
  • 2. Move transaction 
  • 3. Resource transaction
  • 4. Shopfloor status update
  • 5. WIP job completion - Material transaction
With above transactions in WIP, you can:
- Maintain accurate supply and demand information
- Track and report inventory accurately
- Track activity costs
- Value work in process


Basics of Material transaction
  1. Component Pick Release
  2. Replenishment transaction
  3. Backflush Transaction
  4. WIP Component Issue
  5. WIP Component Return
  6. WIP Negative Component Issue
  7. WIP Negative Component Return
  8. WIP Assembly Completion
  9. WIP Assembly Return
WIP Assembly Completion
The JOB is completed and the fnished good is moved to the finished sub inventory
Inv valuation Dr @Cost of FG
                                   WIP Valuation Cr @Cost of FG

Accounting Summary in WIP
1. When component is issued the first transaction takes places and the accountings are
WIP Valuation A/C Dr
                              Inv Valuation A/C Cr

2. When we do the move transavtions - Resources, Overhead and OSPs are charged
WIP Resource Valuation A/C Dr
                                        Resource Absorption  A/C Cr

WIP  Overhead  Valuation  A/C Dr   
                                          Overhead  Absorption  A/C Cr

WIP OSP valuation A/C  Dr       
                                          Receiving  A/C Cr   
                                          Purchase Price Variance A/C  Dr/Cr

Scrap  A/C Dr   
                                            WIP valuation  A/C Cr


3. When the JOB is completed all the costs are relived in WIP
Organization  Material A/C Dr    
                            WIP Material Valuation A/C Cr     

Organization  Resource  A/C Dr    
                                 WIP  Resource  Valuation  A/C Cr    

Organization  Overhead  A/C Dr    
                                   WIP  Overhead  Valuation  A/C   Cr 


4. Following accounts 'll hit when the WIP job is closed
Dr      Material usage variance A/C
                                          Cr      WIP Material Valuation A/C


Dr     Resource effy. variance A/C
                                         Cr     WIP  Resource  Valuation  A/C  
              

Dr     Overhead  variance  A/C
                                        Cr     WIP  Overhead  Valuation  A/C

Component Issues/Backflush Transactions

An issue transaction is a material transaction to issue component items from inventory to work in process.  Issue transactions:
    - Fulfill WIP material requirements on jobs
    - Reduces inventory balances and valuation
    - Incur WIP costs and increase WIP valuation
    - Can be manual or automatic

An example of an automatic issue is a backflush transaction generated from an assembly completion.  It automatically issues component items into work in process from inventory.  In this section you will see how to do a manual issue transaction, also known as ‘Pushing’ material to a job.  Manual issue transactions are required to relieve inventory for items with a WIP supply type of Push.


Create a JOB in released status with 5 components with 5 differnt supply type
1. Assembly pull
2. Operation Pull
3. Push
4. Bulk
5. Supplier


CASE I:
Navigate to WIP issue
The component WIP Supply type PUSH would be available for transaction
(Only components with Supply type PUSH are avialable in WIP issue form for transaction)
If sufficient on Hand is not available for WIP material issue, following error 'll be shown
Now we can verify the Material issued in mterail requirements form
 

CASE II:
Navigate to Move transaction form and move the JOB from OP10 Queue to Run
Verify the issued quantity in material requirement form.
The components with Supply type Operational pull is isuued.
 
(Note : Above form in its format doesnot exist in apps. We hev superimposed the supply tab with quantities to show the supply type)
 
CASE III (Replenishment supply subinventory)
In case II we have seen that operation pull components are automatically backflushed when we do a move transaction in an operation. Similarly when we complete an assembly the components with supply type Assembly pull are backflushed.
If there is not sufficient quantities in backflash sub inventory (The subinventory from which backflush automatically happens, most of the time such sub inventories are given name like WIP, RIP or Stockfloor)
 


CASE III
In case II we have seen that operation pull components are automatically backflushed when we do a move transaction in an operation. Similarly when we complete an assembly the components with supply type Assembly pull are backflushed.
Complete few quantities the JOB and verify the material requirement changes
 
CASE 4:
Complete the JOB and see the final material requirement
 

The componets with supply type supplier and bulk are not issued and needs to be manually transacted.


Copleting the PROCESS
Check the WIP value summary

 

and Finally Close the JOB.

 

and Veify the WIP Summary Value once again.
Notice that there is not net activity and the difference bewteen costs incurred and costs relieved is taken care by variance a/c.

Lets consider the Material cost incurred and relived.
Item           Mat.Cost           Qty                WIP Supply Type
PUR001 -        40                   50                  Assembly Pull
PUR002 -        10                   100                Supplier
Rest of the items has mat cost zero.


As the item PUR002 has an WIP Supply type of supplier, it is not backflushed or pushed so it wont add any value to the cost of the finished good and a misc issue needs to be done to issue out these materials and that 'll hit the exepense account.


 

WIP Material Transaction

When you enter material transactions in the WIP Material Transactions window you must select one of the following transaction types:


 
Definitions
  • Component Pick Release You can select component requirements to issue to jobs and schedules on the Component Pick Release window. This window generates move orders. You can select items for discrete jobs, lot based jobs, repetitive schedules, and flow schedules. Each manufacturing mode has a distinct and individual window. You can also use a rules based system to determine a recommended source location for each component.
  • Replenishment transaction (Backflush transferl) is a material transaction to stage components in advance of backflushing. This ensures that materials are available for backflush transactions.
  • Backflush (op pull/assembly pull) is a material transaction to issue component items from inventory to work in process.
  • Comp. Issue transaction (push) is a material transaction to issue component items from inventory to work in process.
  • Job Completion Completing the WIP job and moving the finished good to the FG sub inventory.
  • Assembly Return Returing the finished good from FG back into the To Move operation on assembly line.
  • Comp. Return transaction is a material transaction to return components from WIP back to inventory. Return transactions increase WIP material requirements, inventory balances, and valuation, and decrease WIP valuation.
 
2 - Replenishment supply subinventory     
Replenishes the supply subinventories of Operation Pull or Assembly Pull supply type components. You can transfer components from a 'source' subinventory/locator to the supply subinventory/locator associated with the component specified. If you replenish components under lot, serial, or lot and serial number control, you must identify the lots and/or serial numbers that are used to replenish the supply subinventory/locator.
    This transaction is similar to a subinventory transfer in Oracle Inventory.
4.1 – WIP Component Issue
WIP valuation Dr @Cost of Raw Mat
                                Inv valuation Cr @Cost of Raw Mat.
Issue components from inventory to jobs to fulfill positive material requirements.
(If you issue components under lot, serial, or lot and serial number control, you must identify which lots and/or serial numbers to issue)

4.2 – WIP Neg Comp Issue

Issues components from jobs to inventory to fulfill negative material requirements.  When you issue components that have negative requirements, components are returned from the job to inventory. (If you return components under lot, serial, or lot and serial number control, you must identify the lots and/or serial numbers to return) Negative material requirements allow you to recover by–products from your manufacturing processes. 
By–Product Recovery
You can create negative material requirements to support the recovery of by–products and other reuseable or recoverable components.  Negative requirements are supplied instead of consumed by jobs.  For example, if you add negative material requirements to a non–standard discrete job that is tracking the disassembly of a completed assembly, the job supplies component materials rather than consuming them. Negative requirements are considered supply by the MRP planning process.  You can define negative requirement usage quantities when you assign components to bills of material in Oracle Bills of Material. Negative requirements can be assigned to lot, serial number, and lot and serial number controlled items.

7.1 – WIP Component Return
WIP component returns reverse WIP component issues. (If you return components under lot, serial, or serial number control, you must identify the lots and/or serial numbers to return) 

7.2 – WIP Neg Component Return
WIP negative component returns reverse WIP negative component issues. When you return components that have negative requirements, components are issued from inventory to the job. (If you issue components that are under lot, serial, or lot and serial number control, you must identify the lots and/or serial numbers to issue)  Negative material requirements allow you to recover by–products from your manufacturing processes.

OSP Cycle

1. Create an OSP Item

  • Inventory Tab:  Non Inventory, Non stockable, Non transactable, Reservable
  • Costing: Not eanbled, Non Asset
  • Purchasing: Purchased, Purchasable, OSP Item Enabled and Unit Type given. List Price shoule be Non Zero value.
 
 
2.1  Define a new resource as OSP and attch the above ITEM to it.

 
2.2  Attach the above resource to a department. You must attach a location with the department if the charge type PO Receipt is used.

 

2.3 Attach the OSP department and resource to the routing of the OSP item.

 
3.1 Create a WIP Job for the above item 

4.1 Req import process is automatically started.

4.2 Create a PO against the Requisition and receive it
 
Notes:
1. Run 'Requisition Import Exceptions Report' to find out the errors caused in requisition import.
2. Verify the finaccial options item validation org. System check the item attributes in that organization.
3. Item should be attached to a valid Inv and purchasing category.
4. The departement should be associated with a location (PO shippment location)
5. Purchasing option should have the ship to & bill to (defaults to the PO)
6. Req import option in purchasing should not be blank,
7.The accounting entries in OSP are
PO Receving
Receving Valuation A/C Dr
                                                 AP Accrual A/C Cr

Res Charge
WIP Resource A/C Dr
                                      OSP Resource Abosrption A/C Cr
When you create an OSP resource, Sytsem defaults the receving valuation account as the OSP Resource Abosrption. Dont change the value else your receiving valuation account will have an incorrect balance.

Creating Discrete Jobs

You can create discrete jobs in the following ways:

  • manually (both standard and non–standard discrete jobs).
  • manually from a simulation (standard discrete jobs only).
  • automatically using Oracle Master Scheduling/MRP and Oracle Supply Chain Planning to plan your standard discrete production, then using the Planner Workbench to implement your planned orders. automatically using Advanced Planning and Scheduling’s High Level Scheduling Engine to schedule jobs and import them into Work in Process.
  • automatically (standard discrete jobs only) from final assembly orders for specific customer configurations and/or standard assemble–to–order (ATO)/configure–to–order items.
  • using the Work Order Interface to import planned orders and updated planned order recommendations.

Planned Discrete Jobs
You can create planned orders and reschedule recommendations using the Planner Workbench in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. You can modify the due dates and quantities of planned orders, and also firm plan these orders. You can create new discrete jobs by implementing all or some planned orders.

When you create jobs using the Planner Workbench, you can specify the WIP accounting class. Accounting classes can be defaulted. If the job being created is for a lot controlled assembly, the WIP Default Lot Number Type parameter is used to determine whether lot numbers are assigned based on the job name or based on the Oracle Inventory lot number rules.

Discrete jobs created from planned orders use the planned order quantity as the default job quantity. The primary bill of materials and primary routings for the assemblies are used to create work in process bills and routings. Jobs created from planned orders are backward scheduled from the required completion date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Planning takes shrinkage rate, component yield, and safety stock into consideration in the planning process. Once you define the standard job, supply is calculated using the following formula:

available supply quantity = (MRP net quantity – quantity
completed – quantity scrapped) x 1 – item shrinkage rate)

You can also use the Planner Workbench to reschedule existing jobs.
For example, you can reschedule every assembly in the plan or you can reschedule only certain specific assemblies.
When you implement planned orders and create discrete jobs, Planning does not take into account the WIP:View Only Released ECOs profile option in the Personal Profile Values window. Oracle Advanced Planning provides a profile option enabling you to align Work in Process production with engineering changes for planning .

Kanban Replenishments
In a pull–based system, inventory items for a particular part or assembly area are replenished as soon as they are needed. When the items are needed, kanban cards in Oracle Inventory change their Supply Status to Empty, and Inventory generates production kanban replenishment request automatically.

  1. If the source type of the kanban card is Production, as opposed to Supplier or Inter–Org, the type of Work in Process Entity that is created is determined based on the assembly referenced by the kanban card per the following rules:
  2. If the lowest priority or primary routing of the assembly is a Flow routing, a Flow schedule is created. This is true even if the items Repetitive Planning attribute is set
  3. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is set, then a repetitive schedule is created.
  4. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is NOT set, then a discrete job is created Signals to create discrete jobs and repetitive schedules are processed by the WIP Mass Load program.

When discrete jobs and repetitive schedules are created in response to kanban replenishment signals, they are automatically loaded into the Work Order Interface and automatically processed. If the replenishment signal creates a discrete job, the kanban card is referenced on that job; however, if the replenishment signal creates a repetitive schedule, the kanban card is not referenced. Once the discrete job or repetitive schedule has been successfully loaded, the status of the kanban card is updated to In process.

When kanban replenishment jobs and schedules fail validation and processing, they are automatically deleted from the interface table. The reason for their failure is noted on the Job and Schedule Interface report, which is automatically printed each time the Mass Load program is run. When imported, non–kanban job and schedule information that fails validation or processing is marked. You can use the Pending Jobs and Schedules window to view, update, and resubmit this information.

Final Assembly Orders
You can automatically create final assembly orders for Assemble to Order (ATO) items entered in Oracle Order Management. These discrete job orders are created on a single job to single sales order delivery basis.

On the Sales Order window (which you open from the Discrete Jobs window in Work in Process), you also can associate discrete jobs for both standard items and ATO items with sales orders and thereby allocate production to specific customers. To determine the job start date, you schedule jobs created from final assembly orders backwards from the order due date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Work Order Interface
You can load planned orders, planned order update recommendations, and suggested repetitive schedules from any source — planning systems, order entry systems, finite scheduling packages, production line sequencing programs, spreadsheets, and even custom entry forms
— into the Work Order Interface. For example, if your plant directly feeds to your customer’s plant, you can take demands directly from your customer rather than waiting for the next MRP run thus reducing response time and eliminating unnecessary overhead.

You then use the Import Jobs and Schedules window to launch the WIP Mass Load program, which validates records in the Work Order Interface table and implements any imported records as new discrete jobs, updated discrete jobs, or pending repetitive schedules.

WIP Accounting Class Defaults
You can set up default WIP accounting classes at several levels:

  • at the category account level for discrete jobs and repetitive line/assembly associations
  • at the Default Discrete Class parameter class level for standard discrete jobs
  • at the project cost group level for project jobs
  •  

 

2.1 Creating Discrete Jobs

You can create discrete jobs in the following ways:

  • manually (both standard and non–standard discrete jobs).
  • manually from a simulation (standard discrete jobs only).
  • automatically using Oracle Master Scheduling/MRP and Oracle Supply Chain Planning to plan your standard discrete production, then using the Planner Workbench to implement your planned orders. automatically using Advanced Planning and Scheduling’s High Level Scheduling Engine to schedule jobs and import them into Work in Process.
  • automatically (standard discrete jobs only) from final assembly orders for specific customer configurations and/or standard assemble–to–order (ATO)/configure–to–order items.
  • using the Work Order Interface to import planned orders and updated planned order recommendations.

Planned Discrete Jobs
You can create planned orders and reschedule recommendations using the Planner Workbench in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. You can modify the due dates and quantities of planned orders, and also firm plan these orders. You can create new discrete jobs by implementing all or some planned orders.

When you create jobs using the Planner Workbench, you can specify the WIP accounting class. Accounting classes can be defaulted. If the job being created is for a lot controlled assembly, the WIP Default Lot Number Type parameter is used to determine whether lot numbers are assigned based on the job name or based on the Oracle Inventory lot number rules.

Discrete jobs created from planned orders use the planned order quantity as the default job quantity. The primary bill of materials and primary routings for the assemblies are used to create work in process bills and routings. Jobs created from planned orders are backward scheduled from the required completion date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Planning takes shrinkage rate, component yield, and safety stock into consideration in the planning process. Once you define the standard job, supply is calculated using the following formula:

available supply quantity = (MRP net quantity – quantity
completed – quantity scrapped) x 1 – item shrinkage rate)

You can also use the Planner Workbench to reschedule existing jobs.
For example, you can reschedule every assembly in the plan or you can reschedule only certain specific assemblies.
When you implement planned orders and create discrete jobs, Planning does not take into account the WIP:View Only Released ECOs profile option in the Personal Profile Values window. Oracle Advanced Planning provides a profile option enabling you to align Work in Process production with engineering changes for planning .

Kanban Replenishments
In a pull–based system, inventory items for a particular part or assembly area are replenished as soon as they are needed. When the items are needed, kanban cards in Oracle Inventory change their Supply Status to Empty, and Inventory generates production kanban replenishment request automatically.

  1. If the source type of the kanban card is Production, as opposed to Supplier or Inter–Org, the type of Work in Process Entity that is created is determined based on the assembly referenced by the kanban card per the following rules:
  2. If the lowest priority or primary routing of the assembly is a Flow routing, a Flow schedule is created. This is true even if the items Repetitive Planning attribute is set
  3. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is set, then a repetitive schedule is created.
  4. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is NOT set, then a discrete job is created Signals to create discrete jobs and repetitive schedules are processed by the WIP Mass Load program.

When discrete jobs and repetitive schedules are created in response to kanban replenishment signals, they are automatically loaded into the Work Order Interface and automatically processed. If the replenishment signal creates a discrete job, the kanban card is referenced on that job; however, if the replenishment signal creates a repetitive schedule, the kanban card is not referenced. Once the discrete job or repetitive schedule has been successfully loaded, the status of the kanban card is updated to In process.

When kanban replenishment jobs and schedules fail validation and processing, they are automatically deleted from the interface table. The reason for their failure is noted on the Job and Schedule Interface report, which is automatically printed each time the Mass Load program is run. When imported, non–kanban job and schedule information that fails validation or processing is marked. You can use the Pending Jobs and Schedules window to view, update, and resubmit this information.

Final Assembly Orders
You can automatically create final assembly orders for Assemble to Order (ATO) items entered in Oracle Order Management. These discrete job orders are created on a single job to single sales order delivery basis.

On the Sales Order window (which you open from the Discrete Jobs window in Work in Process), you also can associate discrete jobs for both standard items and ATO items with sales orders and thereby allocate production to specific customers. To determine the job start date, you schedule jobs created from final assembly orders backwards from the order due date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Work Order Interface
You can load planned orders, planned order update recommendations, and suggested repetitive schedules from any source — planning systems, order entry systems, finite scheduling packages, production line sequencing programs, spreadsheets, and even custom entry forms
— into the Work Order Interface. For example, if your plant directly feeds to your customer’s plant, you can take demands directly from your customer rather than waiting for the next MRP run thus reducing response time and eliminating unnecessary overhead.

You then use the Import Jobs and Schedules window to launch the WIP Mass Load program, which validates records in the Work Order Interface table and implements any imported records as new discrete jobs, updated discrete jobs, or pending repetitive schedules.

WIP Accounting Class Defaults
You can set up default WIP accounting classes at several levels:

  • at the category account level for discrete jobs and repetitive line/assembly associations
  • at the Default Discrete Class parameter class level for standard discrete jobs
  • at the project cost group level for project jobs
  •  

 

Creating Discrete Jobs

You can create discrete jobs in the following ways:

  • manually (both standard and non–standard discrete jobs).
  • manually from a simulation (standard discrete jobs only).
  • automatically using Oracle Master Scheduling/MRP and Oracle Supply Chain Planning to plan your standard discrete production, then using the Planner Workbench to implement your planned orders. automatically using Advanced Planning and Scheduling’s High Level Scheduling Engine to schedule jobs and import them into Work in Process.
  • automatically (standard discrete jobs only) from final assembly orders for specific customer configurations and/or standard assemble–to–order (ATO)/configure–to–order items.
  • using the Work Order Interface to import planned orders and updated planned order recommendations.

Planned Discrete Jobs
You can create planned orders and reschedule recommendations using the Planner Workbench in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. You can modify the due dates and quantities of planned orders, and also firm plan these orders. You can create new discrete jobs by implementing all or some planned orders.

When you create jobs using the Planner Workbench, you can specify the WIP accounting class. Accounting classes can be defaulted. If the job being created is for a lot controlled assembly, the WIP Default Lot Number Type parameter is used to determine whether lot numbers are assigned based on the job name or based on the Oracle Inventory lot number rules.

Discrete jobs created from planned orders use the planned order quantity as the default job quantity. The primary bill of materials and primary routings for the assemblies are used to create work in process bills and routings. Jobs created from planned orders are backward scheduled from the required completion date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Planning takes shrinkage rate, component yield, and safety stock into consideration in the planning process. Once you define the standard job, supply is calculated using the following formula:

available supply quantity = (MRP net quantity – quantity
completed – quantity scrapped) x 1 – item shrinkage rate)

You can also use the Planner Workbench to reschedule existing jobs.
For example, you can reschedule every assembly in the plan or you can reschedule only certain specific assemblies.
When you implement planned orders and create discrete jobs, Planning does not take into account the WIP:View Only Released ECOs profile option in the Personal Profile Values window. Oracle Advanced Planning provides a profile option enabling you to align Work in Process production with engineering changes for planning .

Kanban Replenishments
In a pull–based system, inventory items for a particular part or assembly area are replenished as soon as they are needed. When the items are needed, kanban cards in Oracle Inventory change their Supply Status to Empty, and Inventory generates production kanban replenishment request automatically.

  1. If the source type of the kanban card is Production, as opposed to Supplier or Inter–Org, the type of Work in Process Entity that is created is determined based on the assembly referenced by the kanban card per the following rules:
  2. If the lowest priority or primary routing of the assembly is a Flow routing, a Flow schedule is created. This is true even if the items Repetitive Planning attribute is set
  3. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is set, then a repetitive schedule is created.
  4. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is NOT set, then a discrete job is created Signals to create discrete jobs and repetitive schedules are processed by the WIP Mass Load program.

When discrete jobs and repetitive schedules are created in response to kanban replenishment signals, they are automatically loaded into the Work Order Interface and automatically processed. If the replenishment signal creates a discrete job, the kanban card is referenced on that job; however, if the replenishment signal creates a repetitive schedule, the kanban card is not referenced. Once the discrete job or repetitive schedule has been successfully loaded, the status of the kanban card is updated to In process.

When kanban replenishment jobs and schedules fail validation and processing, they are automatically deleted from the interface table. The reason for their failure is noted on the Job and Schedule Interface report, which is automatically printed each time the Mass Load program is run. When imported, non–kanban job and schedule information that fails validation or processing is marked. You can use the Pending Jobs and Schedules window to view, update, and resubmit this information.

Final Assembly Orders
You can automatically create final assembly orders for Assemble to Order (ATO) items entered in Oracle Order Management. These discrete job orders are created on a single job to single sales order delivery basis.

On the Sales Order window (which you open from the Discrete Jobs window in Work in Process), you also can associate discrete jobs for both standard items and ATO items with sales orders and thereby allocate production to specific customers. To determine the job start date, you schedule jobs created from final assembly orders backwards from the order due date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Work Order Interface
You can load planned orders, planned order update recommendations, and suggested repetitive schedules from any source — planning systems, order entry systems, finite scheduling packages, production line sequencing programs, spreadsheets, and even custom entry forms
— into the Work Order Interface. For example, if your plant directly feeds to your customer’s plant, you can take demands directly from your customer rather than waiting for the next MRP run thus reducing response time and eliminating unnecessary overhead.

You then use the Import Jobs and Schedules window to launch the WIP Mass Load program, which validates records in the Work Order Interface table and implements any imported records as new discrete jobs, updated discrete jobs, or pending repetitive schedules.

WIP Accounting Class Defaults
You can set up default WIP accounting classes at several levels:

  • at the category account level for discrete jobs and repetitive line/assembly associations
  • at the Default Discrete Class parameter class level for standard discrete jobs
  • at the project cost group level for project jobs
  •  

 

2.1 Creating Discrete Jobs

You can create discrete jobs in the following ways:

  • manually (both standard and non–standard discrete jobs).
  • manually from a simulation (standard discrete jobs only).
  • automatically using Oracle Master Scheduling/MRP and Oracle Supply Chain Planning to plan your standard discrete production, then using the Planner Workbench to implement your planned orders. automatically using Advanced Planning and Scheduling’s High Level Scheduling Engine to schedule jobs and import them into Work in Process.
  • automatically (standard discrete jobs only) from final assembly orders for specific customer configurations and/or standard assemble–to–order (ATO)/configure–to–order items.
  • using the Work Order Interface to import planned orders and updated planned order recommendations.

Planned Discrete Jobs
You can create planned orders and reschedule recommendations using the Planner Workbench in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. You can modify the due dates and quantities of planned orders, and also firm plan these orders. You can create new discrete jobs by implementing all or some planned orders.

When you create jobs using the Planner Workbench, you can specify the WIP accounting class. Accounting classes can be defaulted. If the job being created is for a lot controlled assembly, the WIP Default Lot Number Type parameter is used to determine whether lot numbers are assigned based on the job name or based on the Oracle Inventory lot number rules.

Discrete jobs created from planned orders use the planned order quantity as the default job quantity. The primary bill of materials and primary routings for the assemblies are used to create work in process bills and routings. Jobs created from planned orders are backward scheduled from the required completion date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Planning takes shrinkage rate, component yield, and safety stock into consideration in the planning process. Once you define the standard job, supply is calculated using the following formula:

available supply quantity = (MRP net quantity – quantity
completed – quantity scrapped) x 1 – item shrinkage rate)

You can also use the Planner Workbench to reschedule existing jobs.
For example, you can reschedule every assembly in the plan or you can reschedule only certain specific assemblies.
When you implement planned orders and create discrete jobs, Planning does not take into account the WIP:View Only Released ECOs profile option in the Personal Profile Values window. Oracle Advanced Planning provides a profile option enabling you to align Work in Process production with engineering changes for planning .

Kanban Replenishments
In a pull–based system, inventory items for a particular part or assembly area are replenished as soon as they are needed. When the items are needed, kanban cards in Oracle Inventory change their Supply Status to Empty, and Inventory generates production kanban replenishment request automatically.

  1. If the source type of the kanban card is Production, as opposed to Supplier or Inter–Org, the type of Work in Process Entity that is created is determined based on the assembly referenced by the kanban card per the following rules:
  2. If the lowest priority or primary routing of the assembly is a Flow routing, a Flow schedule is created. This is true even if the items Repetitive Planning attribute is set
  3. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is set, then a repetitive schedule is created.
  4. If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is NOT set, then a discrete job is created Signals to create discrete jobs and repetitive schedules are processed by the WIP Mass Load program.

When discrete jobs and repetitive schedules are created in response to kanban replenishment signals, they are automatically loaded into the Work Order Interface and automatically processed. If the replenishment signal creates a discrete job, the kanban card is referenced on that job; however, if the replenishment signal creates a repetitive schedule, the kanban card is not referenced. Once the discrete job or repetitive schedule has been successfully loaded, the status of the kanban card is updated to In process.

When kanban replenishment jobs and schedules fail validation and processing, they are automatically deleted from the interface table. The reason for their failure is noted on the Job and Schedule Interface report, which is automatically printed each time the Mass Load program is run. When imported, non–kanban job and schedule information that fails validation or processing is marked. You can use the Pending Jobs and Schedules window to view, update, and resubmit this information.

Final Assembly Orders
You can automatically create final assembly orders for Assemble to Order (ATO) items entered in Oracle Order Management. These discrete job orders are created on a single job to single sales order delivery basis.

On the Sales Order window (which you open from the Discrete Jobs window in Work in Process), you also can associate discrete jobs for both standard items and ATO items with sales orders and thereby allocate production to specific customers. To determine the job start date, you schedule jobs created from final assembly orders backwards from the order due date. The calculated start date is used to determine the bill and routing revisions and revision dates.

Work Order Interface
You can load planned orders, planned order update recommendations, and suggested repetitive schedules from any source — planning systems, order entry systems, finite scheduling packages, production line sequencing programs, spreadsheets, and even custom entry forms
— into the Work Order Interface. For example, if your plant directly feeds to your customer’s plant, you can take demands directly from your customer rather than waiting for the next MRP run thus reducing response time and eliminating unnecessary overhead.

You then use the Import Jobs and Schedules window to launch the WIP Mass Load program, which validates records in the Work Order Interface table and implements any imported records as new discrete jobs, updated discrete jobs, or pending repetitive schedules.

WIP Accounting Class Defaults
You can set up default WIP accounting classes at several levels:

  • at the category account level for discrete jobs and repetitive line/assembly associations
  • at the Default Discrete Class parameter class level for standard discrete jobs
  • at the project cost group level for project jobs
  •  

 

Defining Discrete Jobs Manually

You can manually define standard, non–standard, and project jobs. You can assign bills and routings to standard discrete jobs to create material requirements, schedule operations, and create resource requirements.
You can optionally assign alternate bills of material and/or alternate routings when you define standard discrete jobs (however, neither bills of material nor routings are required). You also can assign bill of material references and/or routing references to non–standard discrete jobs to create material requirements, schedule operations, and create resource requirements.
Further, you can attach illustrative or explanatory files (in the form of text, images, word processing documents, spreadsheets, video, and so on) to discrete jobs.
After saving a job, use the Component and Operations buttons to immediately view the details of the job, including its material requirements, operations, and operation material and resource requirements.

Default job names can only be automatically generated by the automatic sequence generator if a prefix has been specified for the WIP:Discrete Job Prefix profile option.



1. Enter or generate the Job name.
You can generate a default Job name by choosing Apply Default Job Name from the Tools menu or by simply pressing the tab key. If you do enter the job name, it must be unique and alphanumeric.

2. Select the job Type, either Standard or Non–Standard.

3. If defining a standard discrete job, select the job Assembly. The assembly is the item you are building. If a primary bill of
material, primary routing, or both exist for this assembly, they are defaulted.
You cannot select an assembly that has a primary routing that is Flow related. If you do, a warning is displayed and you are prompted to enter another routing designator.

Assemblies are optional for non–standard discrete jobs, however, you must enter them for non–standard discrete jobs with routings if you want to track shop floor move and resource transactions.

4. Select the accounting Class.
If a default discrete WIP accounting class can be found, it is used. For non–standard jobs, you can select any active Asset
Non–standard or Expense Non–standard accounting class.

5. Select the job Status.
When you define a job, its status defaults to Unreleased but can be changed to Released or On Hold.

Check the Firm check box to firm your job. You cannot firm a non–standard discrete job.
Firming a discrete job prevents MRP from suggesting rescheduling and replanning recommendations when changes to supply or demand occur. If replanning is required, the MRP planning process creates new jobs to cover the new demand.

6. Enter the job Start quantity.
Standard discrete jobs must have a start quantity greater than zero. When you enter a start quantity for jobs with bills and routings, the component material requirements, department schedules, resource load, and job start and end dates are all determined automatically.
For non–standard jobs, if you enter a start quantity of 0 and specify a bill of material reference, the corresponding bill is exploded but material requirements equal to 0 are created. To perform move and completion transactions for a non–standard job, the start quantity must be greater than zero.

Enter the MRP Net quantity.
The MRP net quantity is the number of assemblies that MRP considers as supply on the scheduled completion date.
For standard and non–standard discrete jobs with assemblies, the MRP net quantity is derived from the job start quantity. For non–standard discrete jobs without assemblies, the default is zero.

1.4 Profile Option Descriptions

The following information provides you with a description of each Work in Process profile option and its values.

TP: WIP: Concurrent Message Level
Determines the level of detail reported in the move transaction concurrent log file during move transaction validation and processing. Available values are listed below:
Reports errors only.
Reports processing activities and errors.
Reports and time stamps processing activities and errors.

TP:WIP:Completion Transactions First Field
Determines which field the cursor defaults to when you first enter the Completion Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transactions First Field

Determines which field the cursor defaults to when you first enter the Move Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transaction Quantity Default
Indicates if and how move transaction quantities are defaulted.
Available values are listed below:
None :  No transaction quantity is defaulted.
Minimum Transfer Quantity : When you perform a move transaction, the transaction quantity defaults to the minimum
transfer quantity if the minimum transfer quantity is less than or equal to the available quantity. If the minimum transfer quantity is greater that the available quantity, and the available quantity is not zero, then the available quantity is defaulted.
Available Quantity : When you perform a move transaction, if the available quantity is not zero, the transaction quantity defaults to the available quantity

TP: WIP: Work Order–less Default Completion
Determines the default for the Scheduled flag in the Work Order–less Completions window. Set this profile according to your business requirements. The default can be overridden. Available values are listed below:
Scheduled: The Schedule flag defaults to checked. Use this option if most of your work order–less completions are based upon flow schedules generated by the Line Scheduling Workbench.
Unscheduled: The Scheduled flag defaults to unchecked. Use this option if most of your work order–less completions
are manually entered and not based upon flow schedules generated by the Line Scheduling Workbench.

WIP: Default Job Start Date
Determines whether the start dates for jobs default to the current date and time or not at all when defining jobs in the Discrete Jobs window. The options are Yes or No.

WIP: Discrete Job Prefix
Specifies the job prefix to use when autogenerating job names in the Discrete Jobs, Simulate Discrete Jobs, Import Jobs and Schedules, and AutoCreate windows in Work in Process, and in the Planner Workbench window in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. It is also used when autogenerating the numbers for flow schedules created in the Work Order–less Completions window.

Work in Process concatenates this prefix with a value from the sequence WIP_JOB_NUMBER_S to create a default discrete job name.

WIP:Enable Outside Processing Workflows
Determines whether or not outside processing workflows are enabled.
Yes: All outside processing workflows are enabled.
No: outside processing workflows are enabled.

Profile Option Descriptions

The following information provides you with a description of each Work in Process profile option and its values.

TP: WIP: Concurrent Message Level
Determines the level of detail reported in the move transaction concurrent log file during move transaction validation and processing. Available values are listed below:
Reports errors only.
Reports processing activities and errors.
Reports and time stamps processing activities and errors.

TP:WIP:Completion Transactions First Field
Determines which field the cursor defaults to when you first enter the Completion Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transactions First Field

Determines which field the cursor defaults to when you first enter the Move Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transaction Quantity Default
Indicates if and how move transaction quantities are defaulted.
Available values are listed below:
None :  No transaction quantity is defaulted.
Minimum Transfer Quantity : When you perform a move transaction, the transaction quantity defaults to the minimum
transfer quantity if the minimum transfer quantity is less than or equal to the available quantity. If the minimum transfer quantity is greater that the available quantity, and the available quantity is not zero, then the available quantity is defaulted.
Available Quantity : When you perform a move transaction, if the available quantity is not zero, the transaction quantity defaults to the available quantity

TP: WIP: Work Order–less Default Completion
Determines the default for the Scheduled flag in the Work Order–less Completions window. Set this profile according to your business requirements. The default can be overridden. Available values are listed below:
Scheduled: The Schedule flag defaults to checked. Use this option if most of your work order–less completions are based upon flow schedules generated by the Line Scheduling Workbench.
Unscheduled: The Scheduled flag defaults to unchecked. Use this option if most of your work order–less completions
are manually entered and not based upon flow schedules generated by the Line Scheduling Workbench.

WIP: Default Job Start Date
Determines whether the start dates for jobs default to the current date and time or not at all when defining jobs in the Discrete Jobs window. The options are Yes or No.

WIP: Discrete Job Prefix
Specifies the job prefix to use when autogenerating job names in the Discrete Jobs, Simulate Discrete Jobs, Import Jobs and Schedules, and AutoCreate windows in Work in Process, and in the Planner Workbench window in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. It is also used when autogenerating the numbers for flow schedules created in the Work Order–less Completions window.

Work in Process concatenates this prefix with a value from the sequence WIP_JOB_NUMBER_S to create a default discrete job name.

WIP:Enable Outside Processing Workflows
Determines whether or not outside processing workflows are enabled.
Yes: All outside processing workflows are enabled.
No: outside processing workflows are enabled.

1.4 Profile Option Descriptions

The following information provides you with a description of each Work in Process profile option and its values.

TP: WIP: Concurrent Message Level
Determines the level of detail reported in the move transaction concurrent log file during move transaction validation and processing. Available values are listed below:
Reports errors only.
Reports processing activities and errors.
Reports and time stamps processing activities and errors.

TP:WIP:Completion Transactions First Field
Determines which field the cursor defaults to when you first enter the Completion Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transactions First Field

Determines which field the cursor defaults to when you first enter the Move Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transaction Quantity Default
Indicates if and how move transaction quantities are defaulted.
Available values are listed below:
None :  No transaction quantity is defaulted.
Minimum Transfer Quantity : When you perform a move transaction, the transaction quantity defaults to the minimum
transfer quantity if the minimum transfer quantity is less than or equal to the available quantity. If the minimum transfer quantity is greater that the available quantity, and the available quantity is not zero, then the available quantity is defaulted.
Available Quantity : When you perform a move transaction, if the available quantity is not zero, the transaction quantity defaults to the available quantity

TP: WIP: Work Order–less Default Completion
Determines the default for the Scheduled flag in the Work Order–less Completions window. Set this profile according to your business requirements. The default can be overridden. Available values are listed below:
Scheduled: The Schedule flag defaults to checked. Use this option if most of your work order–less completions are based upon flow schedules generated by the Line Scheduling Workbench.
Unscheduled: The Scheduled flag defaults to unchecked. Use this option if most of your work order–less completions
are manually entered and not based upon flow schedules generated by the Line Scheduling Workbench.

WIP: Default Job Start Date
Determines whether the start dates for jobs default to the current date and time or not at all when defining jobs in the Discrete Jobs window. The options are Yes or No.

WIP: Discrete Job Prefix
Specifies the job prefix to use when autogenerating job names in the Discrete Jobs, Simulate Discrete Jobs, Import Jobs and Schedules, and AutoCreate windows in Work in Process, and in the Planner Workbench window in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. It is also used when autogenerating the numbers for flow schedules created in the Work Order–less Completions window.

Work in Process concatenates this prefix with a value from the sequence WIP_JOB_NUMBER_S to create a default discrete job name.

WIP:Enable Outside Processing Workflows
Determines whether or not outside processing workflows are enabled.
Yes: All outside processing workflows are enabled.
No: outside processing workflows are enabled.

Profile Option Descriptions

The following information provides you with a description of each Work in Process profile option and its values.

TP: WIP: Concurrent Message Level
Determines the level of detail reported in the move transaction concurrent log file during move transaction validation and processing. Available values are listed below:
Reports errors only.
Reports processing activities and errors.
Reports and time stamps processing activities and errors.

TP:WIP:Completion Transactions First Field
Determines which field the cursor defaults to when you first enter the Completion Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transactions First Field

Determines which field the cursor defaults to when you first enter the Move Transactions window. Set this option based on your predominant manufacturing environment: assemble–to–order, project or discrete job, or repetitive.
The available first field values are Line, Assembly, Job, or Sales Order.
You can navigate to another field to override the default.
Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job.

TP: WIP: Move Transaction Quantity Default
Indicates if and how move transaction quantities are defaulted.
Available values are listed below:
None :  No transaction quantity is defaulted.
Minimum Transfer Quantity : When you perform a move transaction, the transaction quantity defaults to the minimum
transfer quantity if the minimum transfer quantity is less than or equal to the available quantity. If the minimum transfer quantity is greater that the available quantity, and the available quantity is not zero, then the available quantity is defaulted.
Available Quantity : When you perform a move transaction, if the available quantity is not zero, the transaction quantity defaults to the available quantity

TP: WIP: Work Order–less Default Completion
Determines the default for the Scheduled flag in the Work Order–less Completions window. Set this profile according to your business requirements. The default can be overridden. Available values are listed below:
Scheduled: The Schedule flag defaults to checked. Use this option if most of your work order–less completions are based upon flow schedules generated by the Line Scheduling Workbench.
Unscheduled: The Scheduled flag defaults to unchecked. Use this option if most of your work order–less completions
are manually entered and not based upon flow schedules generated by the Line Scheduling Workbench.

WIP: Default Job Start Date
Determines whether the start dates for jobs default to the current date and time or not at all when defining jobs in the Discrete Jobs window. The options are Yes or No.

WIP: Discrete Job Prefix
Specifies the job prefix to use when autogenerating job names in the Discrete Jobs, Simulate Discrete Jobs, Import Jobs and Schedules, and AutoCreate windows in Work in Process, and in the Planner Workbench window in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. It is also used when autogenerating the numbers for flow schedules created in the Work Order–less Completions window.

Work in Process concatenates this prefix with a value from the sequence WIP_JOB_NUMBER_S to create a default discrete job name.

WIP:Enable Outside Processing Workflows
Determines whether or not outside processing workflows are enabled.
Yes: All outside processing workflows are enabled.
No: outside processing workflows are enabled.

Security Functions

Function security is the mechanism by which user access to applications functionality is controlled. System administrators
administer function security.
Access to Work in Process functionality is controlled either by menus and form functions/subfunctions or by form function parameters.

Form Function Parameters
Some Work in Process forms are coded to accept particular parameters.
Parameters can be used to limit access to form elements such as:

  •  Window options
  •  Tools menu options
  •  Buttons
The syntax for entering form function parameters is:
PARAMETER = VALUE
For example, to enter a negative Boolean parameter value for the WIP_WIPDJMDF_CLOSE function, you would enter the following in the Parameters field in the Form Functions window:
UNCLOSE = N
The following table describes the Work in Process form function parameters. All values are either Y (Yes) or N (No). A detailed description of each form function parameter follows the table:
 
Define Discrete Jobs: Close Discrete Jobs
Determines whether you can unclose jobs using the Close Discrete Jobs window. When this function security parameter (UNCLOSE) is added and set to N, the Unclose option does not appear in the Tools menu.
The default for this option is Y.

Move Transactions: Allow Skipping Over No Move Statuses
Determines whether you can override ‘no move’ shop floor statuses when performing a move transaction. If the WIP Allow Moves Over No Move Shop Floor Statuses parameter is set to N and this function security parameter (OVERRIDE_NO_MOVE_NO_SKIP) is set to Y, you can move assemblies over no move shop floor statuses.
The default for this option is N.

Move Transactions: No Completion Transactions
Determines whether you can perform assembly completion and return move transactions using the Move Transactions window. When this function security parameter (ALLOW_CMP) is set to N, the Complete and Return options do not appear in the Transaction Type region of the Move Transactions window.

Move Transactions: No Resource Transactions
Determines whether you can initiate a manual resource transaction from the Move Transactions window. When this function security parameter (RESOURCE_TXNS) is set to N, the Resources button does not appear in the Move Transactions window. The default for this option is Y.

Completion Transactions: No Final Completions

Determines whether you can perform WIP final completions in an average costing organization. When this function security parameter (ALLOW_FINAL_ COMPLETIONS) is set to N, the Final Complete check box does not appear in the Completion Transactions window.

Function Security
A form function invokes an Oracle Forms form. A non–form function (subfunction) is a securable subset of a form’s functionality: in other words, a function executed from within a form. When the subfunction associated with a certain functionality is included in a menu, that functionality is enabled.

The following table describes the subfunction used in Work in Process. A detailed description of each function (subfunction) follows the table:

Allow Overcompletions
You can complete more assemblies than have been defined for discrete jobs and repetitive schedule.

Material Control

You can control and monitor which materials are used and how they flow from inventory to discrete jobs and repetitive schedules and from jobs and schedules to inventory.

When you create jobs and repetitive schedules that have bills of material, routings, or both, material requirements for the appropriate components are automatically created. These requirements (demands) are considered ’open’ until they are fulfilled.
The MRP planning process and available to promise calculations include open requirements as demand but do not formally allocate them to their parent jobs and repetitive schedules.

Open material requirements are satisfied when components are issued and backflushed. Material shortages occur when insufficient inventory exists to cover open requirements. The MRP planning process reports current and projected material shortages and develops a plan to satisfy those shortages.

Negative Requirements/By–Product Recovery

You can use negative material requirements to recover by–products or other reusable components. Negative requirements are supplied instead of consumed by jobs and schedules. For example, if you add negative material requirements to a
non–standard discrete job that is tracking the disassembly of a completed part, the job supplies component materials rather than consuming them. Negative requirements are considered supply by the MRP planning process.

You can define negative requirement usage quantities when you assign components to bills of material in Oracle Bills of Material. Negative requirements can be assigned to lot, serial number, and lot and serial number controlled items.

Available–to–Promise Materials
You can view available–to–promise (ATP) status of components as you define, simulate, and view discrete jobs and as you view repetitive schedules.

WIP Shortage Reporting
The Discrete Job Shortage and Repetitive Schedule Shortage Reports list shortages or open requirements for jobs and repetitive schedules based on requirement date. You can optionally include quantities in non–nettable subinventories in the on–hand quantities displayed on these reports. You can also use these report to view bulk and supplier component requirements.
The View Material Requirements window can be used to view the requirements for a component across jobs and schedules. You can view quantities required and issued for each component.

Material Control Process Diagram

Adding and Updating Material Requirements

You can add material requirements to discrete jobs and repetitive schedules with statuses of Unreleased, Released, On Hold, and Complete.
Note: You can also add material requirements to jobs and schedules by issuing components not required by the job or
schedule.

To add or update material requirements Navigate to the Material Requirements window.

 

1.1 Select the Job or repetitive Line and Assembly.
You can only select a discrete job or a repetitive line and assembly for a repetitive schedule if the job or schedule has a status of Unreleased, Released, On Hold, or Complete.

1.2. From the Main tabbed region of the Material Requirements region, select the Component to update or add.
You can add items with Push, Assembly Pull, Operation Pull, Bulk, Phantom, and Supplier supply types. If you add Phantom items, their supply types are changed to Push. Supply types are also changed to Push if you add Assembly Pull items to jobs or schedules without bills of material. Similarly, if you add Operation Pull items to jobs or schedules without routings, their supply types are changed to Assembly Pull.

In the case of non–standard discrete jobs, you can add the primary assembly as a component. In other words, the job assembly requires itself. This is useful when you use non–standard jobs to manage rework or disassembly.

2.1. If adding a component, select the Operation Sequence number.
You can only add components at existing operations. The operation sequence identifies where the material is required.
If you add a requirement to a job or schedule without a routing, the system displays 1 as the default operation sequence. This value cannot be updated.

2.2. In the Quantities tabbed region, enter the Per Assembly Quantity or the Required Quantity for the component.
If you are adding a component, the per assembly quantity defaults to 1 and the required quantity is derived from the job or schedule quantity and displayed in the component’s primary UOM. It can be updated. If you update the per assembly quantity, the required quantity is automatically calculated. Conversely if you update the required quantity, the per assembly quantity calculated. You can enter a decimal value, such as 1.25, for both the per assembly and the required quantity. You can also enter a required or per assembly quantity of zero.

2.3. In the Supply tabbed region, select the Supply Type.
When you add components, the supply type specified for the item in Oracle Inventory is normally defaulted. If the item does not have a supply type, the supply type defaults to Push. Supply type selection is restricted based on the type and makeup of the job or schedule. You cannot, for example, change the supply type of a Push component to Assembly Pull if the job or schedule has no routing.

2.4. If the component’s supply type is Assembly Pull or Operation Pull, you must select the Supply Subinventory, and if required by the supply subinventory, the supply Locator.
 

2.5. Check the MRP Net check box to include material requirements as demand in the calculation of net requirements.
If a negative quantity for a standard discrete job or repetitive schedule is entered, this check box is disabled. For non standard–jobs with a negative quantity, the MRP check box is enabled. However, Oracle planning nets the negative
requirement as supply rather than demand.

When initially creating non–standard discrete jobs, this flag is unchecked. You must manually mark the check box for components to be considered as demand by Oracle planning applications.

Deleting Material Requirements

You can delete material requirements from Unreleased discrete jobs and repetitive schedules. You cannot delete material requirements that have been issued even if their due quantity is 0. You cannot delete material requirements if any transactions gave been made for a particular component.
To delete material requirements:
1. Navigate to the Material Requirements window.
2. Select the Job or Line and Assembly.
3. If you select a line and assembly, choose the repetitive schedule by selecting the first unit start date of that schedule. If you have selected a discrete job, the system displays the scheduled start date of the job.
4. Choose the Find button to populate the Material Requirements region.
5. In the Material Requirements region, select the Component.
6. Choose Delete Record from the Edit Menu.
7. Save your work.

Component Pick Release

Component picking, obtaining requirements for specific jobs and schedules, is the process of moving items from source locations and issuing them to work orders. In previous versions of Oracle Work in Process, items were issued from locations specified for each component on the bill of material. Now you can also use a rules based system to determine a recommended source location for each component. The features for component picking include:

  • The Component Pick Release window is used to select requirements and create move orders for discrete jobs, lot based jobs, repetitive schedules, and flow schedules.
  • Move orders are created for picked items. Move orders are requests for the movement of material within an organization. They enable the replenishment of material within a warehouse or manufacturing shop floor.
  • The source for material picked is based on Oracle Inventory allocation rules entered on the Picking Rules window. Or, if Oracle Warehouse Management is installed, rules based picking recommendations.
  • Rules based picking uses the Warehouse Management Rules engine. This employs user defined rules to recommend locations to pick from, and specific items to pick.
  • The destination for picked material depends on the supply type. It can be a staging area, or directly to a job or schedule.
  • You have the option to release picking tasks at the time of the pick release. Or you can choose another time to release.

Job and Schedule Values for Picking
Depending on the job or schedule type, specific values control which records display on the Component Pick window, and how material issues are transacted:

Discrete Jobs
  • Status must be Released or Complete – Charges Allowed
  • Material is defined at the operation and autocharge is enabled
  • Item status attribute in Oracle Inventory is Transactable
Lot Based Jobs
  • Status must be Released or Complete – Charges Allowed
  • Components are picked based on the network routing
  •  Item status attribute in Oracle Inventory is Transactable
  •  Move order quantities are calculated as assemblies per operation multiplied by components per assembly, or: The sum of all the quantities in each intraoperation step (Queue, Run, To Move, Reject and Scrap) Multiplied by the component’s quantity per assembly
Flow Schedules
  • Material must be defined at a valid line operation
  • Status must be Open
  • Item status attribute in Oracle Inventory is Transactable
  • Move orders are generated when all quantities for the flow schedule components can be filled
  • Components must be a supply type of Push
Note: In flow schedules, material and resources are specified in the events associated with the line operation. If components are not assigned to specific events, or events are not assigned to line operations – the value in the Line Operation field is 1. This indicates an unassigned line operation for that material requirement.

Repetitive Schedules
  • Status must be Released or Complete – Charges Allowed
  • Material is defined at the operation and autocharge is enabled
  • Item status attribute in Oracle Inventory is Transactable
  • The Days of Supply value is used to calculate the quantity of components to pick.
Setup
Indicate if operation pull and assembly pull supply type components are included in picking.
Mark the Release Backflush Components check box on the WIP Parameter window. This check box is located on the Backflush Defaults tabbed region.

Material Destination
Material destination is automated with move orders in the component picking process; it depends on the supply type:
Operation Pull and Assembly Pull
Components are moved from the supply subinventory to a specific staging area. The staging area location is defined on the Bills of Material window, the Subinventory field (and applicable Locator) in the Material Control tabbed region.
If not defined, the default value on the Backflush Defaults tab of the WIP Parameters window is used.

Push
Push transactions are performed automatically by the system.
Components are moved directly to the job or schedule. Specifically, the destination is defined as the department, job, and operation combination. The source of the material is the subinventory (and locator, if applicable) recommended by the sourcing rules. You can override this recommendation and enter another location as the source of the material.

Push items with predefined staging subinventory You can define a staging subinventory on the bill of material if you
do not want the push transaction automatically generated. If the staging subinventory is defined on the bill of material, the
components are considered the same way as pull items – they are moved to that staging area. However, another step must be performed: you will have to manually move the parts to the job or schedule.

Component Issues and Returns

You can issue components from inventory to jobs and repetitive schedules and return issued components from jobs and schedules to inventory using the WIP Material Transactions window. There are two issue and return options available from this window: All Material and Specific Component.


Push and Pull Components
You can issue and return both push and pull components. You can ’push’ components from inventory to specific job and repetitive schedule operations. A component’s supply type determines how it is supplied to a job or schedule.

Negative Component Issues and Returns
You can issue components to satisfy negative job and schedule requirements. When you issue negative requirement components, the components are returned from the job or schedule to inventory. You can reverse negative component issues with negative component returns. When you return components that have negative requirements, the components are issued from inventory to the job or repetitive schedule.

Negative Inventory Balances
You can set the Allow Negative Balances Parameter in Oracle Inventory so that the inventory balances of items can be driven negative. If this parameter is set, a warning message is displayed to notify you that balances are about to be driven negative. You can continue with the transaction or stop it and fix the condition.

Requirement Quantities
You can issue partial requirement quantities. You can also over–issue requirements. Material that is required, but not issued, is considered an open requirement.

Ad Hoc Requirements
You can issue and return components that do not appear as job or schedule material requirements using the ’Specific Component’ option. When you issue or return components using this option, the system determines if the item is a material requirement for the job or schedule. If the item is not a material requirement, is a backflush component, or is not required at the operation sequence a warning message is displayed, but you can continue with the transaction. Components added in this manner are commonly referred to as ’ad hoc’ components.

Bulk, Supplier, and Phantom Components

You can issue Bulk, Supplier, and Phantom supply type items, which do not normally appear as requirements in the WIP Material Transactions window, using the ’Specific Component’ option.

Serial Number Validations
You can issue and return component items that are under lot, serial number, or both lot and serial number control. Available serial number records are restricted for use when issuing a serialized item, returning it to stock, and then to a different job. At the time of completion, serialized components are available from stock if they have the following values set in the Serial Numbers window in Oracle Inventory:
Component Issues and Negative Component Returns -  State value: Resides in stores.
Component Returns and Negative Component Issue -  State value: Defined but not used.
This is restricted to serial numbers that were previously issued or negative returns–for the same job or schedule that you are
performing the component return or negative component issue.

Supply Subinventory and Locator Replenishment

You can replenish supply subinventories and locators to replace components that you have issued to jobs or repetitive schedules and to insure a source of material for backflush transactions. You can replenish components for an entire job or repetitive schedule, or for a specified number of days of repetitive production. Specifically you can do the following:

 

1. Replenish supply subinventories and locators by transferring components from any subinventory and locator into the supply subinventory and locator for the job or repetitive schedule.
This method works well if you stage the pull components one job or repetitive assembly at a time. For example, if you wanted to replenish the supply subinventory and locator for all the operation pull material requirements on a job, you would:
– Generate the Discrete Job Pick List report for pull components. This report identifies material requirements,
subinventories and locators with available inventory, and supply subinventories and locators where you backflush
from. You would then pick the components using the pick list and transfer them into the appropriate supply subinventories and locators. Repetitive replenishment works the same way except you would replenish for an assembly for a number of days instead of for a job.
– You can also use the Component Pick Release window to select material using rules based picking.

2. Replenish supply subinventories and locators for higher level assemblies by completing lower level assemblies into the next
level’s supply subinventory and locator.

This method works well if your plant is set up with feeder lines that physically flow to consuming lines. For example, assume
you build a subassembly on a feeder line that ends at the consumption point of the subassembly into the higher level
assembly. You can set the completion subinventory and locator on the subassembly to be the supply subinventory and locator of the subassembly on the next level bill of material. Then, as you complete the subassembly into its completion subinventory and locator using the Completion Transactions window, Move Transactions window, or the Inventory Transaction Interface, you automatically replenish the supply subinventory and locator on the next level bill of material.

3. Transfer components from any subinventory and locator into the supply subinventory and locator in Oracle Inventory using subinventory transfers to replenish supply subinventories and locators.
This method works well when you are replenishing for more than one job or one assembly on a line. For example, you can
run a Repetitive Pick List report for all assemblies on a line to identify all the operation and assembly pull requirements for all
repetitive schedules on the line regardless of their parent assembly. You can then use this consolidated pick list to pick the
components. Then you can transact the transfer of the components into the supply subinventories and locators. You can
also use the Component Pick Release window to select material using rules based picking.

4. Requisition material automatically to replenish supply subinventories in Oracle Inventory using internal requisitions.
This method works well when you have consistent material flows within your plant and can estimate reasonable floor stock
inventory levels. For example, you can set a minimum quantity for a component item in a supply subinventory. As you reduce the balance in the supply subinventory due to push issues or backflushes, Oracle Inventory automatically generates a
requisition when the balance for the component reaches the minimum quantity. Then when you fulfill the internal
requisition, you replenish the supply subinventory.

5. Receive components directly from your supplier into supply subinventories and locators in Oracle Purchasing.
This method works well if you have a smooth flow of raw materials from your suppliers and have space on the shop floor
to inventory components you receive. For example, if you purchase a component that is consumed out of a supply
subinventory, you could receive that component directly into that supply subinventory and locator using the Enter Receipts
window in Oracle Purchasing. This method avoids a subsequent subinventory transfer of the component thereby saving both time and a transaction.

Backflush Transactions

Backflush transactions ’pull’ components with Operation Pull and Assembly Pull supply types from inventory onto jobs and repetitive schedules. Backflush transactions can be launched by:

  • Completing assemblies at operations using the Move Transactions window
  • Moving and completing assemblies into inventory using the Move Transactions window
  • Completing assemblies into inventory using the Completion Transactions window
  • Receiving assemblies from an outside processing operation using the Oracle Purchasing, Enter Receipts window.
Move transactions imported through the Open Move Transaction Interface can also create backflush transactions. Transactions imported through the Oracle Inventory, Inventory Transactions Interface can also create backflush transactions.

Additional Information: Backflushing reduces the number of manual material transactions required to process the discrete jobs and repetitive schedules.

Reverse Backflush Transactions
You can reverse backflush transactions and automatically return backflushed components back to inventory. For example, pull components that are backflushed as you move assemblies to the next intraoperation step in a routing are automatically returned to inventory if you move assemblies to a previous step in the routing. Reverse backflush transactions can be created as you do the following:
  • reverse operation completion transactions using the Move Transactions window
  • return completed assemblies from inventory to jobs and schedules using the Completion Transactions
  • move and return assemblies from inventory to jobs and schedules using the Move Transactions window
  • return or correct transaction receipts in the Enter Returns or Enter Corrections windows in Oracle Purchasing.
Move transactions imported through the Oracle Work in Process Open Move Transaction Interface can also reverse backflush transactions as can return transactions imported through the Inventory Transaction Interface.
Note: You can, if necessary, issue and return pull components to and from jobs and schedules to inventory using the ’Specific Component’ option in WIP Material Transactions window

Revision Control
For component items under revision control, the system always defaults the revision based on the item’s current revision as of the date of the transaction

Backflush Transaction Rules

The following rules are enforced when performing backflush transactions:
  • an enabled default supply subinventory and, if required by the subinventory, locator must be defined for the component.
  • routing references must be specified for non–standard discrete jobs.
  • the component item must be transactable.
  • the subinventory you are backflushing from must be an asset subinventory if the Oracle Inventory Allow Expense to Asset
  • Transfer profile option is set to No.
  • backflush quantities that are calculated as decimal values, must be at least five decimal places in order to create the backflush transaction
  • yield calculations are based on exact requirements, rather than rounded values
Backflush Supply Subinventories and Locators
Supply subinventories and locators can be defined at the item or bill of material component level. If they are not defined, the system uses the supply subinventory and locator specified by the WIP Backflush Supply Subinventory and Locator Parameters when components are backflushed.
To ensure adequate supply for backflush transactions, you can replenish supply subinventories and locators as required

Negative Inventory Balances during Backflushing
You can use the following two Oracle Inventory settings to determine whether or not inventory balances can be negative:
  •  Allow Negative Balances parameter: you use this parameter to specify whether or not negative inventory balances are allowed.
  • Override Negative for Backflush profile option: you use this profile option to override a No setting on the Allow Negative Balances parameter during backflush transactions. This allows backflush transactions to drive the inventory negative even though the organization does not allow negative balances on any other types of transactions.
The only exception is when the component that you are backflushing is under lot, serial, or lot and serial number control. In this case, you will not be able to complete the backflush transaction unless you select a subinventory and locator that contains a sufficient quantity of valid lot and/or serial numbered items.

Assembly Completions and Returns

You can complete assemblies from Discrete jobs and Repetitive schedules into inventory, and you can return completed assemblies from inventory to jobs and repetitive schedules. You also can complete a greater quantity than the job or schedule start quantity (over–complete) into inventory, as long as it is within the tolerance level set. Further, on Repetitive schedules and non–standard Discrete jobs, you also can return more assemblies than were completed.

Assemblies can be completed and returned using the Completion Transactions and the Move Transactions windows. You can also import assembly completion and return transactions through the Inventory Transaction Interface in Oracle Inventory.

Completion Quantities
Completing assemblies from a job or schedule with a routing reduces the assembly quantity in the To move intraoperation step of the last operation sequence and increases the job or schedule completed quantity.

Return Quantities
Returning assemblies to a job or schedule with a routing, increases the assembly quantity in the To move intraoperation step of the last operation sequence and decreases the job or schedule complete quantity.

Alternate Units of Measure
You can complete and return assemblies in their alternate unit of measure. If you enter an alternate unit of measure for the item, the transaction quantity is converted using the conversion information you specified when you defined the unit of measure in Oracle Inventory.
You can change this quantity if desired.

Lot and Serial Number Control
You must assign a lot or serial number if the assembly is under lot, serial number, or lot and serial number control. For discrete jobs, the lot number you specified when you defined the job as the default displays.

If you are completing assemblies that have lot controlled Assembly Pull components and the WIP Backflush Lot Selection parameter is set to Manual, you must manually select which lots to backflush. If you are completing assemblies that have serial controlled or lot and serial controlled components, you must manually select which lots and/or serial numbers to backflush.

Revision Control
When you complete assemblies under revision control, the revision defaults based on the assembly revision of the job or repetitive schedule. For assemblies under revision control, the bill revision is completed from the job or the earliest released repetitive schedule. If there is no bill revision on the job or repetitive schedule, but the assembly is under revision control, the assemblies’ current revision is completed as defined in Oracle Inventory.

Completion Subinventory and Locator
When you complete assemblies, the completion subinventory defaults from the job or repetitive line/assembly association. For subassemblies, the completion subinventory can be the supply subinventory for higher level assemblies, for final assemblies or finished goods the completion subinventory can be finished goods inventory. You can change the default completion subinventory as you complete assemblies.

If you have set your organization, subinventory, or item controls to require locators, you must also enter locator as you complete assemblies.

Final Assembly Orders Completion
Reservations are automatically transferred from the job to the subinventory and locator as you complete assemblies from final assembly orders. Reservations are automatically transferred based on sales order line delivery due dates. You can override the automatic transfer. When assemblies are returned to a final assembly order, you must enter the sales order line and delivery information so that the system knows which specific reservations to transfer back from inventory.

Completions into License Plate Numbers
If Oracle Warehouse Management is installed, you can use License Plate Number functionality for tracking completions. License plate numbers are unique identifiers for containers in the supply chain. You can perform assembly completions and work order–less completions into license plate numbers. Multi–level nesting enables containers to be packed within another container.. The container’s genealogy provides content and transaction history for each license plate.
Note: LPN completions are supported only in standard cost organizations

Label Printing at Completion
Label printing capabilities are available at the time of completion in the Completion Transactions and Work Order–less Completions windows.
This functionality enables you to create labels for shipping, order management, manufacturing, and other types of information. Labels are created by selecting a format type and setup in Oracle Inventory – and using a third–party label printing system. If Oracle Warehouse Management is installed, you can set up compliance labeling using bar
code specifications and symbol content. This creates customer specific labels to comply with your customer’s requirements.

If collection plans exist for the line operation, you can enter quality data within the Flow Workstation, and print labels for the quality plan at the first operation or subsequent operations.

Discrete Workstation

The Discrete Workstation provides you with a single window to obtain critical production information and perform common shop floor transactions. The workstation displays information by department or for a resource, and it lists all of the job operations for immediate and future dispatch at that department or resource.

You can view broad information, such as the utilization, efficiency, productivity, and load on the resources within a department or on a specific resource across all departments. You also can obtain detailed component and resource information on each individual job scheduled for the department or resource. You can perform move, completion, and other common transactions directly on the workstation’s tabs, or open their corresponding Work in Process windows directly from the workstation. There is also a link to Oracle Project Contracts records associated with specific jobs.

The Discrete Workstation can record and track discrete production in organizations enabled for Oracle Shopfloor Management. You can use all the capabilities of monitoring and transaction work on discrete jobs in a mixed mode organization where discrete and lot based jobs are both used.

The Discrete Workstation window is composed of two panes. The left pane displays the navigational tree. The right pane displays one or more tabs of detailed information that correspond to the branch or tab that you select from the tree.


Navigational Tree
The workstation’s left pane contains its navigational structure, which displays a hierarchical listing of the workstation contents. Since its structure is analogous to a tree with branches, it is referred to as the workstation tree.
  • The tree displays four branches or levels of information. When you select a branch (the branch is highlighted), information relevant to that branch is displayed on tabs in the right pane of the workstation.
The first, topmost branch on the Discrete Workstation tree displays information for the department or the resource that you selected when you launched the workstation. Listed below it are its two main branches:
1. The Immediate Dispatch List branch, which displays all of the job operations that are ready to be worked on in the department or by the resource (there is a quantity of assemblies in its queue).
2. The Upstream Dispatch List branch, which displays all of the job operations that are to be worked on in the department or by the resource in the near future (there is a quantity of assemblies ready to be moved in the previous operation).
Expanding any of the individual job operation branches under either main branch displays two additional branches, the components and resources branches for that job.
  • Branch Naming Conventions :The branch names displayed on the Discrete Workstation are automatically generated by the system. They contain the name of thejob (which you created when you defined the job in the Discrete Jobs window), and the number of the operation, separated by a colon. For example: BIKE_Assy1:20 is the BIKE_Assy1 job at operation 20.
  • The information on the tree is always current, as jobs are completed – they are automatically removed from the tree. You can update the display at any time by choosing the Refresh tool.
  • You can choose to view the information on the workstation tree in Vertical (the default), Interleaved (horizontal), or Org Chart (organization chart) format. These choices are available through tools on the toolbar, or as menu selections under the View menu.
Tabbed Regions
The workstation’s right pane displays one or more tabs of detailed information pertaining to the branch that you selected from the tree. The information is displayed either in tables, on lists, pictorially, or on graphs, so that you can quickly assess the status of the job. Tabs may also have buttons that enable you to:
  • Perform common transactions directly from the tab, such as issuing components, performing assembly moves, or charging resources. Open the WIP Material Transactions, Move Transactions, and Resource Transactions forms directly from the workstation .Obtain attachments previously appended to a job, such as drawings and instructions
  • View proerties, Assembly moves,Component shortages, Time Charges
Launching the workstation
The Discrete Workstation provides you with production information on the jobs assigned to a particular department or resource. In order to launch the workstation, you must first select the department or the department and the resource whose jobs you want to view.
  • If you want to view all of the job operations scheduled to be worked on in a department, you select only the  epartment, then launch the workstation.
  • If you want to view the job operations that are assigned to a resource associated with a specific department, you select the department and the resource, then launch the workstation.
  • If you want to view a different department or resource, you must close the workstation, and launch it again, choosing a new department and resource from the workstation startup window.

Work in Process Costing

Oracle Work in Process provides a complete cost system to track and report your production costs.

WIP Accounting Classes
You use WIP accounting classes to establish your valuation and variance accounts. You can enter different accounts for each cost element within a WIP accounting class for maximum elemental account visibility. You can also enter the same account for more than one cost element. If you are assign the same account to more than one cost element, you can choose to have the values of these cost elements summarized before being transferred to General Ledger.

Multiple Cost Elements
Through the multiple cost elements (material, material overhead, resource, outside processing, and overhead) that you assign to your accounting classes, the system can track all your production costs to the correct valuation and variance accounts.

Costing Methods
All Oracle costing methods support Oracle Work in Process. However, you can only cost repetitive schedules using standard costs.

Job Costs
You can cost standard and non–standard asset discrete production by job. You can report job costs on a period–to–date and cumulative–to–date basis.

Project Costs
If you are using Oracle Project Manufacturing Costing, you can cost jobs by project. Project jobs can be specific to a single contract or a group of contracts for a specific customer.

Period Costs
You can cost and report your repetitive and non–standard expense production by period.

Repetitive Assembly and Line Costs
You can track your repetitive production costs by assembly on a line so you do not have to review your costs by individual repetitive schedule.  You can also track repetitive costs by assembly across lines or by line so you can compare costs for your production lines.

Transaction Based Costs
You can track and report costs through the various stages of production. The system calculates all costs and reports move, issue, resource, overhead, completion, scrap, period close, and job close transaction costs.

Resource Charging
You can charge resources automatically or manually.

Overhead Charging
You can charge overhead automatically based on resource value charges, resource charges, or operation completions.
Fixed and Variable Resource, Outside Processing and Overhead Charging You can set up resources, outside processing, and overheads with a basis of Lot for fixed charges per job or schedule, such as setup and teardown. You can use a basis of Item for resources, outside processing, and overheads that vary based on the job or repetitive schedule quantity.

Flexible Resource, Outside Processing, and Overhead Absorption You can assign separate absorption accounts by sub–element, such as individual resources, outside processing resources, and overheads. As you charge resources, outside processing, and overheads, work in process valuation automatically absorbs your payroll, accounts payable accruals, and overhead cost pools. At period end, you can compare absorbed amounts with actual costs incurred in your general ledger
cost pools and accounts.

Actual Labor Charging
You can charge resources at standard resource rates, standard employee rates, or actual rates.

Actual Purchase Price Charging
You can charge outside resources at predefined or actual purchase prices.

Period Close
When you close an accounting period, period close costs are calculated. The system costs and transfers all production costs by account to Oracle Financial products. You can transfer in summary and detail depending on your Oracle Inventory option.
Variances You can track and report previous level usage variances for materials and this level efficiency variances for resources and overheads. The system calculates standard cost adjustment variances when the standard cost update is run.
Valuation Reporting The system can provides complete valuation reporting including current balances, period to date charges, and cumulative to date charges. You can also report your work in process balances by cost element and level.

Work in Process Costs

You use standard and non–standard discrete jobs, project jobs, repetitive schedules, and flow schedules to collect the costs of production. For standard and non–standard discrete jobs, you value and report work in process costs based on jobs. For project jobs, you value work in process costs based on the projects that jobs are associated with. For repetitive schedules, you value and report work in process costs based on assemblies on a line in a period, not on specific repetitive schedules.

You can cost standard discrete jobs, non standard discrete jobs, project jobs, and flow schedules in average costing  organizations. You can cost repetitive schedules in standard costing organizations only. Costing methods are assigned in the Organization Parameters window in Oracle Inventory.

The following table summarize which costing methods can be used with which manufacturing methods.

Manufacturing Standard Cost Transactions

The following cost transactions can occur when Oracle Work in Process is installed:

  1. Component Issue and Return Transactions
  2. Move Transactions
  3. Resource Charges
  4. Outside Processing Charges
  5. Overhead Charges
  6. Assembly Scrap Transactions
  7. Assembly Completion Transactions
  8. Job Close Transactions
  9. Period Close Transactions
  10. Work in Process Cost Update Transactions
Component Issue and Return Transactions
Issue transactions increase the work in process valuation and decrease the inventory valuation. The accounting entries for issue transactions are:
Account                                    Debit     Credit
WIP accounting class valuation accounts     XX
            Subinventory elemental accounts           XX


The accounting entries for return transactions are:
Account                                    Debit     Credit
Subinventory elemental accounts    XX
   WIP accounting class valuation accounts     XX

Subinventory accounts are defined in the Define Subinventories window in Oracle Inventory. WIP elemental accounts are defined in the WIP Accounting Classes window in Work in Process.

Move Transactions
A move transaction moves assemblies within an operation, such as from Queue to Run, or from one operation to the next. Move transactions can automatically launch operation completion backflushing and charge resources and overheads. You can perform move transactions using the Move Transactions window, Open Move Transaction Interface window, or the Enter
Receipts window in Purchasing.

Backflush Material Transactions
With backflushing, you issue component material used in an assembly or subassembly by exploding the bills of material, and then multiplying by the number of assemblies produced. Move transactions can create operation pull backflush material transactions that issue component material from designated WIP supply subinventories and locators to a job or repetitive schedule. For backflush components under lot or serial number control, you assign the lot or serial numbers during the move transaction. When you move backward in a routing, Work in Process automatically reverses operation pull backflush transactions. The accounting entries for move transactions are:

Account                                              Debit         Credit
WIP accounting class valuation accounts     XX
         Subinventory elemental accounts                      XX

The accounting entries for return transactions are:
Account                                              Debit         Credit
Subinventory elemental accounts             XX
       WIP accounting class valuation accounts               XX

Moved Based Resource Charging
As the assemblies you build pass through the operations on their routings, move transactions charge all pre–assigned resources with an auto–charge type of WIP Move at their standard rate. You can charge resources based upon a fixed amount per item moved in an operation (Item basis) or based upon a fixed lot charge per item moved in an operation (Lot basis). For resources with a basis of Lot, Work in Process automatically charges the lot cost upon completion of the first assembly in the operation.

You can also enter manual resource transactions associated with a move, or independent of any moves. You can manually charge resources to a job and repetitive schedule provided the job and repetitive schedule has a routing. You can also transact resources through the Open Resource Transaction Interface.

Resource Charges

WIP supports four resource autocharging methods: Manual,WIP Move,PO Move,and PO Receipt.You can charge resources at an actual rate. You can also charge resource overheads automatically as you charge resources.

WIP Move Resource Charges
You can automatically charge resources at their standard rate to a job or repetitive schedule when you perform a move transaction using either the Move Transactions window or the Open Move Transaction Interface. When you move  assemblies from the queue or run intraoperation steps forward to the to move, reject, or scrap intraoperation steps, or to the next operation, WIP charges all pre-assigned resources with an charge type of WIP Moveat their standard rates.

For resources with a basis of item, WIP automatically charges the resource's usage rate or amount multiplied by the resource's standard cost upon completion of each assembly in the operation. For resources with a basis of lot, WIP automatically charges the resource's usage rate or amount multiplied by the resource's standard cost upon completion of the first assembly in the operation.

You can undo the WIP move resource charges automatically by moving the assemblies from queue or run of your current operation to queue or run of any prior operation, or by moving the assemblies from the to move, reject, or scrap intraoperation steps backward to the queue or run intraoperation steps of the same operation, or to any intraoperation step of any prior operation.

WIP applies WIP Move resource transactions to multiple repetitive schedules on a line based on how the assemblies being moved are allocated. WIP allocates moves across multiple repetitive schedules based on a first in, first out basis.

Manual Resource Charges
You can charge manual resources associated with a move transaction or independent of any moves. Manual resource transactions require you to enter the actual resource units applied rather than autocharging the resource's usage rate or amount based on the move quantity. You can charge resources using that resource's unit of measure or any valid alternate. You can manually charge resources to a job or repetitive schedule provided that the job or repetitive schedule has a routing.

If you use the Move Transactions window to perform moves and manual resource transactions at the same time, then WIP displays all pre-assigned manual resources with an charge type of manual assigned to the operations completed in the move. If the resource is a person-type resource, you can enter an employee number.

In addition to the resources that appear, you can manually charge any resource to a job or repetitive schedule, even if you have not previously assigned the resource to an operation in the job or repetitive schedule. You can also manually charge resources to an operation added ad hoc by entering any resource defined for the department associated with the operation. WIP applies manual resource transactions to the first open repetitive schedule on the line.

You can correct or undo manual resource transactions by entering negative resource units worked.

Costing Resource Charges at Resource Standard
Resource charges increase WIP valuation. Here are the accounting entries for resource transactions:

Costing Labor Charges at Actual
You can charge labor charges at actual in two ways. You can enter an actual rate for the employee using the Open Resource Transaction Interface or when you define employee rates. Here are the accounting entries for labor charges using an actual or employee rate for a resource for which charge standard rate is turned off:

Any difference between the total labor charged at actual and the standard labor amount is recognized as an efficiency variance at period close.
If the Standard Rates check box is selected and you enter an actual rate for a resource, then the system charges the job or repetitive schedule at standard. If Autocharge is set to Manual and actual rates and quantities are recorded, then a rate variance is recognized immediately for any rate difference. Any quantity difference is recognized as an efficiency variance at period close. Here are the accounting entries for the actual labor charges:

Overhead Charges

Move Based Overhead Charging
WIP automatically charges appropriate overhead costs as you move assemblies through the shop floor. You can charge overheads directly based on move transactions or based on resource charges. For overheads charged based on move transactions with a basis of item, WIP automatically charges overheads upon completion of each assembly in the operation. WIP automatically reverses these charges during a backward move transaction.

For overheads based on move transactions with a basis of lot, WIP automatically charges overheads upon completion of the first assembly in the operation. WIP automatically reverses these charges during a backward move transaction if it results in zero net assemblies completed in the operation.

Resource Based Overhead Charging
WIP automatically charges appropriate overhead costs as you charge resources. You can charge overheads based on resource units or value. WIP automatically reverses overhead charges when you reverse the underlying resource charge.


Assembly Scrap Transactions

You can move partially completed assemblies that you consider unrecoverable to the scrap intraoperation step of that operation. If necessary, you can recover assemblies from scrap by moving them to another intraoperation step. By moving into the scrap intraoperation step, you can effectively isolate good assemblies from bad.

WIP considers a move into the scrap intraoperation step from the queue or run of the same operation as an operation completion, and thus updates operation completion information, backflushes components, and charges resource and overhead costs according to the elemental cost setup. You can also move assemblies back to the scrap intraoperation step of the previous operation for queue or run if no work has been completed at the current operation.

Costing Assembly Scrap Transactions
When you define WIP parameters, you can specify whether moves into the scrap intraoperation step require a scrap account. If you enter a scrap account or alias when you move assemblies into scrap, then the scrap account is debited and the job or repetitive schedule elemental accounts for the standard cost of the assembly through the scrap operation are credited. This removes the cost of the scrapped assemblies from the job or repetitive schedule. If you do not enter a scrap account or select an alias, then the cost of the scrap remains in the job or schedule until job or period close. If you recover assemblies from scrap, then the scrap account is credited and the job or repetitive schedule elemental accounts for the standard cost of this assembly through this operation are debited. Here are the accounting entries for scrap transactions:

Assembly Completion Transactions

Use the Completion Transactions window, Move Transactions window, and Inventory Transaction Interface to move completed assemblies from WIP into subinventories. Completion transactions relieve the valuation account of the accounting class and
charge the subinventory accounts (for example, finished goods) based upon the assembly's elemental cost structure.

Overcompletions
If you have overcompleted a job, it is not necessary to change the job quantity. However, if you are overcompleting assemblies associated with lot based resources and overheads, these resources and overheads are over-relieved from WIP.

Costing Assembly Completion Transactions
Completions decrease WIP valuation and increase inventory valuation at standard costs. Here are the accounting entries for completion transactions:

 
Earning Assembly Material Overhead on Completion
You can assign overheads based on item, lot or total value basis. For standard discrete jobs and repetitive schedules, you can earn these overheads as you complete assemblies from WIP to inventory.
Here are the the accounting entries for material overhead on completion transactions for standard discrete jobs and repetitive schedules:

Account                                                        Debit       Credit
Subinventory material overhead account              XX          -
 Inventory material overhead absorption account    -           XX

Use non-standard expense jobs for such activities as repair and maintenance. Use non-standard asset jobs to upgrade assemblies, for teardown, and to prototype production. Non-standard discrete jobs do not earn overhead on completion. Because you have already earned overhead to produce the assemblies as you are repairing or reworking, WIP prevents you from double earning material overhead on these assemblies.
Here are the accounting entries for material overhead on completion transactions for non-standard expense and non-standard asset jobs:

Account                                                      Debit         Credit
Subinventory material overhead account             XX            -
 WIP accounting class material overhead account   -             XX

Note: This accounting entry does not indicate that the jobs are earning material overhead, but rather that material overhead already in the job from a previous level is being credited. Unlike average costing, non-standard discrete jobs do not earn overhead on completion in standard costing.

Job Close Transactions

Until you close a job or change the status of the job to Complete - No Charges, you can make material, resource, and scrap charges to the job. Closing a discrete job prevents any further activity on the job.

Costing Job Close Transactions
Closing a job calculates final costs and variances. The actual close date that you specify determines the accounting period that WIP uses to recognize variances. You can back date the close to a prior open period if desired.

The close process writes off the balances remaining in the WIP elemental valuation accounts to the elemental variance accounts that you defined by accounting class, leaving a zero balance remaining in the closed job. If there is a positive balance in the job at the end of the close, here are the accounting entries for a job close:

Account                                                        Debit       Credit
WIP accounting class variance accounts                XX           -
WIP accounting class valuation accounts                -            XX

Period Close Transactions - Standard Costing

The period close process in Inventory recognizes variances for non-standard expense jobs and repetitive schedules. It also transfers the WIP period costs to the general ledger.

Costing Nonstandard Expense Job Period Close Transactions
You can close discrete jobs and recognize variances for non-standard expense jobs at any time. In addition, the period close process automatically recognizes variances on all non-standard expense job charges incurred during the period. Therefore, open non-standard expense jobs have zero WIP accounting balances at the start of a new period.
If there is a positive balance in the job at the end of the period, here are the accounting entries for nonstandard expense jobs at period close:

Account                                                        Debit       Credit
WIP accounting class variance accounts                XX             -
  WIP accounting class valuation accounts               -              XX


Costing Repetitive Schedule Period Close Transactions
You do not close a repetitive schedule. However, you do recognize variances on a period basis that result in zero WIP accounting balances at the start of the new period. You should check your transactions and balances using the Repetitive Value Report before you close a period.

When you define WIP parameters, you can specify which repetitive schedule variances that you recognize when you close an accounting period. You can either recognize variances for all repetitive schedules when you close an accounting period, or recognize variances for those repetitive schedules with statuses of either Complete - No Charges or Cancelled.

Assuming positive balances in the repetitive schedules at the end of the period, here are the accounting entries for repetitive schedules at period close:

Account                                                        Debit       Credit
WIP accounting class variance accounts                XX            -
    WIP accounting class valuation accounts            -             XX

Work in Process Standard Cost Update Transactions

The standard cost update process revalues standard and non-standard asset discrete jobs and updates pending costs to frozen standard costs. Repetitive schedules and non-standard expense jobs do not get revalued by the cost update.
The cost update creates accounting transactions by job and cost element valuation account. Each standard and non-standard asset discrete job is updated using the following formula:

Standard cost update adjustment = [new costs in (material, resource, outside processing, and overhead charges) - new costs out (scrap and assembly completion charges)] - [old costs in (material, resource, outside processing, and overhead charges) - old costs out (scrap and assembly completion charges)]

If the result of the cost update is an increase in the standard cost of the job, here are the accounting entries for a cost update transaction:

Account                                                         Debit       Credit
WIP accounting class valuation accounts                XX           -
  WIP Standard cost adjustment account               -           XX

If the result of the cost update is a decrease in the standard cost of the job, here are  the accounting entries for a cost update transaction:

Account                                                         Debit       Credit
WIP Standard cost adjustment account                 XX          -
  WIP accounting class valuation accounts                 -          XX

When the cost update occurs for open jobs, standards and WIP balances are revalued according to the new standard, thus retaining relief variances incurred up to the date of the update.

Outside Processing Charges

WIP automatically creates resource transactions at the standard or actual rate for all outside processing resources with an charge type of PO Receipt or PO Move when you receive assemblies from an outside processing operation back into WIP, using the Enter Receipts window in Purchasing. For outside processing resources with an charge type of PO Move, WIP also performs a move of the assemblies from the queue or run intraoperation step of your outside processing operation into the queue intraoperation step of your next operation or into the to move intraoperation step if the outside processing operation is the last operation on your routing.

If you assigned internal resources to an outside operation with an charge type of manual, then use the Move Transactions window or the Open Resource Transaction Interface to charges these resources. If you return assemblies to the supplier, then WIP automatically reverses the charges to all automatic resources associated with the operation. You must manually reverse all manual resource charges using the Move Transactions window.

For outside processing resources with an charge type of PO Move, WIP automatically moves the assemblies from the queue intraoperation step of the operation immediately following the outside processing operation into the queue intraoperation step of your outside processing operation.

If the outside processing operation is the last operation on your routing, then WIP automatically moves the assemblies from the to move intraoperation step to the queue intraoperation step. WIP applies PO Move resource transactions to multiple repetitive schedules on a line based on how the assemblies being moved are allocated. WIP allocates moves across multiple repetitive schedules based on a first in, first out basis. WIP applies PO Receipt resource transactions to the first open  repetitive schedule on the line.

Costing Outside Processing Charges at Standard
When you receive the assembly from the supplier, Purchasing sends the resource charges to WIP at either standard cost or actual purchase order price, depending upon how you specified the standard rate for the outside processing resource.
If the Standard Rates option is enabled for the outside processing resource being charged, then the application charges WIP at the standard rate and creates a purchase price variance for the difference between the standard rate and the purchase order price. Here are the accounting entries for outside processing items:

Account                                                                                  Debit        Credit
WIP accounting class outside processing valuation account               XX              -

Purchase price variance account (Debit when the   
actual rate is greater than the standard rate. Credit when       XX             XX            
the actual rate is less than the standard rate.)

Organization Receiving account                                             -              XX

Any quantity or usage difference is recognized as an outside processing efficiency variance at period close.
The accounting entries for return to supplier for outside processing are:

Account                                                                 Debit           Credit
Organization Receiving account                                   XX                 -
  Purchase price variance   account
  (Debit when actual rate is less than
  the standard rate. Credit when the                           XX               XX
  actual rate is greater than the standard
  rate.)

   WIP accounting class outside processing valuation      -                 XX
   account

Costing Outside Processing Charges at Actual Purchase Order Price
If the Standard Rates option is disabled for the outside processing resource being charged, then the system charges WIP the purchase order price and does not create a purchase price variance.
Here are the accounting transactions for outside processing charges at purchase order price:

Account                                                                 Debit           Credit
WIP accounting class outside processing                       XX                 -
valuation account
         Organization Receiving account                            -                  XX

Any difference from the standard is recognized as a resource efficiency variance at period close.

Discrete Workstation Transactions

From the Discrete Workstation, you can issue components, move assemblies, complete assemblies and operations, and charge resources without having to return to the main menu. You can either perform the transactions directly on the workstation tabs, or open the appropriate Work in Process window for that transaction.

Issue Components
To issue components to a job from the workstation, you choose the Issue Components button, which opens the WIP Material Transactions window. All relevant job information is automatically defaulted into the window from the workstation.

Move Assemblies
You can perform simple assembly Move transactions directly on the Assembly Move tab graphic using the mouse. The graphic displays a bucket for each intraoperation step, and uses a red ball to represent the assembly quantity. You move assembly quantities from one intraoperation step to another. by dragging the red ball to the bucket at that step.
When you move the assemblies, a window opens so that you can indicate the quantity that you want to move. The assembly quantity at each intraoperation step is displayed numerically above the step, and changes to reflect the number of assemblies that you move in or out of that step.


For more complex Move transactions, for example, if you want to over–complete, over–move, or complete lot and serial number controlled assemblies, you use the Work in Process Move Transactions window. You open the window directly from the workstation by choosing the Move Assemblies button on the Assembly Moves tab. All relevant job information is automatically defaulted into the window from the workstation.

Charge Resources
Resources are automatically charged when you move assemblies, unless you set them up to be charged manually. If you are set up to charge resources manually, you charge them on the Resource Transactions window, which you an open directly from the workstation by choosing the Charge Resources. All relevant job information is automatically defaulted into the window from the workstation.

You also can use the workstation Time Charges tab to charge person and machine time to a resource. On this tab, you select the resource that you want to charge, and enter the Start and End Dates, and the workstation calculates the time. The time is charged at the standard rate unless you select the Use Employee Rate check box, which charges the time at the employee rate.

Complete Assemblies and Complete Operations
You can complete assemblies and complete operations directly on the workstation Assembly Moves tab. You complete assemblies and operations when you drag the red ball graphic into the Complete Assembly or Complete Operation bucket on the tab’s interactive graphic. You also can complete and over–complete assemblies on the Move transactions window, which you open by choosing the Move Assemblies button.

Completing Assemblies
You can complete assemblies on the Assembly Moves tab if you are at the last operation on the routing. The completed assembly is then moved into the completion subinventory designated on the routing.

Completing Operations
You can complete the operation on the Assembly Moves tab for any operation other than the last operation The assembly is moved into the Queue of the next operation.

Serial Control
If you want to over–complete or over–move assembly quantities, or complete assemblies that are lot or serial number controlled, you choose the Move Assemblies button, which opens the Move Transactions window.

Sales Orders and Outside Processing Operations
When a job with outside processing operations is changed to complete, closed, or canceled status – an informational warning message displays if open purchase orders or requisitions exist for any of the operations.
Changing a job status to completed, closed, or canceled is prevented if open reservations exist. If you attempt one of these transactions for a job linked to a sales order, an error message displays. You have two options in order to continue:
  • Unlink the sales order reserved to this job
  • Reduce the job quantity of the job to equal the completed quantity.

Utilization, Efficiency, Productivity and Load Tab

Utilization Graph
The Utilization tab displays in graph and table format, the department’s or resource’s daily percent utilization during the past five days (the default date range), or during a date range that you select. The top section of the tab displays the name of the department or resource and its description, and provides you with two Date fields that you can use to change the date range of the graph.

The Utilization graph displays as a percentage the hours the department or resource was actually used compared to the hours it was available to be used. It shows the daily percent utilization of the resources within the selected department, or of a particular resource across all departments, depending on whether you chose to view a department or a department/resource when you launched the workstation.

The utilization formula is: Utilization = Actual Hours / Available Hours.

The default view for the graph displays information for the last five working days, however, you can change the date range (you are restricted to dates in the past). If you change the graph dates, you use the Redraw Graph button to refresh (update) the display.
The following information on the graph is also displayed in a table below the graph:
• Date: a day in the selected date range (the default date range is the last five working days)
• Actual Hours: the actual hours charged
• Available Hours: the hours defined in Bills of Material resource definitions
• Utilization Percent (%): Actual Hours / Available Hours

Demand class, kanban identifier, lot number, description, and Overcompletion tolerance


1. On the More tab, select the Demand Class.
You can select any enabled and active demand class. Demand classes are not required.

2. If the assembly is under lot control, select a Lot Number.
Lot numbers are automatically assigned based on how the Default Lot Number Type parameter is set, either by job name or based on Inventory lot number rules, but can be overwritten or deleted.
When you complete or return assemblies using the Completion Transactions window, job lot numbers entered here are
automatically defaulted but can be changed. Job lot numbers must be entered here before you can move and complete or move and return lot controlled assemblies using the Move Transactions window.

3. Enter the job Description.
Descriptions can be used to identify jobs on standard reports. They can be up to 240 characters of alpha numeric text. They are optional.

4. Enter the Kanban reference.

5. In the Overcompletion region, select the Tolerance Type. The options are Percent or Amount. If you do not select the Tolerance Type, it implies an infinite tolerance value.

6. Enter the Overcompletion Tolerance Value that corresponds to the Overcompletion Tolerance Type that you selected.
• If you did not select an Overcompletion Tolerance Type, no tolerance is indicated and you can over–complete all assemblies on this job.
• If you indicate a value of zero, you will not be able to over–complete any assemblies on this job.

Schedule group and project information

:
1. On the Schedule Group, Project tab, select the Schedule Group.
You have the option to assign discrete jobs to any active schedule group.

2. Enter a Build Sequence identifier.

3. Select a production Line.
You can select any active production line. Production lines are optional for discrete jobs. They are not used for scheduling or
transactional purposes. However, if you do select a production line, the combination of schedule group, build sequence, and
production line must be unique.

4. Select a Project and, if required, a task.
You can only select a project if the current organization’s Project References Enabled parameter is set in Oracle Inventory. You must select a task if the Project Control Level parameter is set to Task and you have entered a project.

5. Enter the Unit Number. This enables you to associate an end item model/unit effectivity number with the item.
You must have Oracle Project Manufacturing installed, the item must be under model/unit effectivity control, and you must have a model/unit number associated with it to enable this functionality. If the item is not under model/unit number control, this field is disabled.
Note: You can update unit effectivity through Mass Load for discrete jobs that are unreleased and project related.

6. Save your work.

If you are defining a discrete job, you must save the job before viewing component requirements and operations for that job.

Manufacturing Scheduling

If you have installed Oracle Manufacturing Scheduling, you can use the fields on this tab to change scheduling information
defaulted from the WIP Parameters window. To enable this functionality, select the Constraint Based Scheduler check box on the Scheduling tab of the WIP Parameters window.
Warning: Do not check the Constraint Based Schedule check box unless you have installed Oracle Manufacturing
Scheduling.

1. Select the Scheduling tab.

2. In the Requested Due Date field, you can enter a due date that is different than the completion date for the job.

3. In the Scheduling Priority field, enter a number ranging from 1 to 99, with 1 being the highest priority. The default priority is 10.

4. In the Penalty Per Day Late field, enter a penalty factor value used for scheduling jobs not completed by the scheduled due date. Higher penalties generate attempts in scheduling to circumvent such an event.

5. In the Due Date Tolerance (days) field, specify the maximum number of days the job can be delayed during scheduling.

6. Save your work.

Linking Sales Orders and Discrete Jobs

You can reserve assemblies on a Discrete job for a specific sales order line whether or not the assemblies are Assemble–to–Order (ATO) items. You link both standard and non–standard Discrete jobs to sales orders by selecting one or more sales orders from the Sales Order window when you create the job. You can link one or more sales order lines with one or more jobs.

You can also enter the demand class for the job to help you track production by sales channel. When you are building final assembly orders, the demand class is automatically loaded based on the customer. You can enter any valid demand class.
When linking ATO sales orders and jobs, however, the following rules are applied:

  1.  the assembly item cannot be a Pick–to–order item
  2.  the sales order line item must be demanded, but not yet shipped
  3.  the assembly item must be a standard item or an ATO item, not a model or an option
  • The WIP parameter, Respond to Sales Order Changes, determines the response to changes for configured sales orders and their linked Discrete jobs. Options are to ignore the sales order change or change the status of linked jobs to On Hold. When making changes to sales order lines with ATO items, this parameter is ignored by the system.
  •  
  • You cannot cancel jobs linked to sales orders without first undoing the links between them
 

1. You can select multiple sales orders as long as the total quantity allocated does not exceed the job quantity. You cannot select a sales order that has order lines that are currently being satisfied by a Flow schedule.

2. You can attach a sales order to a job before entering an assembly, start quantity, or demand class for a job. Work in Process defaults the assembly, start quantity, or demand class based upon the sales order you specify.

3. Over–completion Quantities Reserved to Sales Orders
You can reserve over–completion quantities from jobs linked to sales orders when using the Completion Transactions and Move Transactions windows.
To reserve over–completions:
  • The linked sales order must be open.
  • You enter the sales order number for each completion line. This reserves the surplus amount, otherwise the over–completion is unreserved excess inventory.
Note: Oracle Mobile Supply Chain Applications does not support this feature.

Serial Number Tracking Throughout Manufacturing

You can track your jobs using serial control throughout the manufacturing process. This enables you to assign and associate serial numbers to a job, and track the assembly by serial number as it progresses on the shop floor. Serial number tracking is enabled for discrete jobs, both standard and non–standard. This feature also includes:

  • Serial control beginning at a specific point in the routing
  • Association of serial numbers to jobs before build
  • Serial based transaction entry
  • Import and auto–generation of serial numbers
  • Serial number label printing
You can view the genealogy of the serialized assembly including move transactions, component issues, returns to stock, and completions.
Serial tracking for work in process transactions is only supported in the online mode through Oracle Mobile Supply Chain Applications

Setting Up Serial Number Control Tracking
Serial control for items is defined in Oracle Inventory. Work order serial tracking for assemblies is set in the Work in Process Parameters window.

1.1 Specify the serial control type as Predefined. This value is defined in Inventory attribute, Serial Generation.
Work in process serial tracking is only enabled when you use the value of Predefined.

1.2 Establish the type of serial number uniqueness for your organization in the Oracle Inventory Organization Parameters
window. Your options for serial number uniqueness are Within inventory items, Within an organization, or Across organizations.

1.3 Optionally, you can predefine serial numbers in Oracle Inventory. You can generate serial numbers using the Serial Number Generation concurrent program,

2.1 Default Serialization Start Operation
Determines the job operation where serial number tracking begins.
The serial start operation on the item routing is always copied to the job routing during job creation. If there is no serialization start operation on the item routing, and this parameter is enabled – the serialization start operation is defaulted to the first operation on the job routing, This value displays on the Discrete Jobs window. If this parameter is not enabled, the serialization start operation on the job routing is blank, and serialization is disabled.

2.2 Auto Associate Serial Numbers on Job Creation From Interface If this parameter is enabled, serial numbers are automatically generated and associated to a job when a job is created through the WIP Mass Load Interface.
When you submit the WIP Mass Load program using the Import Jobs and Schedules window, new standard and non–standard discrete jobs are created. The Work Order Interface uses the value in this parameter to create serialized records for the new jobs.

2.3 Default Intraoperation Step for Assembly Moves
This parameter is used for move transactions on a serialized job. It defines a default value for the intraoperation step where you are moving assemblies – the To step. Your choices are Queue, Run, To move, and Null. The following table shows the next move for for Default Intraoperation Step values in this parameter.

3. Transaction Processing Mode
This parameter has two settings: Online and Background. For serialized transactions, this parameter is ignored and will always
use the Online setting.

Associating and Modifying Serial Number Job Information
The Associate Serial Numbers window is accessed from the Discrete Jobs window, and is enabled only for jobs under serialization. If you are creating a new job, you must first save your record in order to enter information on this window.
This window enables you to generate and associate new or existing serial numbers to the job. You can also print labels for these serial numbers from this window.

Label Printing for Serialized Parts
Labels can be printed after serial numbers have been associated to a job. You can set up serial label printing either in Oracle Inventory, or Oracle Warehouse Management. This includes selecting serial number label types, formats, and assigning printers. You can print labels from the Associate Serial Numbers window, or from the mobile device window.

Moving Serialized Assemblies
You can perform serialized move transactions through Oracle Mobile Supply Chain Applications using a mobile device. The location of the assembly on the routing determines the window used for the transactions. For example, jobs not serialized do not require serial entry
– and serialized jobs require serial number entry before you can proceed. This functionality uses the following rules:
• Before reaching the serialization start operation, move transactions are performed using the window where serial
number entry is not available.
• Once a serialized assembly moves to the Queue of the serialization start operation, move transactions are performed
using a window requiring serial number entry.

Building Discrete Jobs

Steps involved in building discrete jobs include:
1. Releasing jobs to production.
2. Issuing components to jobs and, if necessary, returning them back to inventory.
3. Using Shop Floor Control to coordinate, on an as required basis, the following:
– Moving assemblies between routing operations and intraoperation step.
– Scrapping assemblies.
– Backflushing or issuing and returning operation pull and assembly pull components automatically with move transactions
– Charging resources.
4. Changing jobs to accommodate changes in production.

Note: If you have Oracle Shop Floor Management installed, you can use lot based jobs in your manufacturing. The entire
quantity of a lot based job moves on the basis of the network routing.

Releasing Discrete Jobs
You must release a job to production before transacting against it. Releasing a discrete job with a routing automatically loads the job quantity into the Queue intraoperation step of the first operation. If PO Move or PO Receipt resource requirements exist at the first operation, purchase requisitions for these resources are automatically generated.


Printing Reports for Current Discrete Jobs
If you are in the Discrete Jobs, Close Discrete Jobs, Purge Discrete Jobs, or View Discrete Jobs window, you can use the Print Reports Tools menu option to print the Discrete Job Routing Sheet, Discrete Job Pick List Report, or the Discrete Job Shortage Report for the active or current job.

3. Building Discrete Jobs

Steps involved in building discrete jobs include:
1. Releasing jobs to production.
2. Issuing components to jobs and, if necessary, returning them back to inventory.
3. Using Shop Floor Control to coordinate, on an as required basis, the following:
– Moving assemblies between routing operations and intraoperation step.
– Scrapping assemblies.
– Backflushing or issuing and returning operation pull and assembly pull components automatically with move transactions
– Charging resources.
4. Changing jobs to accommodate changes in production.

Note: If you have Oracle Shop Floor Management installed, you can use lot based jobs in your manufacturing. The entire
quantity of a lot based job moves on the basis of the network routing.

Releasing Discrete Jobs
You must release a job to production before transacting against it. Releasing a discrete job with a routing automatically loads the job quantity into the Queue intraoperation step of the first operation. If PO Move or PO Receipt resource requirements exist at the first operation, purchase requisitions for these resources are automatically generated.


Printing Reports for Current Discrete Jobs
If you are in the Discrete Jobs, Close Discrete Jobs, Purge Discrete Jobs, or View Discrete Jobs window, you can use the Print Reports Tools menu option to print the Discrete Job Routing Sheet, Discrete Job Pick List Report, or the Discrete Job Shortage Report for the active or current job.

Building Discrete Jobs

Steps involved in building discrete jobs include:
1. Releasing jobs to production.
2. Issuing components to jobs and, if necessary, returning them back to inventory.
3. Using Shop Floor Control to coordinate, on an as required basis, the following:
– Moving assemblies between routing operations and intraoperation step.
– Scrapping assemblies.
– Backflushing or issuing and returning operation pull and assembly pull components automatically with move transactions
– Charging resources.
4. Changing jobs to accommodate changes in production.

Note: If you have Oracle Shop Floor Management installed, you can use lot based jobs in your manufacturing. The entire
quantity of a lot based job moves on the basis of the network routing.

Releasing Discrete Jobs
You must release a job to production before transacting against it. Releasing a discrete job with a routing automatically loads the job quantity into the Queue intraoperation step of the first operation. If PO Move or PO Receipt resource requirements exist at the first operation, purchase requisitions for these resources are automatically generated.


Printing Reports for Current Discrete Jobs
If you are in the Discrete Jobs, Close Discrete Jobs, Purge Discrete Jobs, or View Discrete Jobs window, you can use the Print Reports Tools menu option to print the Discrete Job Routing Sheet, Discrete Job Pick List Report, or the Discrete Job Shortage Report for the active or current job.

3. Building Discrete Jobs

Steps involved in building discrete jobs include:
1. Releasing jobs to production.
2. Issuing components to jobs and, if necessary, returning them back to inventory.
3. Using Shop Floor Control to coordinate, on an as required basis, the following:
– Moving assemblies between routing operations and intraoperation step.
– Scrapping assemblies.
– Backflushing or issuing and returning operation pull and assembly pull components automatically with move transactions
– Charging resources.
4. Changing jobs to accommodate changes in production.

Note: If you have Oracle Shop Floor Management installed, you can use lot based jobs in your manufacturing. The entire
quantity of a lot based job moves on the basis of the network routing.

Releasing Discrete Jobs
You must release a job to production before transacting against it. Releasing a discrete job with a routing automatically loads the job quantity into the Queue intraoperation step of the first operation. If PO Move or PO Receipt resource requirements exist at the first operation, purchase requisitions for these resources are automatically generated.


Printing Reports for Current Discrete Jobs
If you are in the Discrete Jobs, Close Discrete Jobs, Purge Discrete Jobs, or View Discrete Jobs window, you can use the Print Reports Tools menu option to print the Discrete Job Routing Sheet, Discrete Job Pick List Report, or the Discrete Job Shortage Report for the active or current job.

Viewing Pending Job Transactions

You can use the Transaction Summary window to determine if there are pending transactions or unprocessed documents associated with a job. You cannot purge or close jobs if pending transactions or unprocessed documents exist. In some instances, you also cannot change a job from one status to another. For example, you cannot change jobs from a Released to an Unreleased status if pending information exists

.

Updating Discrete Jobs

You can make the following changes to your discrete jobs:

  • Change the name of existing jobs in the Discrete Jobs window, but only if the WIP:Job Name Updatable profile option is set.
  • Change dates, quantities, bills, statuses, and routings.
  • Add, update, and delete operations.
  • Add, update, and delete material requirements.
  • Add, change, and delete resource requirements.
  • Implement engineering change orders in Oracle Engineering.
  • Add, change, and delete WIP Attachments..
  • If you have Oracle Shop Floor Management installed, you can create and update lot based jobs. The entire quantity of a lot based job moves on the basis of the network routing.
Changing Discrete Jobs
You can change discrete jobs using the Discrete Jobs and Discrete Jobs Summary windows. The status of the job determines if and what information can be changed.

Quantities
You can increase or decrease the job quantity with no restrictions if the job is unreleased. If the job is released and work has begun on the assembly, you cannot decrease the job quantity lower than the number of assemblies that have already passed the Queue intraoperation step of the first operation. If a sales order is linked to the job, you cannot decrease the job quantity lower than the order quantity. The material requirements and job dates are automatically adjusted based upon the quantity change. If the job’s assembly is an MPS–planned item, the update process automatically adjusts the MPS relief quantity.

Dates
You can reschedule standard and non–standard jobs to respond to changes in plans or unexpected downtime by changing their start and/or completion dates and times. Jobs might require rescheduling when capacity or material schedules change, or when standards change.

Statuses
You can change the status of a discrete job although some changes from one status to another are disallowed and others are conditional
Rescheduling Discrete Jobs
You can reschedule standard and non–standard discrete jobs with and without routings. You can enter job start and completion dates earlier than the current date to maintain relative date priorities for department schedules and material requirements. You can also reschedule discrete jobs by rescheduling their operations.

2.3 Updating Discrete Jobs

You can make the following changes to your discrete jobs:

  • Change the name of existing jobs in the Discrete Jobs window, but only if the WIP:Job Name Updatable profile option is set.
  • Change dates, quantities, bills, statuses, and routings.
  • Add, update, and delete operations.
  • Add, update, and delete material requirements.
  • Add, change, and delete resource requirements.
  • Implement engineering change orders in Oracle Engineering.
  • Add, change, and delete WIP Attachments..
  • If you have Oracle Shop Floor Management installed, you can create and update lot based jobs. The entire quantity of a lot based job moves on the basis of the network routing.
Changing Discrete Jobs
You can change discrete jobs using the Discrete Jobs and Discrete Jobs Summary windows. The status of the job determines if and what information can be changed.

Quantities
You can increase or decrease the job quantity with no restrictions if the job is unreleased. If the job is released and work has begun on the assembly, you cannot decrease the job quantity lower than the number of assemblies that have already passed the Queue intraoperation step of the first operation. If a sales order is linked to the job, you cannot decrease the job quantity lower than the order quantity. The material requirements and job dates are automatically adjusted based upon the quantity change. If the job’s assembly is an MPS–planned item, the update process automatically adjusts the MPS relief quantity.

Dates
You can reschedule standard and non–standard jobs to respond to changes in plans or unexpected downtime by changing their start and/or completion dates and times. Jobs might require rescheduling when capacity or material schedules change, or when standards change.

Statuses
You can change the status of a discrete job although some changes from one status to another are disallowed and others are conditional
Rescheduling Discrete Jobs
You can reschedule standard and non–standard discrete jobs with and without routings. You can enter job start and completion dates earlier than the current date to maintain relative date priorities for department schedules and material requirements. You can also reschedule discrete jobs by rescheduling their operations.

Updating Discrete Jobs

You can make the following changes to your discrete jobs:

  • Change the name of existing jobs in the Discrete Jobs window, but only if the WIP:Job Name Updatable profile option is set.
  • Change dates, quantities, bills, statuses, and routings.
  • Add, update, and delete operations.
  • Add, update, and delete material requirements.
  • Add, change, and delete resource requirements.
  • Implement engineering change orders in Oracle Engineering.
  • Add, change, and delete WIP Attachments..
  • If you have Oracle Shop Floor Management installed, you can create and update lot based jobs. The entire quantity of a lot based job moves on the basis of the network routing.
Changing Discrete Jobs
You can change discrete jobs using the Discrete Jobs and Discrete Jobs Summary windows. The status of the job determines if and what information can be changed.

Quantities
You can increase or decrease the job quantity with no restrictions if the job is unreleased. If the job is released and work has begun on the assembly, you cannot decrease the job quantity lower than the number of assemblies that have already passed the Queue intraoperation step of the first operation. If a sales order is linked to the job, you cannot decrease the job quantity lower than the order quantity. The material requirements and job dates are automatically adjusted based upon the quantity change. If the job’s assembly is an MPS–planned item, the update process automatically adjusts the MPS relief quantity.

Dates
You can reschedule standard and non–standard jobs to respond to changes in plans or unexpected downtime by changing their start and/or completion dates and times. Jobs might require rescheduling when capacity or material schedules change, or when standards change.

Statuses
You can change the status of a discrete job although some changes from one status to another are disallowed and others are conditional
Rescheduling Discrete Jobs
You can reschedule standard and non–standard discrete jobs with and without routings. You can enter job start and completion dates earlier than the current date to maintain relative date priorities for department schedules and material requirements. You can also reschedule discrete jobs by rescheduling their operations.

2.3 Updating Discrete Jobs

You can make the following changes to your discrete jobs:

  • Change the name of existing jobs in the Discrete Jobs window, but only if the WIP:Job Name Updatable profile option is set.
  • Change dates, quantities, bills, statuses, and routings.
  • Add, update, and delete operations.
  • Add, update, and delete material requirements.
  • Add, change, and delete resource requirements.
  • Implement engineering change orders in Oracle Engineering.
  • Add, change, and delete WIP Attachments..
  • If you have Oracle Shop Floor Management installed, you can create and update lot based jobs. The entire quantity of a lot based job moves on the basis of the network routing.
Changing Discrete Jobs
You can change discrete jobs using the Discrete Jobs and Discrete Jobs Summary windows. The status of the job determines if and what information can be changed.

Quantities
You can increase or decrease the job quantity with no restrictions if the job is unreleased. If the job is released and work has begun on the assembly, you cannot decrease the job quantity lower than the number of assemblies that have already passed the Queue intraoperation step of the first operation. If a sales order is linked to the job, you cannot decrease the job quantity lower than the order quantity. The material requirements and job dates are automatically adjusted based upon the quantity change. If the job’s assembly is an MPS–planned item, the update process automatically adjusts the MPS relief quantity.

Dates
You can reschedule standard and non–standard jobs to respond to changes in plans or unexpected downtime by changing their start and/or completion dates and times. Jobs might require rescheduling when capacity or material schedules change, or when standards change.

Statuses
You can change the status of a discrete job although some changes from one status to another are disallowed and others are conditional
Rescheduling Discrete Jobs
You can reschedule standard and non–standard discrete jobs with and without routings. You can enter job start and completion dates earlier than the current date to maintain relative date priorities for department schedules and material requirements. You can also reschedule discrete jobs by rescheduling their operations.

Simulating and Saving Simulated Jobs

You can simulate a standard job to determine what materials, operations, and operation resources are required to support that job.
You can specifically do all of the following:

  • Vary the job quantity and/or start and completion dates to determine scheduling and requirement constraints
  • View both on–hand and available to promise quantities for simulated component requirements
  • Vary the bills of material and/or routings and their associated revisions and revision dates
When you are satisfied with the simulated job, you can convert it into an actual job and save it.

2.2 Simulating and Saving Simulated Jobs

You can simulate a standard job to determine what materials, operations, and operation resources are required to support that job.
You can specifically do all of the following:

  • Vary the job quantity and/or start and completion dates to determine scheduling and requirement constraints
  • View both on–hand and available to promise quantities for simulated component requirements
  • Vary the bills of material and/or routings and their associated revisions and revision dates
When you are satisfied with the simulated job, you can convert it into an actual job and save it.

Simulating and Saving Simulated Jobs

You can simulate a standard job to determine what materials, operations, and operation resources are required to support that job.
You can specifically do all of the following:

  • Vary the job quantity and/or start and completion dates to determine scheduling and requirement constraints
  • View both on–hand and available to promise quantities for simulated component requirements
  • Vary the bills of material and/or routings and their associated revisions and revision dates
When you are satisfied with the simulated job, you can convert it into an actual job and save it.

2.2 Simulating and Saving Simulated Jobs

You can simulate a standard job to determine what materials, operations, and operation resources are required to support that job.
You can specifically do all of the following:

  • Vary the job quantity and/or start and completion dates to determine scheduling and requirement constraints
  • View both on–hand and available to promise quantities for simulated component requirements
  • Vary the bills of material and/or routings and their associated revisions and revision dates
When you are satisfied with the simulated job, you can convert it into an actual job and save it.

Completing Discrete Jobs

You complete job assemblies into inventory using the Completion Transactions and Move Transactions windows. You also use these windows to return completed assemblies back to jobs. When you complete or return assemblies, any remaining quantities are automatically updated. Note: You can also complete Work in Process assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface.


Over–completions
You can complete an assembly quantity into inventory that is greater than the job start quantity, or move an assembly quantity that is greater than the quantity at an intraoperation step, whether or not the assemblies have a routing. This is referred to as an “over–completion,” and it is useful when your production process yields more assemblies than planned.
Note: You also can over–complete assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface, but you must explicitly specify the over–completion transaction quantity, as it will not be derived by Work in Process.

To be able to over–complete assemblies on jobs, you must:
  • Set up a tolerance level to restrict the number of assemblies that can be over–completed
  • Enable the over–completion feature by checking the Over–completion check box on the Completion Transaction or Move Transaction windows when completing assemblies When you over–complete assemblies to Discrete jobs, all resources
  • are charged and any backflush components are backflushed
Backflushing
When you complete assemblies, all components with the supply type of Assembly pull are automatically backflushed. When components for assemblies under lot control, serial number control, or lot and serial control are backflushed upon assembly completion, you must assign lot and/or serial numbers to the components.

Shop Floor Statuses
You cannot complete assemblies from a job if a shop floor status that prevents shop floor moves has been assigned the To move intraoperation step of the last operation. In this case, you must assign a status that allows shop floor moves in order to complete the assemblies.

Outside Processing Operations
When a job or schedule with outside processing operations is changed to complete status – an informational warning message displays if open purchase orders or requisitions exist for any of the operations.

Sales Orders
Changing a job status to completed is prevented if open reservations exist. If you attempt one of these transactions for a job linked to a sales order, an error message displays. You must reduce the job quantity, or unlink the sales order to continue the transactions.

Non–Standard Job Completions
You must have an assembly and job quantity to complete a non–standard discrete job. You can complete an assembly quantity greater than the job start quantity, with or without a routing, as long as the quantity is within the tolerance set. For some non–standard jobs, such as those used for disassembly or equipment maintenance, there is no need to complete assemblies.

Final Assembly Order Completions
When you complete assemblies from final assembly orders using a completion transaction, reservations are automatically transferred from the job to the subinventory and locator based on sales order line delivery due dates. You may override the automatic transfer. When returning completed assemblies back to a final assembly order, you must enter the sales order line and delivery information so that the system knows which reservations to transfer from inventory to WIP.

Costing
Under standard costing, assemblies are received into inventory at standard cost and the job is relieved of costs at standard. Under average costing, assemblies are received and the job relieved of costs at average.

Serial Number Validations for Discrete Assembly Completions
For a serialized item returned to stock, validations occur to preventre–issuing to a different job. At the time of completion, serialized assemblies and components are available from stock if they have specific values set for discrete assemblies and components in the Serial Numbers window in Oracle Inventory:

Label Printing at Completion
Label printing capabilities are available at the time of completion. This provides the ability to create labels for any descriptive information or customer requirements.

4. Completing Discrete Jobs

You complete job assemblies into inventory using the Completion Transactions and Move Transactions windows. You also use these windows to return completed assemblies back to jobs. When you complete or return assemblies, any remaining quantities are automatically updated. Note: You can also complete Work in Process assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface.


Over–completions
You can complete an assembly quantity into inventory that is greater than the job start quantity, or move an assembly quantity that is greater than the quantity at an intraoperation step, whether or not the assemblies have a routing. This is referred to as an “over–completion,” and it is useful when your production process yields more assemblies than planned.
Note: You also can over–complete assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface, but you must explicitly specify the over–completion transaction quantity, as it will not be derived by Work in Process.

To be able to over–complete assemblies on jobs, you must:
  • Set up a tolerance level to restrict the number of assemblies that can be over–completed
  • Enable the over–completion feature by checking the Over–completion check box on the Completion Transaction or Move Transaction windows when completing assemblies When you over–complete assemblies to Discrete jobs, all resources
  • are charged and any backflush components are backflushed
Backflushing
When you complete assemblies, all components with the supply type of Assembly pull are automatically backflushed. When components for assemblies under lot control, serial number control, or lot and serial control are backflushed upon assembly completion, you must assign lot and/or serial numbers to the components.

Shop Floor Statuses
You cannot complete assemblies from a job if a shop floor status that prevents shop floor moves has been assigned the To move intraoperation step of the last operation. In this case, you must assign a status that allows shop floor moves in order to complete the assemblies.

Outside Processing Operations
When a job or schedule with outside processing operations is changed to complete status – an informational warning message displays if open purchase orders or requisitions exist for any of the operations.

Sales Orders
Changing a job status to completed is prevented if open reservations exist. If you attempt one of these transactions for a job linked to a sales order, an error message displays. You must reduce the job quantity, or unlink the sales order to continue the transactions.

Non–Standard Job Completions
You must have an assembly and job quantity to complete a non–standard discrete job. You can complete an assembly quantity greater than the job start quantity, with or without a routing, as long as the quantity is within the tolerance set. For some non–standard jobs, such as those used for disassembly or equipment maintenance, there is no need to complete assemblies.

Final Assembly Order Completions
When you complete assemblies from final assembly orders using a completion transaction, reservations are automatically transferred from the job to the subinventory and locator based on sales order line delivery due dates. You may override the automatic transfer. When returning completed assemblies back to a final assembly order, you must enter the sales order line and delivery information so that the system knows which reservations to transfer from inventory to WIP.

Costing
Under standard costing, assemblies are received into inventory at standard cost and the job is relieved of costs at standard. Under average costing, assemblies are received and the job relieved of costs at average.

Serial Number Validations for Discrete Assembly Completions
For a serialized item returned to stock, validations occur to preventre–issuing to a different job. At the time of completion, serialized assemblies and components are available from stock if they have specific values set for discrete assemblies and components in the Serial Numbers window in Oracle Inventory:

Label Printing at Completion
Label printing capabilities are available at the time of completion. This provides the ability to create labels for any descriptive information or customer requirements.

Completing Discrete Jobs

You complete job assemblies into inventory using the Completion Transactions and Move Transactions windows. You also use these windows to return completed assemblies back to jobs. When you complete or return assemblies, any remaining quantities are automatically updated. Note: You can also complete Work in Process assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface.


Over–completions
You can complete an assembly quantity into inventory that is greater than the job start quantity, or move an assembly quantity that is greater than the quantity at an intraoperation step, whether or not the assemblies have a routing. This is referred to as an “over–completion,” and it is useful when your production process yields more assemblies than planned.
Note: You also can over–complete assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface, but you must explicitly specify the over–completion transaction quantity, as it will not be derived by Work in Process.

To be able to over–complete assemblies on jobs, you must:
  • Set up a tolerance level to restrict the number of assemblies that can be over–completed
  • Enable the over–completion feature by checking the Over–completion check box on the Completion Transaction or Move Transaction windows when completing assemblies When you over–complete assemblies to Discrete jobs, all resources
  • are charged and any backflush components are backflushed
Backflushing
When you complete assemblies, all components with the supply type of Assembly pull are automatically backflushed. When components for assemblies under lot control, serial number control, or lot and serial control are backflushed upon assembly completion, you must assign lot and/or serial numbers to the components.

Shop Floor Statuses
You cannot complete assemblies from a job if a shop floor status that prevents shop floor moves has been assigned the To move intraoperation step of the last operation. In this case, you must assign a status that allows shop floor moves in order to complete the assemblies.

Outside Processing Operations
When a job or schedule with outside processing operations is changed to complete status – an informational warning message displays if open purchase orders or requisitions exist for any of the operations.

Sales Orders
Changing a job status to completed is prevented if open reservations exist. If you attempt one of these transactions for a job linked to a sales order, an error message displays. You must reduce the job quantity, or unlink the sales order to continue the transactions.

Non–Standard Job Completions
You must have an assembly and job quantity to complete a non–standard discrete job. You can complete an assembly quantity greater than the job start quantity, with or without a routing, as long as the quantity is within the tolerance set. For some non–standard jobs, such as those used for disassembly or equipment maintenance, there is no need to complete assemblies.

Final Assembly Order Completions
When you complete assemblies from final assembly orders using a completion transaction, reservations are automatically transferred from the job to the subinventory and locator based on sales order line delivery due dates. You may override the automatic transfer. When returning completed assemblies back to a final assembly order, you must enter the sales order line and delivery information so that the system knows which reservations to transfer from inventory to WIP.

Costing
Under standard costing, assemblies are received into inventory at standard cost and the job is relieved of costs at standard. Under average costing, assemblies are received and the job relieved of costs at average.

Serial Number Validations for Discrete Assembly Completions
For a serialized item returned to stock, validations occur to preventre–issuing to a different job. At the time of completion, serialized assemblies and components are available from stock if they have specific values set for discrete assemblies and components in the Serial Numbers window in Oracle Inventory:

Label Printing at Completion
Label printing capabilities are available at the time of completion. This provides the ability to create labels for any descriptive information or customer requirements.

4. Completing Discrete Jobs

You complete job assemblies into inventory using the Completion Transactions and Move Transactions windows. You also use these windows to return completed assemblies back to jobs. When you complete or return assemblies, any remaining quantities are automatically updated. Note: You can also complete Work in Process assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface.


Over–completions
You can complete an assembly quantity into inventory that is greater than the job start quantity, or move an assembly quantity that is greater than the quantity at an intraoperation step, whether or not the assemblies have a routing. This is referred to as an “over–completion,” and it is useful when your production process yields more assemblies than planned.
Note: You also can over–complete assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface, but you must explicitly specify the over–completion transaction quantity, as it will not be derived by Work in Process.

To be able to over–complete assemblies on jobs, you must:
  • Set up a tolerance level to restrict the number of assemblies that can be over–completed
  • Enable the over–completion feature by checking the Over–completion check box on the Completion Transaction or Move Transaction windows when completing assemblies When you over–complete assemblies to Discrete jobs, all resources
  • are charged and any backflush components are backflushed
Backflushing
When you complete assemblies, all components with the supply type of Assembly pull are automatically backflushed. When components for assemblies under lot control, serial number control, or lot and serial control are backflushed upon assembly completion, you must assign lot and/or serial numbers to the components.

Shop Floor Statuses
You cannot complete assemblies from a job if a shop floor status that prevents shop floor moves has been assigned the To move intraoperation step of the last operation. In this case, you must assign a status that allows shop floor moves in order to complete the assemblies.

Outside Processing Operations
When a job or schedule with outside processing operations is changed to complete status – an informational warning message displays if open purchase orders or requisitions exist for any of the operations.

Sales Orders
Changing a job status to completed is prevented if open reservations exist. If you attempt one of these transactions for a job linked to a sales order, an error message displays. You must reduce the job quantity, or unlink the sales order to continue the transactions.

Non–Standard Job Completions
You must have an assembly and job quantity to complete a non–standard discrete job. You can complete an assembly quantity greater than the job start quantity, with or without a routing, as long as the quantity is within the tolerance set. For some non–standard jobs, such as those used for disassembly or equipment maintenance, there is no need to complete assemblies.

Final Assembly Order Completions
When you complete assemblies from final assembly orders using a completion transaction, reservations are automatically transferred from the job to the subinventory and locator based on sales order line delivery due dates. You may override the automatic transfer. When returning completed assemblies back to a final assembly order, you must enter the sales order line and delivery information so that the system knows which reservations to transfer from inventory to WIP.

Costing
Under standard costing, assemblies are received into inventory at standard cost and the job is relieved of costs at standard. Under average costing, assemblies are received and the job relieved of costs at average.

Serial Number Validations for Discrete Assembly Completions
For a serialized item returned to stock, validations occur to preventre–issuing to a different job. At the time of completion, serialized assemblies and components are available from stock if they have specific values set for discrete assemblies and components in the Serial Numbers window in Oracle Inventory:

Label Printing at Completion
Label printing capabilities are available at the time of completion. This provides the ability to create labels for any descriptive information or customer requirements.

Work in Process

Oracle Work in Process is a complete production management system. Work in Process is part of Oracle Applications, an integrated suite of business solutions. Work in Process supports discrete, repetitive, assemble-to-order, work order-less, project or a combination of manufacturing methods. Inquiries and reports give you a complete picture of transactions, materials, resources, costs, and job and schedule progress.



Integration