Work in Process

Oracle Work in Process is a complete production management system. Work in Process is part of Oracle Applications, an integrated suite of business solutions. Work in Process supports discrete, repetitive, assemble-to-order, work order-less, project or a combination of manufacturing methods. Inquiries and reports give you a complete picture of transactions, materials, resources, costs, and job and schedule progress. Oracle work in process (WIP) records actual production activity. It lets you to report production against discrete jobs or repetitive schedules, or by using work order-less completion transaction. Discrete jobs in WIP(also called Work orders, production orders,or shop orders) represent the production of a specific quantity of a specific item, completed on a specific date. They can be generated by the planning products, creating automatically in response to sales orders(ATO configuration) or created Manually. Discrete jobs define a discrete item to be built and have a fixed quantity, start date, and due date. Repetitive schedules model high volume production of an item on an ongoing basis. They represent a rate of production over a period of time. Repetitive schedules have 4 key dates - the start and completion date and time for the first unit produced on the schedule, and the start and completion date of the last unit. Repetitive schedules model a daily production rate, and the planning process reacts accordingly. Oracle Work in Process Business flow:

WIP Setup

When you log on to the oracle WIP for the first time , you get the below error message So the first setup that you need to do is the WIP parameter setup. Including the WIP parameter there are 12 steps to set up Work in Process, three of which are required. All of the steps are visually depicted on the Work in Process Setup Flowchart

1.1 WIP Supply Types

WHAT: Used to Control how component materials are: supplied to Discrete Jobs planned in Oracle Master Scheduling/MRP and Supply Chain Planning costed in Oracle Cost Management HOW: Assign Supply Types to items defined in Oracle Inventory to components when creating BOMs

WIP Supply Types: Assembly Pull - Components issued to job when completing assemblies - Pulled from the supply subinventory assigned to the component - If a Non-Standard Job, you have an assembly referenced for that job Operation Pull - Components issued to job when completing backflush operations - Pulled from the supply subinventory assigned to the component - CanNOT assign to an assembly without a routing Push

- Issued manually to jobs as required - Can specify the subinventory from which to issue push components - Use 'WIP component issue' from material transaction form to issue the material Phantom - Assigned to BOM component subassemblies and items in Oracle BOM - Components of Phantom subassemblies used as if tied directly to the parent assembly - Do not appear on WIP jobs, as subassemblies they lose their identity and become a collection of their components on the WIP job - When rolling up assembly costs, normally only the material cost under the phantom is rolled up to the parent, not the phantom routing costs. NOTE: Two switches can be set that impacts leadtime and cost rollups. Bulk Can be viewed and displayed on reports Shows Shop Floor requirement but not transacted/backflushed Often used for inexpensive items that are expensed at receipt Can manually issue specific bulk components to a discrete job if desired.

Supplier - Supplier component requirements can be included on bills of material. Requirements for supplier components are created when you define discrete jobs and repetitive schedules in Work in Process. - Supplier component requirements can be viewed and are displayed on reports. They provide information on the component materials that your suppliers provide but need not be transacted. - Supplier components are not backflushed nor do they default when issuing all components for an assembly. You can, however, manually issue specific supplier components to discrete jobs and repetitive schedules.

1.2 WIP parameters

You can use WIP parameters to define modes of operation and to assign default values for various work in process functions. You can only define one set of WIP parameters per organization. 1. Discrete Default Discrete Class Determines which accounting class is used as the default for a Standard Discrete Job. NOTE: Must be entered after WIP Acctg Classes are setup, while rest of WIP parameters must be entered before you can enter WIP Acctg classes. Default Lot Number Type Determines how lot numbers are assigned to discrete jobs. Job Name job lot numbers are based on job name Based on Inventory Rules Job lot numbers are based on the lot number rules you defined in Oracle Inventory.

Respond to Sales Order Changes

