Previous | Next | Contents | Index | Glossary | Library |
Step # | Description | Discrete | Repetitive | Projects | Work Order-less Schedules |
---|---|---|---|---|---|
1 | Define Work in Process Parameters | Required | Required | Required | Required |
2 | Define WIP Accounting Classes | Required | Required | Required | Required |
3 | Set Work in Process Profile Options | Required | Required | Required | Required |
4 | Define Production Lines | Optional | Required | Optional | Optional |
5 | Associate Lines and Assemblies | NA | Required | N/A | Optional |
6 | Define Schedule Groups | Optional | NA | Optional | Optional |
7 | Define Employees (Optional if using resources) | Optional | Optional | Optional | Optional |
8 | Define Labor Rates (Optional if using resources) | Optional | Optional | Optional | Optional |
9 | Define Shop Floor Statuses (Optional if using resources) | Optional | Optional | Optional | NA |
10 | Define Job and Schedule Documents | Optional | Optional | Optional | NA |
11 | Define Operation Documents | Optional | Optional | Optional | NA |
Table 1 - 1. (Page 2 of 2) |
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 you want to use in your routings to allow detailed tracking within operations on the shop floor. Oracle Work in Process always enables queue for each operation and To Move for the final operation in a routing. See: Defining WIP Parameters.
You must define your 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. See: Defining WIP Accounting Classes.
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. See: Work in Process Profile Options.
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/or manufacturing cells that produce one or more of your products. You can build different repetitive assemblies on the same production line. This allows you to use production lines to aggregate, by production line, material requirements for a number of assemblies. You can also build the same assembly on different production lines.
Production lines can optionally be assigned to discrete jobs for informational purposes only. You can update but note delete production lines. See: Defining Production Lines
If you manufacture assemblies repetitively, you must define your repetitive assemblies and associate them with production lines. You must do this before you can define repetitive schedules. See: Associating Lines and Assemblies.
You can define schedule groups then assign them to jobs or work order-less completions. 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.
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: Enter Persons.
If you want to charge employee labor rates in Oracle Work in Process, 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 which do not charge at standard, and when you associate an employee number with the resource you are charging. See: Defining Labor Rates.
If you want to optionally prevent move transactions from steps within an operation, you can define shop floor statuses which prevent moves and assign 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. See: Defining Shop Floor Statuses.
You can define standard job and schedule documents and then attach them to jobs and repetitive schedules. See: Defining Job and Schedule Documents.
You can define operation documents then attach them to work in process routing operations. See: Defining Operation Documents.
Previous | Next | Contents | Index | Glossary | Library |