Oracle Applications 11i

Oracle
Applications 11i
Training On
Oracle Work In Process 11i
A Presentation by EAS – Oracle Applications
September 2003
Agenda
 Introduction to Work In Process

 Overview of Work In Progress
 Setting Up & Implementing WIP
 Create and Update Discrete Jobs
 Scheduling Discrete jobs
 Create and Update Repetitive Schedules
 Scheduling Repetitive production
 Work in Process Transactions - Moves and Resources
 Complete Discrete Jobs and Repetitive Schedules
 Work In Process Interfaces
Introduction to Work in
Process
 Oracle Work In Process is a complete production
management system.
 Work In Process supports discrete, project, repetitive,

assemble-to-order, and work order-less manufacturing.
 Inquiries and reports give a complete picture of

transactions, materials, resources, costs and job/schedule
progress on the shop floor.
Process
Production Methods –Discrete
Discrete production records all production activities against

a discrete job. It represents a plan to produce a specific
quantity of an item on a specific date. All material issues
(Manual and Backflush), and all resource charges
(Automatic and Manual) are charged to a specific job
Discrete job can produce Assemble to Order (ATO) items
and Configure to Order (CTO) item.
Process
Production Methods –Repetitive
Repetitive production models high-volume production of

standard items over a period of time. Production is
recorded against a repetitive schedule that represents a
plan to produce an item at a given daily rate for a period of
time.
Overview of Work in
Process
Overview of Manufacturing Support
Following types of jobs and schedules can be used to support
specific manufacturing needs:
 Standard and Non-Standard Discrete Jobs
 Standard and Non-Standard Project Jobs
 Repetitive Schedules by Production Line/Assembly
 Final Assembly Orders
 Work order less completions
Overvi ew of Wo rk in
Pr oc ess
Overview of Production Scheduling
 Oracle Work In Process can be used to schedule
production resources and materials, to meet customer
delivery requirements and to maintain a smooth production
flow.
 Scheduling establishes expected dates and times for
material and resource requirements, as well as for the
supply availability of assemblies built on the jobs and
repetitive schedules.
Pr oc ess
Overview of Production Scheduling (Cntd..)
Production Scheduling includes:
 Loading/sequencing repetitive production by
assembly/production line.
 Scheduling start / stop times for jobs, operations and
resources to the minute.
 Scheduling fixed, variable and overlapping time elements.
 Forward, backward, manual and midpoint forward
rescheduling.
 Automatically updating the master schedule.
Pr oc ess
Overview of Production Scheduling (Cntd..)
Work In Process uses two scheduling methods:
 Detailed Scheduling
 Repetitive Line Scheduling
Note: Oracle Work In Process only provides unconstrained

scheduling.
Pr oc ess
Overview of Material Control
Oracle Work In Process gives the ability to control and
monitor the materials used for production and to view how
they flow from inventory to discrete jobs/schedules, and
from the discrete jobs/schedules to inventory.
Material transactions:
 Issue and Return Material to Inventory
 Back flush Material
 Replenish Material
Pr oc ess
Overview of Material Control (Cntd.)
While defining jobs and repetitive schedules,
Material can be controlled by:
 Combining bills of material with routings to create specific
material requirements.
 Specifying when and where materials are to be
issued or back flushed.
 Assigning Supply Types to control how materials are
supplied.
Pr oc ess
Overview of Shop Floor Control
Shop floor control helps manage the flow of production in a
plant leading to efficiencies that can lower costs and help to
meet the delivery commitments.
Shop floor control options:
 Move assemblies within operations.
 Load move transaction information from external systems.
 Define and assign shop floor statuses.
 Auto-create purchase requisitions for outside processing
operations .
 Rework problem assemblies.
 Scrap assemblies.
Pr oc ess
Overview of Shop Floor Control (Cntd.)
There are five available intra-operation steps.
 Queue: Default intra-operation step for every operation in a
routing
 Run: Assemblies which are ready to be worked on.
 To Move: Assemblies waiting to be picked up for next
operation.
 Reject: Rejected Assemblies
 Scrap: Scrapped Assemblies
Pr oc ess
Overview of Shop Floor Control (Cntd.)
 Oracle Work In Process considers an assembly to have

completed an operation if the assembly is at To Move,
Reject, or Scrap steps.
 Oracle Work In Process considers an assembly to have not
completed an operation if the assembly is at Queue or Run
steps.
Pr oc ess
Overview of Resource Tracking
 A resource can be assigned to each operation on a Work
In Process routing.
 A resource can be assigned manually, after
creating a job or can be added to the operation while
creating the routing.
 A resource resides within an operation, it can be a person,
a machine, tools, services, etc.
 There are three resource charge types:

-WIP Move
-Manual
-PO Move/PO Receipt
Pr oc ess
Overview of Importing Transactions
Import transactions enables users to:
 Access real time and accurate information to increase
efficiency through out the fulfillment process.
 Key technology enablers

– Mobile Computing & Process Critical devices
– Wireless Networks
– Bar code Technology
Pr oc ess
Overview of Work In Process Costing
 Use WIP accounting classes to establish valuation and
variance accounts.
 Use Standard, Average or LIFO/FIFO costing.
 Cost standard and non-standard asset discrete production
by job.
 Cost jobs by project in Oracle Project Manufacturing
Costing.
 Cost and report repetitive and non-standard expense
production by period.
Pr oc ess
Overview of Work In Process Costing (Cntd.)
 Charge and report resource, outside processing, and
overhead costs by activity.
 Track repetitive production costs by assembly on a line/
individual repetitive schedule.
 Track and report costs through the various stages of
production.
 Period close costs are calculated when an accounting
period is closed.
Setting Up & Implementing WIP
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)
B
A
6.Define Schedule Groups (Optional)
7. Define Employees (Optional)
8.Define Employee Labor Rates (Opt.)
9. Define Shop Floor Statuses (Optional)
10.Define Job/Schedule Docs (Optional)
C
C
11.Define Operation Documents (Optional)

WIP Parameters
 WIP parameters define modes of operation and default
values that affect Work in Process
WIP parameters can be used to define modes of operation

and assign default values for various
work in process functions.
 Only one set of WIP parameters can be defined per

organization.
WIP Parameters – Screen shots
(N) WIP > Set up > parameters
Determines how lot numbers are
.
assigned to discrete jobs Options
are job name & based on inventory
rules
Determines whether the

Determines which accounting
WIP jobs respond to
class is used as the default
Sales order changes
if category default WIP
.Options are Always/never
accounting classes are not set
/When linked 1 to 1 (ATO)
up. Used to default in
Standard/non-standard Discrete
jobs & Work order-less
completions

Applicable only for average costing Determines how resource costs are
organizations determined as assemblies are
Determines
completed from jobs into inventory.
whether the Final
System Calculated : resources can
Completion in the
be costed at either the actual
Completion
resource costs or at resource
Transaction
predefined cost depending on the
window defaults
System Option parameter . For
o checked
assemblies from a non standard job
with no routing, the resource rate
from the Average Rates cost type
Used only when ‘system calculated’ option is is used.
selected. User Defined: you must choose a
Use Actual Resources: Resources costs are user–defined cost type using the
determined based on the actual costs charged Cost Type Parameter. This cost
to the job. type is then used to determine the
Use Predefined Resources: Resources costs resource cost for the assemblies
are determined using the predefined resource being completed.
cost.

Determines which repetitive
schedule variances are posted to
the general ledger when an
accounting period is closed.
Determines the time

period within which the
system automatically
releases the next
Unreleased schedule.

Determines whether a scrap account is required
when you use the Move Transactions window to
move job and repetitive assemblies into and out of
the Scrap intra-operation step of an operation. also
determines how scrap transactions are processed.
Determines whether you Determines whether moves are

