Special Topics For Work in Process Page 1 of 22 Rev 1

Special Topics for Work in
Process
Overview
Copyright © Oracle, 2008. All rights reserved.
Special Topics for Work in Process

Page 1 of 22 Rev 1
System References
Distribution
Job Title*
Ownership
The Job Title [list@YourCompany.com?Subject=EDU42DFY.doc] is responsible for ensuring
that this document is necessary and that it reflects actual practice.

Page 2 of 22 Rev 1

Page 3 of 22 Rev 1
Objectives
Objectives
After completing this lesson, you should be able to:

• Generate reports and concurrent requests
• Understand electronic signatures
• Understand outside processing setup and flow
• Close and purge jobs and schedules

Page 4 of 22 Rev 1
Agenda
Agenda
• Generating Reports and Requests

• Overview of E-Signature Flows in Work in Process
• Outside Processing Flows
• Closing and Purging Jobs and Schedules

Page 5 of 22 Rev 1
Generating Reports
Generating Reports
Generating Reports
Oracle Work in Process provides many reports enabling a complete picture of transactions,
materials, resources, costs, and job and schedule progress. Use reports to help you control shop
floor activities.
When submitting a report, you select report parameters such a sorting features, job, assembly,
department, employee, and date range values. A description of several of the standard reports
offered in Work in Process follows:
Discrete Job Data Report—lists complete information on discrete jobs. You can use this
report to review all details about a job, such as quantities, dates, routing operations, material
requirements, resources, instructions, sales orders, comments, and accounts.
Discrete Job Dispatch Report—lists jobs to be completed. You can use this report to
prioritize the work in each of your manufacturing departments.
Discrete Job Pick List Report—lists open component requirements for jobs with statuses of
Unreleased, Released, Complete, or On Hold. You can use this report when you pick material
from stock to issue to jobs.

Page 6 of 22 Rev 1
Discrete Job Routing Sheet—lists the operations and associated resources and material
requirements for jobs with statuses of Unreleased Released, Complete, and On Hold. You can
use the report output as a traveler for the discrete job on the shop floor.
Discrete Job Shortage Report—lists either jobs with open requirements or jobs with
component requirements where a shortage exists.
Discrete Job Value Report - Standard Costing—assists in analyzing your standard discrete
jobs and non-standard asset jobs.
Resource Transaction Report—lists resource transaction information for discrete jobs and
repetitive schedules.
Shop Floor Statuses Report—lists shop floor statuses in alphabetical order. The report also
lists status descriptions, disable dates, and identifies which statuses prevent you from moving
assemblies.
WIP Account Distribution Report—details account information for work in process cost
transactions including resource, overhead, outside processing charges, cost updates, and period
close and job close variances. The report groups transactions by job or schedule, transaction
type, and orders transactions by earliest transaction date.

Page 7 of 22 Rev 1
Submitting Concurrent Requests

A concurrent request is call for processing that runs simultaneous with you other application
processing. You can create a task for a report or a concurrent program to be scheduled and
submitted as a single request, or multiple reports and programs submitted together as a request
set. You can submit concurrent requests to create transactions in Work in Process such as:
• AutoCreate Final Assembly Orders program creates final assembly work orders from sales
order demand.
• Closing Discrete Jobs enables you to submit criteria for closing jobs based.
• Importing Jobs and Schedules program generates the WIP Mass Load function to create
jobs and update existing jobs.
• Purging Jobs and Schedules enables you to purge old job and schedules records in your
database
The Requests window enables you to:
• View the status of your submitted requests
• Change processing options
• Diagnose errors

Page 8 of 22 Rev 1
• View your request output

Page 9 of 22 Rev 1
Agenda
Agenda


Page 10 of 22 Rev 1
Overview of E – Records and E- Signatures
Overview of E – Records and E- Signatures
The Oracle E-Records application supports Federal Food

and Drug Administration's regulation of electronic records
to monitor activities.
Overview of E-Records and E-Signatures