Determines whether and how the system responds to changes to configure-to-order (CTO) sales orders and their related discrete jobs. IF a configured item is de-linked from a Sales Order or sales order line placed on hold, you have following options: Never Work Order not placed on hold Always Work Order always placed on hold When linked 1 to 1 Work Order placed on hold if it is the only work order reserved to that sales order 2. Repetitive Recognize Period Variances Determines which repetitive schedule variances are posted to GL when an accounting period is closed. All Schedules Post variances for ALL repetitive schedules Cancelled & Complete-No Charges Only Post variances for repetitive schedules with statuses of Cancelled or Complete-No Charges Autorelease Days Determines the time period within which the system automatically releases the next unreleased schedule after you complete a repetitive schedule. 3. Move Transaction Tab Require Scrap Account Clicked on System debits/credits the applicable account and job. Clicked off Cost of scrap remains on the job until job or period close, at which time it is written off as a variance. Determines whether a scrap account is required when you use the Move Transactions window to move job and repetitive assemblies into and out of the Scrap intraoperation step of an operation. It also determines whether a scrap account is required when flow schedule assemblies are scrapped or returned from scrap through the Work Orderless Completions window. If you do not specify that a scrap account is required, it is optional. This parameter also determines how scrap transactions are processed. If you enter a scrap account, the system debits this account and credits the job or schedule elemental accounts through the operation at which the assemblies are scrapped. If you enter a reversing scrap transaction, the system credits this account and debits the job or schedule elemental accounts through the operation at which the assemblies are returned. 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 then written off as a variance.

Allow Creation of New Operations Determines whether you can or cannot add an operation to a discrete job WIP routing during a move transaction. i.e. Add an operation to track unexpected rework.

Allow Moves Over No Move Shop Floor Statuses Determines whether moves are disallowed if an intra-operation step has a No Move Shop Floor Status. Determines whether moves are disallowed if an intraoperation step that disallows moves exists at an autocharge operation and intraoperation step between the From and To operations or at intervening intraoperation step at the From and To operations if they are direct charge. If an intraoperation step that disallows moves is found, a warning message is displayed and the move is disallowed.

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. 4. Material Tab Supply Sub inventory Determines which supply sub-inventory is used as a default when backflushing Operation Pull and Assembly Pull components IF defaults are not defined at the BOM component level or the inventory item level.

Supply Locator Determines default locator used with Supply Sub inventory default if the Supply Sub inventory is Locator controlled. Lot Selection Method Determines how lot controlled Operation Pull and Assembly Pull components are selected during backflush transactions. Expiration Date : Backflush lots selected based on expiration date using FIFO Or Receipt date using FIFO (uses receipt date if the lot is not under shelf life control) Manual : Backflush lots must be manually selected Receipt Date : Backflush lots selected based on inventory receipt date using Lot Verification Determines how lots selected are verified during backflush transactions All : Verifies automatically selected lots were the ones consumed by the Assemblies Exceptions Only : Verifies that manually selected lots were the ones consumed by the Assemblies Release Backflush Components Determines whether operation pull and assembly pull supply type components are used in the Component Pick release process. Note: The Discrete Job Pick List Report does not use this parameter. 5. Intraoperation Tab Determines which intra-operation steps are enabled in your WIP routing operations. Queue Assemblies in the Queue intraoperation step of an operation are waiting for you to perform work on them. Queue is the default intraoperation step for every operation in a routing. When you release jobs, the assembly quantity is automatically loaded into the Queue intraoperation step of the first operation. You can move assemblies from the Queue intraoperation step to any other enabled intraoperation step. Run Assemblies in the Run intraoperation step are ready to be worked on. You can move assemblies from the Run step to any other enabled intraoperation step in the routing. 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. You can move assemblies from the To Move intraoperation step to any other enabled intraoperation step in the routing. Before you can use the Completion Transactions window to complete assembles from jobs and schedules with routings, you must move these assemblies into the To Move intraoperation step of the last operation. For this reason, the To Move intraoperation step is automatically enabled for all final routing operations. Assemblies in the To Move step are considered complete for the operation. Reject Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped. You can move assemblies from the Reject intraoperation step to any other enabled intraoperation step in the routing. Assemblies in the Reject step may not be useable, but they are considered complete for the operation because components and resources have been consumed in their production. Scrap Assemblies in the Scrap intraoperation step are considered unusable. This step is for those assemblies you want to consider as a variance on the discrete job. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning does not consider assemblies in Scrap steps in the MRP planning process. Assemblies in the Scrap intraoperation step are usually not useable. They are considered complete for the operation because components and resources have been consumed in their production. They can be recovered from scrap by moving them to another intraoperation or operation step.