can or cannot add an disallowed if an intra-operation step
operation to a discrete that disallows moves exists at an auto
job work in process charge operation and
routing during a move Intra-operation step between the From
transaction. and To operations or at
intervening intra-operation step at the
From and To operations if they
are direct charge.

Determines which supply subinventory and, if
required by the subinventory, locator are used
when back flushing Operation Pull and Assembly
Pull components that do not have defaults
defined at the bill of material/item level
Determines how lot controlled

Assembly Pull and
Determines how lots that are Component Pull component
automatically selected, based on items are selected during
whether back-flush transactions. Not
the Lot Selection Method used for lot/serial controlled
parameter is set to Receipt Date or items
Expiration
Date, are verified during back-flush
transactions.
Determines which intra-operation steps are enabled in WIP

routing operations. The options are Queue, Run, To Move, Reject
and Scrap. The Queue intra-operation step is automatically
enabled for all operations and cannot be disabled. The To Move
intra-operation step, even if disabled here, is automatically
enabled for the final operations in routings so that assemblies can
be completed into inventory.

Determines which shop floor status is assigned to the
Queue intra-operation step of an outside processing
operation when you create discrete jobs and repetitive
schedules. This status ensures that assembly moves
from an outside processing resource operation can
only be launched by the receipt of a purchase order in
Oracle Purchasing.
Determines whether purchase

requisitions are created for
outside
processing operations
automatically or manually, and
when in the
manufacturing process they are
created
WIP Accounting Classes
Accounting classes are assigned when jobs are defined
and when repetitive assemblies are
associated with production lines.
Any number of WIP Accounting Classes can be defined
and updated.
The valuation and variance accounts that are associated
with these accounting classes determine which accounts are
charged.
WIP Accounting Classes – Screen shots

(N) WIP > Set up > WIP accounting classes
Standard Discrete Accounting Class
 An accounting class must be assigned to every

discrete job, schedule and work order-less completion
 Accounting classes can be defined for each type of

discrete production used:
– Standard Discrete
– Asset Non-Standard Discrete
– Expense Non-Standard Discrete
– Flow Manufacturing
Expense Non-Standard Discrete Accounting Class
Non-Standard Discrete Accounting classes can be

used to group and report various types of non-standard
production costs. Example: To track recurring expenses
-- machine maintenance or projects with non-standard
jobs.
The valuation accounts carry the costs incurred on
these expense jobs as an asset during the period and
automatically write them off to variance accounts at
period close.
Asset Non-Standard Discrete Accounting Class
If non-standard discrete jobs are used to track

production costs as assets, an accounting class with a
type of asset non-standard can be assigned .
 Asset non-standard discrete jobs are costed the same

as standard discrete jobs.
Repetitive Accounting Class
These 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.
Repetitive manufacturing costs can be analyzed by

assembly regardless of the line on which it was
manufactured by using the same accounting class for
all lines that build that assembly.
WIP Accounting Class -Accounts
Material Valuation Account
This is an asset account and tracks material costs.
Under Standard Costing, it is debited at std cost at

material issue to a job/schedule and credited when
assemblies are completed, close a job/accounting
period.
Under Average Costing, this account is debited

at the average cost at the time of issue transaction and
is credited at assembly completion.
WIP Accounting Class
Material Overhead Valuation Account
This tracks material overhead costs.
Under Std Costing, it is debited at std cost at material

issue with a overhead to a job. Under average costing,
this account is debited at the average cost at the time of
the issue transaction.
When assemblies are completed and material

overhead is earned, the material overhead account for
the completion sub-inventory is debited.
Resource Valuation Account
This tracks resource costs.
Under Standard Costing, it is debited at std cost when

resources are charged to a job/schedule and credited
on completion of assembly.
Under Average Costing, this account is debited and

credited at the resource rate at the time the resource is
charged.
Outside Processing Valuation Account
This tracks outside processing costs.
Under Standard Costing, it is debited at standard or

PO cost when items are received for a job/schedule and
credited at standard cost on completion of assembly.
Under Average Costing, the behavior is the same as in

Standard Costing.
Overhead Valuation Account
This is an asset account and tracks resource or

department overhead cost.
Material Variance Account
This account tracks variances that occur when the

previous level material costs charged to the job or
schedule do not equal the previous level material costs
that are relieved.
This calculation gives you a net material usage and
configuration variance.
Resource Variance Account
This account tracks variances that occur when the this

level resource costs charged to the job or schedule do
not equal the this level resource costs that are relieved.
Outside Processing Variance Account
 This account tracks the variances that are occur when

the outside processing costs charged to the job or
schedule do not equal the outside processing costs that
are relieved.
Overhead Variance Account
This account tracks the variances that are occur when the
overhead costs charged to the job or schedule do not equal
the overhead costs relieved from the job or schedule.
Standard Cost Variance Account

Applies only to Standard Discrete and Asset Non-
Standard. It’s charged for the sum of all the elemental
standard cost adjustments when standard cost update
impacts an active job.
Cost updates are not performed for repetitive schedules or
expense non–standard jobs.
Expense Variance Account
Normally an expense account, this account is debited and

credited when issuing and completing non–standard
expense jobs under both standard and average costing.
Shop Floor Statuses

Move transactions are controlled by assigning Shop Floor
Statuses to intra-operation steps on the work in process
routing. For example a “Hold for Quality Check” status can
be assigned to an intra-operation step before moving to the
next assembly step.
Shop Floor Statuses can be assigned to any Intra operation

step associated with a job/repetitive line/assembly.
Shop Floor Statuses

(N) WIP > Move Transactions > Shop Floor Statuses >
Shop floor status
Schedule Groups
Flow schedules and discrete jobs can be assigned to the
schedule groups defined.
Jobs and flow schedules within a given schedule
group can be sequenced.
Sequencing jobs and flow schedules within a schedule
group makes it possible to prioritize, for example, by
customer.
Schedule groups can be updated.
Schedule groups that are assigned to jobs and flow
schedules cannot be deleted.
Schedule Groups
(N) WIP > Setup > Schedule Group
Screen shots
Labor Rates
 Used for defining hourly labor raters to reflect the actual
labor rates.
The effective date of the hourly labor rates can be added,
deleted, and updated for person-type resources
(employees).
Multiple hourly labor rates can be defined for the
same employee, as long as each rate has a
different effective date.
Labor Rates
(N) WIP > Setup > Employees > Labor Rates
Screen shots
Production Lines
A production line describes a unique set of
operations, departments, and/or manufacturing
cells that produce one or more of products.
Production lines can be associated with repetitive

assemblies, discrete jobs, flow routings, schedules, and
work order-less completions.
Production lines can be defined and updated but cannot be

deleted.
Production Lines
(N) WIP > Setup > Production Lines
Screen shots
Operation Documents
 Operation Documents can be defined for discrete

jobs, repetitive schedules, and job/schedule operations.
Operation Documents can then be attached to

discrete jobs, repetitive schedules, and operations
as required.
Operation Documents
(N) Oracle Work in Process > Set Up > Defining Operation
Documents
Profile Options
TP:WIP: Background Shop Floor Material Processing:
Used only when the TP: Move Transaction profile is set to

Background processing & for a move completion/move return
/operation pull back-flush transaction.
Available Values:
Background Processing: Periodic Processing
Concurrent Processing: Inventory Transaction processor is
launched.
Online Processing (Default): Move transaction processor
processes the shop floor material back-flush transactions online
by calling the inventory material transaction processor.
Profile Options
TP:WIP: Completion Material Processing
Controls material processing of assembly completion,

