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. The following summarizes WIP parameters and their defaults:

Discrete Parameters

The following parameters affect discrete manufacturing.

Default Discrete Class

If Category Default WIP Classes are not set up and you are defining a standard, non-project discrete job or performing a work order-less completion, this parameter determines which accounting class is used as the default. See: Default WIP Classes and Associating WIP Accounting Classes with Categories.

You can only select an active, standard discrete accounting class when defining this parameter. See: Discrete Accounting Classes, Defining Discrete Jobs Manually, and Autocreating Final Assembly Orders.

Default Lot Number Type Parameter

Determines how lot numbers are assigned to discrete jobs. The options are as follows:

• Job Name

  Base job lot numbers on the job name you enter when you define the job. This is the default.

• Based on Inventory Rules

  Base job lot numbers on the lot number rules you defined in Oracle Inventory. This restricts you to the one specific lot generated for the job, and will not enable new lots to be created. See: Lot Control and. Defining Revision, Lot, LPN Serial Parameters

• No Default

  There will be no default of any lot if the parameter is set to this value. This also gives the ability to generate the lot number repeatedly for each assembly if multiple lot number creation is required for a job.

Respond to Sales Order Changes

Determines the status of a work order reserved and linked to a sales order: if a configured item is de-linked from a sales order or sales order line placed on hold, you can set the following options:

• Never: The work order will not be placed on hold if you de-link the configured item from the sales order, or if the sales order is placed on hold.

• Always: The work order will be placed on hold if you de-link the configured item from the sales order, or if the sales order is placed on hold.

• When Linked 1 to 1:

  The work order will be placed on hold if it is the only work order reserved to that sales order.

  Attention: When cancelling sales order lines with ATO items, this parameter, is ignored by the system. See: Linking Sales Orders and Discrete Jobs

Repetitive Parameters

The following parameters affect repetitive manufacturing.

• Recognize Period Variances

  Determines which repetitive schedule variances are posted to the general ledger when an accounting period is closed. The options are as follows:

  • All Schedules; Post variances for all repetitive schedules.

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

  When you complete a repetitive schedule, the system searches within the autorelease time frame for an Unreleased schedule, or for a schedule with a status of Released, Complete, or On Hold. If one exists, the status of the newly completed schedule changes to Complete-No Charges and the future schedule is automatically released. If no such schedule exists, the status of the schedule changes to Complete. If more than one schedule exists within the autorelease time frame, only one schedule is released.

Costing Parameters

These parameters affect how WIP assembly completion transactions are costed. The Default Completion Cost Source, Cost Type, and System Option parameters are defaulted when you define standard and non-standard accounting classes in the WIP Accounting Classes window.

The Auto Compute Final Completion parameter is defaulted when you complete jobs. This parameter can be set for both average and standard costing organizations. The other parameters are used only for average costing organizations defined in the Oracle Inventory Organization Parameters window. See: Organization Parameters Window and Defining Costing Information.

• Default Completion Cost Source

  This parameter determines how resource costs are determined as assemblies are completed from jobs into inventory.

  • System Calculated

    If this option is set, resources can be costed at either the actual resource costs or at the resource predefined cost depending on how the System Option parameter is subsequently set.

    When completing assemblies from a non-standard job with no routing, the resource rate associated with the Average Rates cost type is used.

  • User-Defined

    If the option is set, you must choose a user-defined cost type using the Cost Type Parameter. This cost type is then used to determine the resource cost for the assemblies being completed.

    Note: If there are uncleared costs left in the job, they are posted to the job variance accounts when the job is closed. Residual costs could be left in the job if: 1) the Auto Compute Final Completion option is set, but not all assemblies are completed or scrapped or 2) the job earns costs between the last final completion and the close transaction.

  • System Option

    If you select the System Calculated completion cost source, you must select a System Option. The available options are as follows:

  • Use Actual Resources

    Resources costs are determined based on the actual costs that have been charged to the job.

  • Use Predefined Resources

    Resources costs are determined using the predefined resource cost.

    Note: If you have chosen the Use Predefined Resources system option and are overcompleting assemblies that are associated with lot based resources and overheads, these resources and overheads are over-relieved from Work in Process. You can avoid this problem by selecting the Use Actual Resources system option. See: Assembly Over-completions and Over-returns and Move Completion/Return Transactions.

  • Cost Type

    Determines which cost type to use as the default when the Default Completion Cost Source is User-Defined. You can only select a Cost Type if the Default Completion Cost Source parameter is set to User Defined. See: Defining a Cost Type.

  • Auto Compute Final Completion

    Determines whether the Final Completion in the Completion Transaction window defaults to enabled or disabled. If this parameter is enabled, the system automatically calculates completion costs when a transaction completes a job.

