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

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.

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

 

• 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.

• 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.

• 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.

• 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.

• 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.

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.