assembly return, and assembly completion back-flush
transactions initiated using the Completion Transactions window
Background Processing, Concurrent Processing & Online
Processing (Default)
Note: If TP:WIP: Completion Transactions Form profile is set to
Background processing, this profile is not used.
Also, if TP:INV: Transaction Processing Mode profile is set to
Form level processing in average costing scenario , this profile
must be set to Online for sequential transaction procession.
Profile Options
TP:WIP: Completion Transaction Form
Determines whether completion transactions are processed

online or in the background when transacting assembly
completions using the Completion Transactions window.
Background Processing, Online Processing (Default)
Note: Also, if TP:INV: Transaction Processing Mode profile is set

to Form level processing in average costing scenario , this profile
must be set to Online for sequential transaction procession.
Profile Options
TP:WIP: Completion Transactions first field
Determines which field the cursor defaults to when you first

enter the Completion Transactions window. Set this option based
on your predominant manufacturing environment
Line, Assembly, Job (Default) , or Sales Order.
Profile Options
TP:WIP: Concurrent Message Level
Determines the level of detail reported in the move transaction

concurrent log file during move transaction validation and
processing.
-Message level 0 (Default) : Reports errors only.
-Message level 1 : Reports processing activities and errors.
-Message level 2 : Reports and time stamps processing
activities and errors.
Profile Options
TP:WIP: Material Transaction Form
Controls the processing of component issue and return

transactions entered in the WIP Material Transactions window.
Background Processing, Concurrent Processing & Online
Processing (Default)
Note: Also, if TP:INV: Transaction Processing Mode profile is set

to Form level processing in average costing scenario , this profile
must be set to Online for sequential transaction procession
Profile Options
TP:WIP: Material Transactions First Field

enter the WIP Material Transactions window. Set this option
based on your predominant manufacturing environment
Profile options
TP:WIP: Move Transactions:
Determines How move transactions performed using the
Move Transactions form
Available values
- Background processing: Processed on a periodic basis
-(Default) Online processing: The transaction is processed
while saving and control is returned once transaction
processing is done.
Note: Also, if TP:INV: Transaction Processing Mode profile
is set to Form level processing in average costing scenario ,
this profile must be set to Online for sequential transaction
procession.
Profile Options
TP:WIP: Move Transactions First Field

enter the WIP move Transactions window. Set this option based
on your predominant manufacturing environment
Profile Options
TP:WIP: Move Transaction Quantity Default
Indicates if and how move transaction quantities are defaulted.
None: No transaction quantity is defaulted.
Minimum Transfer Quantity: Transaction quantity defaults if the
minimum transfer quantity is less than or equal to the available
quantity. If the minimum transfer quantity is more than the
available quantity then the available quantity is defaulted
Available Quantity: If the available quantity is not zero, the
transaction quantity defaults to the available quantity.
.
Profile Options
TP:WIP: Operation Back flush Setup
Controls the back-flush setup used in the Move Transactions

Window. It also determines how component lot numbers are
derived.
-Background processing: Use this option only when lot
numbers are automatically assigned.
-Online processing: Use this option when lot/serial numbers
must be manually assigned
Profile Options
TP:WIP: Shop Floor Material Processing
Controls processing of operation and assembly pull back-flush,

assembly scrap, move completion, and move return transactions
from the Move Transactions window.
-Background processing: Use this option only when lot
numbers are automatically assigned.
-Concurrent processing:
-Online processing: Use this option when lot/serial numbers
must be manually assigned
Profile Options
TP:WIP: Work Order-less Default Completion
Determines the default for the Scheduled flag in the Work

Order–less Completions window.
-Scheduled : The Schedule flag defaults to checked. Use
this option if most of the work order–less completions are based
upon flow schedules.
-(Default) Unscheduled : The Scheduled flag defaults to
unchecked. Use this option if most of the work order–less
completions are manually entered .
Profile Options
WIP: Default Job Start Date
Determines whether the start dates for jobs default to the
current date and time or not at all when defining jobs in the
Discrete Jobs
window. Available Values are Yes or No (Default)
WIP: Define Discrete Job Form

Indicates how to load the bill of material and routing
information when defining jobs in the Discrete Jobs window.
-Concurrent definition:
-(Default) Interactive definition:
Profile Options
WIP: Discrete Job Prefix
Specifies the job prefix to use when auto-generating job names
in the Discrete Jobs, Simulate Discrete Jobs, Import Jobs and
Schedules, and Auto-Create windows in Work in Process, and in
the Planner Workbench window in Oracle Master Scheduling/MRP
and Oracle Supply Chain Planning.
WIP: Enable Outside Processing Workflows

Determines whether or not outside processing workflows are
enabled. The options are Yes and No (Default)
Profile Options
WIP: Exclude Open ECOs
Determines whether engineering change orders (ECOs) with
Open statuses are excluded while defining jobs/schedules. If so,
only ECOs with Release, Schedule, and Implement statuses are
implemented when you choose a bill of material revision or
revision date and the bill of material is exploded. This profile
option also controls whether revisions associated with open ECOs
can be selected in the WIP Material Transactions.
WIP: Job Name Updateable

Determines whether you can update the names of existing jobs
in the Discrete Jobs window.
Profile Options
WIP: Move Completion Default
Determines the default transaction type for the Move
Transactions window. If you Yes is specified , the transaction type
defaults to Complete. Otherwise, the transaction type defaults to
Move.
WIP: Requirement Nettable Option
Determines which sub-inventories to include when displaying
on–hand quantities in the Material Requirements and View
Material
Requirements windows.
Available values
-View only nettable subinventories:
-View all subinventories (Default) :
Profile Options
WIP: See Engineering Items
Determines whether jobs and schedules for engineering items can
be defined and whether engineering items can be added as
material requirements.
Cr eate and Update Di sc rete
Jobs
Discrete Life Cycle
START
1.Set up discrete manufacturing
2. Define Discrete Jobs
3.Update Discrete Jobs
4.Build Discrete Jobs
4.Close Discrete Jobs

Jobs
Job Name uniquely
Discrete Job Definition identifies the job for the
Issuing components,
(N) WIP > Discrete > Discrete Jobs Moving/scrapping/
completing assemblies
Job Quantities ,Charging resources/
are used to overheads and Defining/
determine: updating job definition
Material
requirements,
Department
Standard - A discrete job
schedules,
controlling material/
Resource load
operation requirements to
& Job dates.
build assemblies/collect
manufacturing costs
Nonstandard • A discrete
job controlling material and
•
collects costs for
Various stages in miscellaneous activities,
the life cycle of such as Rework, service
the discrete job. •
repair ,Upgrade etc
When defining a
job, only
Unreleased/
Released/On Hold
statuses exist
Jobs
Discrete Job Definition
Routing revision
allows you to
select which
version of the
routing you want
to use to
schedule the
operations and
resources.
subinventory in
which completed
assemblies will be
housed.
Jobs
Bill Revision allows
you to select any valid
version of the bill of
material
you want to use to
determine the material
requirements for the
job
Jobs
You can view material

requirements and
operations from the
Discrete Jobs window
as you define and
update jobs
Create and Update D iscrete
Jobs
Creating Components
When a job is defined , WIP copies the assembly bill created
in BOM. It then creates material requirements for the copied
bill of material components. Supply types can be used to
control how to supply the components for the material
requirements on the job.
Jobs
When you click the Components
Discrete Job Definition button on the ‘discrete jobs’
form, the Material Requirements
window is displayed with the
component information. Here you
can view each component’s Main,
Quantity, Supply, Comment, and
ATP information. For those
components with ATP rules, you
can perform an ATP check from
this window
Jobs
WIP Supply Types
Supply types are defined in the bill of material. If the supply
type is changed on discrete job, it overrides the supply types
for all the components on that job.
NAME DESCRIPTION
Based on bill Component requirements with supply types from BOM or
those on the Item Master are defaulted when a job is defined.
Assembly Pull Assembly pull components are issued to the job when the assembly
is completed into inventory.
Bulk These components are not transacted automatically in a job.
Operation Pull Operation pull components are issued to the job when the operation
is completed.
Push Material is issued manually before consumption
Vendor Vendor supplies material directly to WIP
Jobs
WIP Supply Types
For Phantom supply type , Phantom subassemblies are
exploded and their components become material
requirements.
Following BOM parameters to control the inheritance of a

