EDU42D8Y

Creating Discrete Jobs
Overview
Copyright Oracle, 2008. All rights reserved.

Effective mm/dd/yy
Page 1 of 52
267657629.doc
Rev 1

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

Effective mm/dd/yy
Page 2 of 52
267657629.doc
Rev 1

Effective mm/dd/yy
Page 3 of 52
267657629.doc
Rev 1
Objectives
Objectives
After completing this lesson, you will be able to:

Understand an overview of Discrete Manufacturing
Create discrete jobs
View routings and operations on jobs
View material requirements, resource requirements,
and other job details
Understand standard and non-standard jobs
Understand Importing Jobs and Schedules
Release jobs and view job details

Effective mm/dd/yy
Page 4 of 52
267657629.doc
Rev 1
Agenda
Agenda
Overview of Creating Discrete Jobs

Viewing Operations and Resource Requirements
Viewing Material Requirements
Standard Versus Non-standard Jobs
Importing Jobs and Schedules
Releasing, Building, and Updating Jobs
Summary
Instructor Note
Refer participants to the Oracle Work in Process Users Guide for detailed information
regarding setup and implementation prerequisites for discrete jobs.

Effective mm/dd/yy
Page 5 of 52
267657629.doc
Rev 1
Discrete jobs are assemblies built in specific - discrete quantities. The jobs or work orders use specific materials
and resources.
Resources

A discrete job is a production order for the manufacture of a specific quantity of an assembly,
using a routing and operations. You can:
Manage the flow of component material from inventory to jobs. Bills of material can be
used to create job material requirements
Create operations, resources, and material requirements either concurrently or
interactively
Import planned order recommendations from external systems
Define final assembly order jobs to build custom configurations
Oracle Work in Process provides two single interfaces to perform multiple shop floor functions
the Discrete Execution Workstation or the MES Workstation.

Effective mm/dd/yy
Page 6 of 52
267657629.doc
Rev 1

Features:
Standard and Non-standard jobs
Assign bills and routings to create material
requirements, schedule operations, and resources
Overview of Creating Discrete Jobs (continued)

You can create both standard and non-standard discrete jobs:
Standard jobs control the material, resources, and operations required to build
an assembly and collect its manufacturing cost.
Non-standard jobs control material and collect costs for miscellaneous
manufacturing activity.
When you create bills of material you define for your jobs:
Resources
Alternate bills of material
Departments charged
Standard operations
Routings for the job path
Routings are used to schedule job production activities and create requirements. If you have
Oracle Shop Floor Management installed, you can use lot based jobs which follow a network
routing. Network routings provide flexibility in determining the series of operation moves for
the job.

Effective mm/dd/yy
Page 7 of 52
267657629.doc
Rev 1

Features:
Attachments of illustrations and files
Lot and Serial Control
Sales Order Reservation
Sales Orders

You can:
Define standard documents and attach them to jobs, schedules, and operations.
Build jobs for assemblies for both lot and serial control. You can track your jobs using
serial control throughout the manufacturing process; enabling you to assign, perform serial
transaction entry, import serial numbers, and print serial number labels. This functionality
is supported through Oracle Mobile Supply Chain Applications.
Reserve the assemblies to a sales order.

Effective mm/dd/yy
Page 8 of 52
267657629.doc
Rev 1

Features:
Quality Integration
Simulate Jobs

You can:
Collect quality results when performing move and completion transactions.
Simulate a standard job to determine what materials, operations, and operation resources
are required to support that job; and convert your simulated job into an actual job.

Effective mm/dd/yy
Page 9 of 52
267657629.doc
Rev 1
Agenda
Agenda

Summary

Effective mm/dd/yy
Page 10 of 52
267657629.doc
Rev 1
Discrete Life Cycle
Discrete Life Cycle

1
Defining Discrete Jobs
2
Releasing and Building Discrete Jobs
3
Transacting Discrete Jobs
4
Closing Discrete Jobs

Effective mm/dd/yy
Page 11 of 52
267657629.doc
Rev 1
Discrete Job Elements
Job Name
Type
Class
Status
Quantities
Dates
Bill Revision
Routing Revision
Completion Subinventory
Job Attachments

Effective mm/dd/yy
Page 12 of 52
267657629.doc
Rev 1

Header elements include Job Name, Type, Assembly,
Class, and Status
Enter manually or automatically generate the job name
Profile option to specify updates on names
Standard or Non-standard types
Job
Type
Assembly
Class