Move Transaction Parameters

The following parameters affect move transactions.

• Require Scrap Account

  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 work in process routing during a move transaction. For example, you may want to add an operation to keep track of rework you were not expecting.

  Note: In Oracle Manufacturing Execution System for Discrete Manufacturing, this parameter is not supported and the behavior in MES would function as if it was disabled.

• Allow Moves Over No Move Shop Floor Statuses

  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.

  Note: The Move Transactions: Allow Skipping Over No Move Statuses security function can be set to override no move shop floor statuses. See: Security Functions.

  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. See: Shop Floor Statuses.

Material Parameters

The following parameters are used for material transactions.

• Include Component Yield

  Controls if component yield is factored into component quantities during material transactions. You can disable this parameter to avoid rounding decimal quantities. Rounding can inflate transaction quantities, and requirements are then not accurately represented. See: Component Yield and Shrinkage

• Supply Subinventory

  Determines which supply subinventory and, if required by the subinventory, locator are used when backflushing Operation Pull and Assembly Pull components that do not have defaults defined at the bill of material component or at the inventory item level.

  You can select an expense subinventory, if the Oracle Inventory Allow Expense to Asset Transfer profile option is set to Yes. See: Inventory Profile Options.

• Supply Locator

  Determines which supply subinventory, and if required by the subinventory, which locator is used when backflushing Operation Pull and Assembly Pull components that do not have defaults defined at the bill of material component or at the inventory item level.

  Note: If a supply locator for the component is not named on the bill of material, it will default to the machine locator when the job is created.

• Lot Selection Method

  Determines how lot controlled Assembly Pull and Component Pull component items are selected during backflush transactions. The options are as follows:

  • Expiration Date

    Backflush lots are automatically selected based on their expiration date and the first in-first out (FIFO) method or, if the lot is not under shelf life control, the receipt date and the first in-first out (FIFO) method.

  • Manual

    Backflush lots must be manually selected.

  • Receipt Date

    Backflush lots are automatically selected based on their inventory receipt date using the first in-first out (FIFO) method.

  • Transaction History

    Backflush lots are automatically selected based on the previous transaction, for the same component, on the same job.

    Note: This parameter does not apply to components that are under both lot and serial control. When you backflush a component under both lot and serial control, you must enter both the lot and the serial number.

• Alternate Lot Selection Method

  This parameter is only enabled if the Lot Selection Method is set to Transaction History. It is used when previous transactions - for the same component, on the same job - do not exist for defaulting. The options are:

  • Expiration Date

    Backflush lots are automatically selected based on their expiration date and the first in-first out (FIFO) method or, if the lot is not under shelf life control, the receipt date and the first in-first out (FIFO) method.

  • Manual

    Backflush lots must be manually selected.

  • Receipt Date

    Backflush lots are automatically selected based on their inventory receipt date using the first in-first out (FIFO) method.

• Lot Verification

  Determines how lots that are automatically selected, based on whether the Lot Selection Method parameter is set to Receipt Date or Expiration Date, are verified during backflush transactions. When the Lot Selection Method parameter is set to Manual, manually selected lots are verified as if the All option has been specified. The lot verification options are as follows:

  • All

    Verifies that the lots automatically selected were the ones consumed by the assemblies.

  • Exceptions Only

    Verifies exceptions only. If the lot requirement for the component cannot be filled automatically using the FIFO method, you can assign lots to components manually.

• Release Backflush Components

  The Component Pick Release program only considers supply type push components in processing, unless this parameter is enabled. If enabled, operation pull and assembly pull supply type components are included in the pick release process.

  Note: The Discrete Job Pick List Report does not consider this parameter in processing.

  Kanban Components - the system assumes that supply type pull components are used for backflush transactions, that is, for consumption and you are not picking these components for a job. Kanban items are not typically considered in a pick release, but they are often defined as assembly pull components. Appropriate for kanban items, the following behavior occurs for the Release Backflush Components parameter setting:

  • If Release Backflush Components is enabled:

    • Supply type push components are considered in the pick release and not backflushed

    • Supply type pull components are considered in the pick release and are backflushed

  • If Release Backflush Components is disabled:

    • Supply type push components are considered in the pick release and not backflushed

    • Supply type pull components are not considered in the pick release, but are backflushed

    See: Component Picking, and Supply Types