parent phantom’s operation sequence and whether or not
resources and overheads on phantom routings are recognized
for costing and capacity planning purposes.
Use Phantom Routings
Inherit Phantom Inherit Phantom Operation Sequence

Jobs
Creating Operations
When a job is defined , operations and resource
requirements are created based on the assembly
routing.
The routing created in BOM is copied to
become a work in process routing that can be
modified without affecting the BOM routing.
Dates and times for the operations, resource

requirements, and material requirements needed to
build the job can be scheduled using detailed
scheduling.
Jobs
When you click the

Operations button, the
Operations window is
displayed. Here you can
view each operation’s
Main, Quantities, Dates,
and Description. Also, from
this window, you can
display the resource
requirements for a selected
operation.
Jobs
Update Discrete Job Data
In a discrete job, following information can be updated:

 Header information, based on the job status
 Routing information
 Bill information
 Sales order information
 Job operations
 Job requirements
Note: If the profile option WIP: Job Name Updatable is

set to No, the name of the existing job cannot be updated .
Jobs
Update/Delete Discrete Job Operations
An operation from a discrete job can be updated /deleted if:
 There are no assemblies at the operation.

 No assemblies have been completed at the operation.
 There are no pending transactions in the open move
interface table.
 No resources at the operation have been charged.
There are no pending transactions in the open resource
interface
If an operation is deleted , WIP reassigns its material
requirements to the first operation in the routing, or to
operation sequence 1 if there are no operations in the routing.
Jobs
Update/Delete Resources
A resource requirement from a discrete job can be deleted if:
That resource has not been charged to the operation.
There are no pending transactions in the open resource

interface table.
Jobs
Discrete Work Station
Tool to graphically view and perform manufacturing

activities on the shop floor. This workstation enables
to quickly and easily obtain information critical to supporting
business decisions and controlling daily shop floor activities.
Production operators can:
Quickly and easily obtain component and resource

requirements, as well as performance measurements.
Perform shop floor transactions without returning to the WIP
menu.
Jobs
Discrete Work Station
(N) WIP > Discrete > Discrete Workstation

Jobs
Using Non standard Discrete Jobs
Advantages:
 Control materials and resources for nonstandard projects.
 Track costs for various activities.
 Report on all aspects of production.
 Manage the activities like :
– Rework
– Upgrades
– Field service repair and maintenance
– Disassemblies
– Engineering prototypes
–– miscellaneous activities
Jobs
Features of Nonstandard Jobs
Assign any predefined bill/routing of material to a

nonstandard job.
Specify an assembly on a nonstandard job.
Include a job quantity on a nonstandard job.
Add the same assembly which is being built as a material
requirement on the job’s bill of material.
Use expense costing to periodically write nonstandard
production costs to expense accounts
Define the WIP accounting class as an asset or as an
expense to the job.
Scheduling Discrete Jobs
Scheduling Jobs
Business Needs
Planning material and resources quickly and accurately
Establishing appropriate planning time fences for products
Creating purchase orders for material accounting for
vendor lead time
Scheduling material to arrive at the operation where it is
consumed
Scheduling each resource at the operation where it is
consumed
Promising accurate product shipment dates
•
Scheduling Methods:
Oracle Manufacturing supports two scheduling
methods for discrete production: dynamic lead-time
offsetting and detailed scheduling.
Dynamic Lead-Time Offsetting:

Estimating the start date of an order, an operation, or a
resource based on order quantity, lead times, and the
workday calendar.
Scheduling Methods:
Detailed scheduling:
 Jobs are scheduled to the minute based on detailed
resource availability and usages.
 Oracle Bills of Material calculates manufacturing lead
times using detailed scheduling.
 Detailed scheduling is the most precise method in Oracle
Manufacturing.
Lead Time Elements
Preprocessing lead time: The time required to release a

purchase order or a job from the time the requirement is
known.
Post processing lead time: The time to make a purchased
item available in inventory from the time it’s received.
Processing lead time: The time required to procure or
manufacture an item. Processing lead time includes the
fixed and variable portions of lead times.
Lead Time Elements
Cumulative manufacturing lead time: Total time required to

make an item if all raw materials are in stock but all
subassemblies will have to be made level by level; Oracle
Bills of Material automatically calculates this value.
Cumulative total lead time: Total time required to make an

item if no inventory existed and all the raw materials and
make all subassemblies will have to be ordered level by
level; Oracle Bills of Material automatically calculates this
value.
Lead Time Elements
Processing Lead time:

Oracle Bills of Material computes the fixed and variable
portions of processing lead time using routings and detailed
scheduling.
Fixed lead time: That portion of time required to build an
assembly that is independent of order quantity—for
example, setup or teardown.
Variable lead time: That time required to produce one
additional unit of an assembly.
These lead times are used by Oracle Manufacturing in
dynamic lead-time offset calculations
Lead Time Elements

Calculating Processing Lead Time for Manufactured Items:
The algorithm schedules one discrete job for a quantity of

zero (fixed lead time) and a second discrete job for the lead-
time lot-size quantity (variable lead time).
When computing processing lead time, all calendar days are

considered as workdays, regardless of days off or workday
exceptions.
Detailed Scheduling
Business Needs
Detailed scheduling is a method of scheduling production that

considers minute-to-minute resource availability information as
well as exact routing resource requirements
Job completion dates and times for assembly supply availability
Job start dates and times for job release
Operation starts and completion dates and times .
Operation start dates and times for component demand
requirements
Resource load information for capacity planning
Detailed Scheduling: Key Terms

Resource requirement: The amount of a resource that is
required to perform an activity in a routing of a job.
Resource availability: The availability of a resource, taking

into account the manufacturing calendar, including workday
exceptions, shifts, and shift exceptions.
Critical path: The sequence of resources in the routing of a

job that are used to schedule the job.
Overlap: A situation in which two or more scheduled

resources can operate at the same time. This can be in one
operation or across consecutive operations.
Scheduling Rules
All resources that have the Scheduled attribute set to Yes,
Prior, or Next must have a time-based unit of measure.
All resources that have a unit of measure that is not time-

based, such as U.S. dollars, kilograms, or gallons, must
have the Scheduled attribute set to No.
Oracle Capacity performs resource load analysis only for

resources with a time-based unit of measure.
Scheduling Methods: Oracle WIP Versus Oracle

Planning
Oracle WIP Oracle Planning
Schedules all discrete jobs backward Schedules all planned orders
or forward backward from the due date
Schedules jobs into the past if Compresses jobs to start on the
backward scheduling past the current current date if the calculated
date start date would be in the past
Uses detailed scheduling to schedule Uses lead-time offset to
discrete jobs with routings to the schedule planned orders for
minute assemblies with routings and
Uses lead-time offset to schedule without routings to the day
discrete jobs without routings to the
day
Create and update Repetitive
schedules
Repetitive Schedule
 A repetitive schedule builds an assembly on a

production line at a specific daily rate for a specific
number of processing days.
schedules
Discrete Life Cycle
START
1.Set up Repetitive manufacturing
2. Define Repetitive Schedules
3.Update Repetitive Schedules
4.Build Repetitive Assemblies
5.Stop repetitive schedules and analyze

repetitive Costs
schedules
Repetitive Schedule Elements
Daily Quantity: The number of completed assemblies that

are planned to be produced each day. The daily rate can be
any positive number/decimals.
Days: The planned number of working days, from the first