You can manually enter or automatically generate the job name. If you manually enter the job
name, the name must be unique and alphanumeric.
Two profile options are used in creating and updating job names:
The WIP:Discrete Job Prefix specifies the job prefix when auto-generating job names. You
access the automatic sequence generator by choosing Apply Default Job Name from the
Tools menu. This process can be used in the Discrete Jobs, Simulate Discrete Jobs, Import
Jobs and Schedules, and AutoCreate windows.
The WIP:Job Name Updatable determines if you have the option to specify name updates
for existing jobs.
If defining a standard discrete job, select the job assembly you are building. If you set the
WIP:See Engineering Items profile option to Yes, you can define jobs for engineering items.
The accounting class default value is set in the WIP Parameters window, the Discrete
parameters tab. You can change this value.

Effective mm/dd/yy
Page 13 of 52
267657629.doc
Rev 1
Job Status
Job Status
Describes various stages in the job lifecycle, and

controls the activities performed on the job
Some statuses are assigned automatically

Effective mm/dd/yy
Page 14 of 52
267657629.doc
Rev 1
User Statuses
User Statuses
Unreleased
Job is not released to the shop floor
Released
Job is available to begin production
Complete
Job is complete, but still can perform transactions
CompleteNo
Charges
Job is completed, but cannot perform more transactions
On Hold
Transactions cannot be performed
Canceled
Closed
No further activity on the job
User Statuses
You can manually change user controlled statuses. For example, you can change a job's status
from Unreleased to Released to initiate the production cycle. Some user statuses are based on
eventswhen you complete the total quantity of a job into inventory, Work in Process
automatically changes the status of the job to Complete.
Statuses that can be reversed are: Unreleased, Released, CompleteNo Charges, On Hold,
Canceled, and Closed.

Effective mm/dd/yy
Page 15 of 52
267657629.doc
Rev 1
Processing Statuses
Processing Statuses
Pending routing load
Concurrent process is loading the routing
Failed routing load
Concurrent process was unable to load the routing
Pending bill load
Concurrent process is loading the bill for the job
Pending scheduling
Associated with the Manufacturing Scheduling

application
Failed bill load
Concurrent process was unable to load the

bill of material
Pending close
Concurrent process is closing the job
Failed close
Concurrent process was unable to close the job
Processing Statuses
Oracle Work in Process uses these statuses to keep track of the concurrent processing
performed on a job.

Effective mm/dd/yy
Page 16 of 52
267657629.doc
Rev 1
Job Quantities
Job Quantities
Quantities are used to determine:
Material requirements
Schedules
Resource load
Dates
Quantities
Start
MRP Net
Job Quantities
The start quantity value for jobs with bills and routings is used to automatically calculate the
component material requirements, department schedules, resource load, and job start and end
dates.
For non-standard jobs, to perform move and completion transactions, the start quantity must be
greater than zero.
You can specify whether a job's material requirements are included as demand in the MRP
netting process by entering a value in the MRP Net quantity field. This value uses the start
quantity value as a default.

Effective mm/dd/yy
Page 17 of 52
267657629.doc
Rev 1
Job Dates
Job Dates
Discrete Job Dates consist of:

Start date: The date and time you plan to start the job.
Release date: The date the discrete job is released to
the shop floor and becomes transactable.
Completion date: The date and time you plan to
complete production. Used for backward scheduling.
Job Dates
For jobs with routings, if you enter a start date and time the completion date and time are
automatically forward scheduled based on the assembly's routing. Similarly, if you enter a
completion date, the start date and time are automatically backward scheduled based on the
assembly's routing.
For jobs without routings, if you enter only one date and time and your job type is standard, the
missing date and time is calculated using the fixed and variable lead time of the assembly. If
the job type is non-standard, the other dates and times are calculated using the fixed and
variable lead time of the routing reference.
The WIP:Default Job Start Date profile option is used to specify whether the start date for a job
defaults to the current date and time.
Note: A discussion of how dates effect scheduling jobs is discussed in the Defining Scheduling
and Resources lesson.

Effective mm/dd/yy
Page 18 of 52
267657629.doc
Rev 1
Bill Revision
Bill Revision
Bill Revision enables you to select any valid version of the

