Oracle Manufacturing Applications Release 11I: Outside Processing Isupplier Portal

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 30

Oracle Manufacturing

Applications Release 11i


Outside Processing
iSupplier Portal
Overview
• Proposed process flow
• iSupplier Portal integration
• BOM/Routing and related setups
• Example OSP transaction flow
• Cost Management impact
Proposed Outside Processing Flow
Physical Flow
System Flow

Supplier
Print/Fax/E-Mail OR
iSupplier Portal

Ship/Drop Ship PO Receive


Completed
Components
Assemblies
Manual OR
Automatic Release PO Receipt via
LINE RECEIPT
in DMPlus
Autorequisition Backflush
takes place
upon PO receipt

Discrete Job Discrete Job Discrete Job


Created Released Completed
iSupplier Portal
Integration with WIP, PO, AP

iSupplier Portal

Invoices
Invoices Payments
OSP Discrete Jobs

Standard POs
Updated Promised Dates
Blanket Agreements
ASNs
Blanket Releases

Work In
Payables
Process
Purchasing
OSP Setups - Item Master
Item Master attribute indicates OSP item
Bill of Material
• The BOM for OSP items under new process
would be largely the same as the current BOM
• List Coty-supplied items with supply type =
Operation Pull (for backflushing)
• Backflush subinventory/locator would be the
vendor’s specific location within Coty inventory
• List Vendor-supplied items with supply type =
Vendor (to prevent backflushing)
Bill of Material
Routing Terminology
• A resource is anything of value (except materials)
required to manufacture, cost, and schedule products.
Resources include people, machines, and labor purchased
from suppliers.
• A department is a logical and/or physical area which
consists of one or more resources.
• An operation is a step in a manufacturing process where
you perform work on, add value to, and utilize resources
for an assembly. Operations take place inside a
department.
OSP Setups - Resources

This becomes the


“OSP Cost” for
the assembly
OSP Setups - Resources
• Since one OSP resource setup will be
required per OSP item in the item master,
the setup of this process will be automated
using Oracle Workflow
• Other resources can be setup for capacity
planning purposes
OSP Setups - Resources
OSP Setups - Department
OSP Setups - Routing
• Each OSP item must have a routing
• The routing must contain an “outside
processing enabled” resource
• When discrete jobs for the OSP item are
released, Oracle will automatically create a
requisition for the item which is linked to
the OSP-enabled resource
OSP Setups - Routing

Operation 10 represents the


outside processing operation

Operation 20 represents the


total time between when the
assemblies are completed at
the supplier, until they are
received by Coty
OSP Setups - Routing
This is the Outside Processing resource which tells Oracle to create a purchase requisition

40 Labor
HR/1000

100
Assy/HR

These optional resources can be used for scheduling, lead time, and capacity purposes
OSP Setups - Routing

For scheduling purposes, use the machine resource only. In this case, 100 assemblies per hour
OSP Setups - Routing

This adds three days of lead time to the item


Discrete Job MRP/Planner
specifies this

Oracle
calculates this

Lead time = 5 hours (500 at 100 per HR) plus 3 days transit time
Purchase Requisition

Requisition automatically created upon discrete job getting “Released”

Req automatically sourced to blanket PO if one exists


Purchase Order
Before any transactions occur...

All 500 assemblies show up “In Queue” of first operation, meaning they are not yet produced at supplier
PO Receipt

PO Receipt for 150 assemblies performed

PO now shows 350 remaining


Discrete Job

Job still shows 500 remaining


Discrete Job

150 received against PO are now showing “In Queue” of second operation, which represents shipment to Coty
Discrete Job receipt

Discrete Job receipt for 150 assemblies performed, now show up as Completed on job and go into inventory
Discrete Job receipt

150 completed assemblies now show as completing both operations (assembly & shipment)
OSP Checks & Balances
• If planner reschedules an OSP discrete job, choose
“Update PO Need By Date” from Tools menu, and
Workflow will inform buyer & supplier of corresponding
PO date change, along with approve/reject options at each
stage
• If supplier updates promised date through iSupplier Portal,
workflow will notify buyer and planner
• Oracle prevents cancellation of the discrete job as long as
the attached PO is still open
Internal vs. OSP Discrete Jobs
• The BOM attached to OSP orders can be
maintained using standard Oracle “Material
Requirements” screen, using the discrete
job number rather than the PO number
OSP Receiving
• PO receipt will:
– trigger component backflushes
– “complete” the OSP operation on the routing
– automatically close the PO when fully received
• Discrete job receipt will:
– place the OSP items into inventory
– trigger inspection (same as internal jobs)
– “complete” the discrete job when fully received
Cost Management Impact
Cost Element “Outside Processing”
to hold OSP-related costs

You might also like