6.Outside Processing Tab Outside processing business flow

Shop Floor Status for PO Move Resources Determines which shop floor status is assigned to the Queue intraoperation step of an outside processing operation when a discrete job is created. Requisition Creation Time Determines whether Purchase requisitions are created for OSP operations automatically or manually and when in the manufacturing process they are created. At Job/Schedule Release - Creates requisition when Job is released At Operation - Creates requisition when you move assemblies into the Queue intraoperation step of an OSP operation. Manual - Requires manual creation of requisition

Job Roles for Notification Production Scheduler - Ties an employee with Production Scheduler job role to receive notification when there are no purchase orders for OSP items, when OSP assemblies have been shipped or when they will not be shipped. Shipping Manager - Ties an employee with Shipping Manager job role to receive notification when intermediate assemblies are ready to be shipped to an OSP supplier. Propagate Job Change to Purchasing Sets how quantity changes are forwarded to purchasing documents, and initiates cancellation of these documents under certain conditions. Your choices are: Automatic Changes are passed routinely through the workflow. You can choose to have them propagated as fully automatic, or subject to approval. If this parameter is set to Automatic, the requisition and purchase order documents are cancelled if the following conditions exist: The job status is changed to Cancel, Complete No Charge, or Closed. Manual You must update changes directly in the purchasing documents. 7.Scheduling Check the Include Resource Efficiency box if you want job scheduling to consider. Efficiency effects resource loading and is always considered in lead time calculations.

Check the Include Resource Utilization box if you want job scheduling to consider resource utilization. Utilization is always considered in lead time calculations. Resource availability is divided by the utilization percentage for capacity.

Select a simulation set in the Simulation Set field to enable the adjust resource capacity capability. Simulation sets are used to link resource changes to available resource capacity for scheduling and planning.

If you have Oracle Manufacturing Scheduling installed, check the Use Constraint Based Scheduler box to activate the Constraint Based scheduling engine. Note: Do not choose this check box unless you have Oracle Manufacturing Scheduling installed.

Select the constraints that you want the constraint-based scheduling engine to consider in its calculations when it reschedules jobs: Resources (only) or Resources and Material.

In the primary Objective field, select the primary goal of work in process scheduling for your plant.

The choice of objective determines which set of scheduling logic is used on the shop floor. Your choices are maximize Ontime Completion, Minimize Setup, or Minimize Operation Slack.

Enter the number of days in the scheduling Horizon field. The horizon is the number of days in the schedule that the constraint-based scheduling engine is to consider in its calculations when it reschedules jobs (the default is 60 days). The horizon should be at least as long as your longest job on the schedule, and you should also add additional time to take into consideration future material receipts.

In the Maximum Penalty field, enter the maximum penalty factor that can be entered when assigning penalties for scheduling. In the Penalty Per Day Late field, enter the default penalty factor used in scheduling jobs not completed by the scheduled due date.

In the Due Date Tolerance (days) field, enter the default number of days a job can be delayed during scheduling.

8. Serial Parameters