bill of material to determine the requirements for the job.
Bill Revision
Engineering change orders (ECO) are a record of revisions to your bills of material. This
enables you to have the correct revision changes for work as it progresses on the shop floor.
The bill revision and date determines which version of the bill of material is used to create
component and resource requirements. You can update the bill revision of a standard discrete
job as long as the job remains unreleased.
Oracle Advanced Planning provides functionality enabling you to align Work in Process
production with engineering changes for planning. Engineering Change Orders Use-Up
Effectivity is described in the Updating Material Requirements lesson.

Effective mm/dd/yy
Page 19 of 52
267657629.doc
Rev 1
Routing Revision
Routing Revision
Routing Revision enables you to select which version of

the routing to use in scheduling the operations and
resources.
Rev 1
C
Rev 2
Routing Revision
You can select an alternate routing if alternates have been defined for the assembly you are
building. If the WIP:See Engineering Items profile option is set to Yes, you can select
engineering routings as alternates.

Effective mm/dd/yy
Page 20 of 52
267657629.doc
Rev 1
Completion Subinventory is where assemblies are

housed after completed on the production line.
Assemblies are completed into or returned from this subinventory. If the assembly has a
routing, the completion subinventory is defaulted from the routing but can be changed. You can
also change this value when completing assemblies.

Effective mm/dd/yy
Page 21 of 52
267657629.doc
Rev 1
Job Attachments
Job Attachments
You can attach documents and graphics to jobs
Job Attachments
Work in Process provides ability to display attached instructions and documents pertaining to
your production. This can include procedures, diagrams, and assembly instructions.
For jobs created and viewed on the Discrete Jobs window or Discrete Workstation, use the Job
and Schedule Documents window to create a catalog of standard job and schedule documents
For jobs viewed on the Manufacturing Execution System (MES) Workstation, attachments are
defined on the Workstation Parameters page and viewable from the Work Content page.

Effective mm/dd/yy
Page 22 of 52
267657629.doc
Rev 1
Agenda
Agenda

Summary

Effective mm/dd/yy
Page 23 of 52
267657629.doc
Rev 1
Viewing Operations
Viewing Operations
An operation is a step in a manufacturing process

where you perform work, add value, and consume
department resources for an assembly.
An operation consists of a code and a sequence.
OP 10
Assembly
OP 20
Painting
OP 30
Testing
Viewing Operations
The operation code is a label identifying a standard operation. The operation sequence is a
number that orders operations in a routing relative to each other.
After saving a job, you can access the Components and Operations windows to view the details
of the job, including its material requirements, operations, and operation material and resource
requirements. You can view operation information in Work in Process in a variety of ways:
On the Discrete Jobs window, select Operations to display the Operations window
Navigate to Job/Schedule Details to access the Operations window
On the Discrete Workstation, operations display for jobs in a graphical view and
hierarchical list display
On the MES Workstation, operations display on the Operations region page, Dispatch List,
and transaction pages.

Effective mm/dd/yy
Page 24 of 52
267657629.doc
Rev 1
Creating Job Operations
When you define a job, operations and resource

requirements are created based on the assembly routing.
The routing created in Bill of Materials is copied to
become a WIP routing
The WIP routing can be modified without affecting the
BOM routing
OP 10
OP 20
Assembly
Painting
OP 30
Testing

Operations are defined in Oracle Bills of Material. When you created the the job, the
operations associated with that bill of material are assigned to the job. Each routing can have
any number of operations. For each operation, you specify a department that determines the
resources used.
Job operations are discussed in more detail in the Shop Floor Transactions lesson.
Instructor Note
Refer participants to the Oracle Bills of Material Users Guide for detailed information
regarding defining operations.

Effective mm/dd/yy
Page 25 of 52
267657629.doc
Rev 1
Viewing Resource Requirements
A resource is anything - except materials - required to

manufacture, cost, and schedule products.
Includes people, tools, machines, and labor.
OP 10
OP 20
OP 30

After saving a job, you can access resource information. Resources are viewed in Work in
Process in a variety of ways:
On the Discrete Jobs window, select Operations to display the Operations window, and
then select Resource Requirements to display resources for a selected operation.
Navigate to Job/Schedule Details to access the Operations window, and select Resources
On the Discrete Workstation, you can launch the workstation using the resource branch,
and view resources in a graphical or hierarchical display.
On the Resource Workbench view resource information on the Gantt chart.
On the MES Workstation, you have the flexibility to view dispatch lists for one particular
resource or, across multiple resources or departments, or an entire organization. Resources
are also viewed on transaction pages and the Work Content page.

