- Optional BPA
- Sourcing Rules
- Resources (Man, Machine, etc)
- BOM & Routing
In indented bill we can see the bill of material in
multilevel tree structure
The purchase requisition (PR) gets generated for OSP and not
the internal requisition.
And it depends on the Requisition Creation Time
parameter in WIP Parameters 'Outside Processing' Tab.
1. At Job/Schedule Release - The PR gets generated
immediately after the Job or Schedule is released.
2. At Operation - The PR gets generated once the move
transaction reach the Queue of the OSP operation sequence.
3. Manual - PR need to be generated manually.
it is not a module. It is the planning for
implementing the oracle apps in a company.
Planning Bill of Material is BOM which includes component
distribusion percentage. Distribution percentage will get
applied at forecast explode.
Below is general WIP set up.
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)
It is the non-stockable item .phantom items are treated
just like assemblies except that the phantom item itself
does not show up when an assembly is exploded. The child
items of the phantom are blown through and appear as
children of the parent item to the phantom.
For example, I have an assembly called 5887M which contains
a phantom item called 445-0001. When I add the 5887M to a
work order and explode the 5887M ,the 445-0001 will not
appear in the pick list, but it's children will appear.
ERP handles phantom items in work orders in the following
way. A phantom item will be exploded so that all it's
child items will be in the work order. After the work order
is exploded, you will notice that the phantom item will not
appear in the exploded BOM of the work order.
Osp cycle is only carrying out to incur the cost value in
wip summary report,osp is usually doing only for each
job,osp is generally mapping at wip operations level,once u
r operations comming for osp know, that time
automatically/manually we have to creat purchase req,and
press the outside processing button at the footer
level,then it is asking for u r desctete job number,and go
ahead to creat the pur req for that osp,then receive the
osp item directly to shop floor,and the a/c is
automatically in wip summary and in GL a/c.
Work order less completion in WIP helps us to complete the
job manually without creating a job.
Suppose client wants to continue a job creation function in
other ERP like peoplesoft,SAP but they wants to track
inventory in Oracle apps at that we used to go for Work
order less completion.
Accounting classes are assigned and used when jobs, work
orders,and repetive assemblies associated with production
lines are defined.
Generally standard discrete, asset non-standard discrete
and expense non-standard discrete.
We need to assign an accounting class all your discrete
Standard discrete accounting classes can be used to group
job costs. For example, if you
build subassemblies and finished goods, you can define your
accounting classes so that
you can separately value and report the costs associated
with subassembly and finished
goods production. Standard discrete accounting classes can
be automatically defaulted
when you create discrete jobs.
Non-standard discrete accounting classes can be used to
group and report various types
of non-standard production costs, such as field service
repair or engineering projects.
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.
Repetitive Accounting Classes
Repetitive accounting classes are used to group production
costs and must be assigned
to each repetitive line/assembly association that is
created. Every schedule for that
assembly on that line uses these accounts. The accounts are
charged whenever you
transact against the line/assembly association. Repetitive
accounting classes can be
automatically defaulted when you associate repetitive
assemblies with production lines
Negigation is -Work in process-->setup-->Wip accounting