|
|
|
|
|
|
|
|
| Previous | Next | Contents | Index | Glossary | Library |
There are four resource charge types:
WIP Move resources with a basis of Item are charged upon completion of each assembly in the operation. WIP Move resources with a basis of Lot are charged upon completion of the first assembly at the operation. In both cases, the amount charged is based upon the resource's usage rate or amount multiplied by the resource's standard cost at the time of the transaction.
You can reverse a WIP Move resource charge by moving assemblies backward from Queue or Run of the current operation to Queue or Run of any prior operation, or by moving assemblies from the To move, Reject, or Scrap intraoperation steps backward to the Queue or Run intraoperation steps of the same operation, or to any intraoperation step of any prior operation.
WIP Move resource charges are applied on a first in-first out basis to multiple repetitive schedules on a line based on how the assemblies being moved are allocated. For example, if you have 2 released schedules for 100 assemblies each and you move 150 assemblies, the system automatically allocates 100 to the earliest schedule and 50 to the next.
Attention: You can control whether the Resources button appears in the Move Transactions window using function security. See: Security Functions.
When you charge Manual resources, you must enter the actual resource units applied rather than autocharging the resource's usage rate or amount based on the move quantity. You can charge Manual resources using that resources unit of measure or any valid alternate unit of measure. If the resource is a person-type resource, you can enter an employee number. Manual resources for repetitive schedules are charged to the first open repetitive schedule on the line.
You can create ad hoc resource requirements as you charge resources. Ad hoc resource requirements an be created for any resource that is defined for the department that is associated with the operation.
You can reverse Manual resource charges by entering negative resource units. For example, if you intend to charge 8 hours but mistakenly enter 10, you can correct the error by entering an additional resource charge transaction for -2 hours.
When you receive assemblies back from an outside processing supplier in Oracle Purchasing, PO Receipt or PO Move resources, also know as outside processing resources, are automatically charged at the standard or the actual rate. If the receipt involves a PO Move resource, the assemblies are also moved from the Queue or Run intraoperation step of the outside processing operation into the Queue intraoperation step of the next operation or into the To move intraoperation step if the outside processing operation is the last operation on the routing.
Warning: If the Move Transaction manager in Oracle Inventory has not been launched, the assemblies move transactions are not processed. See: Open Move Transactions Interface.
You can track the progress of outside processing assemblies that have been sent to a supplier by moving assemblies within the outside processing operation. You can optionally disallow move transactions from an outside processing step unless they are launched by a purchase order receipt. You can do this by using the Shop Floor Status for PO Move Resource parameter. See: Shop Floor Statuses.
If you return assemblies to an outside processing supplier or enter correcting receipts for an outside processing supplier, Oracle Purchasing creates reversing charges for PO Move and PO Receipt resources associated with the outside processing operation. If the return or correction involves a PO Move resource, the assemblies are also moved from the Queue intraoperation step of the operation immediately following the outside processing operation into the Queue intraoperation step of your outside processing operation. If the outside processing operation is the last operation on the routing, the assemblies automatically move from the To move intraoperation step to the Queue intraoperation step.
PO Move resource transactions are applied to multiple repetitive schedules on a line based on how the assemblies being moved are allocated. Moves are allocated across multiple repetitive schedules on a first in-first out basis. PO Receipt resource transactions are allocated across schedules on a first in first (FIFO) out basis.
For example, if you have 2 released schedules for 100 assemblies each and you move 150 assemblies, the system automatically allocates 100 to the earliest schedule and 50 to the next.
| Previous | Next | Contents | Index | Glossary | Library |