Effective mm/dd/yy
Page 26 of 52
267657629.doc
Rev 1
Creating Resource Requirements

Resources associated with operations represent
activities performed at the operation.
Resource requirements are calculated at job definition.
You cannot create resource requirements without
operations.
OP 10
OP 20
OP 30

Resources are defined in Oracle Bills of Material. When you created the the job, the resources
associated with that bill of materials operation are assigned to the job.
Resources are discussed in more detail in the Defining Scheduling and Resources lesson.
Instructor Note
regarding defining resources.
Refer to Practice Creating Resources, Departments, and Routings [LAB42E5Y]

Effective mm/dd/yy
Page 27 of 52
267657629.doc
Rev 1
Agenda
Agenda

Summary

Effective mm/dd/yy
Page 28 of 52
267657629.doc
Rev 1
Material requirements are the inventory items and

quantities needed to build an assembly.

After saving a job, you can access the Components windows to view the material requirement
details. Material and component requirements are viewed in Work in Process in a variety of
ways:
On the Discrete Jobs window, choose Components. The Material Requirements window
appears and the job's components are displayed. You can then view detailed information
about components in the window's tabbed regions.
Navigate to the View Material Requirements window to view material requirements across
jobs and schedules.
On the MES Workstation, the Components section of the Work Content and Job Details
pages.

Effective mm/dd/yy
Page 29 of 52
267657629.doc
Rev 1
Creating Job Material Requirements
When you define a job, Work in Process copies the

assembly bill created in BOM. It then creates material
requirements for the copied bill of material components.

The supply type on the job is used to direct what the individual components are for the job, the
default supply type is Based on Bill.
For non-standard jobs, bill of material references are used to create material requirements, but
references are not required. You can define the job without material requirements, and then
customize adding requirements.
Material requirements are discussed in more detail in the Updating Material Requirements
lesson.
Instructor Note
regarding defining job components.

Effective mm/dd/yy
Page 30 of 52
267657629.doc
Rev 1
Simulating a Discrete Job
You can simulate a standard job to determine what

materials, operations, and resources are required. This
enables you to:
Vary the quantity and dates
View both on-hand and ATP quantities
Vary the bills of material and routing revisions

You can create and view a simulated job in the Simulate Discrete Jobs window. This window is
also used when the simulation is converted to an actual job. For simulating jobs, you can:
Simulate only standard discrete jobs, however routings are not required.
Simulate jobs for engineering items if the WIP:See Engineering Items profile option is set
to Yes.
Vary the quantity and the start and completion dates to determine scheduling and
requirement constraints.
View both on-hand and ATP quantities for the simulated component requirements.
Vary the bills of material and routing revisions for different materials, operations, and
routing paths.

Effective mm/dd/yy
Page 31 of 52
267657629.doc
Rev 1
Agenda
Agenda

Summary

Effective mm/dd/yy
Page 32 of 52
267657629.doc
Rev 1
Standard discrete jobs control the material, resources,

and operations required to build an assembly and collect
its manufacturing cost.
Non-standard discrete jobs control material and collect
costs for miscellaneous manufacturing activity.
Standard
Non-standard
Standard Versus Non-Standard Jobs

Non-standard job activity can include rework, field service repair, upgrade, disassembly,
maintenance, engineering prototypes, and other projects. Non-standard discrete jobs do not
earn overhead on completion - material overhead at completion is posted directly to the
subinventory material overhead account.
For rework assemblies, you can manually create rework operations or you can use a predefined
rework routing. You can create component requirements at one of the rework operations using
the Material Requirements window. Non-standard jobs for rework enable you to:
Group rejected assemblies on a single rework nonstandard job
Identify the exact rework costs
Inform planning of anticipated supply using the MRP net quantity field
Select an asset type nonstandard accounting class because the job is building assets.

Effective mm/dd/yy
Page 33 of 52
267657629.doc
Rev 1
Bill and Routing Options for Non-standard Jobs
You can assign a bill of material to a nonstandard job.

You can use any bill or routing, including one that does
not match the assembly.
Bills and routings are not used for maintenance work.
Maintenance

An example of using a bill or routing that does not match the assembly is for upgrade work.
You can define an upgrade bill for upgrading several different assemblies using the same
material requirements.

Effective mm/dd/yy
Page 34 of 52
267657629.doc
Rev 1
Quantity Options for Non-standard Jobs
Quantity Options for Non-standard Jobs
You can define a job quantity only if you have specified

