Saranraj Rajakumar Oracle Apps Blog: Job Order Process

Job Order Status

1. Unreleased - The job is not released for transaction activity. You can update but cannot transact against it.

2. Released - The job is available for production and can be transacted against. The job quantity is moved to the Queue of the first routing operation.

3. Complete - The job is completed but accepting transactions and charges. Jobs are automatically updated to this status when the quantity completed into inventory equals the job quantity.

4. Complete No Charges - The job is complete and accepting no further activity.

5. On Hold - You can update the job but cannot transact against it.

6. Cancelled - The job was cancelled before completion.

7. Closed - The job is closed and accepting no further activity. Job are automatically updated to this status upon successful completion of the job close process.

Process Overview

1. Job Order Creation

2. Job Order Release

3. Move Transactions

4. WIP Completion

5. View Material Transactions

6. WIP Valuation Summary

7. Close Job Order

Transaction Process Flow

1. Job Order Creation

Navigation: Work in Progress: Discrete Jobs

Select the inventory organization

Click on new to create the Job Order

Job Order number will be created automatically. Enter the assembly (Finished Good)

Enter the FG Quantity to be produced out of this job order.

Enter the Start Date and End Date to perform the job order activities.

Save the Transaction

Click on components to find the component details ( Raw Materials) which are going to be consumed from the inventory to prepare the finished good.

Click on the Operation to find the list of operation to be performed against this job order.

Click on Resources to view the resource details

2. Job Order Release

Navigation: Work in Progress: Discrete Jobs

Click on Tools and Select the Change the status

Select the Released option to change the status from Unreleased to Released Status.

Job Order Released.

3. Move Transaction

Navigation: Work in Progress: Move Transactions :Move Transactions

Steps are used to control move and resource transactions within and between operations and to track assemblies within operations.

1. Queue - Assemblies are waiting for you to perform work on them. Queue is the default step of the first operation.2. Run - Assemblies in the Run intraoperation step are ready to be worked on.3. To Move - Assemblies in the To move intraoperation step of an operation have been completed and are waiting to be moved to the next operation.

Example: Incase if we have multiple operation then once the 10 operation is complete we can move to 20 operation referring the below screenshot. In our scenario we have only one operation which is 10 so once moving 10 operation from queue to run and then from run you can directly To move by selecting the transaction type as completion.4. Reject - Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped.

5. Scrap - Assemblies in the Scrap intraoperation step are considered unusable. This step is for those assemblies whose yield loss you want to consider as a variance on the discrete job or repetitive schedule. You can incur this variance immediately by entering a scrap account as you move assemblies into this step.

Note:

Assemblies are considered incomplete at an operation if they are in the Queue or Run intraoperation steps. Assemblies are considered complete at an operation if they are in the To Move, Reject, or Scrap intraoperation step. When assemblies are completed at an operation, the system automatically back flushes Operation Pull components and charges resources.

4. WIP Completion

Navigation: Work in Progress: Move Transactions :Move Transactions

Once the job is released the initial step will be under queue.

Select the Transaction Type as “Complete” and perform the move operation by entering the completed quantity. Save the transaction.