The following parameter is used to set features for serial number control tracking throughout manufacturing. Serial control includes control beginning at the routing, association of serial numbers to jobs before their production, serial based transaction entry, generation of serial numbers, and serial label printing. Default Serialization Start Operation Determines the job operation where tracking of the serial number begins. The values are: Enabled: If the serialization start operation is defined on the bill of material item routing, it is copied to the job routing. If this value is not defined on the item routing, the first operation is defaulted to be the serialization start operation on the job routing. Disabled: The serialization start operation on the job routing is blank. Auto Associate Serial Numbers on Job Creation From Interface Determines if serial numbers are automatically generated and associated with a job when a job is created through the WIP Mass Load interface. The job start quantity determines the number of serial numbers created. The values are: Enabled: Serial numbers are automatically generated and associated with a job. Disabled: Serial numbers are not automatically generated and associated with a job. Default Intraoperation Step for Assembly Moves This parameter is used for move transactions on a serialized job. It defines a default value for the intraoperation step where you are moving assemblies the To step. Your choices are Queue, Run, To move, and null. For example, when moving assemblies, if this value is set to: Queue the default intraoperation To step for the next move transaction is the next Queue step in the routing. Run the default intraoperation To step for the next move transactions is the next Run step in the routing. To move the default intraoperation To step for the next move transaction is the next To move in the routing. Null a default is not set, you must specify the step in your move transaction.

There are 2 types of discrete Jobs 1) Standard - Standard discrete jobs are used to manufacture a brand new product using Bill of Materials and Routings. E.g. There is a demand in the sales order for an Assembly item which in turn creates a WIP Job. For this case standard discrete job will be created. 2) Non-Standard - Non Standard discrete jobs are mostly used to repair a defective item. E.g. A product is returned by the customer for some defective reason. For this item a non-standard job is created and item is refurbished. Refurbished meaning renovate.

1.3 WIP Accounting Classes

An accounting class is a group of various General Ledger accounts which allows you to arrive(end up) at job cost, production cost and maintenance costs. WIP (Work in process) accounting is used to track costs for jobs as they pass through the manufacturing process WIP Accounting class is a setup that have Pre-defined list of valuation and variance accounts .

Valuation accounts 1) Material account 2) Material overhead 3) Resource 4) Overhead 5) Outside Processing

Variance Accounts 1) Material Account 2) Material Overhead 3) Resource 4) Overhead 5) Outside Processing 6) Standard Cost 7) Bridging 8)Expense

Standard cost account is applicable to only standard costing method and Bridging and Expense accounts are applicable to average costing method only. Rest all accounts are applicable to both standard and average costing methods.

Standard costing : It is a costing method, which uses pre-determined costs at the time of calculation inventory as well as charging all resources, material & overheads, job costs etc.,

Average costing : it is a costing method, in which the unit cost of an item is the average value of all receipt of that item to inventory on a per unit basis.

WIP Valuation Accounts:

WIP accounting class valuation accounts are charged when you issue components, move assemblies, complete assemblies, and charge resources.

1)Material AccountIt is an asset account, used to track material cost.

under Standard costing - it is debited - when issued material to a job/schedule it is credited - when completed the job/assemblies. under Average costing - it is debited - at the average cost at the time of issue transactions it is credited - when the assemblies completed from a job.

2)Material Overhead It is an asset account used to track the material overhead(burden) cost. under Std costing, it is debited when issued material with material overhead to job or schedules. It is credited, when you complete the job or schedules. under Avg. costing, it is debited, - at the average cost at the time of issue transactions.

3)Resource It is an asset account used to track the resource cost. under Std costing, it is debited, when resource are charged to a job or schedules it is credited , when you complete job or schedules, close a job. under Avg costing, this account is debited and credited at the resource rate at the time the resource is charged.

4)OverheadIt is an Asset account used to track resource or department overhead cost. under Std costing, it is debited, when resource are charged to a job or schedules it is credited , when you complete job or schedules, close a job. 5)Outside processing It is an Asset account used to track outside processing costs. Under Std costing, it is debited, at purchase order cost when you receive items for a job or schedule. And credited, when you complete the job or schedules, or close the job. Under Avg. costing, the debit is based on item receipt.

WIP Variance Accounts:

Variance accounts associated with Standard Discrete, Asset Non standard discrete accounting classes, when the job are closed. Variance accounts associated with Expense Non standard, repetitive (optional) accounting classes, when the accounting periods are closed.