• Allow Quantity Changes During Backflush

  Enables changes to the transaction quantity - therefore Bill of Material required quantity default is not used. This provides the ability to over or under issue pull components when lot or serial entry is required for assembly moves and completions. This functionality is also available for work order-less completions when using Oracle Mobile Supply Chain Applications. See: Backflush Supply Subinventories and Locators

Intraoperation Steps Parameter

Determines which intraoperation steps are enabled in your WIP routing operations. The options are Queue, Run, To Move, Reject and Scrap. See: Intraoperation Steps.

The Queue intraoperation step is automatically enabled for all operations and cannot be disabled. The To Move intraoperation step, even if disabled here, is automatically enabled for the final operations in routings so that assemblies can be completed into inventory.

Outside Processing Parameters

An outside processing operation is an operation that contains an outside resource linked to an outside processing item. The following parameters affect outside processing functionality:

• 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 you create discrete jobs and repetitive schedules. You first define the status on the Shop Floor Statuses window, and it then appears on the list of values for this parameter. See: Defining Shop Floor Statuses You then can assign the status to operations that have PO Move resources assigned to them (but not those assigned PO Receipt). Only no move statuses, those statuses which are not Allow Moves enabled, can be selected. See: Assigning and Viewing Shop Floor Statuses

  This status ensures that assembly moves from an outside processing resource operation can only be launched by the receipt of a purchase order in Oracle Purchasing. This ensures that the same number of assemblies are moved into and out of an outside processing resource operation. Problems in tracking work in process and cost variances are thus avoided. See: Requisitioning Outside Processing Items

• Requisition Creation Time

  Determines whether purchase requisitions are created for outside processing operations automatically or manually, and when in the manufacturing process they are created.

  • At Job/Schedule Release

    Automatically creates purchase requisitions for all outside processing operations on a job or schedule (except non-countpoint/non- autocharge operations), when the job or schedule is released. Creating requisitions at job and schedule release makes it possible to create and release purchase orders to suppliers in advance.

  • At OSP Operation: Automatically creates purchase requisitions when you move assemblies into the Queue intraoperation step of an outside processing operation. This is the parameter's default value. If the outside processing operation is the first operation of the job or repetitive schedule, a requisition is created at that operation when the status of the job or schedule is changed to Released.

  • Manual

    Requires you to manually create purchase requisitions in Oracle Purchasing. This option allows you to automatically charge outside processing resources at an operation, but does not link the creation of the requisition to either the creation or processing of the job or schedule.

    Note: For lot based jobs in Oracle Shop Floor Management, set this is parameter to At OSP Operation. Multiple paths are available in a network routing, and the outside processing operation can change for each manufacturing run.

• Requisition Status at Creation

  This parameter controls the status type inserted into the PO Requisition interface table.

  • Approved: The PO Requisition interface table is populated with the status Approved. No matter whether approval process is automatically initiated or not, the requisition is approved.

  • Incomplete: Requisitions are created with initial status of Incomplete and depending on other settings, approval process can automatically be initiated which changes the requisition status to In-Process, Pre-aprpoved, or Approved

• Job Roles for Notifications

  • Production Scheduler

    Associates an employee with the Production Scheduler job role on outside processing workflow notifications. The production scheduler receives notifications when there are no purchase orders for outside processing items, when outside processing assemblies have been shipped, or when they will not be shipped.

  • Shipping Manager

    Associates an employee with the Shipping Manager job role on outside processing workflow notifications. The shipping manager receives a notification when intermediate assemblies are ready to be shipped to a supplier for outside services. The employee associated with this role receives all notifications for all jobs that have an outside processing operation.

• Job Change Controls for Purchasing Documents

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

• Need-By Date Tolerance

  Controls Need-By date using an early and late day tolerance value. These values are used by the Update OSP Need-by Date concurrent program. If the concurrent program is not submitted, these values are ignored. The concurrent program initiates the workflow for automatic job date changes when the number of days set in the Days Early field and Days Late field is exceeded. See: Changing the Need By Date

Scheduling Parameters