unit start date to the last unit start date. The processing days
can be any positive number/decimals.
Total Quantity: The number of completed assemblies that

are planned to be produced.
Note: If you enter any two of the three values, the
third one is automatically computed.
schedules
Repetitive Schedule Dates
First Unit Start Date (FUSD): The date and time to begin
production of the first assembly on a repetitive schedule.
Equal to start of lead time
First Unit Completion Date (FUCD): The date and time to

complete production of the first assembly on a
repetitive schedule. Equal to FUSD plus the lead time
Last Unit Start Date (LUSD): The date and time to begin
production of the last assembly on a repetitive schedule
Calculated based on the FUSD, repetitive processing days,
and hourly production rate
schedules
Repetitive Schedule Dates
Last Unit Completion Date (LUCD): The date and time to

complete production of the last assembly on a repetitive
schedule. Equal to LUSD plus the lead time
schedules
Repetitive Schedule Definition
(N) WIP> Repetitive Manufacturing > Associating
Lines and Assemblies
The hourly production

rate determines how
fast each line can
produce this
assembly.
schedules
Repetitive Schedule Definition
(N) WIP> Repetitive> Repetitive Schedules
Various stages in the life

cycle of the Repetitive
schedule. When defining a
schedule , only Unreleased/
Released/On Hold statuses
exist
Scheduling Repetitive production
Business needs:
 Optimized use of line capacity
 Effectively sequenced repetitive production
 Time-phase repetitive component demand and

assembly availability
Elements of Repetitive Line Scheduling

 Minimum rate: The minimum number of completed
assemblies a production line can produce per hour.
 Maximum rate: The maximum number of completed

assemblies a production line can produce per hour.
 Line lead time: Time required to complete the 1st

assembly on a production line starting from the 1st
operation to completion into inventory.
 Hourly production rate: The rate at which the
production line can assemble items.

 Line start time: The time a production line starts
running every day. The line start time is used to
schedule repetitive schedules on a line.
 Line stop time: The time a production line stops

running every day. The line stop time is used to
schedule repetitive schedules on a line.
 Daily line capacity: The daily production rate of

assemblies on a production line. This is equal to the
hourly production rate times the line production hours.
 Daily rate: The number of completed assemblies a

repetitive schedule plans to produce per day. Also
known as a production rate.
 Repetitive processing days: The number of days you

plan to work on a repetitive schedule, from the first
unit start date to the last unit start date.
Repetitive Line Scheduling

 Daily quantity is used to specify how many
assemblies per day to build
 Days are used to specify for how many days

an assembly is to be produced at the specified rate
 Line minimum and maximum daily rate can be used

as a guideline for the daily quantity of schedule

 Can specify to the minute the start and completion dates
and times of your repetitive schedule
 Can schedule to the minute each day the operations and
resources of the schedule.
 Can schedule all the requirements based on operation
dates each day of the schedule.
 Must enter either the first unit start date and time and the
first unit completion date and time, or the last unit start date
and time and the last unit completion date and time, in
order to define the lead time for a routing less assembly
running on a routing-based line.
The top horizontal line

indicates the constant
hourly production rate
that was defined for the
line for this assembly.
Schedule production
hours =
quantity per day/ hourly
production rate.

Each shaded area
represents the quantity
produced (the daily
rate) in a day.
The un shaded area
represents idle time for
this assembly on this
line.
The total quantity for

the schedule is
processing days times
daily rate i.e.. the sum
of all the shaded
areas.
Repetitive schedules based on suggestions from

Oracle Planning or any other planning system can
be defined.
Schedules are loaded into Oracle WIP with a status

of Pending—Mass Loaded due to following reasons:
-MRP does not consider existing schedules.
Implementing these schedules without looking at existing ones
can result in overproduction.
-MRP-suggested schedules may overlap with existing
schedules, which is not allowed.

