A number of features are available when defining discrete jobs manually including:

• Defining standard, non-standard, and project jobs

• Assigning bills and routings to standard discrete jobs to create material requirements, schedule operations, and create resource requirement

• Assigning alternate bills of material and alternate routings for standard discrete jobs

• Assigning bill of material references and routing references to non-standard discrete jobs to create material requirements, schedule operations, and resource requirements

• Attaching illustrative or explanatory files in the form of text, images, word processing documents, spreadsheets, and video

After saving a job, you can access the Components and Operations windows to view the details of the job, including its material requirements, operations, and operation material and resource requirements. You can enter a subjective completion percentage on any job operation. The system uses these entries to calculate the percent complete for the entire job. See: Adding and Updating Operations

About Attachments

Creating a Bill of Material

   To define a discrete job:

1. Navigate to the Discrete Jobs window. The Discrete Jobs Summary window appears

2. Choose New to display the Discrete Jobs window.

   You can define discrete jobs one-at-a-time in the Discrete Jobs window. This method is described below. You can, however, also define several jobs simultaneously using the Discrete Jobs Summary folder window.

   Note: The following nine fields cannot be accessed in the Discrete Jobs Summary folder window even if included in your user folder: bill and routing Alternates, bill and routing Revisions and Revision Dates; Completion Subinventory and Locator; and Supply Type. If you need to change the values that are defaulted into these fields, navigate to the Discrete Jobs detail window.

3. Enter or generate the Job name.

   You can generate a default Job name by choosing Apply Default Job Name from the Tools menu or by simply pressing the tab key. If you do enter the job name, it must be unique and alphanumeric.

   Note: Default job names can only be automatically generated by the automatic sequence generator if a prefix has been specified for the WIP:Discrete Job Prefix profile option.

4. Select the job Type, either Standard or Non-Standard. See: Standard Versus Non-Standard Discrete Jobs.

5. If defining a standard discrete job, select the job Assembly.

   The assembly is the item you are building. If a primary bill of material, primary routing, or both exist for this assembly, they are defaulted.

   You cannot select an assembly that has a primary routing that is Flow related. If you do, a warning is displayed and you are prompted to enter another routing designator.

   See: Creating a Flow Routing.

   Assemblies are optional for non-standard discrete jobs, however, you must enter them for non-standard discrete jobs with routings if you want to track shop floor move and resource transactions.

   If you set the WIP:See Engineering Items profile option to Yes, you can define jobs for engineering items.

   Note: If you are defining a job for an ATO sales order, you must enter an ATO item.

   Note: You can define discrete jobs for assemblies that do not have components and for assemblies that have components with disable dates less than or equal to the current date.

6. Select the accounting Class.

   See: WIP Accounting Class Defaults, Discrete Accounting Classes, and Accounting Class Defaults on the Discrete Jobs Window

7. Select the job Status.

   When you define a job, its status defaults to Unreleased but can be changed to Released or On Hold. See: Discrete Job Statuses.

8. Check the Firm check box to firm your job. You cannot firm a non-standard discrete job.

   Firming a discrete job prevents MRP from suggesting rescheduling and replanning recommendations when changes to supply or demand occur. If replanning is required, the MRP planning process creates new jobs to cover the new demand. See: Firm Order Planning, Oracle MRP User's Guide.

   To define job quantities:

1. Enter the job Start quantity.

   Standard discrete jobs must have a start quantity greater than zero. When you enter a start quantity for jobs with bills and routings, the component material requirements, department schedules, resource load, and job start and end dates are all determined automatically.

   For non-standard jobs, if you enter a start quantity of 0 and specify a bill of material reference, the corresponding bill is exploded but material requirements equal to 0 are created. To perform move and completion transactions for a non-standard job, the start quantity must be greater than zero.

   Note: If you link a job to an ATO sales order, the start quantity defaults from the sales order. If you link several sales orders to a single job, the order quantities are totalled and the start quantity is automatically updated.

2. Enter the MRP Net quantity.

   • The MRP net quantity is the number of assemblies that MRP considers as supply on the scheduled completion date.

   • For items with shrinkage rate define, the supply quantity considered by Planning will be [MRP Net - completed quantity - scrapped quantity]* (1 - shrinkage rate).

   • For standard and non-standard discrete jobs with assemblies, the MRP net quantity is derived from the job start quantity. For non-standard discrete jobs without assemblies, the default is zero.

   • On standard jobs, do not use MRP net quantity to identify planned shrinkage due to operation yield loss. The planning processes automatically deduct scrapped assemblies from the quantity as you scrap. Therefore, reducing the MRP net quantity and scrapping assemblies double counts job scrap.

   • You can use MRP net quantity to identify planned shrinkage due to operation yield loss on non-standard jobs. Planning does not include quantities scrapped or the item shrinkage factor in determining available supply from a non-standard job.

   See: Shrinkage Rate, Oracle MRP User's Guide

   To schedule a discrete job with a routing:

1. Enter or select either the Start or Completion date and time.

   If you enter a start date and time the completion date and time are automatically forward scheduled based on the assembly's routing. Similarly, if you enter a completion date, the start date and time are automatically backward scheduled based on the assembly's routing. You can enter a past due start date to forward schedule a job that should have started before the current date. You cannot enter a start date and time greater than the completion date and time.

   You can use the start date of the job to default bill and routing revisions and revision dates. If a start date is not entered, bill and routing revisions and revision dates default based on fixed and variable lead times of the assembly.

   To schedule a discrete job without a routing:

1. Enter or select either the Start and/or Completion date and time.

   If you enter only one date and time and your job type is standard, the missing date and time is calculated using the fixed and variable lead time of the assembly. If the assembly has both a fixed and variable lead time, the lead time for the job is calculated as job quantity times variable lead time plus fixed lead time. If you enter only one date and time and your job type is non-standard, the other dates and times are calculated using the fixed and variable lead time of the routing reference.

   If your job is non-standard and has a routing reference, the fixed and variable lead times of the routing reference are used instead of the assembly lead time. If your job is non-standard and you specify no routing reference, you must enter both dates and times.

   Note: You can use the WIP:Default Job Start Date profile option to specify whether the start date for a job defaults to the current date and time or does not default at all.

   To assign a bill of material reference to a non-standard discrete job and/or an alternate bill of material/revision to a standard discrete job:

1. On the Bill tab, select the bill of material Reference if defining a non-standard discrete job.

   Bill of material references are used to create material requirements for non-standard discrete jobs, however, they are not required. Instead, you can define the job without material requirements, then customize it by adding only those material requirements that are required. See: Adding and Updating Material Requirements.

2. Select the Alternate bill of material. See: Primary and Alternate Bills of Material.

   You can select an alternate bill if alternates have been defined for the assembly you are building. If the WIP:See Engineering Items profile option is set to Yes, you can also select engineering items as alternates.

   For non-standard discrete jobs, you can enter any alternate defined for the bill Reference specified.

3. Select the bill of material Revision.

   The bill revision and date determines which version of the bill of material is used to create job component requirements. The start date of a standard discrete job can be used to default the bill revision and revision date. If a start date is not selected, the revision and revision date are derived based on fixed and variable lead times of the assembly.

   You can update the bill revision of a standard discrete job as long as the job remains unreleased. You can update the bill revision for standard bills or alternate bills. See: Item and Routing Revisions.

   You can explode item revisions that have associated ECOs with Release, Schedule, and Implement statuses. If you set the WIP:Exclude ECOs profile option to None, you can also explode revisions for ECOs that have an Open status. See: .

   If you are building a non-standard job and the Revision Control attribute for the assembly item is set to Yes, the revision of the bill reference must be valid for the assembly. See: Defining Items and Inventory Attribute Group.

   You can create an ECO for a job and specify a cumulative quantity, a range of jobs, or implement changes for specific lots. For example: Job1 quantity is for 100 units of an item. If an ECO is created specifying a cumulative quantity of 50, the existing job is divided into two jobs and the ECO is implemented on the remaining 50 units. See: Defining ECO Revised Items, Oracle Engineering User's Guide

4. Select the bill Revision date and time.

   You can select a bill revision date other than the one that is derived for standard bills, alternate bills, or bill references. You can update this date as long as the job remains Unreleased.

5. Select the Supply Type.

   The supply type defaults to Based on Bill. This supply type indicates that component requirements are supplied based upon their individual supply types. You can override this default by choosing one of the following supply types: Push, Assembly Pull, Operation Pull, Bulk, or Supplier. See: Supply Types.

   To assign a routing reference to a non-standard discrete job and/or an alternate routing/revision to a job:

1. On the Routing tab, select the routing Reference if defining a non-standard job.

   Routing references can be used to create routings (operations and resource requirements) for non-standard discrete jobs, but are not required. You can optionally define non-standard jobs without routings, then customize them by adding only those operations that are required. See: Adding and Updating Operations.

   Note: You can assign any routing to a non-standard job, including one that does not match the assembly you assigned, using the routing reference.

2. Select the alternate Routing.

   You can select an alternate routing if alternates have been defined for the assembly you are building. If the WIP:See Engineering Items profile option is set to Yes, you can select engineering routings as alternates. See: Profile Options and Primary and Alternate Routings.

   For non-standard job, you can enter any alternate defined for the routing reference specified.

3. Select the routing Revision. See: Item and Routing Revisions.

   The start date of a standard discrete job can be used to derive the routing revision and revision date. If a start date is not selected, the revision and revision date are derived based on fixed and variable lead times of the assembly.

   You can update the routing revision as long as the job remains unreleased. For standard discrete jobs, the routing revision determines which version of the routing is used to create the job routing (operations and resource requirements). For non-standard discrete jobs, the routing reference determines the routing for the job. The revision you select for the non-standard job applies to the routing reference, not the assembly.

