You must complete the following steps to set up Work in Process. Each step includes a Context section that indicates whether you need to repeat the step for each set of books, set of tasks, inventory organization, HR organization, or other operating unit under Multiple Organizations.

   Step 1: Define Your Work in Process Parameters (Required with Defaults)

System Requirements: The following parameters define modes of operation and default values that affect Work in Process: Discrete Manufacturing Parameters, Repetitive Manufacturing Parameters, Move Transaction Parameters, Material Parameters, Intraoperation Steps Parameters, Outside Processing Parameters, Scheduling Parameters, and Other Parameters.

To define WIP parameters, you must change the control level for the Costing Enabled and Inventory Asset Value item attributes in the Item Attribute Controls window in Oracle Inventory. This change requires that costs be defined for all organizations that point to other organizations for their costs.

You must define modes of operation that affect other functions in Oracle Work in Process and assign default values before you can perform any transactions in your organization. You must also enable the intraoperation steps that you want to use in your routings to allow detailed tracking within operations on the shop floor. Work in Process always enables Queue for each operation and To Move for the final operation in a routing.

• Define Bills of Material Parameters for Phantom Routing (Required)

  There are two Bills of Material (BOM) parameters that you need to define in order to use phantom routing: Use Phantom Routings (choose whether or not to charge phantom routing cost); and Inherit Phantom OP Seq (choose whether or not phantom components inherit the operation sequence of the parent operation or maintain their own phantom routing sequence).

• Define Parameters for Project Manufacturing (Optional)

  If you are using Project Manufacturing, several parameters are defined for Work in Process transactions: In the Oracle Project Manufacturing Parameters window:

  • Enable Project Reference and Project Control Level parameters enable you to assign project and task references to planned orders, jobs, purchase orders, sales orders, miscellaneous transaction and other entities within Oracle Manufacturing.

  • Allow Cross Product Issues enables components with a different unit number from your assemblies to be issued to work in process.

  In the Organization Parameters window in Oracle Inventory

  • Project Cost Collection Enabled parameter associates an expenditure type with each subelement.

  • Enable Model/Unit Number Effectivity enables model/unit number effectivity for an organization;

• Define Item Tolerance Type (Optional)

  You need to enter an overcompletion tolerance type and tolerance value if you will be overcompleting assemblies on jobs or schedules. On the Master Items form, navigate to the Work in Process tab. Select the tolerance type percent or amount from the list of values, then enter the corresponding tolerance value.

  Context: You need to perform this step once for each applicable item in the master organization where that item is defined.

  See:

  Defining Items.

  Work in Process Attribute Group.

   Step 2: Define your WIP Accounting Classes (Required)

You must define Work in Process accounting classes before you can define discrete jobs and repetitive assemblies. You must define separate accounting classes for standard discrete jobs, non-standard expense jobs, non-standard asset jobs, and repetitive assemblies. Accounting classes include the elemental valuation and variance accounts you use to cost discrete and repetitive production.

System Requirements: you can define any number of accounting classes. Accounting classes define which valuation and variance accounts are charged and when they are charged. Every discrete job and repetitive schedule that you define must be assigned one of the following types of accounting classes: Discrete, Standard Discrete Expense, Non-standard Asset, Non-standard Repetitive, or Lot Based Standard Discrete.

Default: If you skip this step, Discrete will be used as the default value.

Context: Perform this step for each inventory organization in which you use Work in Process.

See: Defining WIP Accounting Classes.

   Step 3: Set your Work in Process Profile Options (Required)

Profile options specify how Work in Process controls access to and processes data. In general, profile options can be set at one or more of the following levels: site, application, responsibility, and user.

System Requirements: the system administrator sets and updates profile values. The Oracle E-Business Suite System Administration Reference Manual contains a list of all profile options available to every Oracle Application. At this step, select the profile options related to the Work in Process (WIP) module. These system profiles must be set in order to have an operational system. See: Profile Option Descriptions

   Step 4: Define Production Lines (Optional)

You can associate production lines with repetitive assemblies, discrete jobs, and work order-less completions. A production line describes a unique set of operations, departments, and manufacturing cells that produce one or more of your products. You can define and update, but not delete production lines.

You must associate production lines with the assemblies that you plan to manufacture repetitively. You can build different repetitive assemblies on the same production line, which allows you to use production lines to aggregate material requirements for a number of assemblies by production line. You also can build the same assembly on different production lines.

Production lines can optionally be used to identify where and how your discrete jobs are built; however, Discrete job production lines are only used for informational purposes.

See: Defining Production Lines

   Step 5: Define your Repetitive Line and Assembly Associations (Optional)

If you manufacture assemblies repetitively, you must define your repetitive assemblies and associate them with production lines before you can define repetitive schedules. When you define repetitive schedules, you must specify the line on which you plan to produce the repetitive assembly and the quantity that you plan to build. Repetitive line scheduling then uses the line start and stop times, production rate, and lead time, along with the workday calendar to schedule your repetitive schedules.

See: Associating Lines and Assemblies

   Step 6: Define Schedule Groups (Optional)

You can define schedule groups then assign them to jobs or work order-less completion transactions. For example, you can define a schedule group then assign that schedule group 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.

See: Defining Schedule Groups.

   Step 7: Define your Employees (Optional)

If you do not install Oracle Human Resource Management Systems with Oracle Work in Process, you use the Enter Employees form to define employees whose labor rates you want to charge.

See: Employee Management.

   Step 8: Define your Employee Labor Rates (Optional)

If you want to charge employee labor for employees that you defined in Step 7, you must define the hourly labor rate of your employees. Oracle Work in Process uses employee rates when you manually charge person-type resources to jobs or repetitive schedules that do not charge at the standard rate, and when you associate an employee number with the resource you are charging.

You can add, delete, and update the effective date of the hourly labor rates for person-type resources (employees). You can define multiple hourly labor rates for the same employee, as long as each rate has a different effective date. If you use actual costing, the hourly labor rate rather than the standard rate is used to compute the actual cost of person-type resources charged to discrete jobs and repetitive schedules. You can enter an employee number when performing a person-type resource transaction in the Resource Transactions window or the Resource Transaction Open Interface Process. The employee's most current hourly labor rate is used to compute the actual cost of the transaction.

See: Defining Labor Rates.

   Step 9: Define your Shop Floor Statuses (Optional)

You have the option to prevent move transactions from steps within an operation by defining shop floor statuses that prevent moves, and assigning them to operations and intraoperation steps within discrete jobs or repetitive schedules. You can also use these statuses to record more detailed information regarding assemblies at a particular step within an operation.

You can assign shop floor statuses to any intraoperation step associated with a job or repetitive line or assembly. You also can assign multiple statuses to an intraoperation step; however, you cannot assign the same shop floor status to more than one intraoperation step within the same operation. Shop floor statuses that are assigned to a repetitive line or assembly are valid for all repetitive schedules being built on that production line.

See: Defining Shop Floor Statuses.

   Step 10: Define Job and Schedule Documents (Optional)

You can define standard job and schedule documents and then attach them to jobs and repetitive schedules.

See: Defining Job and Schedule Documents.

   Step 11: Defining Operation Documents (Optional)

You can define operation documents then attach them to work in process routing operations.

See: Defining Operation Documents.

   Step 12: Setup Discrete Execution Workstation

The Discrete Execution Workstation provides a Manufacturing Execution System interface to perform multiple shop floor functions for viewing the jobs assigned to specific work centers, viewing requirements and instructions for performing work, and monitoring progress and problems. The workstation provides three functional roles.

See: Overview of the Discrete Execution Workstation, Oracle Manufacturing Execution System for Discrete Manufacturing.