This parameter is used to include resource factors in scheduling calculations.

• Include Resource Efficiency (check box)

  This check box provides the option to use resource efficiency in scheduling calculations; it affects both constraint-based and infinite scheduling. This factor influences resource elapsed time calculated during scheduling. Values of less than 100 percent elongate lead time. Resource efficiency is always considered in lead time calculations.

• Include Resource Utilization (check box)

  This check box provides the option to use resource utilization in scheduling calculations; it affects both constraint-based and infinite scheduling. This factor influences resource elapsed time calculated during scheduling. Values of less than 100 percent elongate lead time. Resource utilization is always considered in lead time calculations.

• Simulation Set

  The Simulation Set field enables you to adjust resource capacity. Simulation sets are used to link resource changes to available resource capacity for scheduling and planning. They are defined on the Simulation Sets window. If the Use in Scheduling field is checked for particular simulation sets, capacity moderations associated with that set are used when scheduling jobs.

  When you assign resources to departments, you can use simulation sets for capacity modifications by defining them on the Capacity Changes window in Oracle Bills of Material.

See:

Assigning Resources to a Department

Detailed Scheduling

Overview of Resource Requirements

Calculating Manufacturing Lead Times

Manufacturing Lead Time Computations.

Mobile Parameters

The following parameter is set only if you are using Oracle Mobile Supply Chain Applications. This value must be set if you are entering scrap transactions.

• Default Scrap Account

  The Default Scrap Account value is used for scrap transactions. You can either enter an account number, or select an alias from the list of values. An alias is an easily recognized name or label representing an account.

  Note: This account number is only used in Oracle Mobile Supply Chain Application scrap transactions. It is not used in standard Work in Process scrap transactions.

  Transaction Processing Mode

  Used to control mobile processing, your choices are either:

  • Online: Transactions are processed while you wait, and control is returned when the transaction processing is completed.

  • Background: Transactions are processed on a periodic basis, and control is returned immediately.

• Resource, LPN, and serial tracking transactions ignore this parameter:

  • Resource transactions are always processed in Background mode

  • LPN transactions (including LPN completions, LPN work order-less completions, and LPN flow transactions) are always processed in Online mode

  • Mobile serialized transactions are always processed in the Online mode

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. See: Serial Number Tracking Throughout Manufacturing, and Associating and Modifying Serial Number Job Information

• Default Serialization Start Operation

  Determines the job operation where tracking of the serial number begins. Choices 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

  Determines if serial numbers are automatically generated and associated with a job is created and released. The job start quantity determines the number of serial numbers created. The values are:

  • On Job Release: Serial numbers are automatically generated and associated with a job when it is released.

  • Never: Serial numbers are not automatically generated and associated with a job at release. Use parameter Auto Reserve Serial Numbers on Job Completion for another option for associating serial numbers.

• Auto Reserve Serial Numbers on Job Completion

  Enables you to reserve serial numbers after job completion. If this parameter is checked; you would then manually enter the serial number for the serialized assembly. Completed serialized assemblies can be reserved as supply sources using the Item Reservation window in Oracle Inventory. A reservation record is created by selecting and reserving specific serialized assemblies against a sales order line. See: Item Reservations

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

Other Parameters

The following parameter is used to set features for material availability checking, overcompletions, and component pick release.

• Component ATP Rule

  Determines which ATP Rule is used as the default when checking the material availability of component requirements. You can enter any user-defined ATP rule. See: Viewing Component ATP Information and See: Defining ATP Rules, Oracle Inventory User's Guide.

• Default Overcompletion Tolerance % (percent)

  Determines the percentage of assemblies that you can over-complete on all jobs and schedules.

• Default Pick Slip Grouping Rule

  This field sets the default Pick Slip Grouping Rule displaying on the Component Pick Release window. Grouping rules are used each time you run component pick release; resulting tasks are grouped based on the rule. The grouping rules are defined on the Pick Slip Grouping Rules window in Oracle Inventory. See: Using the Component Pick Release Window

• Default Plan Tasks

  This parameter is used only by Oracle Warehouse Management enabled organizations. It determines the default Plan Tasks value displaying on the Component Pick Release window. The choices are:

  • Enabled: Pick tasks are created, you can choose the time to release the tasks using the concurrent program.

  • Disabled: Pick tasks are created and released when you choose Release on the Component Pick Release window.

  See: Using the Component Pick Release Window