The following information provides you with a description of each Work in Process profile option and its values.
Additional Information: Processing for move related transactions (that is: move, scrap, reject, move and complete, and return and move) enable the parent assembly record to process even if backflush records fail.
In background processing for standard completion and return transactions, once the move completion manager picks up a record for processing, backflushing occurs in the same commit cycle. This prevents the possibility of processing transactions if backflushing fails.
Controls material processing of assembly completion, assembly return, and assembly completion backflush transactions initiated using the Completion Transactions window. Available values are listed below:
| Background processing | When you save a completion transaction, control is returned to you immediately. Assembly completions and returns and their associated backflush transactions are processed on a periodic basis. |
| Concurrent processing | When you save a completion transaction, a concurrent process is spawned and control is returned to you immediately. The concurrent request number, representing the concurrent process executing the material transaction for the job or repetitive schedule, is displayed. |
| Online processing | When you save a completion transaction, the transaction is processed while you wait and control is returned once transaction processing is completed. If you set TP:WIP:Completion Transactions Form profile option to Background processing, this profile option is disregarded. If you are using average costing, and the TP:INV: Transaction Processing Mode profile option in Oracle Inventory is set to Form level processing, you must set this profile option to Online to ensure that transactions are processed in the proper sequence. |
Determines whether completion transactions are processed online or in the background when transacting assembly completions using the Completion Transactions window. A completion transaction includes updating the completion quantity of a job or repetitive schedule, identifying the component items and quantities to be backflushed, and transferring reservations from the final assembly order to appropriate sales order lines and deliveries. This profile is only used if the Inventory profile option, TP:INV:Transaction Processing Mode, is set to From Level Processing. Available values are:
| Background processing | When you save a completion transaction, control is returned to you immediately. Completion transactions are then processed on a periodic basis. |
| Online processing | When you save a completion transaction, it is processed while you wait and control is returned once transaction processing is completed. If you are using average costing, and the TP:INV:Transaction Processing Mode profile option in Oracle Inventory is set to Form level processing, you must set this profile option to Online to ensure that transactions are processed in the proper sequence. |
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.
You can only enter a Sales Order name if you have an ATO sales order linked to a job.
Indicates the level the completed configuration needs to be reserved. Available values are:
| Item | The reservation transferred to Inventory does not include subinventory and locator information. This is organization level reservation. |
| Item/Subinventory | The reservation transferred to Inventory includes subinventory and locator information This is Detail reservation. |
Controls the processing of component issue and return transactions entered in the WIP Material Transactions window. This profile is only used if the Inventory profile option, TP:INV:Transaction Processing Mode, is set to From Level Processing. Available values are:
| Background processing | When you save a material transaction, control is returned to you immediately. Transactions are then processed on a periodic basis. |
| Concurrent processing | When you save a material transaction, a concurrent process is spawned and control is returned to you immediately. The concurrent request number representing the concurrent process executing the issue or return transactions for the job or repetitive schedule is displayed. |
| Online processing | When you save a material transaction, the transaction is processed while you wait and control is returned once transaction processing is completed. If you are using average costing, and the TP:INV: Transaction Processing Mode profile option in Oracle Inventory is set to Form level processing, you must set this profile option to Online to ensure that transactions are processed in the proper sequence. |
Determines which field the cursor defaults to when you first enter the WIP Material 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.
You can only enter a Sales Order name if you have an ATO sales order linked to a job.
Determines whether move transactions performed using the Move Transactions window are processed online or in the background. Available values are listed below:
| Background processing | When you save a move transaction, control is returned to you immediately. Transactions are then processed on a periodic basis. |
| Online processing | When you save a move transaction, the transaction is processed while you wait and control is returned once transaction processing is completed. If you have this option set to Online processing, you cannot move more assemblies than are waiting at an operation step. However, if you have this option set to Background processing, you can move any number of assemblies, but validation of the quantity takes place in the background. You can correct and resubmit transactions that have errors using the Pending Move Transactions window. If you are using average costing, and the TP:INV: Transaction Processing Mode profile option in Oracle Inventory is set to Form level processing, you must set this profile option to Online to ensure that transactions are processed in the proper sequence. |
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.
You can only enter a Sales Order name if you have an ATO sales order linked to a job.
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. |
Determines which navigation field is defaulted when you the Resource Transactions window is opened. 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.
You can only enter a Sales Order name if you have an ATO sales order linked to a job.
Controls processing mode for backflush transactions, assembly scrap, move completion, and move return transactions from the Move Transactions window:
| Background processing | When you save a move transaction, control is returned to you immediately. The operation and assembly pull backflush, assembly scrap, move completion, and move return transactions are then processed on a periodic basis. Do not use background processing if you are backflushing lot controlled components that require manual entry of lot numbers either because of insufficient inventory or because the WIP Backflush Lot Selection parameter is set to Manual. See: Lot and Serial Number Backflushing. |
| Concurrent processing | When you save a move transaction, a concurrent process to process the material port of the move transaction is spawned and control is returned to you immediately. The concurrent request number representing the concurrent process executing the move transactions for the job or repetitive schedule is displayed. |
| Online processing | When you save a move transaction, operation and assembly pull backflush, assembly scrap, move completion, and move return transactions are processed while you wait and control is returned once transaction processing is completed. If you set the TP:WIP:Move Transactions profile option to Background processing, the Move Transactions window disregards this profile option for operation pull backflush, assembly scrap, and move completion transactions and performs the material portion of the move transaction in the background. |
Sets processing mode for the Work Order-less Completions window.
| Background processing | When you create a completion transaction, control is returned to you immediately. The transactions are then processed on a periodic basis. |
| Online processing | When you create a work order-less completion, transactions are processed while you wait and control is returned once transaction processing is completed. |
Determines the default for the Scheduled flag in the Work Order-less Completions window.
| Scheduled | The Schedule flag defaults to checked. Use this option if most of your work order-less completions are based upon flow schedules. |
| 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. |
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.
Sets job creation and update mode when defining jobs in the Discrete Jobs window. Available values are listed below:
| Concurrent definition | When you save a job, a concurrent process is spawned and control is returned to you immediately. The concurrent request number representing the concurrent process is displayed. You can view the status of the process in the Concurrent Requests window. The concurrent process updates the job status to Pending Bill Load, and if the bill of materials load succeeds, updates the job status to Pending Routing Load. The process then loads the routing information (if you defined a routing for the bill). If the routing load succeeds, the job status is updated to the choice you specified for the job (Unreleased, Released, or On Hold), and then loads the costing information. When all costing information is loaded, you can update the discrete job information and transact against it. Concurrent definition produces an output report that indicates the job, assembly, relevant dates, and successful completion of each step (bill of materials load, routing load, and costing load). If the concurrent process fails, the status of the discrete job indicates the source of the problem (Failed bill of material load or Failed routing load). If the bill of material or routing load fails you can resubmit the job once you change the job status to Unreleased, Released, or On Hold. |
| Interactive definition | When you save a job, job definition occurs immediately. The bill of material and routing are loaded while you wait and control is returned when the definition process is completed. If you have complex bills of material and long routings, concurrent processing is recommended. |
Enables display of job operations with quantities only in the Scrap and Reject intraoperation step in the Discrete Workstation.
| No | If all the job operations are completed and there is no quantity remaining in the Queue, Run and To Move steps - the work order will not appear in the Discrete Workstation, even if there is existing quantity in the Reject or Scrap step. |
| Yes | If all the job operations are completed, and the only quantities remaining are in the Reject or Scrap step, they will appear on the Discrete Workstation. |
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 planning products. 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.
Indicates whether the MRP Net check box is enabled on the Material Requirements window by default when creating non-standard jobs. This profile applies to jobs that have the following values:
Job Type is Non-standard.
There is a valid value in the bill of material Reference field on the Bill tabbed region of the Discrete Jobs window.
| No | The MRP Net check box is not enabled on the Material Requirements window when creating non-standard jobs, or when components are added to material requirements. |
| Yes | The MRP Net check box is enabled on the Material Requirements windows when creating non-standard jobs, or when components are added to material requirements. |
Determines whether or not outside processing workflows are enabled.
| Yes | All outside processing workflows are enabled. |
| No | No outside processing workflows are enabled. |
Controls which engineering change orders (ECOs) are included when you define jobs and schedules. This profile option also controls whether you can select revisions associated with open ECOs in the WIP Material Transactions window. See: ECO Statuses in the Oracle Engineering User's Guide.
Choices include:
Open: ECOs with statuses of Release, Schedule, and Implement are considered when you choose a bill of material revision or revision date, and the bill of material is exploded. Open is the default value.
None: Open ECOs are included with the statuses of Release, Schedule and Implement when you choose a bill of material revision or revision date. This enables you to explode item revisions on the bill of material.
All: Only revised item lines with a status of Implemented are considered.
Work Order-less Completions do not consider this profile option.
Provides flexibility to choose whether to create errors or ignore errors and process the transactions when the backflush quantity is less than the quantity of .000005. Choices include:
No: A backflush quantity transaction of less than the quantity of .000005 will create errors and will not be processed.
Yes: A backflush quantity transaction of less than the quantity of .000005 will be processed.
Note: Inventory transactions are not generated for quantities rounded to zero (0).
Controls whether the Requisition Import program triggers the approval process after requisition creation. Values are:
Null or Yes: Requisitions are created in the status of Approved. Another approval process is then launched to automatically approve the newly created purchase order.
No: Requisitions are created in the status of Incomplete. The approval process is not automatically launched to approve a purchase order.
This profile works in combination with the Requisition Creation Time parameter. Regardless of the value selected for this profile, if the parameter is not set to Manual, records are picked up from the Requisition Import interface.
Determines whether you can update the names of existing jobs in the Discrete Jobs window.
Controls whether or not to launch the Requisition Import program for PO Receipt resource transactions. The Requisition Import program is launched for PO move resources depending on the setting of profile option WIP:Enable Outside Processing Workflows. Values are:
Yes: The Requisition Import program is automatically launched for PO Receipt transactions.
No: The Requisition Import program is not automatically launched for PO Receipt transactions.
Determines the default transaction type for the Move Transactions window. If you specify Yes, the transaction type defaults to Complete. Otherwise, the transaction type defaults to Move. Note that you cannot specify that the Return transaction type be used as the default. See: Move Transaction Types.
Determines which subinventories to include when displaying on-hand quantities in the Material Requirements and View Material Requirements windows. Available values are listed below:
| View only nettable subinventories | Include only nettable subinventories when displaying on-hand quantities. |
| View all subinventories | Include all subinventories (nettable and non-nettable) when displaying on-hand quantities. |
Sets rounding for resource usage calculation values. When entry of resource usage values of a routing resource is less than a minute value, this profile enables the value to be rounded to the next minute. This enables resource usage values to be compatible with Advanced Supply Chain Planning calculations.
| Yes | Indicates that resource usage is rounded to the next minute. For example, if resource usage equals 36 seconds, it is rounded to one minute. The lead time calculation is then based on 1 minute instead of 36 seconds. |
| No | Indicates that resource usage is not rounded. |
Determines whether you can define jobs and schedules for engineering items and if engineering items as visible as material requirements.