Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

1.Define WIP parameters (Req.

)
2.Define WIP Accounting Classes (Req.)
3.Set WIP Profile Options (Req.)
4.Define Production Lines (Optional)
5.Define Repetitive assembly (Optional)
6.Define Schedule Groups (Optional)
7.Define Employees (Optional)
8.Define Employee Labor Rates (Optional)
9.Define Shop Floor Statuses (Optional)
11.Define Job/Schedule Docs (Optional)
12.Define Operation Documents (Optional)

11. What are the Required Setups need to be done in Inventory?

Flexfields, Calendars, Locations, Legal Entities, Operating


Units, Inventory Organizations: Acounting Info & Inventory
Info. Costing Period should be open, Transaction Interface
manager should be active

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. The
following summarizes WIP parameters and their defaults:

An accounting class is a group of various General Ledger accounts which allows you to
arrive at job cost, production cost and maintenance costs.
The following are different accounting classes in Oracle WIP:

1) Standard discrete
Standard discrete accounting classes can be used to group job costs for building
subassemblies and finished goods on shop floor. You can define and attach this accounting
classes so that you can separately value and report the costs associated with subassembly
and finished goods production.
2) 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.
3) Expense non-standard discrete
Non-standard discrete accounting classes can be used to group and report various types of
non-standard production costs, such as field service repair. For example to track recurring
expenses – machine maintenance or engineering projects- with non-standard jobs, you can
define and assign an accounting class with a type of expense non-standard to these jobs.
The valuation accounts carry the costs incurred on these expense jobs as an asset during
the period and automatically writes them off to the variance accounts at period close.
4) Repetitive accounting class
Repetitive accounting classes are used to group production costs and must be assigned to
each repetitive line/assembly association that is created. Every repetitive schedule for that
assembly on that line uses these accounts.
5) Standard Lot based
Standard lot based jobs control the material, resources, and operations required to build an
assembly and collect costs. When you build lot based jobs, the standard lot based
accounting class is used to separately value and report costs associated with yielded
production at each individual operation on the routing.
6) Expense non standard lot based
Expense non-standard lot based accounting class jobs control material and collects costs for
miscellaneous activity. These jobs are used for expense work orders for testing, prototypes,
and rework where operation yield costing is not considered. You can perform all transactions
(moves, jumps, scrap, splits, and update assemblies or routings) with the exception of job
merge.
7) Maintenance accounting class
Maintenance accounting classes are used to group costs for work orders used in Oracle
Enterprise Asset Management (eAM) Module . 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.

The following valuation and variance accounts are associated with each accounting class.

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 discrete jobs control the material, resources, and operations which are required to
build an assembly and collect its manufacturing cost. Some comparison is done as below: 1)
Non-standard discrete jobs control material and collect costs for miscellaneous manufacturing
activity.
You can add material requirements to discrete jobs and repetitive schedules with
statuses of Unreleased, Released, On Hold, and Complete.

You can add operations to discrete jobs with statuses of Unreleased, Released,
Complete, or On Hold. You can add operations to repetitive schedules with statuses of
Unreleased. You can add operations to jobs and repetitive schedules with or without
routings.

You can create a routing for a job or schedule that does not have a routing by adding
operations to it. When you add the first operation, the system automatically defaults
an operation sequence of 1 for the new operation and assigns job or schedule material
requirements to this operation. If the job or schedule is already released, the system
also loads the job or schedule quantity into the Queue intraoperation step of the new
operation.

You can use the Purge Discrete Jobs window to purge information associated with
discrete jobs that were closed in a now closed accounting period. You can purge all
discrete job information or just selected information: details (material requirements,
resource requirements, and operations), associated ATO configurations, or associated
move and/or resource cost transactions.

Before purging a job, you can view detail and ATO sales order information for that
job. You can also 

Work Order-less Assembly Completions and Returns


You can complete and return flow schedules and unscheduled flow assemblies without
having to create a work order. When you perform a WIP Assembly Completion,
operation pull, assembly pull, and push components are backflushed and resources and
overheads are charged.

Backflush transactions 'pull' components with Operation Pull and Assembly Pull supply types
from inventory onto jobs and repetitive schedules. Backflush transactions can be launched by:
completing assemblies at operations using the Move Transactions window.

You might also like