4. Select the routing Revision Date and time.

   You can update routing revision dates for standard routings, alternate routings, or routing references. You can update routing revision dates as long as the job remains unreleased.

5. Select the completion Subinventory and, if required by the subinventory, Locator.

   Assemblies are completed into or returned from this subinventory and locator. If the assembly has a routing, the completion subinventory and locator are defaulted from the routing but can be overwritten. For non-standard discrete jobs, you can select completion subinventories and locators only if you specified an assembly.

   If the Oracle Inventory INV:Allow Expense to Asset Transfer profile option is set to Yes, you can select an expense subinventory. See: Inventory Profile Options.

   Note: You can override the completion subinventory and locator you specify here when you complete or return assemblies using the Completion Transactions window.

   Note: You must specify a completion subinventory and locator if you plan to complete or return assemblies using the Move Transactions window since the subinventory and locator specified here are automatically used for those transactions.

   Project locator logic is used if you are assigning a completion subinventory to a project job. See: Locators in Project Manufacturing

   To assign a demand class, kanban identifier, lot number, description, and overcompletion tolerance type and tolerance value:

1. On the More tab, select the Demand Class.

   You can select any enabled and active demand class. Demand classes are not required. See: Overview of Demand Classes, Oracle MRP User's Guide and Creating Demand Classes, Oracle MRP User's Guide.

2. If the assembly is under lot control, select a Lot Number.

   Lot numbers are automatically assigned based on how the Default Lot Number Type parameter is set, either by job name or based on Inventory lot number rules, but can be overwritten or deleted. See: Discrete Parameters.

   When you complete or return assemblies using the Completion Transactions window, job lot numbers entered here are automatically defaulted but can be changed. Job lot numbers must be entered here before you can move and complete or move and return lot controlled assemblies using the Move Transactions window.

3. Enter the job Description.

   Descriptions can be used to identify jobs on standard reports. They can be up to 240 characters of alpha numeric text. They are optional.

4. Enter the Kanban reference.

5. In the Overcompletion region, select the Tolerance Type. The options are Percent or Amount.

6. Enter the Overcompletion Tolerance Value that corresponds to the Overcompletion Tolerance Type selected.

   • If the Overcompletion Tolerance value is set as zero (0), you can only complete the job start quantity. Overcompletions are not allowed.

   • If the Overcompletion Tolerance value is null , the system honors the value set in the Default Overcompletion Tolerance % parameter in the Other tabbed region of the Work in Process Parameters window. If that value is also null or 0, overcompletions are not allowed.

   To define schedule group and project information:

1. On the Schedule Group, Project tab, select the Schedule Group.

   You have the option to assign discrete jobs to any active schedule group. See: Defining Schedule Groups

2. Enter a Build Sequence identifier. See: Build Sequencing.

3. Select a production Line.

   You can select any active production line. Production lines are optional for discrete jobs. They are not used for scheduling or transactional purposes. However, if you do select a production line, the combination of schedule group, build sequence, and production line must be unique.

4. Select a Project and, if required, a task.

   You can only select a project if the current organization's Project References Enabled parameter is set in Oracle Inventory. You must select a task if the Project Control Level parameter is set to Task and you have entered a project. See: Organization Parameters Window and Creating Projects.

5. Enter the Unit Number. This enables you to associate an end item model/unit effectivity number with the item.

   You must have Oracle Project Manufacturing installed, the item must be under model/unit effectivity control, and you must have a model/unit number associated with it to enable this functionality. If the item is not under model/unit number control, this field is disabled. See: Model/Unit Effectivity, Oracle Project Manufacturing Implementation Manual.

   Note: You can update unit effectivity through Mass Load for discrete jobs that are unreleased and project related.

6. Save your work.

   If you are defining a discrete job, you must save the job before viewing component requirements and operations for that job.

   To change a saved job:

1. See: Overview of Changing Discrete Jobs.

   To view pending job information:

1. You can determine if there are any pending transactions or documents for a job using the Pending Actions window. See: Viewing Pending Job Transactions.

   To view operations:

1. Choose Operations The Operation window appears and the job's operations are displayed. You can optionally view the components required at a selected operation by choosing Components. See: Viewing Job and Schedule Operations.

   To view component requirements:

1. Choose the Components button. The Material Requirements window appears and the job's components are displayed. See: Viewing Component Requirements and Viewing Component ATP Information.

   Note: When no routing exists, all components default to operation sequence of 1.

   To view outside processing workflows:

1. See: Outside Processing Workflows.

   To link an ATO sales order to a standard discrete job:

1. See: Linking ATO Sales Orders and Discrete Jobs.

   Note: The Sales Order button is disabled if you are changing a production kanban job.