Previous | Next | Contents | Index | Glossary | Library |
Key | |
You can update the profile option. | |
D, R, P | The profile is applicable to discrete, repetitive, and project manufacturing. |
WO | The profile is applicable to flow manufacturing (work order-less) manufacturing. |
Profile Option | User | System Administrator | Requirements | |||||
User | User | Resp | App | Site | Required? | Default Value | Applies To | |
TP:WIP:Background Shop Floor Material Processing | Required | On-line processing | All | |||||
TP:WIP:Completion Material Processing | Required | On-line processing | D, R, P | |||||
TP:WIP:Completion Transaction Form | Required | On-line processing | D, R, P | |||||
TP:WIP:Completion Transactions First Field | Required | Job | D, R, P | |||||
TP:WIP:Concurrent Message Level | Required | Message level 0 | D, R, P | |||||
TP:WIP:Material Transaction Form | Required | On-line processing | D, R, P | |||||
TP:WIP:Material Transactions First Field | Required | Job | D, R, P | |||||
TP:WIP:Move Transaction | Required | On-line processing | D, R, P | |||||
TP:WIP:Move Transaction First Field | Required | Job | D, R, P | |||||
TP:WIP:Move Transaction Quantity Default | Required | None | D, R, P | |||||
TP:WIP:Operation Backflush Setup | Required | On-line processing | D, R, P | |||||
TP:WIP:Resource Transactions First Field | Required | Job | All | |||||
TP:WIP:Shop Floor Material Processing | Required | On-line processing | All | |||||
TP:WIP:Work Order-less Default Completion | Required | Unscheduled | WO | |||||
WIP:Default Job Start Date | Required | No | D, P | |||||
WIP:Define Discrete Job Form | Required | Interactive definition | D, P | |||||
WIP:Discrete Job Prefix | Required | None | D, P, WO | |||||
WIP:Exclude Open ECOs | Required | Yes | D, R, P, WO | |||||
WIP:Job Name Updatable | Required | Yes | D, P | |||||
WIP:Move Completion Default | Required | No | D, R, P | |||||
WIP:Requirement Nettable Option | Required | View all subinventories | D, R, P, WO | |||||
WIP:See Engineering Items | Required | Yes | D, R, P, WO | |||||
Table 1 - 4. (Page 2 of 2) |
If both of these conditions are met, the move transaction processor processes the assembly move portion of the transaction. How the shop floor material (backflush) portion of the transaction is processed is controlled by this profile. Available values are listed below:
Background processing | When set to background, shop floor material transactions are processed by the inventory transaction processor on a periodic basis. |
Concurrent processing | When set to concurrent, the inventory material transaction processor is launched to process the shop floor material transactions. |
The concurrent request number, representing the concurrent process executing the shop floor material transaction, is displayed. | |
On-line processing | When set to On-line, the move transaction processor processes both the move and shop floor material portions of these transactions. |
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. |
Do not use background processing if you are backflushing lot controlled components that require manual entry of lot numbers. Manual entry could be required 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 material transaction, a concurrent processes is spawned and control is returned to you immediately. |
The concurrent request number, representing the concurrent process executing the material transactions for the job or repetitive schedule, is displayed. | |
On-line processing | When you save a material transaction, the transaction is processed while you wait and control is returned once transaction processing is completed. |
Attention: If you set TP:WIP:Completion Transactions option to Background processing, this profile option is disregarded.
Attention: 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 On-line to ensure that transactions are processed in the proper sequence.
On-line processing is recommended if you are backflushing components under serial number control or manual lot control entry.
Background processing | When you save a completion transaction, control is returned to you immediately. Completion transactions are then processed on a periodic basis. |
On-line processing | When you save a completion transaction, it is processed while you wait and control is returned once transaction processing is completed. |
Attention: 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 On-line to ensure that transactions are processed in the proper sequence.
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.
Message level 0 | Reports errors only. |
Message level 1 | Reports processing activities and errors. |
Message level 2 | Reports and time stamps processing activities and errors. |
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. | |
On-line processing | When you save a material transaction, the transaction is processed while you wait and control is returned once transaction processing is completed. |
Attention: 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 On-line to ensure that transactions are processed in the proper sequence.
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.
Background processing | When you save a move transaction, control is returned to you immediately. Transactions are then processed on a periodic basis. |
On-line processing | When you save a transaction, the transaction is processed while you wait and control is returned once transaction processing is completed. |
Attention: If you have this option set to On-line processing, you cannot move more assemblies than exist in an operation step. However, if you have this option set to Background processing, you can move any number of assemblies, but validates the quantity in the background. You can correct any errors using the Pending Move Transactions window.
Attention: 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 On-line to ensure that transactions are processed in the proper sequence.
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.
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 |
Background processing | When you save a move transaction, control is returned to you immediately. The setup of operation backflushing is processed in the background on a periodic basis. Use this option if automatically assignment of lot numbers is required. |
On-line processing | When you save a move transaction, the setup of operation backflushing is processed while you wait and control is returned once the setup processing is completed. Use this option so that lot number can be manually assigned. |
Attention: If you set the TP:WIP:Move Transactions profile option to Background processing, this profile option is disregarded and executes operation backflush setup in the background.
Attention: You should set this profile to On-line processing if you are backflushing lot, using manual entry, and serial controlled components.
Attention: 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 On-line to ensure that transactions are processed in the proper sequence.
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.
Background processing | When you save a move transaction, control is returned to you immediately. The operation and assembly pull backflush, assembly scrap, and completion 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 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. | |
On-line processing | When you save a move transaction, operation and assembly pull backflush, assembly scrap, and completion transactions are processed while you wait and control is returned once transaction processing is completed. |
Attention: For operation backflushes, assembly scraps and completions, if you set the TP:WIP:Move Transactions or the TP:WIP:Operation Backflush Setup profile option to Background processing, the Move Transactions window disregards this profile option and executes the operation backflush, assembly scraps, and completions in the background.
Attention: 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 On-line to ensure that transactions are processed in the proper sequence.
On-line processing is recommended if you are backflushing components under serial number control or manual lot control entry.
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. |
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. |
Attention: If you have complex bills of material and long routings, concurrent processing is recommended.
Work in Process concatenates this prefix with a value from the sequence WIP_JOB_NUMBER_S to create a default discrete job name.
This profile option also controls whether you can select revisions associated with open ECOs in the WIP Material Transactions window.
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. |
Setting Your Personal User Profile
Previous | Next | Contents | Index | Glossary | Library |