1)Material Variance This account tracks the variance between the previous level material costs charged for an job/schedule to the actual relieved cost of the previous level material for the job/schedule. This calculation gives net material usage and configuration difference.

2)Resource Variance This account tracks the variance between the resource cost charged for job/schedule to the actual relieved cost for the resource charged.

3)Overhead varianceThis account tracks the variance between the overhead costs charged for an job/schedule to the actual relieved costs for the overhead charged of the job/schedules.

4)Outside Processing variance This account tracks the variance between the outside processing charged cost for job/schedule to the actual relieved cost for the outside processing charged.

5)Standard cost variance : This account is applicable only for Standard discrete and Asset non standard accounting class. It is charged during the update of standard cost on the active job.

6)Bridging - optional

7)Expenses optional.

Types of Accounting classes:

Standard Accounting Classes : I. Standard Discrete II. Asset Non Standard Discrete III. Expense Non standard Discrete

Repetitive Accounting Class :

Lot-based job Accounting Class: I. Standard Lot based II. Expense non standard.

i)Standard Discrete: It is used to group job costs. For eg. An Sub-Assembly or FG, if we define accounting class, we can take separately value & cost that are associated with SA & FG.

When you define an accounting class for a job, you must assign valuation and variance accounts to it. When you issue materials to a job that uses this accounting class, the appropriate valuation accounts are charged. When the job is closed, final costs and variances are calculated and posted to the variance and valuation accounts. When the accounting period is closed, these journal entries are automatically posted to the general ledger.

ii)Asset Non Standard Discrete

if you use non-standard discrete jobs to track production costs as assets, you can define and assign an accounting class with a type of asset non-standard.

Asset non-standard discrete jobs are costed the same as standard discrete jobs. Valuation accounts are charged when material is issued to a job and final costs and variances are calculated and posted to the appropriate variance and valuation accounts when the job is closed.

iii)Expense Non-standard discrete It is used to group and report various types of non-standard production jobs like field service repair or engineering projects. For tracking recurring expenses, If we define and assign accounting class of type 'expense nonstandard' for non-standard production like Machine maintenance or engineering projects, the valuation accounts carry the costs incurred on these jobs as an asset during the period and automatically writes off to Variance account at period close.

Repetitive Accounting Class : It is used to group production costs. This account is assigned to the created repetitive line/assembly. The accounts are charged whenever you transact against the repetitive line/assembly. Repetitive accounting class can be automatically defaulted when you associate repetitive assemblies with product lines

Lot Based Accounting class:

Oracle Shop Floor Management extends work in process functionality using network routings, lot based transactions, and yield based operational costing. These accounts are applicable for standard discrete, expense non standard discrete.

Maintenance Account classes:

Maintenance accounting classes are used to group costs for work orders used in Oracle Enterprise Asset Management (eAM). For example, if you are creating work orders for plant maintenance activities, you can define your accounting classes to separately value and report the costs related to asset. Maintenance accounting classes are automatically defaulted when you create eAM work orders.

Profile Options:

During Implementation , you set a value for each user profiles to specify how WIP controls access to and process data.

TO:WIP: Concurrent Message Level TO:WIP : Completion Transaction First Field. TO:WIP: Move transactions First Filed TO: WIP: Move transaction Quantity Field TO:WIP:Word order-less default completion WIP:Default job start date WIP: Discrete job prefix WIP: enable outside processing workflows.