an assembly for the job.
The assembly and job quantity values let you perform
shop floor transactions.
Quantity Options for Non-Standard Jobs

You can specify how Oracle Planning applications plans material requirements and job
quantities. For each material requirement on a non-standard job, you can use the MRP Net field
to specify whether MRP includes the requirement as a demand. For the assembly, you can
specify the MRP net quantity as the number of assemblies you expect the non-standard job to
supply on the completion date of the job.
Do not check MRP Net if you do not want to create demand for items that are supplied from a
non-nettable subinventory.

Effective mm/dd/yy
Page 35 of 52
267657629.doc
Rev 1
Bill of Material Looping for Non-standard Jobs
Bill of Material Looping for Non-standard Jobs
You can add the assembly you are building as a

material requirement to the jobs bill of material.
Bill of Material Looping for Non-Standard Jobs

When you specify the assembly that you are working on to the job as a requirement, it
indicates that you are receiving the assembly out of inventory. For rework or upgrade jobs, this
enables you to issue the broken or outdated assembly to the job, and complete the fixed or
upgraded assembly back into inventory.

Effective mm/dd/yy
Page 36 of 52
267657629.doc
Rev 1
Standard Versus Non-standard Job Fields
Field
Standard Discrete Job
Nonstandard Discrete Job
Assembly
Required
Optional, use if performing

move and completions
Firm
Required for MPS
Cannot enter value in this

field
Quantity
Required
Required, but you can enter 0
Routing
Reference
Cannot enter a value in

this field
Optional, enter a value if

performing job scheduling
based on routing

Effective mm/dd/yy
Page 37 of 52
267657629.doc
Rev 1

Field
Standard Discrete Job
Nonstandard Discrete Job
MRP Net
Quantity
Required, defaults from

Quantity
Required for assemblies,

otherwise you cannot enter a
value
Revision
Optional
Required only for assemblies

with routings
Revision Date Optional
Required only for assemblies

with routings
Bill Reference Cannot enter a value in

this field
Optional, enter a value if you

want to automatically create
material requirements based
on a bill

Effective mm/dd/yy
Page 38 of 52
267657629.doc
Rev 1
Agenda
Agenda

Summary

Effective mm/dd/yy
Page 39 of 52
267657629.doc
Rev 1
You can implement planning orders, and import jobs and

schedules from other systems to create work orders.
Other Systems
Planning
WIP

Effective mm/dd/yy
Page 40 of 52
267657629.doc
Rev 1
Implementing Customer Orders
You can automatically link the sales order for a

configured item to the discrete work order.
If your plant directly feeds your customers plant, you
can access customer demands using the Work Order
Interface

You can load planned orders, planned order update recommendations, and suggested repetitive
schedules from any source - planning systems, order entry systems, scheduling packages,
spreadsheets, and order formsinto the Work Order Interface. This data is used when the WIP
Mass Load program is submitted, creating or updating existing work orders.
Production kanban cards can be used to initiate discrete jobs. In a pull-based system, inventory
items are replenished using signals, or kanban cards. Kanban cards defined in Oracle Inventory
generate replenishment requests automatically. If the source type of the kanban card is
Production, the data is loaded into the Work Order Interface to create discrete jobs through
WIP Mass Load.
Instructor Note
Refer participants to the Oracle Inventory Users Guide for for detailed information regarding
kanban setup. And the Oracle Integration Repository at http://irep.oracle.com for detailed
information regarding the Work Order Interface.

Effective mm/dd/yy
Page 41 of 52
267657629.doc
Rev 1
Work Order Interface and WIP Mass Load
The Import Jobs and Schedules concurrent program

creates a request for a WIP Mass Load. You can:
Automatically implement planning recommendations
Derive job name from a profile option setting

The Import Jobs and Schedules window is used to submit the WIP Mass Load program. When
the WIP Mass Load program is submitted, the system searches the Open Job and Schedule
Interface tableand then creates new jobs and updates existing jobs for all valid records.
The Job and Schedule Interface Report is automatically printed when the WIP Mass Load
program is submitted. This report lists the job and schedules created and updated.
Job values are defaulted from Work in Process settings including:
Job name is defaulted from the database sequence and prefix from the WIP:Discrete Job
Prefix profile option.
Job status defaults to Unreleased.
Planned orders for phantoms are not automatically displayed unless you use a WIP supply
status of Phantom when querying the data.
WIP parameter Auto Associate Serial Numbers on Job Creation From Interface is used for
serial control.

