Documente Academic
Documente Profesional
Documente Cultură
R12.2
Table of Contents
STEP 1: Setup Prerequisites
ORACLE INVENTORY
ORACLE ENGINEERING
DISCRETE:
REPETITIVE:
COSTING:
MOVE TRANSACTION:
MATERIAL:
INTRA OPERATION:
OUTSIDE PROCESSING:
SERIAL:
STANDARD DISCRETE:
Before you set up Work in Process, you must complete the setup for the following: products
ORACLE INVENTORY
Make sure you set up Inventory as described in Overview of Setting Up Inventory. Ensure that all the
following steps have been completed:
ORACLE ENGINEERING
Make sure you set up Engineering as described in Overview of Setting Up Engineering.
TP:WIP:Completion Material
Required On-line processing D, R, P
Processing
TP:WIP:Completion Transaction
Required On-line processing D, R, P
Form
TP:WIP:Completion
Required Job D, R, P
Transactions First Field
TP:WIP:Concurrent Message
Required Message level 0 D, R, P
Level
TP:WIP:Material Transaction
Required On-line processing D, R, P
Form
TP:WIP:Material Transactions
Required Job D, R, P
First Field
TP:WIP:Move Transaction
Required None D, R, P
Quantity Default
TP:WIP:Operation Backflush
Required On-line processing D, R, P
Setup
TP:WIP:Resource Transactions
Required Job All
First Field
TP:WIP:Work Order-less
Required Unscheduled WO
Default Completion
Interactive
WIP:Define Discrete Job Form Required D, P
definition
D, R, P,
WIP:Exclude Open ECOs Required Yes
WO
D, R, P,
WIP:See Engineering Items Required Yes
WO
Try to open the Discrete Jobs form to create the Standard Discrete Jobs
Will get the below error message while opening the Discrete Jobs form
WIP Parameters:
1. Discrete
2. Repetitive
3. Costing
4. Move Transaction
5. Material
6. Intraoperation
7. Outside Processing
8. Scheduling
9. Mobile
10.Serial
11.Other
We must define modes of operation that affect other functions in Oracle Work in Process and assign
default values before we can perform any transactions in our organization. We must also enable the
intra-operation steps we want to use in our 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.
DISCRETE:
Default Discrete Class: Determines the default Account codes for Discrete job transactions.
Default Lot Number Type: Determines how lot numbers are assigned to discrete jobs.
1. Job Name - Lot Numbers are based on the Discrete Jobs Name
2. Based on Inventory Rules - Based on the Inventory Rules which we have defined in Inventory
3. No Default - No Defaults
Respond to Sales Order Changes: Determines if and how the system responds to changes to
assemble-to-order (ATO) sales orders and their related discrete jobs. Determines the status of a work
order reserved and linked to a sales order: if a configured item is de-linked from a sales order or sales
order line placed on hold.
Available Values
1. Never: The work order will not be placed on hold if you de-link the configured item from the
sales order, or if the sales order is placed on hold.
2. Always: The work order will be placed on hold if you de-link the configured item from the sales
order, or if the sales order is placed on hold.
3. When Linked 1 to 1: The work order will be placed on hold if it is the only work order reserved
to that sales order.
Important: When cancelling sales order lines with ATO items, this parameter, is ignored by
the system.
REPETITIVE:
Autorelease Days
Determines the time period within which the system automatically releases the next
Unreleased schedule.
When you complete a repetitive schedule, the system searches within the autorelease time
frame for an Unreleased schedule, or for a schedule with a status of Released, Complete, or On
Hold. If one exists, the status of the newly completed schedule changes to Complete-No
Charges and the future schedule is automatically released. If no such schedule exists, the
status of the schedule changes to Complete. If more than one schedule exists within the
autorelease time frame, only one schedule is released.
COSTING:
For Standard Costing Organizations, this Costing TAB will be greyed out.
System Calculated
User Defined
This parameter determines how resource costs are determined as assemblies are completed
from jobs into inventory.
If this option is set, resources can be costed at either the actual resource costs or at
the resource predefined cost depending on how the System Option parameter is
subsequently set.
When completing assemblies from a non-standard job with no routing, the resource
rate associated with the Average Rates cost type is used.
If the option is set, you must choose a user-defined cost type using the Cost Type
Parameter. This cost type is then used to determine the resource cost for the
assemblies being completed.
Additional Information: If there are uncleared costs left in the job, they are posted to the job variance
accounts when the job is closed. Residual costs could be left in the job if: 1) the Auto Compute Final
Completion option is set, but not all assemblies are completed or scrapped or 2) the job earns costs
between the last final completion and the close transaction.
System Option
If you select the System Calculated completion cost source, you must select a System Option.
Cost Type
Determines which cost type to use as the default when the Default Completion Cost Source is
User-Defined. You can only select a Cost Type if the Default Completion Cost Source parameter
is set to User Defined. See: Defining a Cost Type.
Auto Compute Final Completion
Determines whether the Final Completion in the Completion Transaction window defaults to
checked (Yes).
MOVE TRANSACTION:
Require Scrap Account: If you require to account the Scraps then enable this checkbox.
Allow Creation of New Operations: If this checkbox has enabled then system will allow us to create a
new Operations for that particular Discrete Jobs
Allow Moves Over No Move Shop Floor Statuses If this checkbox has enabled then system will allow
us to move the materials even though there is a restrictions in Shop Floor Statues form ("Allow
Moves" check box will be unchecked in Shop Floor Statues form for a particular status. If we enable
"Allow Moves Over No Move Shop Floor Statuses" this checkbox then system will override the Shop
Floor Statuses settings.)
MATERIAL:
INTRA OPERATION:
Enable the check boxes for the required statuses. If you don't want to move the materials in any of the
statuses then uncheck those things.
OUTSIDE PROCESSING:
Shop Floor Status for PO Move Resources: You can define the statuses in "Shop Floor Status" form
and then you can assign that status in this field.
Requisition Creation Time: When you would like to create the Purchase Requisition?
At Operation: When we move the moterials to Outside Processing Operation then that time the
Requisition Import program will be submitted and Purchase Requisition will be created
At Job/Schedule Release: As soon as we release the Job/Schedule, the Requisition will be created
Manual: Manually we need to create the Purchase Requisitions by running the "Requisition Import"
Program.
Job Roles for Notifications: If you want to notify Production Scheduler and Shipping Manager about
the Jobs then you can enter their names
Propagate Job Change to Purchasing: If you would like to propagate the changes that are made in
Jobs to Purchase Order then enable "Automatic". Else make it as Manual and do changes in Purchase
Orders manually.
Need-By Date Tolerance: System will allow us Plus or Minus the entered date for Need by date.
We 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.
STANDARD DISCRETE:
After defining the WIP Accounting Class for Standard Discrete Jobs, attach this Accounting Class in WIP
Parameters
Likewise you can create the WIP Accounting Classes for RMA Rework, Asset Non-Standard Jobs etc.,
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.
Navigation: Move Transactions > Shop Floor Statuses > Shop Floor Statuses
After creating the Shop Floor Statuses, you can assign these statuses against the Discrete Jobs Operations whenever
it's required
Query by Job number and assign the Shop Floor Status for a particular Operation, Department and Step.
If you want to charge employee labor for employees that you defined, 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.
Responsibility: Work In Process Navigation: Setup > Employees > Labour Rates
Query the Employee that you would to define the Labour Rate
You can define multiple rates for one employee with different dates.
You can define and update, but not delete, production lines. A production line describes a unique set of operations,
departments, and/or manufacturing cells that produce one or more of your products. You can associate production
lines with repetitive assemblies, discrete jobs, and work order-less completions.
For example, enter LINE1 to signify production line number 1, or BOARD to signify the PC board assembly
line.
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.
This is the time at which your production line starts running every day. You can update this field at any time.
This is the time at which your production line stops running every day. You can update this field at any time.
Note: 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.
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 floor scheduling algorithm, the routing of the
assembly, and a quantity of 1.
9. 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.
Attention: For lines with a lead time basis of Routing-based, the lead time is calculated by applying the
detailed shop floor scheduling algorithm to the routing of the assembly.
The Inactive On date can be greater than or equal to the current date. If you do not enter an Inactive On
date, the production line is active indefinitely. You cannot update any repetitive schedule that uses this
production line, nor can you assign this production line to a new repetitive schedule as of this date.
You can define standard job and schedule documents and then attach them to jobs and repetitive schedules.
You can use this window to create a catalog of standard job and schedule documents. You can then attach these
documents to your jobs and repetitive schedules.
Owner: Organization