TP: WIP: Concurrent Message Level Determines the level of detail reported in the move transaction concurrent log file during move transaction validation and processing. Available values are listed below: Reports errors only. Reports processing activities and errors. Reports and time stamps processing activities and errors. TP:WIP:Completion Transactions First Field Determines which field the cursor defaults to when you first enter the Completion Transactions window. Set this option based on your predominant manufacturing environment: assembleto order, project or discrete job, or repetitive. The available first field values are Line, Assembly, Job, or Sales Order. You can navigate to another field to override the default. Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job. TP: WIP: Move Transactions First Field Determines which field the cursor defaults to when you first enter the Move Transactions window. Set this option based on your predominant manufacturing environment: assembletoorder, project or discrete job, or repetitive. The available first field values are Line, Assembly, Job, or Sales Order. You can navigate to another field to override the default. Attention: You can only enter a Sales Order name if you have an ATO sales order linked to a job. TP: WIP: Move Transaction Quantity Default Indicates if and how move transaction quantities are defaulted. Available values are listed below: None : No transaction quantity is defaulted. Minimum Transfer Quantity : When you perform a move transaction, the transaction quantity defaults to the minimum transfer quantity if the minimum transfer quantity is less than or equal to the available quantity. If the minimum transfer quantity is greater that the available quantity, and the available quantity is not zero, then the available quantity is defaulted. Available Quantity : When you perform a move transaction, if the available quantity is not zero, the transaction quantity defaults to the available quantity TP: WIP: Work Orderless Default Completion Determines the default for the Scheduled flag in the Work Orderless Completions window. Set

this profile according to your business requirements. The default can be overridden. Available values are listed below: Scheduled: The Schedule flag defaults to checked. Use this option if most of your work order less completions are based upon flow schedules generated by the Line Scheduling Workbench. Unscheduled: The Scheduled flag defaults to unchecked. Use this option if most of your work orderless completions are manually entered and not based upon flow schedules generated by the Line Scheduling Workbench. WIP: Default Job Start Date Determines whether the start dates for jobs default to the current date and time or not at all when defining jobs in the Discrete Jobs window. The options are Yes or No. WIP: Discrete Job Prefix Specifies the job prefix to use when autogenerating job names in the Discrete Jobs, Simulate Discrete Jobs, Import Jobs and Schedules, and AutoCreate windows in Work in Process, and in the Planner Workbench window in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. It is also used when autogenerating the numbers for flow schedules created in the Work Orderless Completions window. Work in Process concatenates this prefix with a value from the sequence WIP_JOB_NUMBER_S to create a default discrete job name. WIP:Enable Outside Processing Workflows Determines whether or not outside processing workflows are enabled. Yes: All outside processing workflows are enabled. No: outside processing workflows are enabled.

Shop Floor Statuses

We can define shop floor statuses in WIP and assign these statuses to a intra-operation steps of the WIP routing operations. Shop floor statuses can be used to control/stop shopfloor move transactions. You can define as many as you required.

For eg. There could be some quality problem in manufacturing you can view this status during move transactions. We assigned to an intraoperation step of an operation, that is associated with a particular repetitive line and assembly, the status applies to all repetitive schedules of all assemblies on that line.

1. Navigate to the Shop Floor Statuses window.

2Enter an alphanumeric Status name For example, enter WIPHold to signify that shop floor assemblies are on WIP hold or, QAHold to signify that the shop floor assemblies are on quality assurance hold. 3. Enter a Status description. Descriptions can be used to identify shop floor statuses on standard reports. They can be up to 240 characters of alpha numeric text. 4. Uncheck Allow Moves so that you can use this status to control move transactions. Allow Moves defaults to checked. 5. Enter the Inactive On date.As of this date, you can no longer use this status. 6. Save your work.

Assign Shop Floor Statuses Shop floor statuses can be attached to WIP jobs in Assign Shop Floor Statuses form

Defining Production Lines

A Production line describes a set of operations, department and manufacturing cells that produce one or more products.

You can associate production lines with repetitive assemblies, discrete jobs, flow routings, schedules, and work order-less completions. You can define and update production lines. But you cannot delete production lines. 1. Navigate to the Production Lines window. 2. Enter the production line Name. For example, enter LINE1 to signify production line number 1, or BOARD to signify the PC board assembly line. 3. Enter the production line Description. 4. Optionally, select an Exception Set. Production lines are rate-based resources. The exception sets that you assign to them help you identify capacity problems. . 5. Optionally, select an ATP Rule. See: Defining ATP Rules, Oracle Inventory User's Guide You can select any user-defined ATP rule. The ATP rule that you assign to the production line is used when determining the capable to promise status of the line resource. See: Capable to Promise, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide. 6. Enter the Minimum Hourly Rate. This represents the minimum number of assemblies the line can produce per hour. The minimum hourly rate must be greater than or equal to 0 and less than or equal to the maximum rate. 7. Enter the Maximum Hourly Rate. This represents the maximum number of assemblies the line can produce per hour. The maximum hourly rate must be greater than or equal to the minimum rate. 8. Enter the production line Start time. This is the time at which your production line starts running every day. You can update this field