Effective mm/dd/yy
Page 42 of 52
267657629.doc
Rev 1
Pending Jobs and Schedules
Pending Jobs and Schedules
Use the Discrete Mass Interface Status Load report to

view the jobs loaded from the interface table.
You can view, update, delete, or resubmit job records
that have failed and remain in the Open Job and
Schedule Interface table.

Effective mm/dd/yy
Page 43 of 52
267657629.doc
Rev 1
Agenda
Agenda

Summary

Effective mm/dd/yy
Page 44 of 52
267657629.doc
Rev 1
Releasing and Building Jobs
You must release a discrete job to production before

performing transactions
You then build the job by issuing components

Discrete jobs are created with a status of Unreleased, when you change the status to Released
you can perform transactions against it. You can release discrete jobs in either the Discrete Jobs
Summary window or the Discrete Jobs window.
When there are a large number of jobs to release, you can mass change the records. In the
Discrete Jobs Summary window, select the jobs to change, and then access the Change Status
window from the Tools menu.
Releasing a discrete job with a routing automatically loads the job quantity into the Queue
intraoperation step of the first operation.
Building a job by issuing components is discussed in the Updating Material Requirements
lesson.

Effective mm/dd/yy
Page 45 of 52
267657629.doc
Rev 1
Updating Discrete Jobs
Updating Discrete Jobs
After creation, you can update the discrete job. Specific

fields can be changed depending on job status.
Job

Effective mm/dd/yy
Page 46 of 52
267657629.doc
Rev 1
Updating Discrete Job Information
Fields that cannot be changed:

Type
Assembly
Unit of Measure
Bill Reference
Supply Type
Sales Order Number
Sales Order Line
Sales Order Item

Effective mm/dd/yy
Page 47 of 52
267657629.doc
Rev 1
Field
Status Unreleased Released On Hold
Complete
Job
Class
Status
Firm
Start Quantity
MRP Net Quantity
Start Date/Time
Completion Date/Time

If the profile option WIP:Job Name Updatable is set to Yes, you can update the name of the
existing job.

Effective mm/dd/yy
Page 48 of 52
267657629.doc
Rev 1
Updating Discrete Job Information Routing Tab
Updating Discrete Job Information Routing Tab
Field
Complete
Reference (for
nonstandard jobs)
Alternate
Revision
Revision Date/Time
Completion Sub
Completion Locator

Effective mm/dd/yy
Page 49 of 52
267657629.doc
Rev 1
Updating Discrete Job Information Bill Tab
Updating Discrete Job Information Bill Tab
Field
Complete
Reference
Alternate
Revision
Revision Date/Time
Supply Type
Refer to Practice Creating and Releasing a Discrete Job [LAB42E6Y]

Effective mm/dd/yy
Page 50 of 52
267657629.doc
Rev 1
Agenda
Agenda

Summary

Effective mm/dd/yy
Page 51 of 52
267657629.doc
Rev 1
Summary
Summary
You should now be able to do the following:
Define discrete jobs using the Discrete Job window
View routings, operations, resources, and material
requirements on your jobs
Use nonstandard discrete jobs to manage rework,
upgrades, and maintenance activities
Understand how to implement planned orders and
import jobs and schedules into work in process
Release a job so it is ready to build for transactions
Update job information, as necessary, based on the
status of the job

Effective mm/dd/yy
Page 52 of 52
267657629.doc
Rev 1

EDU42D8Y

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

EDU42D8Y

Diunggah oleh

Hak Cipta:

Format Tersedia

Creating Discrete Jobs

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Creating Discrete Jobs

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Creating Discrete Jobs

Creating Discrete Jobs

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

After completing this lesson, you will be able to:

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Overview of Creating Discrete Jobs

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs (continued)

Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs (continued)

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs

Overview of Creating Discrete Jobs (continued)

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Overview of Creating Discrete Jobs

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Discrete Life Cycle

Discrete Life Cycle

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Discrete Job Elements

Discrete Job Elements

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Discrete Job Elements

Discrete Job Elements

Discrete Job Elements

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Describes various stages in the job lifecycle, and

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs

Job is not released to the shop floor

Job is available to begin production

Job is complete, but still can perform transactions

Job is completed, but cannot perform more transactions

Transactions cannot be performed

No further activity on the job

Copyright Oracle, 2008. All rights reserved.

Creating Discrete Jobs