The Oracle E-Records application supports Federal Food and Drug Administration's (FDA)
code regulation 21 CFR Part 11. This regulation supports the creation of electronic records to
monitor activities by regulated industries such as food, pharmaceuticals, and medical devices.
These industries are subject to audit, retention of records, and capture of legally binding
signatures.
Oracle Manufacturing’s support of these features enables compliance for companies falling
under FDA regulation and similar global regulations. Manufactured product data is
electronically captured and has a complete audit trail. The e-records and e-signatures
framework uses Oracle Workflow business events and Oracle XML Gateway. This framework
enables you to define event metadata to specify the reporting format for the event. To use this
functionality, you must set transaction processing to online mode, and install Oracle Workflow.
Note
Refer participants to the Oracle e-Records Implementation Guide for detailed information
regarding setup and details of e-records.

Page 11 of 22 Rev 1
Work in Process E- Signatures
Work in Process E- Signatures
Work in Process transactions creating electronic

signatures include material, move, and completion
transactions.
A B C D
Work in Process E-Signatures

The Work in Process transactions creating electronic signatures include material transactions,
assembly moves, and assembly completions:
• Material Transactions, this includes the following transaction types:
- WIP component issue
- WIP component return
- WIP negative component issue
- WIP negative component return
• Move Transactions, the following transaction types are included:
- Move
- Complete
- Return
• Completion Transactions, the following transaction types are included:
- WIP assembly completion
- WIP assembly return

Page 12 of 22 Rev 1
Agenda
Agenda


Page 13 of 22 Rev 1
Setting Up Outside Processing
Oracle Manufacturing enables you to include supplier

sourced components and resources in your manufacturing
processes.
Supplier PO to supplier for components

You can define outside processing items that represent supplier sourced items, resources, and
services that you include in your build process. These items can be non-stocked items which
represent the supplier contribution in your build process, or you can define the assembly itself
as an outside processing item. The outside processing item is the item on your requisition or
purchase order and the item you receive in purchase order receipts. These components are
defined by using the Supplier supply type on bills of material to identify components. Supplier
components are not backflushed
Outside resources can be defined and associated with these items. The outside resources are
included on your routings for scheduling and costing purposes.
Automatic Requisition Generation
Work in Process automatically generates a purchase requisition for outside processing
operations, unless you specify that they be created manually. The timing of the creation of the
purchase requisition is based on the setting of the Requisition Creation Time parameter. If you
set the parameter to:
• At Job/Schedule Release, a purchase requisition is created for all outside processing
operations on a job or schedule when you release the job or schedule.

Page 14 of 22 Rev 1
• At Operation, a purchase requisition is created when you move into the Queue
intraoperation step of an outside processing operation. You then use the Autocreate feature
to convert these requisitions to purchase orders or releases against blanket agreements.
The Requisition Import process automatically runs when using PO Move and PO Receipt
resource types. However, only PO Move initiates the Intermediate Shipment workflow.

Page 15 of 22 Rev 1
Outside Processing Flows
• When you receive outside processing items, they are

moved to Queue of the next operation or To Move of
the final operation.
• If it is the last operation for PO Move resources, the
assembly is completed.
OP 40 Queue Run To Move

If you receive more assemblies than the quantity in the Queue of the outside processing
operation, WIP automatically moves a quantity up to the over-completion tolerance limit on
the assembly being built.
If the outside processing operation is the last operation on the routing, and the resource has a
charge type of PO Move, Work in Process automatically completes both full and partial outside
processing assembly quantities into Inventory when they are received back from the supplier.
Values for job date, status, and quantity changes are passed to related purchasing documents.

Page 16 of 22 Rev 1
Outside Processing Workflows
• Intermediate Shipment
• Ship and Receive Intermediates
• Notify Second Buyer and Supplier
1 2 3

To enable you to track your outside processing assemblies from the shop floor to the supplier,
Work in Process provides the following four workflows. The workflows automatically send
notifications and activate processes during specific points in the outside processing process:
• Intermediate Shipment workflow tracks outside processing assemblies from the shop floor
to the supplier.
• Ship and Receive Intermediates workflow notifies the shipping manager and the supplier
that outside processing assemblies are ready to ship.
• Notify Second Buyer and Supplier workflow is used when you have two consecutive
outside processing operations.
• Change Order Approval Workflow in Oracle Purchasing is used to change date, quantity,
or status on the purchase order. If the supplier approves the change, the need by date is
updated on the requisition and the purchase order, and a notification is sent to the buyer
and supplier.

