Non-standard jobs are similar to standard jobs, however, there are noteworthy differences including:
Non-standard jobs are more flexible than standard jobs. Because of this they can be used to manage such varying activities as rework, field service repair, upgrades, disassembly, maintenance, engineering prototypes, and other miscellaneous projects.
Oracle planning products do not create planned orders or reschedule recommendations for non-standard jobs. You must manually define and reschedule non-standard jobs. However, if a non-standard job is assigned an assembly bill of material, a routing, or both, planning considers the job's material requirements as demand and its assemblies as supply.
Oracle planning products do not deduct scrapped assemblies from the MRP net quantity, or deduct the MRP net quantity by the item shrinkage rate for non-standard jobs. As such, you must identify planned assembly shrinkage by entering an MRP net quantity that is less than the job quantity. See: Shrinkage Rate, Oracle MRP User's Guide
Non-standard expense jobs are period costed and are not subject to cost updates, whereas standard discrete and asset type non-standard jobs are costed when closed and are automatically revalued by the cost update. Non-standard discrete jobs do not earn overhead on completion. Instead material overhead at completion is posted directly to the subinventory material overhead account. See: Discrete Job and Repetitive Schedule Costs.
Work in Process does not implement engineering change orders (ECOs) on non-standard jobs. See: ECO Implementation by Status
You can use a bill and routing from another assembly. For example, you can set up a standard upgrade routing to use for a group of assemblies.
You can define bill of material loops, that is, you can define the assembly itself as a requirement on its bill. This is useful for upgrade, disassembly, and repair activities.
The WIP Mass Load program calculates start and completion dates in non-standard discrete jobs differently than discrete jobs. For non-standard discrete jobs, with operations and resources:
If the Allow Explosion flag is set to Yes, either the start or completion date is used if the other date is null.
If the Allow Explosion flag set to No, and values are provided for both start and completion dates, the job is rescheduled from completion date (that is, it is backward scheduled).
If the Allow Explosion flag set to No, and either start or completion date is provided, the WIP Mass load program fails because the other date cannot be derived.
The following table illustrates the differences between non-standard and standard discrete jobs.
| Job Field Values | Standard Discrete Job | Non-Standard Discrete Job |
|---|---|---|
| Name | Required | Required |
| Type | Required | Required |
| Description | Optional | Optional |
| Assembly | Required | Optional. Enter if you want to perform move and/or completion transactions. |
| Job Class | Required | Required |
| Status | Required | Required |
| Quantity | Required | Required. You can enter 0. Enter a positive number if you want to perform move and/or completion transactions. |
| MRP Net Qty | Required. Defaults from Quantity. | Required. Defaults from Quantity. If you do not enter an assembly then you cannot enter a value in this field. |
| Start Date | Required | Required. If a routing exists for the job, then you can enter either a start or a completion date. Otherwise, you must enter both a start and completion date. |
| Completion Date | Required | Required. If a routing exists for the job, then you can enter either a start or a completion date. Otherwise, you must enter both a start and completion date. |
| Firm | Required. Defaults to Yes if item is MPS planned. Otherwise, defaults to No. | You cannot enter a value in this field. Defaults to No. |
| Lot Number | Optional | Optional |
| Routing Reference | You cannot enter a value in this field. | Optional. Enter a value if you want to perform job scheduling based on a routing. |
| Alt. Routing | Optional | Optional |
| Revision | Optional | Optional. You must enter a value in this field if you have a routing for the assembly. |
| Revision Date | Optional | Optional. You must enter a value in this field if you have a routing for the assembly. |
| Completion Sub. | Optional | Optional |
| Completion Locator | Optional | Optional |
| Bill Reference | You cannot enter a value in this field. | Optional. Enter a value if you want to automatically create material requirements based on a bill of materials. |
| Alt. Bill | Optional | Optional |
| Revision | Optional | Optional. You must enter a value in this field if you have a bill for the assembly. |
| Revision Date | Optional | Optional. You must enter a value in this field if you have a bill for the assembly. |
| Supply Type | Required. Defaults to Based on bill. | Required. Defaults to Based on bill. |