at any time. 9. Enter the production line Stop time. This is the time at which your production line stops running every day. You can update this field at any time. The difference between the Start and Stop times represents the amount of time per day a line is available. If the Start and Stop times are the same, the production line is considered to be available 24 hours per day. 10. Select the Lead Time Basis. If the lead time varies by assembly, you can schedule the repetitive production time based on the routing of the assembly the line is building. You can set a fixed lead time if the lead time is determined by the production line and does not vary by assembly. You can update this field at any time.

Fixed: The system schedules the first unit completion date and the operations of all repetitive schedules on this production line based on the fixed lead time hours you enter for the production line. Scheduling is done regardless of actual capacity or the lead time of the routing of the repetitive assembly.

Routing-Based: The system schedules the first unit completion date and the operations of all repetitive schedules on this production line using the detailed shop 2-58 Oracle Work in Process User's Guide floor scheduling algorithm, the routing of the assembly, and a quantity of 1. 11. If the lead time basis is fixed, you must enter the Fixed Lead Time, in hours per assembly, for the production line. This is the amount of time it takes to produce the first assembly, from start to finish on the production line. The daily quantity from that point on is set when you define individual repetitive schedules and must be less than or equal to the maximum hourly rate. The fixed lead time entered here is used to schedule repetitive schedules produced on this production line. You can update this field at any time. You cannot enter a value in this field for a routing-based production line.

12. Enter the Inactive On date.

13. Save your work.

Defining Tolerance Fences

Tolerance fences provide temporary increases to capacity above the standard operating rate to handle increases in orders.

1. Choose Tolerance Fences from the Production Lines window. 2. In the Days in Advance field, enter the number of days of notice needed before increasing the line capacity. The Days in Advance value should be equal to or greater than the fixed lead time value. 3. In the Tolerance Percent field, enter the percentage you want to increase the line capacity.

For example, the lead time for an assembly is 3 days on a line, and you know you can increase your capacity by 5 percent if given 5 days notice. Set Days in Advance at 8 days (the lead time plus number of days required for notice), and the tolerance percentage at 5. 4. Save your work.

Schedule Groups

You can define schedule groups then assign them to the jobs that you create. For example, you can define a schedule group then assign it to a group of jobs that are being built on a specific production line and that must be completed on a specific date for a planned departure. You can update schedule groups. You cannot delete schedule groups that are not assigned to jobs.

Schedule groups are used to group jobs. For example, you can create a Week01 schedule group to identify which jobs are to be released and built during the first week of your current production cycle. Schedule group names can be up to 30 characters and must be unique within the organization.

Build Sequencing You can sequence your discrete manufacturing production using schedule groups. You can do this by grouping discrete jobs into schedule groups then sequencing jobs within these groups.

You can sequence jobs within a schedule group

2.4 Defining Labor Rates

You can add, delete, and update the effective date of the hourly labor rates for persontype resources (employees). You also can define multiple hourly labor rates for the same employee, as long as each rate has a different effective date

2. Select the employee Name or Number. 3. Select the Effective Date for each hourly labor rate. The hourly rate remains effective until the next effective date or until the inactive date of the employee. You can only update or delete future effective dates. 4. Enter the Hourly Labor Rate for the employee. You can define multiple hourly labor rates for the same employee as long as they have different effective dates.

If you use actual costing, the hourly labor rate rather than the standard rate is used to compute the actual cost of persontype resources charged to discrete jobs and repetitive schedules