Not allowing overlap
enables WIP to perform
flow charging for
(Flow charging is when
a repetitive assembly
and line is charged
rather than a specific
job. It is based on FIFO.
Work in Process Transactions -
Moves and Resources
Work In Process Flow -Definitions
Types of Material Transactions
Issue transaction is a material transaction to issue

component items from inventory to work in process.
Replenishment transaction is a material transaction to

stage components in advance of backflushing.
Return transaction is a material transaction to return

components from WIP back to inventory. Return
transactions increase WIP material requirements, inventory
balances, and valuation, and decrease WIP valuation.
Moves and Resources
Material issue transactions fulfill WIP material

requirements on jobs or schedules. These reduce inventory
balances and valuation & incur WIP costs and increase
WIP valuation.
Supply types are used to control how components are
supplied to fulfill material requirements.
Push issue transaction is a material transaction to issue
component items from inventory to work in process before
you manufacture the assembly.
Moves and Resources
Backflush transaction is a material transaction that

automatically issues component items into work in process
from inventory when you move or complete the assembly.
A backflush transaction is also known as post–deduct or
pull.
Moves and Resources
Move Transactions
Move transactions move assemblies from any operation on the
routing to any other operation. Moves normally follow the
sequence as per routing.
Move Transactions can initiate other transactions

- Backflush issue transactions for components with supply type
Operation Pull
- Automatic resource transactions for resources with autocharge
type WIP Move
- Overhead transactions for overheads with basis type Item or Lot
Moves and Resources
Move Transactions
Intraoperation moves are assembly moves within an operation.
Intraoperation steps are phases within an operation used to
track assembly locations in detail. The steps are Queue, Run,
To Move, Reject, and Scrap.
Operation completions occur when quantities move into to

move, reject, or scrap.
Interoperation moves are assembly moves from one operation

to another in a routing.
Moves and Resources
Move Transactions
autocharge flag controls
operation completions
It’s advisable that
and associated automatic the Backflush flag
transactions. of the last
operation
on a routing
always be set to
Count point determines Yes, to make sure
that all
the default for the next components are
operation for a move issued.
transaction.
Backflush flag controls

when to process
Backflush transactions.
Moves and Resources
Backward Move Transactions
Backward move is used to correct a mistake or to perform
additional work at a previous operation. An operation can be
uncompleted by reversing any of the moves that constitute
operation completion
When an operation is uncompleted, system automatically

reverses any backflushing transactions that have taken place
during the forward move.
On uncompletion, system automatically reverses WIP move

resource charges. Automatic resource charges for Lot-based
resources are reversed when all assemblies have been
uncompleted at the operation.
Moves and Resources
Move Transactions
WIP (N) Move Transaction > Move Transactions
Moves and Resources
Overcompletions
 Can over move or over complete within tolerance
 Move and complete more assemblies than at
operation
Assignment of Shop Floor Statuses

(N) Move Transaction > Shop Floor Statuses > Assign Shop
Floor Statuses
System provides an option that prevents users from
performing move transactions over operations and
intraoperation steps that have No Move statuses,
depending on the autocharge types of the operations.
Moves and Resources
Costing Move Transactions: Accounting Entries
Costing Backflush Material Transactions
Move transactions can automatically launch backflush

transactions and charge resources and overheads.
Backflush material transactions increase WIP valuation
and decrease inventory valuation.
The accounting entries for backflush material transactions:
Account Debit Credit
WIP accounting class valuation accounts XX
Inventory valuation accounts XX
Moves and Resources
Costing Move-Based Resource Transactions
Resource charges increase your work in process valuation.

The accounting entries for resource transactions:

WIP accounting class resource XX
valuation accounts
Resource absorption account XX
Moves and Resources
Costing Overhead Charges
Overhead charges increase work in process valuation.

The accounting entries for overhead transactions:

WIP accounting class overhead account XX
Overhead absorption account XX
Moves and Resources
Costing Backward Move Transactions
Charges Reversed.
Backflush material Yes
Resource charges only WIP Move resource charges are
reversed.
Overhead charges Overhead charges reversed if default
basis is Item.
Reversed if default basis is Lot only if
the move results in zero net
assemblies completed in the operation
Moves and Resources
Overhead Charging
Charging Method Default Basis Overhead Charge
Move-based Item Fixed amount per item

overhead charging
Lot Fixed amount for
first unit completed
Resource-based Resource units Fixed amount for each
overhead charging resource unit charged
Resource value Percentage of the
resource value
Moves and Resources
Overhead Charging
Move-Based Overheads
Upon completion of an operation, system automatically

charges move-based overheads. Move based overheads are
overheads that have a default basis of Item or Lot. Upon
uncompletion, overhead charges are reversed. For Lot-based
overheads, charges are reversed when all assemblies have
been uncompleted at the operation.
Moves and Resources
Overhead Charging
Resource-Based Overheads
If the operation completion move resulted in automatic

resource charges for WIP Move resources, and these
resources have associated overheads, the overheads will be
charged when the resource is charged. Therefore, a move
transaction that completes an operation can result indirectly in
resource-based overhead charges. Resource-based overhead
charges are reversed when the resource transaction is
reversed.
Moves and Resources
Managing Rejected Assemblies
Definitions:
 Reject is an intraoperation step in an operation at which

assemblies that require rework or need to be scrapped are
recorded.
 Scrap is an intraoperation step at which assemblies that
cannot be reworked or completed are moved.
 Scrap account is an account used to charge scrap
transactions.
Moves and Resources
There are five ways to manage rejected assemblies in WIP
 Move rejected assemblies to Reject.

 Scrap rejected assemblies.
 Add rework operation.
 Inline rework.
 Rework in a nonstandard job.
Moves and Resources
Move rejected assemblies to Reject.
 Rejected assemblies can be moved to the Reject
intraoperation step to possibly rework them at that operation or
later move them to Scrap.
Benefits
 Isolates questionable assemblies.
 Works well if there is space near the work center to
temporarily store the
 questionable assemblies (same operation, same department).
 Option to scrap or recover the questionable assemblies.
Moves and Resources
Scrapping Rejected Assemblies
 Assemblies that cannot be recovered can be moved to the
Scrap intraoperation step.
Benefits
 Isolates material.
 Deducts from MRP supply on standard discrete jobs.
 Offers the option to write off scrap immediately instead of
waiting for the job close (standard discrete/nonstandard asset
jobs) or period close (repetitive/nonstandard expense jobs).
 Offers the option to undo the transaction later if necessary.
Moves and Resources
Reworking Rejected Assemblies
 rejected assemblies can be reworked directly in the job by
adding a rework operation in the WIP routing.
Benefits
 Use predefined rework operations for repeatable rework
activities.
 Add the rework operation when necessary.
 Easily charge incremental material, resource, and overhead
costs at rework operation.
Moves and Resources
Reworking Rejected Assemblies
 rejected assemblies can be reworked directly in the job by
adding a rework operation in the WIP routing.
Benefits
 Use predefined rework operations for repeatable rework
activities.
 Add the rework operation when necessary.
 Easily charge incremental material, resource, and overhead
costs at rework operation.
Moves and Resources
Inline Rework
 Can use a routing with a rework operation and rework rejected
assemblies directly in the job/schedule. This is a std operation
with a Count point No and the resources charge type Manual.
Benefits
 Allows to predefine & use the rework operation on the routing
when rework is anticipated.
 Rework can be performed on a repetitive production line
(Previous option applies only to discrete jobs as operations can’t
be added to a repetitive routing).
 Can easily charge incremental material/resource/overhead at
rework operation.
Moves and Resources
Using a Nonstandard Job to Rework Assemblies
 Can rework rejected assemblies currently in an MRB

subinventory using a nonstandard job.
 Optionally you can store the assemblies in that subinventory
until you are ready to rework them.
Benefits
 Standardization of Process
 Can use a separate Accounting class to track such orders

Moves and Resources
Charging Resources
Resource is a thing of value, except material and cash, that is
required to manufacture, cost, and schedule products.
Resources include people, tools, machines, services purchased
from a vendor, and physical space.
Resource basis is the basis for resource usage quantity that

indicates whether that quantity is required per item or per lot.
Lot-based resources are resources whose usage quantity

represents the amount required per job or schedule. For
example, it could be setup time for a machine.
Moves and Resources
Charging Resources
Item-based resources are resources whose usage quantity

represents the amount required per assembly you make. For
example, it could be the amount of time required to process
each assembly at an operation for the job.
Resource transaction is a transaction where resource costs

are charged to a discrete job or repetitive schedule. Transacting
a resource is synonymous with charging a resource.
Moves and Resources
Charging Resources
WIP Move Resource : A WIP move resource is a resource that

is automatically charged to a discrete job or repetitive schedule
by a move transaction that completes an operation. The
autocharge type for this type of resource is WIP Move.
Manual Resource: A manual resource is a resource that you

manually charge to a discrete job or repetitive schedule. The
autocharge type for this type of resource is Manual.
Moves and Resources
Charging Resources
Manually Charging Resources
Resources can manually be charged to a discrete job/repetitive

assembly and line with or without an associated move
transaction.
Manually charging resources without a move

Manually charging resources with a move
Manually reversing resource charges
Moves and Resources
Charging Resources
Manually Charging Resources with a Move
Move transaction can be performed normally .

Resources with an autocharge type of Manual assigned to the
operations completed during the move can be charged. (WIP
displays those resources automatically).
If the standard rate flag for a manual resource is No, and the
resource type is Person, the resource can be charged at the
employee labor rate instead of the standard rate by specifying
an employee identifier.
This transaction is done from the Move Transactions window
using Resources button.
WIP (N) Move Transaction > Move Transactions (B) Resources
Moves and Resources
Charging Resources
Manually Charging Resources without a Move
Any resource assigned to an operation in a job or schedule

can be charged.
Any resource not previously assigned to an operation in a job

or schedule can be charged. The resource must be defined for
the department associated with the operation. It can have
autocharge type Manual/WIP move.
This transaction is done by navigating to the Resource

Transactions window.
WIP (N) Resource Transactions > Resource Transactions
Moves and Resources
Charging Resources
Manually reversing Resource charges
User can manually reverse resource charges at any time by

specifying negative resource units applied.
This transaction is done by navigating to the Resource

Transactions window.
WIP (N) Resource Transactions > Resource Transactions
Moves and Resources
Charging Resources
Automatic Resource Transactions
Automatically charging resources at standard rate

 Completing an operation and automatically charging
resources
 Reversing resource charges
Moves and Resources
Charging Resources
Automatically Charging Resources at Standard Rate
Resources can be automatically charged at their standard rate

to a discrete job or repetitive assembly and line while performing
a move transaction.
Moves and Resources
Charging Resources
Completing an Operation and Automatically Charging Resources
All resources with an autocharge type of WIP move are

charged at their standard rate.
WIP move resources with a basis type of Item are charged upon
completion of each assembly at the operation the resource is tied
to.
WIP move resources with a basis type of Lot are charged upon
completion of the first assembly at the operation the resource is
tied to.
Moves and Resources
Charging Resources
Reversing Resource Charges
If an uncompletion is performed, system automatically reverses

any resource charges associated with the completion for WIP
move resources.
If a WIP move resource has a basis type of Lot, system

reverses the resource charges only if all assemblies are
uncompleted at the operation.
Moves and Resources
Charging Multiple Schedules
Flow charging is a repetitive transaction method in which
system charges material, move, resource, and overhead
transactions to a specific assembly on a line rather than a
specific repetitive schedule.
If more than one schedule has a status that allows charges,
user can perform transactions against the consolidated sum of all
the schedules.
For example, if there are three schedules for 100 units each
with status Released for the same assembly and line
combination, up to 300 units could be moved with one
transaction.
Moves and Resources
Advantages of Flow Charging
Flow charging means that shop floor data entry can be performed
by charging against the assembly and line.
Flow charging means that all transactions against an assembly
on a line can be batched and then enter all of them in one
transaction.
Flow charging supports the idea of a schedule being less of an
individual entity than a discrete job is. As long as two schedules
build the same assembly on the same line, system does not
distinguish between them for transaction purposes.
Moves and Resources
Repetitive Allocation
Repetitive allocation is a system technique for applying

transaction quantities and costs across several repetitive
schedules that are building the same repetitive assembly on the
same line.
The repetitive allocation algorithm allows the system to allocate
the transactions that were flow charged to particular schedules.
Moves and Resources
Costing Resource Charges at Resource Standard
Resource charges increase work in process valuation. The
accounting entries for resource transactions are:
WIP accounting class resource
valuation account XX
The accounting entries for negative manual resource

transactions and backward moves for WIP move resources are:
Moves and Resources
Costing Labor Charges at Actual
For labor charges using an actual or employee rate for a resource
with the Standard Rate check box clear, the job or schedule is
debited at the actual or employee rate. The employee rate used
needs to be set up at the organization level. The absorption
account is credited at the same rate. The variance between actual
and standard is captured at the time of accounting close.
accounting entries for resource transactions are:

Moves and Resources
Costing Resource Transactions
If the actual rate is greater than the standard rate, the accounting
entries are:
Resource rate variance account XX
If the actual rate is less than the standard rate, the accounting
entries are:
Resource rate variance account XX
Moves and Resources
Weighted Average costing
Material can be charged to WIP at average cost.
Resources can be charged to WIP at actual or average cost.
Outside processing resources can be defined under average

costing.
The average cost of completed assemblies in WIP can be

calculated.
Complete Discrete Jobs
and Repetitive Schedules
Completing Jobs
Definitions
Assembly completion transaction is a material transaction in which

assemblies are received into inventory from a job or repetitive
assembly/line upon completion of the manufacture of the
assembly.
Completion subinventory is an inventory location at the end of

production line or shop floor routing where completed assemblies
from work in process are received . This is often the supply
subinventory for subassemblies or finished goods inventories for
final assemblies.
Completing Jobs
Completion Transaction Process
The finished assemblies are received into inventory, either to be

used as subassemblies or to be shipped as finished goods.
All Assembly Pull material attached on the bill is backflushed.
The quantity in the To Move step of the last operation is

decreased, if there is a routing.
The Quantity Complete on the job or repetitive schedule is

increased.
Completing Jobs
Completion Transaction Process
If the quantity completed equals the total quantity for a schedule,
and there are other active schedules following it on the
assembly/line, the schedule’s status is changed to Complete—No
Charges. If the schedule is the last active schedule, its status is
changed to Complete.
Job and repetitive schedule statuses are automatically updated

to Complete when the total number of assemblies completed and
scrapped on a job or repetitive schedule is greater than or equal to
the required quantity.
Completion Transactions
Complete assemblies from jobs and repetitive schedules into
inventory
Return completed assemblies from inventory to jobs and

repetitive schedules
over-complete assemblies
(N) WIP > Material Transactions > Completion Transactions
Assemblies can
be over
completed to
inventory from
jobs and
schedules per
established
tolerance limits
without changing
the job start
quantity.
Work order less completions
Using work order-less completions:
 Complete assemblies without having to create a job
or schedule
 Do several tasks in one step at completion
 Substitute components
 Support lot and serial number control
 Cost transactions using standard and average
costing
Work order less completions
(N) WIP > Material Transactions > Workorder-less
Returning Assemblies from Inventory to WIP
Completed assemblies can be returned to work in process
using the Completion Transactions window as well as the
Move Transactions window.
Reasons to Return Assemblies to WIP

 User want to perform additional processing.
 User found a quality problem.
 User mistakenly completed unfinished assemblies to
inventory.
 User performing a disassembly using a nonstandard job.
Returning Assemblies from Inventory to WIP
Return Characteristics
 User can return assemblies from inventory to WIP by
selecting Return as the transaction type.
 User can return as many assemblies as needed.
 Any assembly pull components that were backflushed
upon completion are unbackflushed; that is, they are
returned to inventory when you return the assembly to
work in process.
Costing Completion Transactions
Costing Assembly Completion Transactions
Completion transactions decrease work in process valuation
and increase inventory valuation. The accounting entries
for assembly completion transactions are:
Subinventory elemental
accounts XX
WIP accounting class
valuation accounts XX
Costing Completion Transactions
Earning Assembly Material Overhead on Completion
 Overheads can be assigned based on the total value of
an item. These overheads can be earned as assemblies into
are completed into inventory. The accounting entries are:
Subinventory material overhead
account XX
Inventory material overhead
absorption account XX
Manufacturing Average Costing
 Items can be costed at a weighted average perpetual cost.
 Completions are valued using the sum of the actual costs of
resources and materials issued to a job
 Partial completions are valued using the appropriate
proportional sum of actual resource and materials issued to
a job
 Final completions are valued using the total net value in a
job
 The unit cost of a completion is computed elementally
Material ,Material and overhead ,Resource, Overhead &Outside processing
Completion Transactions for Repetitive Schedules
Roll forward Rules
 When all assemblies of a schedule are completed, WIP
checks the schedule for any excess components resulting
from over issue of material requirements.
 If the subsequent schedule is released, or if it is unreleased
and falls into the auto release time fence, WIP rolls the
excess material charges forward to that schedule.
 If there is no subsequent schedule to auto release, WIP does
not roll the excess material charges forward.
Completion Transactions for Repetitive Schedules
Autorelease
 Repetitive production can be streamlined by automatically
releasing the next schedule when one schedule is
completed.
 A line can continue running and build repetitive assembly if
another schedule is defined for the assembly on that line.
 If the schedule is defined but unreleased, the completion of
the preceding schedule can serve as a signal to
automatically release the next unreleased schedule.
Closing Discrete Jobs
Can the Status of a Closed Job Be Changed?
 To be able to unclose jobs, the Close Discrete Jobs function
security parameter must be set to Y.
 Only jobs closed in error should be unclosed, it should be
done this immediately after the close using the Close
Discrete Jobs window.
 If assembly costs are rolled up between the time a job is
closed and unclosed, costs may be incorrect because the
unclose process does not revalue the job.
 A job that is linked to a sales order cannot be unclosed.
 A job that was closed in an accounting job that is no longer
open cannot be unclosed
Work In P rocess Interfa ces
WIP Interfaces
 Open Move Transaction Interface

 Open Resource Transaction Interface
 Work Order Interface
WIP Interfaces
Open Move Transaction Interface
 This interface is used to transfer WIP move transaction
information into Oracle Applications. The records can be
loaded into the Open Move Transaction Interface from a
variety of sources, including external data collection devices
such as bar code readers, automated test equipment, cell
controllers, and other manufacturing execution systems.
 The interface validates the records & marks invalid
transactions, so that the transactions can be corrected &
resubmitted
WIP Interfaces
This interface enables users to perform many of the functions
possible from the Move Transactions window.
 Move assemblies between operations and intra-operation steps
 Scrap assemblies
 Move assemblies from an operation and complete them into
inventory with a single transaction
 Over-complete a quantity greater than the job or schedule
quantity if over-completions are enabled
 Return assemblies from inventory and move to an operation
with a single transaction
WIP Interfaces
Ad hoc operations cannot be added through this interface even if
the WIP Allow Creation of New Operations parameter is set.
The table populated while inserting records into the interface is
WIP_MOVE_TXN_INTERFACE
Types of move transactions

Move transaction
Move Completion
Move Return
WIP Interfaces
 Columns to be populated:
FM_INTRAOPERATION_STEP_TYPE,FM_OPERATION_SEQ_NUM,
LINE_CODE, ORGANIZATION_CODE, PROCESS_PHASE,
PROCESS_STATUS, TO_INTRAOPERATION_STEP_TYPE,
TO_OPERATION_SEQ_NUM, TRANSACTION_DATE,
TRANSACTION_QUANTITY, TRANSACTION_UOM, WIP_ENTITY_NAME
 FM_INTRAOPERATION_STEP_TYPE,FM_OPERATION_SEQ_NUM
are only required for move transaction/ completion transactions
 TO_INTRAOPERATION_STEP_TYPE,TO_OPERATION_SEQ_NUM are
only required for move transaction & move return transactions
WIP Interfaces
Open Resource Transaction Interface
 This interface is used to charge resources. External data

collection devices such as bar code readers, payroll
systems, and time card entry forms can be used to collect
resource and overhead transaction data, then load the data
into the Open Resource Transaction Interface for WIP to
process.
 The interface validates the data and marks any that are
invalid so that it can be corrected and resubmitted.
WIP Interfaces
This interface enables users to perform many of the functions
possible from the Resource Transactions window.
 Charge labor resources
 Charge overhead resources
 Charge outside processing resources
 Add ad hoc resources
Note: Non-person resources cannot be charged at an actual
usage rate or amount through the Resource Transactions
window. This feature is unique to the Resource Transaction
Interface.
WIP Interfaces
The table populated while inserting records into the interface is
WIP_COST_TXN_INTERFACE
 Columns to be populated:
OPERATION_SEQ_NUM, ORGANIZATION_CODE, ORGANIZATION_ID,
PROCESS_PHASE, PROCESS_STATUS, RESOURCE_SEQ_NUM,
TRANSACTION_QUANTITY, TRANSACTION_DATE,
TRANSACTION_TYPE, TRANSACTION_UOM, WIP_ENTITY_NAME
WIP Interfaces
 PROCESS_PHASE describes the current processing phase of the
transaction. The Cost Worker processes each transaction row
through the following two phases
Values: 1 Resource Validation ,2 Resource Processing
 PROCESS_STATUS contains the state of the transaction.
Values: 1 Pending , 2 Running ,3 Error
 TRANSACTION_TYPE should be set to:
Values: 1 for normal resource transactions,2 for overhead
transactions & 3 for outside processing transactions
WIP Interfaces
Work order Interface
The Work Order Interface enables users to import Discrete job
and Repetitive schedule header information, and Discrete job
operations, material, resource, and scheduling information from
any source, using a single process.
Options available:
 Planned orders for new Discrete jobs,
 Discrete job operations, components, resources, resource
usage, and scheduling details,
 Update and reschedule recommendations for existing Discrete
jobs, and suggested Repetitive schedules
WIP Interfaces
 The Work Order Interface consists of two tables: the
WIP_JOB_SCHEDULE_INTERFACE table (Open Job and Schedule
Interface table), and the WIP_JOB_DTLS_INTERFACE table (WIP
Job Details Interface table). Header information is loaded into
the WIP_JOB_SCHEDULE_INTERFACE table, and operations,
components, resources, and scheduling information into the
WIP_JOB_DTLS_INTERFACE table.
WIP Interfaces
 The Work Order Interface consists of two tables: the
WIP_JOB_SCHEDULE_INTERFACE table (Open Job and Schedule
Interface table), and the WIP_JOB_DTLS_INTERFACE table (WIP
Job Details Interface table). Header information is loaded into
the WIP_JOB_SCHEDULE_INTERFACE table, and operations,
components, resources, and scheduling information into the
WIP_JOB_DTLS_INTERFACE table.
Picki ng for Man ufacturi ng
Picking for Manufacturing
 Introduced in 11.5.7 Family pack for manufacturing
 Combines the functionality of Manufacturing & Warehouse
management system to provide rule based component
picking..
 Operation or assembly pull material can be excluded from the
tasks.
 Migration to the new Picking for Manufacturing is optional for
WIP users.
 Move orders will be created for all component requirements.

Picking supports discrete/lot based jobs, as well as flow &
 The use of move orders will allow users to use the standard
inventory picking rules, as well as to track and transact the
component requirements.
 Supply type push
- Material issued directly to job
- Transacting the move order / task decrements inventory
 Supply type assembly / operation pull
- Material moved to supply subinventory
- Material pulled at operation move or assembly completion
- Optionally excluded from process
 Pick release selected jobs
-Use Inventory Rules to allocate material
-Allocated material cannot be used for other transactions
-Create move orders for the required material
-Missing material is backordered and available for re-
release
 Optionally print move order pick slip report
 Move order transacted on desktop
-Query on specific jobs or schedules
-Update allocations if necessary
Current Functionality in Release 11.5.9
 User can specify upto which operation the material needs to be
pick released for a single or set of jobs.
 Various picking methodologies (like cluster pick, bulk pick, zone
pick etc.) supported by Order management also can be used.
However this feature is limited to Discrete jobs only.
 All the material requirements for a job is released under a
single move order irrespective of the supply types.
 User will have the option on printing of the pick slips at the time
of pick release.
.
Current Functionality in Release 11.5.9
 User can choose whether to plan tasks by default or not for
each pick release. This option can also be set at organization
level and can be overridden by user while pick releasing.
.
 After the pick release, if allocation was partial, user can check
the leftover requirements for a job by clicking on a particular
job node.
 User can see the backordered quantity for each component.
.
(N) WIP> Discrete> Component Pick Release
.
Q&A

Oracle Applications 11i

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Applications 11i

Uploaded by

Copyright:

Available Formats

Oracle

A Presentation by EAS – Oracle Applications

 Introduction to Work In Process

 Work In Process supports discrete, project, repetitive,

 Inquiries and reports give a complete picture of

Discrete production records all production activities against

Repetitive production models high-volume production of

Note: Oracle Work In Process only provides unconstrained

 Oracle Work In Process considers an assembly to have

 There are three resource charge types:

 Key technology enablers

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 (Opt.)

9. Define Shop Floor Statuses (Optional)

10.Define Job/Schedule Docs (Optional)

11.Define Operation Documents (Optional)

WIP parameters can be used to define modes of operation

 Only one set of WIP parameters can be defined per

Determines whether the

WIP Parameters – Screen shots

WIP Parameters – Screen shots

Determines the time

WIP Parameters – Screen shots

Determines whether you Determines whether moves are

WIP Parameters – Screen shots

Determines how lot controlled

WIP Parameters – Screen shots

Determines which intra-operation steps are enabled in WIP

WIP Parameters – Screen shots

Determines whether purchase

WIP Accounting Classes – Screen shots

 An accounting class must be assigned to every

 Accounting classes can be defined for each type of

Non-Standard Discrete Accounting classes can be

If non-standard discrete jobs are used to track

 Asset non-standard discrete jobs are costed the same

These are used to group production costs and must be

Repetitive manufacturing costs can be analyzed by

This is an asset account and tracks material costs.

Under Standard Costing, it is debited at std cost at

Under Average Costing, this account is debited

This tracks material overhead costs.

Under Std Costing, it is debited at std cost at material

When assemblies are completed and material

Under Standard Costing, it is debited at std cost when

Under Average Costing, this account is debited and

Under Standard Costing, it is debited at standard or

Under Average Costing, the behavior is the same as in

This is an asset account and tracks resource or

This account tracks variances that occur when the

This account tracks variances that occur when the this

Outside Processing Variance Account

 This account tracks the variances that are occur when

Standard Cost Variance Account

Normally an expense account, this account is debited and

Shop Floor Statuses

Shop Floor Statuses can be assigned to any Intra operation