Page 17 of 22 Rev 1
Agenda
Agenda


Page 18 of 22 Rev 1
Closing Jobs and Schedules
You can close discrete jobs using:

• Close Discrete Jobs (SRS)
• Close Discrete Jobs window

You can close discrete jobs using the Close Discrete Jobs (SRS) and Close Discrete Jobs
windows. Information associated with a job is not deleted when the job is closed. You can
view information for closed jobs, and print reports. The window you choose depends on your
requirements for closing jobs:
The Close Discrete Jobs window enables you to:
• Submit and immediately process job close requests
• Specify a close date other than the system date
• Unclose discrete jobs
• Check and resubmit failed job close requests
• View discrete jobs before closing them
The Close Discrete Jobs (SRS) window enables you to:
• Specify when to submit the close request (concurrent or scheduled processing)
• Specify a close date other than the system date
• Use criteria for closing jobs based on a range of accounting classes, job numbers, and
dates—including release, start, and completion dates

Page 19 of 22 Rev 1
• Exclude or include jobs:
- Linked to sales orders
- Uncompleted jobs
- Jobs with pending transactions
Prior to closing discrete jobs, review job value information using the Discrete Job Value
Report.
Close Discrete Jobs Window
You cannot close a job that has pending material, resource, or move transactions including
those that the concurrent manager has not processed. You also cannot close a job that has
uncosted material transactions, however you have the option to close these types of jobs in the
concurrent program.
• When a job with outside processing operations is changed to complete, closed, or canceled
status - an informational warning message displays if open purchase orders or requisitions
exist for any of the operations.
• Changing a job status to completed, closed, or canceled is prevented if open reservations
exist. You have two options in order continue:
- Unlink the sales order reserved to this job
- Reduce the job quantity of the job to equal the completed quantity
When you query jobs to close on the Close Discrete Jobs window, the Summary window
appears with the results of your query.
• Select a record to close, and choose Close from the Tools menu. The Close Discrete Jobs
Request window appears.
• Select a Report Type (or no report) and options and formats (such as summary or detail).
Reports are printed per the Report Type specified, after the close process computes job
close variances.
- For standard costing, the Discrete Job Value Report - Standard Costing is printed
- For average costing, the Discrete Job Value Report - Average Costing is printed.
• Select an Actual Close Date and a Submission Date and time. The system date and time is
the default.
Unclose Requirements
Use the Close Discrete Jobs window to unclose jobs, that is, correct jobs closed in error.You
cannot unclose a job that does not have a status of Closed, linked to a sales order, or closed in a
closed accounting period.
Close Discrete Jobs (SRS)
The close requirements for the concurrent program are the same as when using the Close
Discrete Jobs window. In the concurrent program, you can also use criteria for closing jobs
based on a range of accounting classes, job numbers, and dates. You can also close jobs as of a
specific date, rather than the date the program is executed.

Page 20 of 22 Rev 1
Purging Jobs and Schedules

Closed jobs should be purged on a periodic basis to remove unneeded records and maintain
database performance. You can use the Purge Jobs and Schedules 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 such as material
requirements, resource requirements, operations, associated ATO configurations, or associated
move and resource cost transactions.
After selecting which jobs/schedules to purge, you can choose from the following action type
options:
• Purge and Report purges the selected jobs/schedules and prints a report.
• Report Only prints a report listing the selected jobs/schedules but does not purge them.
• Purge Only purges the selected jobs/schedules but does not print a report.
Refer to Practice Closing Discrete Jobs [LAB43B8Y]

Page 21 of 22 Rev 1
Summary
Summary
In this lesson, you learned how to:

• Generate reports and concurrent requests
• Use electronic signatures
• Set Up outside processing and understand the
flow
• Close and purge jobs and schedules

Page 22 of 22 Rev 1

Special Topics For Work in Process Page 1 of 22 Rev 1

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Special Topics For Work in Process Page 1 of 22 Rev 1

Caricato da

Copyright:

Formati disponibili

Special Topics for Work in

Copyright © Oracle, 2008. All rights reserved.