Previous | Next | Contents | Index | Glossary | Library |
Parameters | Required? | Default Value |
---|---|---|
Discrete | ||
Default Discrete Class | Optional | Null |
Default Lot Number | Required | Job Name |
Respond to Sales Order Changes | Required | Always |
Repetitive | ||
Recognize Period Variances | Optional | All Schedules |
Autorelease Days | Optional | 0 |
ATP | ||
Component ATP Rule | Optional | Null |
Average Costing | ||
Default Completion Cost Source | Required | System Calculated |
System Option | Cond. Required | Use Predefined Resources |
Cost Type | Cond. Required | Null |
Auto Compute Final Completion | Optional | No |
Move Transactions | ||
Shop Floor Status for PO Move Resources | Optional | Null |
Require Scrap Account | Optional | Disabled |
Allow Creation of New Operations | Optional | Disabled |
Allow Moves Over No Move Shop Floor Statuses | Optional | Enabled |
Backflush Default | ||
Supply Subinventory | Optional | Null |
Supply Locator | Optional | Null |
Lot Selection Method | Optional | Expiration Date |
Lot Verification | Optional | All |
Intraoperation Steps | ||
Intraoperation Steps | Optional | All are enabled |
Table 1 - 2. (Page 2 of 2) |
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.
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. See: Lot Control and Defining Revision, Lot, Serial Parameters. |
Never | If you implement changes to a sales order in Oracle Order Entry, and that sales order is linked to one or more discrete jobs, the system ignores the sales order change and does not stop the current production for the discrete job. |
Always | If you unassign the configuration item from the sales order using the ATO Configurable Item window in Oracle Order Entry/Shipping and if the linked jobs are Unreleased, then the statuses of the linked jobs are changed to On Hold. See: Linking ATO Configurations. |
When Linked 1 to 1 | If you implement changes to a sales order in Oracle Order Entry, and that sales order is the only sales order linked to a single discrete job, Oracle Order Entry automatically changes the status of the discrete job to On Hold. You can then update it to reflect the changes to the sales order. |
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. |
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.
Additional Information: You can only set these parameters if your current organization has been defined as an average cost organization in the Oracle Inventory Organization Parameters window. See: Organization Parameters Window and Defining Costing Information.
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. | |
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. |
Additional Information: 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.
User 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. |
Moves from, but not to, outside processing steps with this status are disallowed except when the move transaction is 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 Queue at an outside processing step. Problems in tracking work in process and cost variances are thus avoided. See: Requisitioning Outside Processing Items.
If you enter a scrap account as you move assemblies into a Scrap intraoperation step, the system debits this account and credits the job or repetitive schedule elemental accounts at standard through this operation. If you enter a scrap account as you move assemblies out of a scrap intraoperation step, the system credits this account and debits the job or repetitive schedule elemental accounts at standard through this operation. 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 written off as variance.
Additional Information: 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.
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.
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 selected based on their inventory receipt date using the first in-first out (FIFO) method. |
Additional Information: 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.
All | Verify that the lots automatically selected were the ones consumed by the assemblies. |
Exceptions Only | Verify exceptions only. If the lot requirement for the component cannot be filled automatically using the FIFO method, you can assign lots to components manually. |
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.
Setting Up Discrete Manufacturing
Setting Up Repetitive Manufacturing
Setting Up Resource Management
Previous | Next | Contents | Index | Glossary | Library |