Manufacturing Foundation R19A Student Guide

Schedule: Timing Topic
05 minutes Lecture
00 minutes Practice
05 minutes Total
Oracle SCM Cloud: Manufacturing Foundation 1 - 2
This slide lists the lessons in this course.

Oracle Supply Chain Management Cloud documentation is available in the Oracle Help Center:
https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/books.html
• Getting Started with Your Manufacturing and Supply Chain Materials Management
Implementation: https://docs.oracle.com/en/cloud/saas/supply-chain-
management/19a/fammi/getting-started-with-your-manufacturing-and-supply-chain-materials-
management-implementation.pdf
• Using Manufacturing: https://docs.oracle.com/en/cloud/saas/supply-chain-
management/19a/faumf/using-manufacturing.pdf
• Using Functional Setup Manager: https://docs.oracle.com/en/cloud/saas/applications-
common/19a/oafsm/using-functional-setup-manager.pdf
• Integrate Oracle Fusion Manufacturing Cloud Service with Oracle IoT Production Monitoring
Cloud Service documentation is available at https://docs.oracle.com/en/cloud/saas/iot-production-
cloud/iotpp/integrate-oracle-manufacturing-cloud-oracle-iot-production-monitoring-cloud-
service.html#GUID-394D20BA-6F65-434D-B9EE-74725A74F6F8

You can refer to the following white papers:
• Integrations with Manufacturing Cloud [Doc ID: 2218040.1] available at
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=346880738094749&id=2218040.
1&_adf.ctrl-state=1otun0u4i_349
• Using Outside Processing in Oracle Supply Chain Management Cloud [Doc ID: 2277846.1]
available at
• Oracle Fusion Business Process Models: Production [Doc ID: 2134638.1] available at
• White Papers for Oracle Fusion Supply Chain Orchestration [Doc ID: 2257314.1]: available at
• CTO – Configure to Order: A Guide to Key Application Setups available at
https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceI
d=2257314.1&attachid=2257314.1:CTO_SETUP&clickstream=yes
• Contract Manufacturing: A Guide to Key Application Setups available at
d=2257314.1&attachid=2257314.1:CON_MANF_SETUP&clickstream=yes
• Back-to-Back Supply Creation and Fulfillment: A Guide to Key Application Setups available at
d=2257314.1&attachid=2257314.1:B2B_SETUP&clickstream=yes

• Cloud Customer Connect (https://cloudcustomerconnect.oracle.com/pages/home) is Oracle's
online cloud community — specifically designed to promote peer-to-peer collaboration and sharing
of best practices, enable members to keep pace with product strategy, and provide a cloud solution
feedback channel directly to Oracle development. Within this community, members benefit by
leveraging the collective knowledge of Oracle Cloud customers and product experts.
o Manufacturing Forum
(https://cloudcustomerconnect.oracle.com/resources/3351513efb/summary) enables you
to network and collaborate on real-life challenges and solutions with fellow members.
Share best practices as you strive to deliver consistent, personalized customer
experiences, and connect every customer engagement with your brand.
o The Idea Lab (https://cloudcustomerconnect.oracle.com/pages/b2b501d83a) allows you to
contribute to our product roadmap that is derived from a variety of influences, such as
market changes, compliance and regulatory forces, industry trends, and one of our best
sources, our customers.
o The Events (https://cloudcustomerconnect.oracle.com/resources/28806a6537/summary)
tab lists upcoming and replays of Supply Chain Management events.
• The Manufacturing Release Readiness Material (https://cloud.oracle.com/saas/readiness) allows
you to learn about the latest innovations in our Supply Chain Management products. In the left of the
web page, click Supply Chain Management and then, select Manufacturing.
• Industry 4.0 with Oracle IoT Production Monitoring Cloud
(https://www.youtube.com/watch?v=eKzzoRYXBmc): Learn the technologies contributing to Industry
4.0 and how Oracle IoT Production Cloud Monitoring helps improve factory operations with this
YouTube video.

• Product experts schedule Customer Connect training. These sessions provide more information on
topics already discussed in this training or discuss topics relevant to the implementation and use of
the product. The replays of these sessions can be found here:
https://cloudcustomerconnect.oracle.com/posts?tagName=Manufacturing. You can also select one
of the available Event Series. The event series filters the events by training and product areas.
• The Oracle Supply Chain Management Integration Overview
(https://cloudcustomerconnect.oracle.com/posts/5d7d178db7) discusses core integration capabilities
for Supply Chain Management including external web services, integration with PaaS, business
events, file-based data import, ADFdi and common messaging framework.

15 minutes Lecture and Demo
00 minutes Practice
15 minutes Total
This section discusses how Oracle Manufacturing Cloud supports the end-to-end scope of
manufacturing.

This diagram depicts how Oracle Manufacturing Cloud delivers core Manufacturing capabilities in
the cloud to allow you to efficiently set up, manage, execute, and cost your production operations,
and connect through social network collaboration tools. It allows you to do the following:
• Design the manufacturing process and processing standards
• Create and manage work orders, and monitor shop floor status
• Execute work orders quickly and easily while enforcing execution compliance
• Analyze and control work order costs
Oracle Manufacturing Cloud is an integral part of the Oracle Supply Chain Cloud and supports In
House or Contract Manufacturing, Standard or Configured products, and can be executed to plan or
order.

Material, Operation transactions performed in Oracle Manufacturing Cloud are interfaced to Oracle
Asset Lifecycle Management Cloud for tracking product genealogy.
For Contract Manufacturing, Oracle Manufacturing Cloud does the following:
• References the Purchase Order details maintained in the Oracle Procurement Cloud for
display in the Contract Manufacturing Work Orders
• Interacts with Oracle Receiving Cloud to create receipt of the Contract Manufacturing Service
Item
• Raises business events on a Work Order, for SCO to get progress details of a Contract
Manufacturing Work Order
• For contract manufacturers to report material consumption and production progress, provides
public web services for applications used by external parties
For Outside Processing, Oracle Manufacturing Cloud does the following:
• Sends purchase and shipment requests to SCO to create purchase requisition and shipment
lines in Oracle Procurement Cloud and Oracle Shipping Cloud applications.
• Interacts with Oracle Procurement Cloud to display outside processing Purchase Orders from
the review supplier operation details page.
• Interacts with Oracle Shipping Cloud to display outside processing shipment details from the
review supplier operation details page.
• Interacts with Oracle Receiving Cloud to progress quantities at supplier operations when
goods are delivered to Manufacturing, and display the outside processing receipt and
delivery details from the review supplier operation details page.
Supply Chain Orchestration (SCO) interacts with the Oracle Manufacturing Cloud to create and
update Work Orders against the Supply Orders created in SCO. It communicates the details of
purchasing and shipping that are created in outside processing and notifies supply operations
exceptions to Oracle Manufacturing Cloud.
The Lots and Serials maintained in the Oracle Inventory Management Cloud are used in Oracle
Manufacturing Cloud for Work Order based, and Orderless Execution. Material transactions created
in Oracle Manufacturing Cloud are interfaced to the Oracle Inventory Management Cloud. On Hand
and Reservation details maintained in the Inventory Management application are displayed in Work
Orders. Work Order supply reservations in Oracle Inventory Management Cloud are updated after
performing operation transactions in the Oracle Manufacturing Cloud.
Oracle Manufacturing Cloud supports importing Work Definitions through ADFdi (ADF Desktop
Integrator). Additionally, Work Definitions, Work Orders, Operations, Resources, and Material
Transactions can be imported through File-Based Data Import (FBDI) and REST based web
services.

This section discusses the high level functional architecture of Oracle Manufacturing Cloud.

This diagram represents the high level functional architecture of Oracle Manufacturing Cloud and
highlights its dependencies and interactions with other Fusion Applications. It also shows the ways
and means by which external applications can interact with Oracle Manufacturing Cloud.
Oracle Manufacturing Cloud references Items and Item Structures maintained in Fusion Product
Model to create and maintain Work Definitions, Work Orders, and record Material Transactions.
Manufacturing lead times calculated in Oracle Manufacturing Cloud are updated in the Fusion
Product.
Oracle Manufacturing Cloud references Plant Parameters, UOMs, Subinventories, Locators,
Calendars, Shifts, and Exceptions maintained in Supply Chain Common Components for Work
Definition and Work Execution.
Oracle Manufacturing Cloud interacts with Planning Central and Supply Planning for un-constrained
Work Order Scheduling. Planning Central collects Manufacturing data for supply chain planning.
Resource Rates and Work Definitions maintained in the Oracle Manufacturing Cloud are referenced
by Oracle Cost Management Cloud for Cost Planning. Work Order Status updates, Operations, and
Resource transactions in the Oracle Manufacturing Cloud are transferred to Cost Management for
Cost Accounting.
Inspection characteristics and inspection plans are defined and maintained in Oracle Quality
Management Cloud. Oracle Manufacturing Cloud invokes inspection plans during work order
operation transactions to report inspection results and to automatically decide on dispositions of the
inspected quantities or serials.

Manufacturing interacts with Electronic Signatures and Electronic Records, or ERES, to
capture electronic signatures and generate electronic records while managing standard
operations, work definitions, production exceptions, and reporting work execution
transactions.
Material, Operation transactions performed in Oracle Manufacturing Cloud are
interfaced to Oracle Asset Lifecycle Management Cloud for tracking product
genealogy.
For Contract Manufacturing, Oracle Manufacturing Cloud does the following:
• References the Purchase Order details maintained in the Oracle Procurement
Cloud for display in the Contract Manufacturing Work Orders
• Interacts with Oracle Receiving Cloud to create receipt of the Contract
Manufacturing Service Item
• Raises business events on a Work Order, for SCO to get progress details of a
Contract Manufacturing Work Order
• For contract manufacturers to report material consumption and production
progress, provides public web services for applications used by external
parties
For Outside Processing, Oracle Manufacturing Cloud does the following:
• Sends purchase and shipment requests to SCO to create purchase requisition
and shipment lines in Oracle Procurement Cloud and Oracle Shipping Cloud
applications.
• Interacts with Oracle Procurement Cloud to display outside processing
Purchase Orders from the review supplier operation details page.
• Interacts with Oracle Shipping Cloud to display outside processing shipment
details from the review supplier operation details page.
• Interacts with Oracle Receiving Cloud to progress quantities at supplier
operations when goods are delivered to Manufacturing, and display the
outside processing receipt and delivery details from the review supplier
operation details page.
Supply Chain Orchestration (SCO) interacts with the Oracle Manufacturing Cloud to
create and update Work Orders against the Supply Orders created in SCO. It
communicates the details of purchasing and shipping that are created in outside
processing and notifies supply operations exceptions to Oracle Manufacturing Cloud.
The Lots and Serials maintained in the Oracle Inventory Management Cloud are used
in Oracle Manufacturing Cloud for Work Order based, and Orderless Execution.
Material transactions created in Oracle Manufacturing Cloud are interfaced to the
Oracle Inventory Management Cloud. On Hand and Reservation details maintained in
the Inventory Management application are displayed in Work Orders. Work Order
supply reservations in Oracle Inventory Management Cloud are updated after
performing operation transactions in the Oracle Manufacturing Cloud.

Oracle Manufacturing Cloud supports importing Work Definitions through ADFdi (ADF
Desktop Integrator). Additionally, Work Definitions, Work Orders, Operations,
Resources, and Material Transactions can be imported through File-Based Data
Import (FBDI) and REST based web services.

This section discusses the capabilities of Oracle Manufacturing Cloud.

Let us discuss the capabilities of Oracle Manufacturing Cloud from the following perspectives:
• Setting up Manufacturing Plant Data
• Monitoring and Managing Discrete Production
• Executing Discrete Production
• Planning, Accounting, and Reviewing Manufacturing Costs

Oracle Manufacturing Cloud empowers manufacturing engineers with intuitive visualization, and
web-based interface tools to build a foundation of manufacturing plant data, and design the Discrete
Manufacturing process for items. It allows you to quickly define the necessary manufacturing setup
data of your plant hierarchy, and process standards as follows:
• Production calendars, work areas, work centers, and resources
• Standard operations that may be reused across different production processes
You can then visually define the production process on a new object called a Work Definition, which
combines the item structure and manufacturing steps into a single view.
You can define your operations, and then drag and drop resources and structure items to the
process to complete the flow, defining shop floor controls (such as, which components must be
manually issued and which components can be automatically backflushed).
Finally, you can collaborate with colleagues using Oracle Social Network conversation, which is
connected to the work definition.

Let us discuss the capabilities of Oracle Manufacturing Cloud from the perspective of monitoring and
managing discrete production.

Oracle Manufacturing Cloud allows production supervisors to effectively manage shop floor activities
while on the move.
The production supervisor starts on a landing page page. The landing page displays infolets that
provide quick and important information such as the status of work orders, rework, open exceptions,
operations, work in process inspections, scheduled vs. actual issues with single click access to drill
from the metrics into the details, and take action to resolve issues.
Oracle Manufacturing Cloud allows production supervisors to manage plant and work center
resource working times by defining shift and resource exceptions. It provides the ability to create and
manage standard, non-standard, rework and transform work orders and enforce serialization
enabled manufacturing. It allows production supervisors to manage and resolve production
exceptions that are logged by shop floor personnel. In addition, Oracle Manufacturing Cloud
provides the ability to manage work order operations that are outsourced to suppliers.
Work orders are also social network enabled, and OTBI gives the production supervisor quick and
easy reporting capabilities.
Work orders are optimized for use on a tablet, so the supervisor can take action while on the move.
Using the Supervisor Mobile Application, production supervisors can get to access the work order
execution status and take actions on the go using a smart phone. This application is available on
both iPhone and Android mobile platforms and can be downloaded from the Apple app store or the
Google play store.

Let us discuss the capabilities of Oracle Manufacturing Cloud from the perspective of executing
discrete production.

Oracle Manufacturing Cloud provides insight into work center-level operation information for
production operators. It provides a simple, intuitive, easy-to-use dispatch list with two clicks, required
to issue materials, charge resources, or complete an operation. The user interfaces to review work-
related information, and report transactions are optimized for use on a tablet.
Oracle Manufacturing Cloud allows users to adhere to serialization enabled transaction reporting,
indicate when the production activity for a work order operation has started or stopped, and calculate
the runtime for a work order operation. It allows entering inline inspection results while performing an
operation completion transaction.

Oracle Manufacturing Cloud allows the reporting of orderless transactions. It also allows production
operators to report production exceptions such as material unavailability, machine breakdown as
they occur on the shop floor. In addition, Oracle Manufacturing Cloud provides the ability to print
Travelers, Components List, and Product Labels required for Production, and allows you to review
production transaction history.

Oracle Manufacturing Cloud offers several benefits, which include the following:
• Allows users to create and maintain data with ease, through the provision of predefined
templates and simplified setups
• Provides rich, consumer grade user experience by providing visual, intuitive tools for work
definition and tablet friendly design for work execution
• Facilitates information-driven production management and execution, with embedded
performance analysis and reporting, and allows users to take action while on the move
• Improves productivity of shop floor personnel through several visual cues, and streamlined
reporting with just two clicks
• Provides a comprehensive end-to-end supply chain solution for Discrete Manufacturing
companies with Oracle Manufacturing Cloud and Oracle Supply Chain Management Cloud

This section discusses the cross-functional business flows.

Oracle Manufacturing Cloud is an integrated part of the complete Supply Chain Management Cloud.
It supports cross-functional business processes be it either in-house, or outside processing where
one or more operations of a work order are outsourced to a supplier who provides specialized
manufacturing services, or contract Manufacturing where an Original Equipment Manufacturer
(OEM) outsources the entire manufacturing process to an external manufacturing service provider
commonly referred to as a Contract Manufacturer. It also supports building Standard or Configured
Products, or executing Plan-to-Produce scenarios, or Back-to-Back Customer Order Fulfillment of a
sales order by manufacturing the product representing a build to order scenario.

60 minutes Practice
80 minutes Total
This section discusses how you can set up a manufacturing plant.

This high level process flow diagram depicts the sequence of steps to set up a manufacturing plant.
The setup includes Plant setup, Manufacturing Common setups, and Manufacturing setups.

This section discusses how you can set up Oracle Social Network.

This screenshot depicts that each business object that is enabled for social, can be configured for
the list of attributes that are displayed on the social wall for that object.
In the Oracle Manufacturing Cloud, a Work Definition, Work Order, or Exception can be enabled
for social collaboration using the Manage Oracle Social Network Objects for Supply Chain
Management task.

This section discusses how you can set up a plant, plant parameters, and plan security.

This screenshot highlights the Time Zone list and the Organization is a manufacturing plan
option. Inventory Organizations always represent facilities for the shipping and receiving of goods.
When these facilities additionally manufacture goods, the organization must also first indicate that it
represents a manufacturing plant. After this is done, the default parameters for the manufacturing
plant can be set up and maintained independently of the inventory parameters.
The Time Zone field identifies the time zone where the manufacturing plant is physically located.
To enable manufacturing for an organization, select an existing organization or create a new one
from the Search Results region of the Manage Inventory Organizations task. Then select the
Manage Inventory Organization Parameters button to edit the organization settings, including those
to enable manufacturing.
The Organization is a manufacturing plant check box when exclusively selected, represents an in-
house manufacturing plant. If the manufacturing organization represents a contract manufacturer,
then select the Organization represents a contract manufacturer check box. When this check box is
selected, the Supplier and Supplier Site fields are required.

This screenshot depicts the Manage Plant Parameters page. The Manufacturing Calendar may be
the same or different from the calendar used by Logistics. It specifies the working time in the plant,
and is used to determine availability for scheduling work orders.
To enable automatic reporting of Component issue transactions, the Default Supply Subinventory
and Default Supply Locator must be provided. To enable defaulting of completion subinventory in
operation completion transactions, the Default Completion Subinventory and Default Completion
Locator must be provided.
The Starting Operation Sequence and Operation Sequence Increment are used within work
definition and work order, to automatically default the operation sequence when operations are
added.
The behavior of how to process components that have supply type as phantom is addressed by the
Phantom Operation Inheritance field. The values Material Only and Material and Resources
determine if only materials or both materials and resources of the phantom’s work definition must be
inherited.
The Work Order Prefix and Work Order Starting Number determines the document numbering
scheme when work orders are created.
The Allow Quantity Changes During Backflush parameter determines if quantities can be
changed during backflush of materials and resources.

The Default Label and Work Order Traveler Template parameters enable customers to use their
own BI publisher templates for these reports. The user can specify the file path and file name of their
templates in this parameter. If the parameter is left blank, the defined templates will be used.
The Default Over Completion Tolerance parameter specifies the default over completion that is
enforced through work orders.
The Default Transaction Mode parameter can be set to All or Entered to set the default transaction
mode. If the user chooses the All mode, all push components and manual resources for the
operation would be defaulted, and the user can transact against them. In the Entered mode, the
user is allowed to scan and add components sequentially, or manually enter the required resources.
The Default Transaction Quantity parameter can be set to none, both, material, or resource.
This parameter enables the transaction quantity to be defaulted as that of the required quantity
during Material and Resource transactions in a work order. The user would be able to make changes
to the defaulted quantity.
The Include component yield in material requirements parameter check box determines whether
component yield is factored into the calculation of required quantities of the components in the work
order.
The Automatically associate serial numbers during work order import parameter check box
enables serial numbers to be automatically generated when serial tracked production-enabled work
orders are imported, or created from other applications.
The Capture Level for Serialization Operations parameter enables the level at which operators
record production start or stop for serialization enabled operations.
The Material Reporting Level for Serialization Operations parameter enables the level at which
operators report materials for serialization-enabled operations.
The parameter Purchase Requisition Trigger determines how the requisitions for outside
processing are created. If it is set to Work Order Release, purchase requisitions are created for all
supplier operations on a work order when the work order is released. If the parameter is set to Prior
Operation Completion, purchase requisitions are created for a supplier operation on a work order
when quantities are completed at the prior count point operation.

Oracle Manufacturing Cloud provides three predefined job roles. Based on the roles assigned to the
user, manufacturing tasks are accessed and performed through the following two distinctly different
work areas:
• Work Definition: This work area provides insight into key setup information for a
manufacturing plant, and lists all the tasks to define and manage manufacturing setup data.
• Work Execution: This work area provides insight into plant, work area, and work center level
production information, and lists all the tasks to manage and execute production activities.

This screenshot depicts that data access is provided using the Manufacturing plant as the security
context.

This section discusses how you can set up profile options, lookups, and descriptive flexfields.

This table depicts the profile options that impact the usage of Oracle Manufacturing Cloud. The table
has the following:
• Columns: Profile Name, Profile Code, and Explanation
• Rows are as follows:
- The SCM Common: Default Service Duration Class profile option must be set at
site level. It identifies the unit of measure (UOM) class, which represents the time unit
of measures. If the Resource usage UOM is set to any UOM within this class, then
they are treated as schedulable resource. All resources with other UOMs cannot be
scheduled.
- The Hour Unit of Measure profile option must be set at site level. It represents the
equivalent of the real world hour UOM. It is used internally by the unconstrained
scheduling engine to convert the Resource usage UOMs to equivalent real world time
UOMs. Hour UOM should be within the UOM class set by the Default Service
Duration Class profile option to allow scheduling and lead time calculation.
- The Default Manufacturing Plant Organization profile option can be set at user
level to indicate the default plant the user will access in Oracle Manufacturing Cloud.

The table contains the following:
• Columns: Lookup Name, Lookup Code, and Explanation
• Rows are as follows (in bold font):
This table depicts lookups that can be set up by users:
• Resource Class enables the user to group resources into resource groups for planning
activities.
• Work Center Resource Group enables grouping of resources for work center planning
activities
• Work Order Operation Transaction Reason Codes enables Reason Codes for Scrap and
Reject Transactions.
The following Lookups can be extended by users by adding new values:
• Work Order Sub Type enables for a capture of a specific nature of the work order for a given
work order type. This specific nature of work being performed can be Standard Production,
Prototyping, Repair and so on.
• Work Definition Operation Resource Activity enables for the Activity name of the work
definition operation resource.

This table depicts the descriptive flexfields that can be optionally set up to capture additional
information for setup and work definition entities. The table contains the following:
• Columns: Flexfield Name, Flexfield Code, and Module
• Rows: Work Area, Production Resource, Work Center, Standards Operation Resources,
Standard Operations, Work Definition Operations, Work Definition Operation Resources, and
Work Definition Operation Materials

This table depicts descriptive flexfields that can be optionally set up to capture additional information
for work execution entities. The table contains the following:
• Columns: Flexfield Name, Flexfield Code, and Module
• Rows: Work Order Header, Work Order Operation, Work Order Operation Resource, Work
Order Operation Item, Work Order Operation Transactions, and Work Order Resource
Transactions

This section discusses the work definition work area.

This screenshot depicts the Work Overview page. It is the default overview page for the
manufacturing engineer.
On a typical work day, the engineer has a quick glance at the various manufacturing setup data, and
visits the most recent work definitions that need attention.
The Overview page takes the user to the various Tasks in a dynamic tab mode, and allows the
following:
• Provides a quick view of key setup metrics for a manufacturing plant, and quick access to the
daily tasks performed by the manufacturing engineer
• Helps the manufacturing engineer view the most recent work definitions being worked on

A Work Area identifies a physical, geographical, or logical grouping of work centers.
Production Operators can report material, resource, and operation transactions performed at work
centers that belong to a specific work area.
The Manage Work Area page enables users to search, create, edit, and inactivate work areas.
REST Services for Work Areas:
A REST service is also available for Work Areas. Using the workAreas resource, you can View
(GET), Create (POST), Update (PATCH), and Delete (DELETE) Work Areas. For more information,
refer to the following link: https://docs.oracle.com/en/cloud/saas/supply-chain-
management/19a/fasrp/index.html.

Resources are charged to the work order based on a rate. Users can click the Define Rates button
to view the Resource costs defined for the selected resource.
REST Services for Production Resources:
A REST service is also available for Production Resources. Using the productionResources
resource, you can View (GET), Create (POST), Update (PATCH), and Delete (DELETE) Production
Resources. For more information, refer to the following link:
https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/fasrp/index.html.

• A work center is a grouping of resources belonging to a department, a production line, or a
process cell.
• Production operators can report material, resource, and operation transactions performed at
work centers.
• The Manage Work Center page allows you to search, create, edit, and inactivate work
centers.
REST Services for Work Centers:
A REST service is also available for Work Centers. Using the workCenters resource, you can
View (GET), Create (POST), Update (PATCH), and Delete (DELETE) Work Centers. For more
information, refer to the following link: https://docs.oracle.com/en/cloud/saas/supply-chain-

This screenshot depicts the Add Work Center Resource dialog.
If a resource is available for scheduling 24 hours on work days, then select the Available 24 Hours
check box. If the resource is available to be scheduled only within the shift hours of work days as
defined in the calendar, then leave this check box blank. The Check Capable To Promise check box
determines if you need Global order promising engine to consider this resource’s capacity while
promising.
The Utilization and Efficiency Percentages are by default set to 100%. When these percentages are
set to less than 100%, they extend the scheduled duration of the resource during work order
scheduling. For example, if 2 hours of work are required to be done using resource LATHE1 from 9
AM onwards on a specific work order, and if its efficiency is 50%, and utilization is 50%, then the
scheduler will determine the end time for this resource as 5 PM. [ 2/ (0.5*0.5) = 8 hours]

Resource Instances represent the actual machines and people belonging to a resource used in
manufacturing. A labor type resource instance can be optionally but uniquely associated with either an
employee, contingent worker or partner contact. An equipment type resource instance can be
optionally but uniquely associated to an asset number defined in Maintenance Management cloud. The
asset number should have been defined with a location organization corresponding to the
manufacturing plant and a location type of Work center to be eligible to be associated as an equipment
resource instance in manufacturing.
After you define labor or equipment types resource instances, you can assign them to work order
operations, and then charge their usage in resource transactions. In addition, you can report
exceptions on a resource instance. You can analyze the usage of Resource instances using Oracle
Transactional Business Intelligence or OTBI.
Resource instances provide you with a better visibility of utilization of manpower and machinery used in
the production shop floor. Associating the specific people and machines to the manufacturing work
orders promotes better accountability of the work being carried out and provides historic trace back of
the work performed.

This section discusses how you can define standard operations.

This screenshot depicts the Edit Standard Operation: Drilling page. Standard Operations are
commonly used operations by users, to define a template to use in work definitions and work orders.
Standard operation Code uniquely identifies a standard operation, and is plant specific. Standard
operations can be defined for in-house and supplier operations. A predefined value of Supplier for
Operation type is used for standard supplier operations in outside processing. Users can optionally
add alternate resources for the resources used in the standard operation.
A standard operation can be deleted only if it is not used in a work definition, or a work order. In the
case of work definitions where an operation is marked as referenced, any change to the standard
operation definition will be reflected automatically without forcing a new work definition version.
Changes can be implemented on a standard operation and its associated resources which in turn,
are reflected in all referenced work definitions. Once unreferenced, the operation is no longer
considered a standard operation, and cannot be changed back to referenced again. In the case of
Work Order, a standard operation is always a copy.
Only Active Standard Operations (with a null or future Inactive Date) are enabled to be added to
work definitions and work orders. Attachments such as work instructions for the standard operation
and its resources are also copied to the work definition and work order. If a standard operation
needs to be used during the creation of automatic work definitions, select the attribute Default for
automatic work definition.
REST Services for Standard Operations:
A REST service is also available for Standard Operations. Using the standardOperations resource,
you can View (GET), Create (POST), Update (PATCH), and Delete (DELETE) Standard Operations.
For more information, refer to the following link: https://docs.oracle.com/en/cloud/saas/supply-chain-

Capture E-Signatures and E-Records for Standard Operations:
Note that the process to generate E-Records and capture E-Signatures is not initiated when a standard
operation is created and updated through ADF desktop integration (ADFdi), File-Based Data Import
(FBDI), or REST services.
When you create or edit the standard operation, you can also be an approver. You can review the
electronic records, enter comments, indicate your approval or rejection, and sign the E-Record in the E-
Signature page. The standard operation is not saved until all approvals are completed. Depending
upon the outcome of the approval, the standard operation creation or update is either saved or rolled
back.

This section discusses how you can manage production calendar and add exceptions.

This screenshot depicts the Manage Production Calendar page. The Production Calendar allows
the visual display, and management of the working time in the manufacturing plant. A calendar
consists of time shifts, which repeat in a pattern of work days. These shifts are shown in the
production calendar in the plant time zone.
A production calendar may be used by one plant, multiple manufacturing plants, or by any number of
other Fusion business objects. Changes to the definition of working times that occur only at a single
plant are defined through the production calendar.
In Oracle Manufacturing Cloud, working time exists at a plant level. Changes to the schedule for
each plant are easily made through shift exceptions. For planning and scheduling, working time
exists at a resource level. Changes to the availability for each resource are easily made through
resource exceptions.
Changes to a plant’s working time happen for a variety of reasons. Holidays occur when the entire
plant is shut down. Scheduled shut downs occur for periods of time, and overtime is added to a
weekend. The shift exception enables these plant-centric time changes to be defined. There are
many scenarios where changes to resource availability are required. Training is scheduled, but only
for a subset of the staff. Equipment maintenance implies that one or more work centers are offline,
while the remainder of the plant continues to operate normally. The resource exception enables time
periods to be defined, where one or more resources have adjusted override values for their normal
availability.
To add a shift, modify a shift, or remove a shift to indicate a holiday, the shift must be created,
edited, or deleted within the production calendar. Select a shift and right-click or choose the Actions
menu to create one.

This screenshot depicts the Manage Production Calendar: Edit Shift Exception page. When a shift is
required to be modified for all activities within a manufacturing plant, a Shift Exception is created.
The Shift Exception represents a change to the working time, that all resources and work centers in
the plant must adhere to.
The Shift Exception provides the definition of the shift, such as the start time and duration. The shift
can be modified to indicate how to change the working time. The four types of shift exceptions are:
• Change shift
• Remove shift
• Split shift
• Add shift
A shift can only be added by selecting non-working time in the calendar. Shift Exceptions default to a
single day, but can also recur over multiple days. The exception will replace the shift in the
production calendar as necessary.
Shift Exceptions just need to reflect changes to plant working time. A name for the exception is
required, and the exception has to change either the start time, or the duration of the shift being
updated.
By default, the change to the shift time impacts all resources in the plant. You can also change the
number of resources available during the exception.

This screenshot depicts the Manage Work Center Resource Calendar page. The Resource Calendar
allows the visual display and management of the working times, for a single resource in the
manufacturing plant. This calendar is displayed in the manufacturing plant time zone. Just like the
production calendar, it consists of time shifts, which repeat in a pattern of workdays. These shifts are
visible in the resource calendar.
When resources are assigned to a work center, the number of available units are specified for each
shift in the calendar. These values are shown in the resource calendar as well. To address changes
to the staffing levels, it may be necessary to alter the number of available units for one or more
resources on occasion. For example, if a work center has to be taken offline, or if a subset of
resources needs to work overtime, the working time for the entire plant does not need to change.
When it is necessary to change the number of resources for a given time period, a Resource
Exception is created and edited within the resource calendar. Select a shift showing the resource
availability, and right-click or choose the Actions menu to create one.

This screenshot depicts the Manage Work Center Resource Calendar: Edit Work center Resource
Availability page.
A Work Center Resource Exception is created when the availability of one resource or a set of
resources needs to be modified within a manufacturing plant.
The resource exception provides a way for you to identify periods of time where the availability will
deviate from the norm. By default, a resource exception will inherit the definition of the shift if it is
based on one. For example, if illness or vacations reduce the count for a resource, it will be for the
entire shift.
The primary change being captured in the exception is the override value for availability. As a
convenience, the exception will always reflect the resource that was being viewed in the calendar.
But the filters of resources may be cleared or altered to find any other resources within the plant.
This allows all the resources in a work center to be quickly found and updated.
The exception will contain the changes for any number of resources, although the Resource
Calendar only shows the exception for the selected resource.
Resource Exceptions default to a single day, but can also recur over multiple days.
The exception will replace the availability inherited from the shift in the resource calendar as
necessary.

• 3-1: In this practice, you create work areas.
• 3-2: In this practice, you create resources and add resource instances.
• 3-3: In this practice, you create a work center and associate a resource.
• 3-4: In this practice, you create standard operations.

0 minutes Practice
40 minutes Total
This section discusses Outside Processing setup.

This screenshot depicts the Outside Processing Service list which indicates if the item is an outside
processing service. In addition to the finished goods and components, an “Outside Processing
Service” item must be defined in Oracle Product Information management) PIM to represent the
value- added service (for example, plating) in outside processing. This will be used to account for the
supplier contribution in the build process. The outside processing item will be referenced in the
purchasing documents, in the shipping documents, and will be used to receive goods against an
outside processing purchase order.
It is important to note that the Outside Processing service item will also serve as a proxy to represent
the outgoing partially finished assembly (or PFA) shipped to the Manufacturing Partner (which we’ll
call the MP-- an example of this is machined PFAs that are sent to the MP for plating. It will also
serve as a proxy to represent the incoming PFA received from the MP (for example, plated PFAs
that are received from MP). Receiving the outside processing item would implicitly mean receipt of
the incoming PFA.

This screenshot depicts that to derive the PO Charge Account required for creating Outside
Processing POs, you must define rules for the predefined Outside Processing mapping set.
You can create a mapping set based on the following attributes:
• Inventory Organization
• Work Order Sub Type
• Purchasing Category Code
• Item Number
Navigation: Setup and Maintenance > Define Transaction Account Rules > Manage Mapping Sets
(Scope: Cost Management) > Outside Processing
Mapping rules is enhanced to add a business rule that an Outside Processing Cost Component is
mapped to an Outside Processing Cost Element alone.

This screenshot depicts creating suppliers and supplier sites, which is an essential part of the
procurement process. In the context of outside processing, a supplier refers to an external party that
provides specialized manufacturing services to manufacture a product. Suppliers should be created
using the Create Supplier task in Suppliers work area and be defined for buying the value added
services.
A supplier is modeled as a global entity. It is not created within a business unit or any other
organizational context. A procurement business unit establishes a relationship with a supplier
through the creation of a site which maintains internal controls for how to procure to pay transactions
are executed with the supplier.
Navigation: Procurement > Suppliers > Create Supplier

This screenshot depicts that to enable automatic creation and approval of POs in outside
processing, you must define an outside processing blanket agreement for the outside processing
service item in Oracle Purchasing. In the absence of a blanket agreement, the POs need to be
manually created from the requisition.

This section discusses Inspection setup for Manufacturing execution.

This screenshot highlights the Type field in the Details section of a WIP Inspection Plan. An
Inspection Plan states the characteristics and their quality specification requirements for an item,
item catalog, or resource as well as the criteria for when and where inspection should be enforced.
Creating an inspection plan for an item catalog can help streamline data maintenance, unless there
are exceptions, in which case you would define a separate item-specific inspection plan.
The inspection plan Type helps determine how to apply an inspection plan to an inspection point as
defined in the inspection criteria. Depending on the ‘Type’, inspection criteria, and setup, an
inspection plan can be implemented for inline or ad hoc inspection. Inline inspection means that
quality results are required and embedded as part of a business transaction, like work order
operation completion. Ad hoc inspection means that it is not tied to a business transaction and is
distinguished by the inspection plan being marked as optional.
A production supervisor or production operator can do the following inspections: Inline Work In
Process inspection, Ad hoc Work In Process inspection, Ad hoc Inventory inspection, and Ad hoc
Resource inspection.
For inline Work in process inspection, you need to setup Inspection characteristics and then
Inspection plans
• Inspection plan should be for the Assembly
• Inspection plan should be of type WIP Inspection
• It should be in Approved state

The capabilities of the Work In Process inspections:
• Inspection is triggered when the production operator initiates a work order operation
transaction.
• The inspection plan for inspection result collection is displayed if the work order operation is
associated with a mandatory (not optional) inspection plan.
• Reporting of inspection results can be performed using quick complete or complete with
details action.
• The production operator must enter the inspection results for the inspection quantity or
serials.
• The inspection plan logic will decide to accept or reject the inspection quantity or serials
based on the inspection result values and specifications setup.
• For inspection result values that are out of spec, a non-conformance is logged automatically
for further action.
• The accepted quantity or serials must be completed at the operation.
• The rejected quantity can be reworked or scrapped.
• After rework of the rejected quantity, inspection can be initiated with the same inspection plan
or with a different inspection plan.
• Production operator can also initiate standalone inspections with or without an inspection
plan and associate the inspection results collected with a work order operation or resource or
inventory.

This screenshot highlights the Inspection Plan Specifications section. You can select Specifications
to mention the inspection characteristics to be measured or collected during inspection. In this
release, an inspection characteristic can only be listed once in the specifications.
You can select both item based and non-item based inspection characteristics. Characteristics can
be added individually, or as a group.
For Item-based characteristics, if the specification is being defined for a specific item, the values for
minimum, maximum and target values, as well as the unit of measure, are pulled in from the PIM
attributes to which these values are mapped. If no value is was entered for the PIM attribute for the
specified item, then the user will be able to specify the value to use during inspection.
Inspection results are automatically evaluated against the applicable inspection plan specifications to
determine the overall inspection disposition.

This screenshot highlights the Inspection Criteria section. WIP Inspection Criteria allows you to
specify under what conditions the inspection plan is applicable.
For different types of inspection plans, different criteria are to be applied.
No criteria is entered for Resource type inspection Plans.
The last infotile of the inspection plan defines the conditions under which an inspection plan applies
to a particular inspection point in Work in Process.
For example, Work in Process criteria can be set up to enforce inline inspection at a particular
operation or operation dispatch status. Note that the same inspection plan could apply to a first time
inspection as well as a re-inspection use case by adding both the Ready and Reject dispatch status
criteria.
And Inventory criteria can be applied to ad hoc inspection at a particular subinventory designated for
quality-related purposes such as Material Review Board or quarantine.
The Resource inspection plan type only supports ad hoc inspection for an organization and
resource. No additional inspection criteria can be entered for this type.
The inspection criteria works together with the inspection plan header attributes in order to determine
the best applicable inspection plan for an inspection point or event. For an inline Work In Process
inspection, a mandatory inspection plan is automatically selected based on a matching logic using
the inspection point or event details (for example, organization, item, and work order and operation).
For an ad hoc Work In Process inspection, the matching logic may return a mandatory or optional
inspection plan.

This section discusses the integration of IoT Production Monitoring Cloud Service with
Manufacturing Cloud.

IoT Production Monitoring is designed for factory managers and manufacturing leaders who want to
monitor the execution of their manufacturing processes. It allows them to get answers to questions
such as “Is my factory on track to produce per the production plan?", “If the production is behind plan,
where is the bottleneck?", “Which machines are most idle in my assembly lines?", etc.
IoT Production Monitoring has out-of-box integration with Manufacturing Cloud to automatically track
work orders defined in Manufacturing Cloud for their real-time progress. IoT Production Monitoring
allows you to gain real time operational visibility. In addition, you can:
• Monitor real time performance and derive KPIs of factory, product, and machines
• Deep dive into production lines and machines to gain operational insights
• Compare KPIs across factories, products, and machines to identify best and worst performers
• Analyze KPIs over time to understand if the sub-par performance is enduring
• Identify root cause of sub-par performance using deep dive on specific KPIs and sensor data
• Identify anomalies in machine performance and its effect on production
• Monitor machine performance via real-time KPIs
• Predict the future state of equipment
The screenshot depicts the Configuration: Settings page in the IoT Production Monitoring Cloud
Service.

After you enable Oracle Manufacturing Cloud integration in Oracle IoT Production Monitoring Cloud
Service, data is periodically pulled in from Oracle Manufacturing Cloud.
By default, the sync job runs once per hour, at the beginning of each hour. The manufacturing entities,
namely manufacturing organizations, items, work orders, and resources are imported from
Manufacturing Cloud. This translates into the following manufacturing-related entities in Oracle IoT
Production Monitoring Cloud Service:
• Factories
• Products, Product Routing, and Production Data information
• Work Orders
• Machine Types and Machines
• Operator Types
You can edit the imported entities, as required in Oracle IoT Production Monitoring Cloud Service. For
example, you can edit the factories to add location information.
In addition, you can assign machines to the imported work orders, and create the production line.
For more information, you can refer to the following link: https://docs.oracle.com/en/cloud/saas/iot-
production-cloud/iotpp/integrate-oracle-manufacturing-cloud-oracle-iot-production-monitoring-cloud-

• 4-1: In this demonstration, you query outside processing mapping set
• 4-2: In this demonstration, you query a blanket agreement for an Outside Processing item
• 4-3: In this demonstration, you query a WIP Inspection Plan

30 minutes Practice
75 minutes Total
This section discusses work definitions and how they are used in manufacturing.

A work definition defines the manufacturing process for a product, which consists of operations,
materials, and resources. The work definition effectively combines an item structure and routing into
a single view. It corresponds to a single buildable level of the item structure. The primary work
definition is used as the default for creating standard work orders of the item. You can also define
alternate work definitions to account for variations in the manufacturing process in terms of
operations, components, or resources. The advanced graphical editing tool with drag and drop
interactions and data visualization views allows you to visually design the work definition. You can
use Microsoft Excel spreadsheet for mass creation and update.
Oracle Manufacturing Cloud supports work definitions for standard items and Assemble to Order
(ATO) models. The focus of this course is on standard items. ATO model work definition is covered
in depth in Configure to Order course.

This flow diagram depicts the features available in Manage Work Definitions. Most of the key work
definition actions are accessible from the Manage Work Definitions page. They are:
• Manage Work Definition Names
• Create a Work Definition
• Delete a Work Definition
• Deactivate a Work Definition
• Search Work Definitions
• Manage Versions
• Edit Priorities (Production and Costing)
• Print Work Definition Report
Process Item Structure Changes is available as a task in the panel drawer.
The Manage Work Definitions page serves as a starting point for the manufacturing engineer. You
can use the Personalize Saved Searches feature to save multiple search criteria, set the most used
search criteria as the default, and make it run automatically. The next time you come to the Manage
Work Definitions page, your key work definitions will be displayed, with links to navigate to the work
definition details.

A work definition requires a work definition name. This diagram depicts the major steps in creating a
new work definition which are as follows:
1. Enter the work definition header details
2. Create the operations
3. Assign items to the operations
4. Assign resources to the operations
You can create a work definition in the user interface (UI). In addition, you can create a work
definition by using ADFdi spreadsheet, file-based data import (FBDI), or REST APIs.

This section discusses work definition names and how they correspond to different manufacturing
processes.

This screenshot highlights the Used in Planning check box on the Manage Work Definition Names
page. It’s explained below.
Work definition names correspond to multiple manufacturing processes that a given product may
have. Work definition names can be of type Standard, Rework, or Transform. You can immediately
use the predefined work definition name Main of type Standard for your primary work definition.
Similarly work definition name Rework of type Rework and Transform of type Transform can be used
to create a rework work definition or transform work definition. If a product has more than one
manufacturing process, for example, an alternate process, you must first define a work definition
name before you can define an additional work definition for that product.
The work definition name is used in aligning lower level phantom work definitions during the work
definition explosion process while creating the work order for the product. Select the Used in
Planning check box for work definitions of type Standard, if you want Planning to plan the materials
and resources. Work definition names of type Rework or Transform cannot have the Used in
Planning check box enabled.
REST Service for Work Definition Names

A REST service is also available for Work Definition Names. Using the workDefinitionNames
resource, you can View (GET) work definition names. For more information, refer to the following
link: https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/fasrp/api-manufacturing-
work-definition-names.html

This section discusses how you can create, update, manage, and delete work definitions as well as
review predefined manufacturing reports for work definitions.

This screenshot depicts the Create Work Definition page.
Create a Work Definition
Work definition name and structure name are not shared. They are set up separately. If a structure
name is not specified, then the item structure visualization will not display an item structure. You can
only assign existing items (ad hoc items) to the operations.
You can create a serial tracked work definition if the item’s serial generation is set up as Predefined
Serial number. Completion Locator is required only if the completion subinventory is locator
controlled. Costing Batch Output Size defaults from the Standard Lot Size item attribute and can
be overridden. Attachments are carried to the work order.
Creating the first work definition for a work definition name of type Standard (with Used in
Planning selected) and item combination requires the production priority to be set to 1. This is
considered the primary work definition, which is used by Planning to generate the planned orders
and create the standard work orders of the item. Creating another work definition for the same item
requires a different work definition name with production priority higher than 1. These are considered
alternate work definitions. Costing priority is used in cost planning scenario to determine which work
definition is to be picked up when rolling up costs. You will need to manually enter the costing
priority. If you have a prescribed way of reworking a product, you can define a rework work definition
using work definition name of type Rework. If you perform upgrade or downgrade to a product to
produce a finished good that is of higher or lower specifications, you can define a transform work
definition using work definition name of type Transform. Transform work definition requires the
Transform from Item, which is the item being transformed to the work definition item.

This screenshot depicts the Edit Operations page.
A work definition must have at least one operation. Operations are executed in a linear path based
on the operation sequence. You can use standard operations as work definition operations, or you
can manually enter the operations. When you reference a standard operation, you will not be able to
edit its attributes, until you unreference it.
Operation Type can either be In-house or Supplier. An in-house operation means that the operation
is performed in-house. A supplier operation means that the operation is performed by a supplier that
provides value added manufacturing services in the Outside Processing business model.
A count point operation is always performed and requires manual reporting. The last operation
must always be a count point. An automatically transact operation is always performed and
automatically completed, the pull components are backflushed, and resources are automatically
charged when the next count point operation is completed. Count point and automatically transact
operations are mutually exclusive.
If the work definition is for a serial-tracked item, then setting Serialization attribute to Yes indicates
that the operation is a serialization start operation. The Serialization attribute for the subsequent
operations must also be set to Yes.
Lead Time Percent represents the offset of a given operation as a percentage of the manufacturing
lead time considering all operations of the work definition. These lead time percent values are used
as an input in the calculation of cumulative lead times.

This screenshot depicts the Operations page.
You can define work definitions with one or more supplier operations and they can be consecutive. A
supplier operation can also be the last operation sequence. Additional details of a supplier operation
are as follows:
• Outside Processing Item: An item that represents the value added service being performed
on the assembly in outside processing. Ensure that Outside Processing Service is set to Yes
for the outside processing service item. The primary UOM of the OSP item must be the same
as that of the end product (work definition item).
• Supplier: The recommended supplier used in creating the requisition. It becomes required if
the prior operation is also a supplier operation.
• Supplier Site: The recommended supplier site. It becomes required if the prior operation is
also a supplier operation.
• Generate Shipment: Indicate whether shipment lines will be created at the supplier
operation when quantities are completed at the prior count point operation.
• Lead Times UOM: The unit of measure for the lead time of a supplier operation.
• Fixed Lead Time: The fixed lead time for the operation and is independent of the order
quantity.
• Variable Lead Time: The variable lead time for the operation and is dependent on the
quantity.

After creating operations, the next step in defining a work definition is to assign components to
operations. You walk through the item structure, and determine to which operation a component
should be assigned and the usage. You are allowed to split components quantity to multiple
operations. After you assign a component to an operation, a visual indicator is displayed on the item
structure to indicate that the component is now assigned. The quantity of an operation item must be
positive in a standard work definition, but it can be negative in a rework or transform work definition.
If an item structure component has substitutes defined, then those are automatically pulled to the
work definition. If the primary component quantity is split across multiple operations, then the
substitutes quantity is proportionately distributed among the operations.
As part of the item assignments process, you also need to determine the supply type, which
controls how the material is going to be supplied. The value of supply type is operation pull,
assembly pull, push, phantom, bulk, or supplier. You can optionally specify the supply
subinventory to control where the material is supplied from. The hierarchy for defaulting the supply
type is in the following order: item structure > item master > push. The hierarchy for defaulting the
supply subinventory and supply locator is in the following order: work center > item structure > item
master > plant parameter.
The work definition operation item attributes are defaulted from the item structure component
attributes. Basis determines whether the quantity of the component used is a fixed amount or varies
linearly with the quantity produced. Basis cannot be overridden. Yield is the amount of good or
acceptable material available after the completion of a process. A yield factor of 0.90 means that
only 90% of the usage quantity of the component is acceptable to be included into the finished
assembly. Quantity, Inverse Quantity, UOM, and Item Yield can be overridden provided the user has
the function security. Supply Type, Supply Subinventory, and Supply Locator can be overridden.

Notes: A phantom can either be a grouping of components, or a stocked subassembly. If a phantom
is a stocked subassembly, it has its own work definition. The work definition of the phantom is taken
into account by the work definition explosion process, while creating the work order for the finished
good.
You can also assign existing items to operations, and these are considered as ad hoc items. This
functionality requires function security. A use case for this is adding materials such as cleaning
supplies, tools, or lubricating oil that are used in the production process, but are not considered
components in making the product, and hence not included in the item structure.

The last step in the work definition creation is to assign resources to operations. If you use a
standard operation, then you don’t need to perform this activity because the resource assignments
are referenced from the standard operation definition. You will not be able to update the resource
assignments in the work definition, because they are referenced.
If you use a manually entered operation, you will have a pool of resources that come from the work
center assigned to the operation available for assignment. While assigning a resource to the
operation, you must determine the number of resource units to be assigned, basis (fixed or variable),
usage or inverse usage, whether the resource is scheduled and how the resource should be charged
(automatic or manual). If you assign more than one resource to an operation and they share the
same resource sequence number, then you must mark one as the primary resource.
If the resource is scheduled, then Planning will schedule the operation, and come up with the
recommended operation start and end dates, which in turn roll up to the work order start and end
dates.
You can define alternate resources for a primary resource, and they are ranked by priority. Basis,
Scheduled, and Charge Type are inherited from the primary resource and cannot be updated.
Usage, Inverse Usage and Units Assigned are defaulted from the primary resource definition
and can be updated.

This screenshot depicts some important elements on the Edit Work Definition Details page. You can
establish work definitions as favorites with a click on the Star icon that appears next to the work
definition name. One click identifies the work definition as a favorite (solid yellow star), and one click
removes it from favorites (empty star).
The important elements of the Edit Work Definition Details graphical user interface are:
• The Item Revision drop-down list displays all the applicable item revisions that are in the
effective date range of the work definition version being viewed or edited.
• The Date drop-down list displays all the distinct component effective start dates that
correspond to the item revision in bullet #1. For a change implemented through a Change
Order in Oracle Product Information Management (PIM), the component’s effective start date
also displays the change order concatenated with the corresponding change order line
number.
Selecting an item revision in the Item Revision drop-down list, and a date in the Date drop-down
options does the following:
• Updates the item structure view (right side), and displays the effective components as of that
date
• Updates the work definition (left side), and displays the effective work definition as of that
date

This screenshot highlights the Existing work definition radio button on the Create Work Definition
page. In addition, it depicts that Product and Structure Name can be different.
Reasons for copying a work definition:
• Define the same manufacturing process to make a different product.
• Define the same manufacturing process for an alternate item structure that makes the same
product (product is the same, structure name is different).
• Define an alternate manufacturing process to make the same product (product and structure
name are same, work definition name is different).
Rules for creating a new work definition from an existing work definition:
• Operations and operation resources are copied
• If the product and structure name are the same, then the operation items are copied.
• If the product is changed in the new work definition, then the operation items are not copied.
• If the product is the same, but the structure name is changed in the new work definition, then
the operation items are not copied.
• Based on the work definition type selected for the existing work definition, only the work
definition names of the same type can be selected for the new work definition.

This screenshot depicts how a search for work definition returns a matching entity and highlights it.
Contains search is conducted across operations, items, and resources. The search result cards for
the matching entities are displayed in the search results panel, and they are also highlighted in the
work definition region. The like objects can then be dragged and dropped to the Collected Items
icon for updating. You can also right-click the search result card to perform an action like Edit.

This screenshot depicts that when you create an ATO model work definition, you have visibility to the
multilevel ATO model item structure. You can expand option classes and standard item phantoms
and assign a component from any level to an operation. You can create an applicability rule based
on an option class, option item, and transactional item attribute and assign it to an option-dependent
operation. An export mechanism is available to export operation item assignments to Excel. This
allows you to quickly determine if there is pending work in terms of operation item assignments.
ATO model work definition is covered in depth in the Configure to Order course.

This feature is applicable for a light assembly manufacturing that does not require shop floor control.
These screenshot depict that the Create Automatic Work Definition action is enabled only for the
primary item structure of a standard item. You only need to perform this action once. Future changes
to the item structure will be synchronized automatically to the work definition.
You can search automatic work definitions. A new work definition attribute called Automatic indicates
that the work definition is system generated. To create an automatic work definition, the application
uses the predefined work definition name ORA_MAIN and the standard operation selected as the
default for automatic work definition. The work definition name is not hyperlinked, and therefore you
cannot update an automatic work definition.
You can create an automatic work definition for a set of items using Create Automatic Work
Definitions scheduled process. The parameters of the scheduled process are Organization, User
Item Type, Item Category, From Item, and To Item.
You can use a scheduled process to create a large number of automatic work definitions for a given
user item type, or item category, or both. You can also schedule the process to run periodically so
that as new items are created, automatic work definitions are subsequently created.
If you are going to use an automatic work definition, ensure that you don’t create manual work
definitions prior to creating an automatic work definition. The reason is when the system creates an
automatic work definition, it is created with production priority 1. You can however create manual
work definitions after creating an automatic work definition. If the automatic work definition is no
longer the primary way of making the product, you can update the production priority and costing
priority accordingly.

You can delete a work definition that has been created by mistake from Manage Work Definitions page
for either a manual or an automatic work definition. It deletes all versions of the work definition name
for an item. To maintain data integrity, you cannot delete a work definition if it is referenced by work
orders or used in published cost scenarios.

Deactivating a work definition is a mechanism to render a work definition obsolete. For example, when
a work definition represents a manufacturing process that is no longer valid, you can deactivate it.
Deactivating a work definition deactivates all the versions of a work definition, and the work definition
becomes inactive immediately. The work definition status is updated from Active to Inactive, and the
Inactive On date is populated with the system date when you deactivate the work definition. You cannot
update or reactivate an inactive work definition.
You can search and view an inactive work definition, and create a new work definition by copying an
inactive work definition. However, inactive work definitions are not available for use by consuming
applications. You cannot create a work order using an inactive work definition in Manufacturing;
however, any existing work orders using an inactive work definition can proceed. Planning does not
create planned orders using inactive work definitions. Costing does not use inactive work definitions in
cost rollup if the cost scenario effective date is greater than the inactive on date. In the event that a
work definition that has been used in an existing unpublished cost scenario is deactivated, the status of
the cost scenario will be updated to indicate to the user that cost rollup has to be re-run.
Deactivating a work definition is supported in work definition file-based data import (FBDI) and REST
service. In the FBDI template, you can deactivate a large volume of work definitions by performing
UPDATE action and specifying the work definition status as INACTIVE. To support data migration, you
can also upload inactive work definitions by performing CREATE action and specifying the work
definition status as INACTIVE. The Inactive On date is the date when the scheduled process is
completed.
You can also use the REST service workDefinitionRequests, to deactivate work definitions through
integration with external systems.

Note that if E-Signature for the Work Definition Management transaction is enabled, you can deactivate
only approved work definitions. Deactivating a work definition initiates the approval process and
updates the work definition status to Pending Inactivation. After the last required approver approves,
the work definition status becomes Inactive. Inactive On date is the date on which the last required
approver approves.

This section discusses how you can import work definitions through File-Based Data Import or FBDI.

Import Work Definitions through File Based Data Import, or FBDI, allows you to import high volumes of
discrete work definitions to support an initial data load to the system. In addition, you can mass update
discrete work definitions including the addition and removal of operations, operation items for standard
items, operation items for ATO models, operation resources and operation alternate resources.
The FBDI functionality simplifies migration to the cloud by supporting initial data load of discrete work
definitions from legacy systems. It also facilitates the mass update of existing work definitions when
processes change. It utilizes the Purge Records from Interface feature to allow you to delete records in
the interface tables that were not processed due to errors. After correcting the errors in the FBDI
template, you can reuse the same batch code if the corresponding records have been purged.
REST Services for Work Definitions:

A REST service is also available for Work Definitions.
• Using the workDefinitions resource, you can View (GET) Work Definitions.
• Using the workDefinitionRequests resource, you can Create (POST) Work Definitions (This is a
POST-only REST service based on interface tables so that it can handle high volume REST calls for
CREATE and UPDATE).

REST Service for Work Definition Requests:
A REST service is also available for Work Definition Requests. Using the workDefinitionRequests
resource, you can Create (POST) work definitions to an interface table. These records are then
automatically processed using a scheduled process to create or update work definitions. For more
information, refer to the following link: https://docs.oracle.com/en/cloud/saas/supply-chain-
management/19a/fasrp/api-manufacturing-work-definition-requests.html

This section discusses work definition report.

This diagram depicts that a work definition report can be printed from the Manage Work Definitions
page through an action. The same action is also available while editing the work definition version.
An alternate way to print the work definition report for multiple work definitions is through a
scheduled process. This can be accessed as a task from the work definition work area.

A work definition report provides the option for offline review, to ensure that the work definition has
been set up correctly.
The report also allows exchanging information offline, for example, with the contract manufacturer.
In a contract manufacturing organization, the work definition report by default, prints the key
milestone operations. The report is attached to the Blanket Purchase Agreement (BPA) and is
communicated to the contract manufacturer.
The submission of the scheduled process can be performed through the Print Work Definition Report
task in the Work Definition Work Area task panel.

This screenshot highlights the following:
• Work Definition Operation details
• Work Definition Operation Items
• Supplier Operation details
If the work definition includes a supplier operation for an outside processing item, the additional
attributes such as supplier details along with the outside processing item would be dynamically
displayed in the operations table.
Substitute Items are defined and maintained for an Item Structure component in Fusion PIM. If
defined, all the substitutes for an operation item would be displayed in a nested table.
If the work definition item is an ATO model, the additional attributes such as Option dependent would
be dynamically displayed in the operations table. The component hierarchy for an operation item
would also be displayed in a nested table.
Alternate Resources can also be defined as part of the Standard Operation setup. If defined either at
the Standard Operation or directly in the work definition operation resource, these alternate
resources would be displayed in a nested table.

This section discusses calculation and roll up of cumulative manufacturing and cumulative total lead
times.

The manufacturing lead time calculation considers the primary work definition of the item. For in-
house operations, the duration of scheduled resources are considered; for supplier operations, the
lead times specified at the operation level are considered. The manufacturing lead time is expressed
in Days, and it represents the number of working days it takes to manufacture the lot size of that
item taking into consideration the plant’s shift duration.
With the lead time program, you can calculate and roll up lead time of multiple items. These are
displayed in a hierarchical format in an output text file. This provides a snapshot view of the lead
times of all the selected items in a single place. The ESS program for calculating the lead times can
be run to calculate the Manufacturing Lead times, the Cumulative Lead times, or both Manufacturing
and Cumulative Lead times.

This section discusses how you can process item structure changes to work definitions.

Any user granted the Manage Work Definitions function privilege will receive the worklist notification,
provided they have also been granted data access to the manufacturing plant, in which the item
structure change was performed. Changes to the item attributes will not generate a notification.
The notification consolidates all the component changes for a given item, which have occurred at the
time Process Item Structure Changes to Work Definitions program was executed.

Worklist notification is generated when all the following conditions are met:
1. Item changes include at least one change to the item structure.
2. Oracle Product Information Management (PIM) publishes the business events generated for
item structure changes.
3. The Process Item Structure Changes to Work Definitions delivered by Oracle
Manufacturing Cloud picks up the business events in bullet #2 and the program completes
successfully.
4. There is at least one work definition in Manufacturing for the item structure component
change that was completed in PIM.
In the case of a standard item work definition, component changes to Quantity, Inverse Quantity,
UOM (if overridden on the work definition), Yield (if overridden on the work definition), and Supply
Type require manual update on the work definition. In the case of an ATO model work definition, the
Process Item Structure Changes to Work Definitions scheduled process automates all the
component attribute changes, with the exception of the Supply Type attribute. New component
addition to an item structure always requires manual update on the work definition in both ATO
model and standard item work definitions.

This screenshot depicts the Notification Detail page that provides a summary, and detail level view
of the Item Structure changes. The Impacted work definitions link to navigate to the Manage
Work Definitions page, with a pre-queried subset of work definitions impacted by these changes,
helps you assess the manufacturing impact.
The worklist notification is typically sent when the manufacturing engineer needs to manually make
changes to the work definitions.
As the notification opens in a separate browser, a typical flow for you to alternately view two
separate browser sessions (one for making the work definition changes, and the other for the
notification details).
You decide which of these item structure changes qualify to update existing work definition versions
and which ones necessitate creating new work definition versions depending on the company's
change management policies.

This section discusses the need for versioning a work definition and how you can achieve it.

Work definition always has one effective version at any given time, starting with the base version,
which may be future dated.
The defined operations align to either the start date or end date or both (effectivity), of the work
definition version.
For any work definition that is currently effective:
• A new version is warranted upon addition of a new operation or deletion of an existing
operation. These are considered major changes.
• User discretion dictates the version creation for all other changes to the work definition.
For any work definition that is future effective, the user decides on which change(s) would
necessitate a work definition version. Work definition versions do not have overlapping effective
dates. Enhanced visibility to the change order details should help the engineer with the decision on
the work definition versioning.

Additionally, note the following:
• Item revisions and work definition versions are maintained separately. Multiple item revisions
can come into play within a work definition version. Or conversely, multiple work definition
versions using the same item revision can exist in Manufacturing.
• Managing work definition versions (create, edit, or delete) is handled in a separate UI and
flow from creating a work definition.
While being very flexible, most businesses do exercise restraint when performing major changes to a
current production process, for example, introducing a new operation. It is a benefit to the business
to align the production process with the product changes. It is a benefit to the business to align the
production process with the product changes, especially the important ones, such as implemented
change orders or new revisions to the item structure. As defined by the item definition, a
corresponding work definition version is ideal. These product changes may require adding or
deleting operations.

This section discusses how you can capture electronic records and signatures for work definitions.

Capture E-Signatures and E-Records for Work Definition Management:
Oracle Electronic Records and Electronic Signatures is a framework you can configure for securely
capturing, storing, retrieving, and printing electronic records and signatures. Using this feature, you can
review electronic records for work definitions and capture electronic signatures.
A new work definition version and any changes to an existing version go through the electronic
signature process. You can initiate the deferred electronic signature capture process when you submit
the work definition for approval.
Once you enable electronic signatures for a manufacturing work definition, the created work definition
has a version in Draft status. You can continue to save changes to a Draft work definition version. A
work definition is available for use in production after the first version for that work definition is
in Approved status. Work definition version that is not in Approved status is not available for creating
a work order or be used in Planning or Costing. Electronic records are generated and the electronic
signatures are captured during this approval process. The work definition version is updated
as Approved for an approved outcome and Draft for a rejected outcome.
Work definition version status works in conjunction with the workflow for the deferred approval and can
have one of the following statuses:
• Draft
• Pending Approval
• Approved

Note that you cannot update an existing approved version.
The behavior for the work definition operations, operation materials and resources for an approved
work definition version is the same as the work definition that is pending approval. The only differences
for an approved work definition being:
• Further changes can be made by creating a new work definition version.
• Work definition priorities can be changed without requiring a new electronic signature.
• Item structure component changes approved and completed in the Oracle Fusion Product Model are
processed by the Process Item Structure Changes to Work Definitions scheduled process.
Any changes including any deleted data such as deleting operations are only available for use in
production after these are approved.
Approvers can access notifications in the Oracle Cloud application. They can review the electronic
records before adding their electronic signature. Approvers can also enter comments, indicate their
approval or rejection, and sign the electronic record by using a password. Approvers also have the
visibility to the current status of the approval process in the approval History region in the approval
workflow notification.
Note: You cannot initiate the Electronic Records and Electronic Signatures process when you create a
work definition and update it through the ADF desktop integration (ADFdi) or the supported web
services.

In this practice, you create and update an Outside Processing work definition for a non-serialized
item.

20 minutes Practice
120 minutes Total
This section discusses the Work Execution work area.

This diagram describes the high-level process flow, and the tasks that are relevant for in-house,
outside processing Oracle Manufacturing Cloud execution, both work order–based execution and
orderless execution.
In work order-based execution, work orders are created and released to production. After work order
execution is completed, the work orders can be closed. You will be reviewing the work order-related
aspects in this lesson.
The remaining tasks are covered in the Execute Production lesson.

The Overview page in the Work Execution work area serves as a landing page, which is a
collection of infolets providing a high level summary for the shop floor personnel to monitor
production activities. It provides insight into plant, work area, work center level production
information using the View By filters.
By default, the Manufacturing Organization is set to plant as defined in the profile Default
Manufacturing Plant Organization. Users can change the organization to another plant based
which plant they have access to.

This screenshot depicts the Work Execution Work Area and highlights some important elements that
are explained below.
The Work Orders is a text layout based infolet that displays the count of work orders which are Past
Due, On Hold and Unreleased, having at least one operation with the selected work area or work
center. The Past Due metric displays the count of work orders in Released status whose completion
date is less than the current date. The On Hold metric displays the count of work orders in On Hold
status. The Unreleased metric displays the count of work orders in Unreleased status.
The Rework infolet is a text layout based infolet that displays the count of rework and transform work
orders, having at least one operation with the selected work area or work center. The Rework Orders
metric displays the count of work orders in Unreleased, Released and On Hold status having work
order type of Rework. The Transform Orders metric displays the count of work orders in Unreleased,
Released and On Hold status having work order type of Transform.
The WIP Inspections infolet is a text-layout-based infolet that displays the percentage of rejected
WIP samples or serials compared to the WIP samples or serials inspected in the last 7 days in the
plant.

The Operation Scheduled Versus Actual infolet is a ring chart based infolet that displays the
aggregated sum of production quantities in different dispatch statuses. These are displayed for all in-
house count point operations belonging to the selected work area or work center whose scheduled
completion date falls within the current shift. The total operation quantity scheduled in the current
shift is displayed in the center of the ring chart. The ring segments corresponding to the Ready,
Complete, Reject and Scrap represent operation quantities in their corresponding dispatch status.
The Not Ready segment represents the operation quantity that is scheduled in the current shift but
not in any of these dispatch statuses.
The Open Exceptions infolet is a text layout based infolet that displays the count of open exceptions
that were logged today and the count of total open exceptions logged in the plant. The production
supervisor can view more detail of the total count of open exceptions by clicking on the expanded
view icon. The expanded view of Open Exceptions infolet is a ring chart based infolet that displays
the count of total open exceptions by exception type.
The Operations infolet is a text layout based infolet that displays the count of operations which are
Past Due, Ready and Reject, which belongs to the selected work area or work center. The Past Due
metric displays the count of operations whose scheduled completion date is less than the current
date. The Ready metric displays the count of operations whose dispatch status is Ready. The Reject
metric displays the count of operations whose dispatch status is reject. User can click on any of the
metric, and drill down to the respective page to view more details or perform further actions. The
panel drawer provides quick access to the tasks in the work execution work area without having to
navigate back to the overview page. The tasks in the panel drawer are grouped and ordered based
on the functional usage of the tasks.
Using the panel drawer in the work execution work area, the user can also create new reports or view
existing reports using the manufacturing subject areas in Oracle Transactional Business Intelligence
(OTBI).

This section discusses Manufacturing Work Orders in general.

A Manufacturing Work Order is a document, group of documents, or schedule conveying authority
for the manufacture of specified parts or products in specified quantities.
The Manage Work Orders feature also provides necessary web services and events framework to
integrate with other internal supply chain management modules for creation and change
management of work orders. The work order integrates with other SCM modules, such as Oracle
Fusion Product Model, Inventory, Costing, Planning Central, and Purchasing.
The item and item structure details are other attributes referenced from Product Model.
Subinventory, Locators, Serials, Lots, On hand quantities are referenced from Inventory.
Manufacturing cost management is performed for work orders in Costing.
Oracle Orchestration Cloud Service creates supply in Oracle Manufacturing Cloud against sales
orders for Back-to-Back work orders, and configured item work orders.
Planning Central creates work order as supplies during the supply planning run.
Contracting manufacturing and outside processing are enabled through Purchasing.
The Import Work Orders feature uses the File Based Data Import (FBDI) to import work orders by
using spreadsheets. Manage Work Order pages are designed for tablet friendly user interfaces, and
are optimized for 1024 x 768 resolution.
Work orders are enabled for Oracle Social Networking (OSN), and the supervisor can use OSN to
communicate with stakeholders for better fulfillment of work order supply.

This section discusses how you can manage work orders.

This flow diagram shows the features that are available in the graphical user interface:
• Search Work Orders, includes simple and advanced search. It has a link to edit work order,
actions for mass update of work order status and priorities, and print reports. You can view
the comprehensive details of the work orders based on priority, past due indicators for start
and completion dates, progress indicators, and so on.
• Create Standard Work Order allows the production supervisor to create a work order
quickly, with minimal data or with additional details. In the plan to produce business flow,
work orders are created from Planning as part of the Supply Planning process. As part of
back-to-back flow, work order is created as a supply for the sales order.
• Create Transform Work Order allows the production supervisor to create a transform work
order that is used to upgrade or downgrade an assembly that is already completed and
available in inventory.
• Create Rework Work Order allows the production supervisor to create a rework work order
that is used to perform a repair or rework the assembly that is already completed and
available in inventory.
• Create Nonstandard Work Order creates a work order with or without work definition.

The Manage Work Orders feature provides robust capabilities for the production supervisor to
efficiently create and manage work orders.
The work order is designed for easy navigation, and captures minimal mandatory information to
quickly create and update work orders.
Work orders created on assemblies that require Serialized manufacturing can be associated with
predefined assembly serial numbers.
Users can view reservation details of the work order against the sales orders.
Work Order History information and Production Transactions History are maintained against each
work order, and can be viewed at any time.

The Manage Work Orders page provides the ability to search for work orders by using basic search
or advanced search.
The default basic search criteria allows users to retrieve all work orders that start today and the next
7 days, which are in status Unreleased, Released, or On Hold.
Users can also personalize the search criteria using the saved search feature and set them as the
default search if required.
The Manage Work Orders page provides the supervisor with the ability to create, edit, and print work
orders.
Separate actions are available to create standard, nonstandard, rework, and transform work orders.
You can select multiple work orders and perform mass actions like status changes and update
priority.
You can print reports such as Work Order Traveler, Print Component Lists, and Print Labels using
the Print PDF action for the selected work order.

This screenshot highlights the following:
• The search results region shows the work order priority. This is used to prioritize and sort
work orders for execution.
• The Work Order Priority is entered during the work order creation process (edit work order
action).
• The start and completion dates of the work order display a Past Due indicator as well, if the
work order start or completion dates are past due.
• Additionally, the progress indicator indicates if the work order execution has started. These
icons represent In Progress, Not Started, and Completed states of the work order.
• Progress icons indicate the following:
- Not Started icon: Unreleased status
- Completed icon: Completed status
- In Progress icon: Shows work orders in the Released or On Hold status, when
execution has started.
- No icon: Closed or Canceled
• System displays an icon to signify that open production exceptions exist against the work
order (Production exceptions will be discussed in detail in Lesson “Execute Production”).
Contextual actions on the Item field provide instant details of the product being
manufactured.

This screenshot depicts the high level steps to create a standard work order.
Standard Work Order is a type of work order; scenarios where a standard work order needs to be
created manually (instead of planning), it is mandatorily created with a work definition. Ensure that
the Build in WIP attribute for an item is set to Yes to allow work order creation. Consider the
following:
• The standard work order can be created by specifying the item and quantity.
• The primary Unit of Measure (UOM) of the item and the work order start date values are by
default the system date.
• The system selects the primary work definition of the item, and explosion occurs. The user
can also select a non-primary work definition.
• The system selects the primary work definition of the item, which is the work definition with a
production Priority of 1. When saved, the work definition is exploded, and the operation,
components, and resources requirements are populated from work definition to the work
order.
• The standard work order is created in the unreleased status, and the user can update it as
required.
• The standard work order can also be created through file based data import.

This screenshot depicts the separate dialog to create a standard work order. Standard work orders
are created using a work definition and are used as a means to initiate regular production.
When the work order is created using a work definition, the operations to be performed along with
the material and resource requirements are exploded from the work definition, based on the work
definition date.
During the work definition explosion, if there is any phantom item, the work definition of the phantom
item is further exploded to get the material and resource requirements. Based on the plant
parameter, Phantom Operation Inheritance, only material, or material and resources is inherited
for the phantom item.
When a work definition is provided, the user can either specify the start or completion dates of the
work order, and the system will forward or backward schedule accordingly, to determine the
completion or start dates of work order, respectively.
Work order numbers are automatically created when not specified by the user. The system
autogenerates a unique number using the numbering scheme defined in Manage Plant
Parameters. The user can also manually specify a unique work order if required.
When the user clicks the Show More link, the Standard Work Order page with additional details
are displayed.

The screenshot depicts the dialog to create a nonstandard work order that can be created with or
without a work definition. They are typically used to initiate a pilot, prototype work, and so on.
The Create Nonstandard Work Order feature provides the ability to initiate production with or without
work definition. When a work definition is provided the behavior would be like a standard work order.
If a work definition is not provided, the user manually adds the operations to be performed, along
with the material and resource requirements.
Work order numbers are automatically created when not specified by the user. The system auto
generates a unique number using the numbering scheme defined in Manage Plant Parameters. The
user can also manually specify a unique work order if required.

This screenshot depicts the dialog to create a rework work order. When creating a Rework work
order, all the valid Rework work definitions defined for the item are displayed and the user can select
one among them.
Also, for the Rework work order, work definition is optional. User can create a Rework work order
without a work definition.
The current subinventory is specified along with the current locator, if needed.
The current subinventory is the subinventory from where the rework item would be automatically
issued to the first operation of the work order when it is released.

This screenshot depicts the dialog to create a transform work order. For a Transform work order,
the work definition is optional. However, users must specify the Transform from Item.
Transform from Item is the item from which the work order item is being transformed to.
The valid work definitions of type Transform that are defined for the work order item and the
Transform from Item combination are displayed, and the user can select one among them.
The Transform work order can be created in a Released, Unreleased or On-hold status if a work
definition is provided, or created in an Unreleased or On-hold status if a work definition is not
provided.
The remaining behavior is same as that of a standard or a nonstandard work order.

This screenshot highlights the following on the Edit Work Order page :
• Social: Oracle Social Network link for Work Orders
• Additional Information: Descriptive flexfield framework to capture additional information for
the operation
The Edit Work Order General Information tab displays details such as work order status, work order
dates, product quantity details, work definition details, and other details.
The work order can be updated to Released, Unreleased, On Hold, Closed, or Canceled status
during its lifecycle of work order execution.
The work order quantity, start and completion dates, work definition names, and other details can be
updated based on the status of the work order. For example, the work definition can be updated only
when the work order is in Unreleased status. The quantity can be updated in any status except
Closed or Canceled status.
The details of the work order priority and description can be updated. The item structure details can
be viewed.
In case of rework work order, when the work order is updated to Released, the rework item would be
automatically issued to the first operation.

The user can also view details such as work order type, back-to-back and contract manufacturing
indicators, and update Firm flag. The work order attachments are managed in the Details region of
the Edit Work Order page.
The completion information like, over completion tolerance type and value, completion subinventory,
and locator are updated here.
The Oracle Social Network (OSN) for work orders is enabled on the Edit Work Orders page.
Note: OSN feature is not described in the Manufacturing Foundation course.
Additional information can be captured at work order level using descriptive flexfields framework.

The Operations tab displays a list view of all operations, operation items, and operation resources
requirements.
The following details are available for work order operations:
• Summary of operations
• Operation sequence number, code, and name
• Start date, completion date, and Work Center
• Execution details of the operation consist of the indicators for Operation completion status,
Attachment, Count Point or Automatically Transact, and Serialization.
The status along with the unit of measure is displayed for the operation quantity for each of the
execution statuses such as, Ready, Completed, Rejected, and Scrapped.

Additionally, there are links for each of the actions such as, add, edit, and delete operations. The
Midpoint Rescheduling icon is enabled for operation that has at least one scheduled resource.
The following details are available for the work order operation items:
• Summary of components for each operation, and total number of items for each operation
• Execution details of components such as required and issued quantity, and indicator to show
issue status
• Edit Operation Items action
The following details are available for the work order operation resources:
• Summary of the resources, and total number of resources for each operation
• Execution details of resources such as required and issued quantity, and indicator to show
issue status
• Edit Operation Resources action

This screenshot depicts the Operations tab that displays a list view of all operations, operation items,
and operation resource requirements along with the transacted quantities from work execution. In
addition, you can add or edit operations, operation items, and operation resources, and also perform
midpoint rescheduling by anchoring a specific operation.
If there is a long list of components for any operation, then the first three components are displayed.
For the rest of the components that display the edit operation items page, a hyperlink is provided. A
similar link is provided for resources as well.

This screenshot highlights the Standard operation to which all item structure components are
assigned in the Operations tab on the Edit Work Order page.
The automatic work definition can be used to create a standard work order for an item. There is only
one operation, and that is the standard operation that is selected as the default. All of the item
structure components are assigned to the default standard operation. The work definition as of date
determines which components are effective on the item structure on that date, and those are the
components that are included on the standard work order.

This screenshot highlights the following actions that you can perform in the Edit Operations page:
• Operation sequence number is by default, based on plant parameters.
• Capture additional information of the operation using descriptive flexfields.
• If the operation type is Supplier, then Supplier operation details (Outside processing item,
Supplier, Site, Generate Shipment indicator, lead time values) are updated.
• Add and manage attachments at operation level.
In addition, you can:
• Add new operations, update or delete the existing operations.
• Add a standard operation or a nonstandard operation.
• Enter operation name and work center details for a nonstandard operation.
• Serialization indicator is based on the work definition selected for the work order, and cannot
be updated at operation level.
Note: Attachments uploaded by the operator in the dispatch list or detail complete of operation
transaction will be available as operation level attachments in the work order.

This screenshot depicts the following:
• Component is specified for an item sequence number.
• Attachments can be added and managed at component level.
• Additional information of the components using descriptive flexfields can be captured.
• Quantity per product can be negative for Rework and Transform work orders.
In addition, you can perform the on the Edit Operation Items page:
• Add, update, and delete items (or components), requirements for the operation.
• Details such as Basis, Quantity per product, Required date, Supply type, and Item yield are
populated by default.
• Required quantity, Inverse values are calculated.
• The required date is by default the operation start date, and can be updated to a date
encompassing the operation start and completion dates.
• Supply subinventory and locator details are specified.
• Issued quantity, open quantity, and organization on-hand balance quantity details are
displayed from inventory based on material transaction.

This screenshot highlights the following actions you can perform on the Edit Operation Resources
page:
• Principal resource is indicated, if more than one resource is specified for same resource
sequence number.
• Optionally, labor or equipment resource instances can be assigned to the resource.
• Attachments can be added and managed at resource level.
• Additional information of the resource using descriptive flexfields can be captured.
In addition, you can:
• Add, update, and delete resource requirements to the operation.
• Resource name and Usage rate are specified. Other details like Basis, UOM, Scheduled, and
Charge type are populated by default.
• Required usage and Inverse values are calculated.
• Resource activity is optionally specified.
• Actual resource usage is displayed based on resource transaction.

The screenshot at the top right depicts the scheduling methods available and the screenshot in
bottom-right shows the midpoint rescheduling options available.
• Scheduling: Work Order scheduling is invoked in the background during work order creation
from user interface, file based data import, or from Oracle Orchestration Cloud Service. Work
orders are forward scheduled if start date is provided, and backward scheduled if completion
date is provided.
• Rescheduling: Work orders are rescheduled when certain attributes of the work order are
updated. If start date or completion date is updated, then work order is forward or backward
scheduled. If work order quantity or work definition name or work definition date is updated,
then the user is presented with a choice for selection of the required rescheduling method. In
addition, the user can initiate a midpoint rescheduling by fixing an operation’s start or
completion date as the anchor point.
• Forward and Backward scheduling: During Forward scheduling, the specified work order
start date is considered as the anchor point to calculate the resource dates, operation dates,
and the work order completion dates. Similarly, for Backward scheduling, the completion
date of the work order is considered as the anchor point to calculate all other dates.
• Midpoint rescheduling: The operation start date or completion date is considered as the
anchor point. All operations and resources before this selected operation is backward
scheduled. Similarly, all operations and resources after this selected operation is forward
scheduled.

During work order scheduling, system performs an unconstrained scheduling considering infinite
resource capacity. However, resource availability is taken into consideration by looking at the Plant
calendar and Work Center resource calendar definitions. Any shift exceptions or work center
resource exceptions are also considered during scheduling.

This diagram depicts that in the work order creation process, if a work definition with Serial Tracked
Production indicator enabled is referenced in a work order, then serial numbers can be assigned to
the work order.
During work order execution, the operation completion, material and resource transactions can be
performed based on the work order serial numbers.

The screenshots depict the following:
• Serial tracked production indicator enabled for the work definition
• Generate and associate serial numbers action
If a work definition that is serial tracked is referred in a work order, then pre-assigned serial numbers
can be associated to that work order.
The actions that a user can perform are generate and associate serials, manually associate serials
that are already defined, and delete the serials.
The following are the serial statuses that are displayed as and when the work order is executed:
• Associated: Serial is assigned in the work order.
• In Process: When the first transaction is performed for the serial at the operation.
• Rejected: Serial is rejected at any operation.
• Scrapped: Serial is scrapped at any operation.
• Completed: Serial is completed at the last operation into Inventory.
The details of the serial numbers displayed are:
• Operation sequence and name: The operation where the serial was last transacted
• Work Center: The work center name of the operation
• In case of rework work order, if the work order item is lot controlled and serial controlled, the
lot and serial details are shown in separate tabs.

This section discusses work order reservations, exceptions, history, and picking.

This screenshot depicts the Reservations tab that allows yare viewed in work order reservations.
You can view the reservation details of work order as a source of supply, and sales order as
demand.
The work order supply details displayed are Work order quantity and the Unit of measure.
The demand details displayed are: Document type (such as Sales Order), Customer number and
name, Document number and line number, Due date, Reserved quantity, and the Unit of measure.
A work order can be reserved against one or more sales orders. Reservations are generally created
when a back-to-back sales order or a configured items sales order is reserved for the work order.
Manual reservations can also be done for a work order in Inventory.
If the sales order header or line has attachments, they can be viewed by clicking on the attachments
icon. You can define user-defined attachment categories for sales orders and enable the attachment
category security to control visibility of those attachments to manufacturing users having production
supervisor or production operator roles.

This screenshot depicts the Edit Work Order page and highlights the following in it:
• The exception tab in work order detail displays the exceptions that were reported for this
work order.
• Production supervisor can close the exception reported for the work order.

The History tab displays the work order history information such as quantities completed, work order
dates for various status changes, and status transition history. In addition, it provides links to view to
the production transaction history and inspection history for the work order.
The work order quantities displayed are:
• Remaining quantity: Quantity of work order yet to be completed in the last operation
• Completed quantity: Quantity of work order completed in the last operation
• Scrapped quantity: Sum of scrapped quantities across operations

This screenshot depicts the following in the History tab:
• Work Order quantities
• Work order dates and cancellation reason
• Work order status change history
The work order dates displayed are:
• Released date: Date when the work order is released
• Completion date: Date when the work order is completed
• Closed date: Date when the work order is closed
• Canceled date and reason: Date when the work order is canceled, and the user specifies
reason for cancellation
The status change history displays the following details:
• Status change date: Date when the work order status changes
• From and To status: Work order status that is transitioned
• Reason for status change: User specified reason, if the work order is canceled. The user
updates the status.

You can pick materials for work orders by using the ESS job, from the Manage Work Orders page, or
from the Material Availability Assignments page. The screenshot highlights the Pick Materials for Work
Orders task under Execute Production.

Let’s cover these parameters in detail:
• Organization is a required field, and defaults to the current organization/plant the user is logged into.
If this page is launched from scheduled process user interface, it isbe blank. The dropdown lists all
the organizations that the user has access to.
• Work Method is a required field. The values are All, Discrete Manufacturing, Maintenance. This
value is populated based on the organization that is selected.
• Work Order Type is also a required field. Depending upon the Work Method the value is shown. The
values shown are: All, Standard, Nonstandard, Rework, Transform, Preventive, Corrective (if the
Work Method is All); All, Standard, Nonstandard, Rework, Transform (if Work Method is Discrete
Manufacturing); All, Preventive, Corrective (if Work Method is Maintenance).
• Hours Ahead is a required field, and the default value is 8. The number of hours ahead that the
system looks at to consider materials requirements. This value represents the cut off time for the
work orders that have material required at operations on or before the sysdate plus hours provided.
Any materials required beyond that cut off time are ignored. This is integer enforced value and the
maximum value can be 500. If the sysdate is 14-Jan-2018 06:00:00 Hrs and Hours Ahead is 8; the
all the components with required date less than or equal to 14-Jan-2018 14:00:00 Hrs are
considered.
• Pick Slip Grouping Rule values are defaulted from Plant Parameters. They are used to group the
pick slips.

• Print Pick Slips is the option to print pick slips, the value is defaulted from Plant Parameters.
• And finally, pick a work order only if all eligible components are available, you can optionally enable
this indicator.
Other eligibility check for components to be picked are, supply type to be push, supply type as
operation pull or assembly pull is considered based on the plant parameter and component pending
quantity to be picked (if partial picking is done already). Then, you submit the ESS job.

This section discusses manually procuring materials for work orders.

Navigation: Overview> Mange Work orders> Purchased Item Details
With this feature, you can easily create and associate purchase requisitions to work orders to procure
regular and ad-hoc items for an operation without having the need to stock the material beforehand. In
addition, you can track details of the items or services requisitioned, ordered and received at a work
order operation to manage the availability of materials and services at the right time and location.
For example, if there is a need for a particular item for a work order, a production supervisor can
quickly login to the self service procurement application, browse through a catalogue and easily select
and request for the desired item to be procured for the work order. Also, with visibility into the
procurement and delivery status of the item, the production supervisor has access to all the information
that is required to track and manage the availability of the item in a more efficient manner. The
screenshot depicts the Edit Work Order page and highlights the Review Purchased Item Details button
as well as the Purchased Items column.
• You can create a purchase requisition in procurement and associate it with a work order operation in
a work order in “Released” status. The purchase requisition can be for a stocked, non-stocked, or
description based item. The purchase requisition is created with destination type as "Work Order,"
and goods are directly delivered to the work order after receipt. When the purchase requisition
progresses in the procurement cycle to purchase order, receipts etc., the association with the work
order operation is maintained.
• You can view the list of items for a work order operation or for all the work order operations from the
work order. The Purchased Item Details page provides a summary view of all the items and the
quantities requisitioned, ordered, and received for each of them. This helps you to understand the
status of procurement of the required items.

• From the summary view, the supervisor can identify any issues in the procurement process like
quantities that are requisitioned but not ordered, ordered but not received, etc. In case of any issues,
the production supervisor can get a detailed view of the procurement life cycle like the requisition
number, order number, quantity, status, and also the details of receipts against these orders to plan
and execute appropriate corrective actions. Since the items procured against work order operations
are delivered directly to work orders, the supervisor can also initiate corrective actions like receipt
corrections, return to supplier or receiving etc.
• The purchased items for a work order operation are displayed in production reports like work order
traveler and component lists and also in transaction history pages.
management/19a/faumf/managing-production.html#FAUMF3266099.

This section discusses the file based data import (FBDI) work order process.

This diagram depicts the file based data import (FBDI) work order process that works as follows:
1. The work order data is populated in the xlsm template and the csv file is generated.
2. The csv file is uploaded in the Universal Content Manager (UCM) cloud server.
3. The Load Interface File scheduled process is run.
4. System populates the Work Execution (WIE) interface tables.
5. The Import Work Order process is invoked.
6. The scheduled process output is reviewed for errors if any, or the work order data gets
imported.
7. The user can update the work order further through import process.
REST Services for Work Orders:

A REST service is also available for Work Orders. Using the workOrders resource, you can View
(GET), Create (POST), Update (PATCH), and Delete (DELETE) Work Orders. Note that DELETE is
only enabled for child resources and not applicable for header resources.
REST Services for Production Transactions:

A REST service is also available for Production Transactions. Using the materialTransactions,
resourceTransactions, and operationTransactions resources, you can Create (POST) Material
Transactions, Resource Transactions, and Operation Transactions, respectively.

Oracle SCM Cloud: Manufacturing Foundation 6 -

This section discusses audit trail for work orders.

The changes to the work orders are tracked automatically along with the name of the person who
updated the record and the date and time of update. The audit records capture the attribute that was
updated and also the old and new values for each update. The description of the audit record captures
the unique reference for each object. For example, the work order number for a work order record and
Work order number and operation name for the work order operation record. This helps you to search
the change history for a specific work order you are interested in. Additional context values like the
manufacturing plant, operation sequence are also captured and stored to uniquely identify the record
that was updated.

This section discusses the Work Order Components List report.

This screenshot depicts a Components List Report and highlights the following on it:
• Details of the work order
• Details of the components of the work order
Manage work orders allows you to print the components list for the selected work order. The report is
generated as a PDF, and can be viewed or printed.
The components list report contains the work order components, operation, quantity, required date,
and subinventory and locator details.
The production users can print the work order component lists report from the Manage Work Orders
page, and also through a scheduled process for multiple work orders.

This section discusses the import of Manufacturing work orders into IoT Production Monitoring Cloud
Service.

You can import work orders from Oracle Fusion Manufacturing Cloud Service into Oracle Internet of
Things (IoT) Production Monitoring Cloud Service.
In Oracle Fusion Manufacturing Cloud Service, a work order refers to a document that conveys the
authority for the production of a specific product. It contains information about what, how, how many,
and when to manufacture a product. The product item, work definition details, operations, resources,
components, quantities, and dates are specified in the work order.
After you enable Oracle Fusion Manufacturing Cloud Service integration in Oracle IoT Production
Monitoring Cloud Service, the work orders are periodically synchronized between the two services. By
default, the synchronization job runs at the beginning of each hour.
To track work order performance, you add resources (for example, machines, product lines, products
and operators) to the imported work orders in Oracle IoT Production Monitoring Cloud Service. By
adding geographic information, you view the status of your factories in a the Map view, and work order
information in the Factory view.
The screenshot depicts the Configuration: Work Orders page.
The work orders from Oracle Fusion Manufacturing Cloud Service automatically appear in Oracle IoT
Production Monitoring Cloud Service.
After enabling Oracle Fusion Manufacturing Cloud Service integration, you may have to wait an hour
for the work orders to appear, because the default synchronization duration between Oracle IoT
Production Monitoring Cloud Service and Oracle Fusion Manufacturing Cloud Service is one hour.

You can search and filter the list of work orders downloaded from Oracle Fusion Manufacturing Cloud.
You can download work orders as csv files, as individual work orders, or as a group of work orders.
You can also upload edited work order files back to Oracle IoT Production Monitoring Cloud Service.
You can manually download work order data to your local disk, edit the work orders, and upload work
orders back to Oracle IoT Production Monitoring Cloud Service. Click Download All to download all
the work orders in the CSV format. Click the Download icon against the work order row to download a
specific work order.
You can edit the work orders to assign machines and operators to the work orders in IoT Production
Monitoring Cloud Service.
The work order data downloaded from Oracle Fusion Manufacturing Cloud Service includes machine
type, and operator type, information (Resource Id and Resource Name). You need to ensure that your
machines are of the required machine types created in Oracle IoT Production Monitoring Cloud
Service. You can then edit the work orders to assign the machines in Oracle IoT Production Monitoring
Cloud Service. If your work order data contains operator type information, then you can also assign
operators in Oracle IoT Production Monitoring Cloud Service.
For more information, refer to the following link: https://docs.oracle.com/en/cloud/saas/iot-production-
cloud/iotpp/integrate-oracle-manufacturing-cloud-oracle-iot-production-monitoring-cloud-

• 6-1: In this demonstration, you create and update a standard work order. In addition, you pick
materials and release the work order.
• 6-2: In this demonstration, you create and update rework work order without a work definition.

In this practice, you create and update standard work order with a supplier operation.

00 minutes Practice
20 minutes Total
This section discusses the Material Availability Workbench.

In order to ensure an efficient and productive shift, you need to ensure all the materials are available
for a work order prior to its release to the shop floor. As you may be aware, the Planning Central
module allows you to know whether work orders are ready-to-build based on the material availability on
a weekly time horizon. In real time, the status of material availability changes in the last minute due to
changing conditions such as damage to the warehouse inventory, delayed supplier delivery, defective
materials. It may be necessary to reprioritize the work.
Oracle Manufacturing Cloud provides you a workbench which gives you a visibility to material
availability status for the prioritized work orders, which are expected to start or complete in the next 24
or 48 hours. This material availability workbench allows you to configure rules to recommend prioritized
list of work orders based on specific attributes such as critical items, customer, scheduled ship date.
The diagram on the slide depicts that after the list of work orders are identified in the order of priority,
the materials available in inventory to transact are assigned to higher priority work orders. After the
“available to transact quantity” is assigned to the materials of work orders in the order of higher to lower
priority, and arrive at whether materials are available, or whether there is a shortage for the work order.
You can manually reassign the materials to the work order with material shortages by unassigning
materials from other work orders that have higher assignment priority. Similarly, you can unassign
materials from the work orders to reassign them to lower-priority work orders that have material
shortage. After you are satisfied with the results, you can release work orders to shop floor that are
ready for execution, and unrelease or place a hold on work orders that you do not want the shop floor
to work on at the moment.

You can configure the material availability rules for the manufacturing plant in the Material Availability
Rules page. On this page, you can configure the material assignments priority, inclusion criteria and
forced assignment criteria. You can define the work order material assignment priority based on certain
business attributes such as item, customer, work order planned start, and scheduled ship date in the
assignment priority tab. The most common setup is high-value items, high-priority customers and
scheduled ship date.
The first screenshot depicts the Work Order Assignment Priority tab. With this tab, you can to assign a
rule sequence and select one of the listed attributes and choose a value. The lower the integer value
for the rule sequence means the higher the priority for the attribute to identify the work orders for
material prioritization. “Sort order ascending or descending” is enabled for certain attributes like item,
customer and date.
For example, if the sort order for the attribute “Planned start date” is set as ascending, the work orders
are prioritized in the order of earlier to later dates.
If there are no assignment sequences defined, the default assignment sequence is applied. The default
assignment sequence is based on ascending order of “Work order planned completion date” first and
“Planned start date” next.
The second screenshot depicts the Inclusion Criteria tab that allows you to define the work order and
material inclusion criteria. You can include work orders within a specified time fence for a work order
date type, work order status, type, and subtypes.

For example, if you have specified the time fence as 24 hours for planned start date, this will include all
open work orders which are planned to start in next 24 hours from now. The eligible work order
statuses include unreleased, released, on hold and completed. The completed work orders are
considered for material availability check to address unlikely situations, where materials are pending for
issues against the assembly.
You can include components for material availability check based on work order operation item supply
type, and whether the material is internally manufactured or procured from a vendor. The eligible
supply type values are assembly pull, operation pull, and push.
In manufacturing of final assembly, you may require certain non-critical items which may be in
abundance in the inventory, or you may not require to consider those items for availability check. An
example of these types of items is nuts, screws etc. The inclusion criteria tab in the Material Availability
Rules page allows you exclude those items based on item name and item category.
The third screenshot depicts the Forced Assignment Criteria tab that allows you can define the forced
assignment criteria. This setup is to restrict you to take away manually the materials assigned to work
orders to satisfy the material requirement for other work orders, based on certain criteria. The criteria to
exclude work orders is based on specific attributes. The attributes are item number, item category, user
item type, work order status, work order type, work order subtype, work order priority, customer, and
ship to country.

After you have configured the material availability rules for the manufacturing organization, you are
required to invoke the action “Calculate Material Availability,” which is a background process. You can
schedule the background process to execute at fixed intervals depending on the business need.
Based on the inclusion criteria in the Material Availability Rules page, the calculation engine identifies
the work orders and the work order materials for the material availability check. Once the work orders
are identified, the assignment priority is assigned to the work order, based on the unique sequence
associated for the attributes in the work order assignment priority rules. The background process
include materials for availability check based on the inclusion criteria rules. You can view the list of
recommended work orders in the order of the assignment priority in the Work Orders tab of the
Materials Availability Assignments page. The background process uniquely identifies the assignment
priority for the list of work orders.
After the assignment priority is associated to the work orders, the “available to transact” quantity in the
organization is retrieved as part of background processing, and assigned to the work order materials to
arrive at the material shortage at the work order level. There is a visual indicator which shows you that
materials are completely available, partially available, or that materials are not available for the work
order.
The material availability indicator at the work-order level is derived based on work order materials and
the shortage quantity.

Material Shortage Quantity = Open Quantity - (Projected Available Quantity+Allocated Quantity-Picked
Quantity)
'Allocated Quantity' - The quantity of a material that is allocated to a work order during the picking
process when a movement request is created for a work order operation item.
'Picked Quantity'- The quantity of a material that is picked when the pick slip is confirmed and is issued
either directly to the work order or is moved to the staging subinventory.
The projected available quantity is the material quantity available based on the work order assignment
priority-- for example, if there are two work orders ‘X’ and ‘Y’ for the same assembly, each for one
quantity. The assignment priority for the work order ‘X’ is 1 and for work order ‘Y’ is 2. Material ‘A’ with
one quantity per assembly is required for the assembly. The “available to transact quantity” for the
material ‘A’ is 1 in the inventory. The projected available quantity for the work order ‘X’ will be ‘1’ and
for the work order ‘Y’ will be ‘0’.
In case of material shortages, you can view the expected supplies against different supply documents
in the work order material availability details panel. The documents include purchase requisitions,
purchase orders, inter organization transfers, transfer orders and work orders. Viewing the expected
supplies allows you to able to decide whether to release a work order or to unrelease a released work
order.
You can view the work orders that require materials and the corresponding availability and shortages
pertaining to the material in the Material Availability Assignments page. This helps you to know which
material is critical for a work order, and you can decide to manually adjust the work order material
assignments.

From the list of prioritized work orders, you can manually change the material assignments. You can
force assign materials to a work order, which has a material shortage. Force assign means manually
taking away the materials assigned to a lower priority work order to satisfy the material requirement of
a higher priority work order in the list. Similarly, you can force unassign materials from a work order to
manually reassign the materials to other work orders that have a material shortage. When you force
assign a work order, the materials are taken from the work orders in the descending order of
assignment priority. When you force unassign a work order, the materials are released to work orders
in the ascending order of assignment priority.
Lets take the example of work orders shown in here. There are four work orders. The work orders are
‘M1-1849,’ having assignment priority as 1, ‘M1-1850,’ having assignment priority as 2, ‘M1-1851,’
having assignment priority as 4, and ‘M1-1852,’ having assignment priority as 3.
The work order 'M1-1851‘ has a shortage for the material ‘STORAGEUNIT1’ required for the
manufacture of assembly 'SPARC_SERVER2'.
Material ‘STORAGEUNIT1’ is available for ‘M1-1849’ and partially available for the work orders ‘M1-
1850’, ‘M1-1851’ and ‘M1-1852’. You want to expedite the work order ‘M1-1851’ which has assignment
priority 4.
You will force assign the work order M1-1851, which results in unassigning materials from the 3 work
orders having assignment priority 1, 2 and 3.

In order to make materials available for the work order M1-1851, the material for the work order with
assignment priority 3 is taken first. As the material quantity is still not enough to make the material
available for the force assigned work order, the material for the work order with assignment priority 2 is
taken next, and then taken from the work order with assignment priority 1 to make the materials
available for the work order.
The first screenshot depicts how you can view and adjust material assignments for work order
prioritization. The second screenshot depicts a preview of force assigned and unassigned work orders.
The third screenshot depicts how you can view the force assigned and unassigned work orders.

When changing the material assignment, you can preview the changes affecting the selected work
order and other impacted work orders that are prioritized or deprioritized. The screenshot depicts the
Material Availability Assignments page that displays visual indicators of reassigned materials shown in
the list of work orders after implementing the change.
After you have previewed the material assignments and adjusted your changes accordingly, you can
release the prioritized work orders with all critical materials available to shop floor for execution.
You can unrelease work orders released previously in lieu of higher priority work orders. And, you can
hold work order with material shortages until supplies are expected to be available in the inventory.

You can also pick materials from Material Availability Assignments. Once the work orders are selected,
and ‘Release and Pick Components’ action is executed, a popup is shown to update the parameters.
This popup is common for both: the Manage Work Orders and Material Availability Assignments pages.
Then, the eligible work orders are set to released status and pick release action is performed. An ESS
job is launched and picking is initiated.
The screenshot depicts the Material Availability Assignments page and highlights the Release and Pick
Materials mass action that allows you to release and pick materials for work orders.

75 minutes Practice
340 minutes Total
Oracle SCM Cloud: Manufacturing Foundation 8-2
This section discusses various production execution transactions.

This diagram depicts the high level process flow, and the tasks that are relevant to in-house Oracle
Manufacturing Cloud execution, for both work order–based execution and orderless execution. Work
order based executions support outside processing of certain operation where the operation is
performed at a supplier location and also inspections at operations if set up. The Create Work Order
and Release Work Order tasks are discussed in lesson 6, titled “Manage Work Orders.” This lesson
discusses other tasks on the diagram.
In work order–based execution, work orders are created and released to production. Using the
Review Dispatch List task, production operators view the scheduled operations of the released
work orders, and perform the production activities. Operators can inspect subassemblies after any
operation. Operators can either manually issue materials or charge resources using the Report
Material Transactions or Report Resource Transactions tasks, respectively. Upon completion of
the production activity for the operation, Operators can report Operation Completions using the
Report Operation Transactions task. Materials are backflushed, and the resources automatically
transacted, as defined in the work order as part of the Operation Transaction. For the last operation
sequence in production, the completed items are sent to inventory. Production supervisors can
manage and execute supplier operations from the Manage Supplier Operations task. Unforeseen
events on the shop floor can be reported as Production Exceptions by production operators.
Production supervisors can view the exceptions, analyze and take the necessary steps to resolve
the same.

In orderless execution, work orders are not created, and production activity is reported only upon
completion using the Report Orderless Transactions task in reference to a work definition.
Materials are backflushed, and resources are automatically transacted based on the work definition,
and the completed items are put away into inventory.
The production transactions for both work order–based execution, and orderless execution are
transferred automatically through Transfer Transactions from Production to Costing task.
Production supervisors can close work orders using the Close Work Orders task. They can review
and monitor the production activities, for both work order–based execution and orderless execution
using the Review Production History task.
Production supervisors can review the inventory and material transactions for a specified lot or serial
number using the Review Genealogy task.
REST Services for Operations Starts and Stops:
A REST service is also available for Operations Starts and Stops. Using the operationStartStops
resource, you can View (GET), Create (POST), Update (PATCH), and Delete (DELETE) Operation
Starts and Stops. The Operation Starts and Stops resource manages the start time and stop time of
one work order operation. If a serial controls the operation, then this resource stores the start time
and stop time of the work order operation for the assembly serial. For more information, refer to the
following link: https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/fasrp/index.html.

This section discusses how you can review dispatch list.

This screenshot highlights the following on the Review Dispatch List page:
• Actions menu that lets you initiate actions like printing labels, traveler, etc.
• View attachments from work order and sales order
In addition, the screenshot highlights the following indicators:
• Serial start/pause
• Operation start/pause
• Manual reporting of material and resources. If the plant parameter Material Reporting Level
for Serialization Operations is set to Item Serial, material reporting is enabled for each item
serial.
The Oracle Manufacturing Cloud provides an intuitive and easy-to-use dispatch list that displays In-
House work order operations ordered in the sequence to be worked upon for a chosen work area,
and one or more work centers.
It provides several visual indicators to highlight records requiring attention, and allows users to report
production transactions while on the move.

The Dispatch List is generated based on the chosen work area and work centers, and lists quantities
in different dispatch statuses, such as Ready, Scrap, Reject, and Complete. The list also displays
optional operations. In addition, it provides several visual indicators to highlight records that are
either past due, or require manual reporting of material and resource usages.
For any given operation in the dispatch list, users can review the related work order details, print
work order traveler, product labels, and conditionally report operation, material and resource
transactions. The View menu enables users to show or hide columns, reorder columns, and change
the sort orders in the dispatch list.
The Review Dispatch List page is specifically designed for shop floor users, and allows users to
report production progress with just two user clicks. It also provides access to review, and enter
additional details required to complete a transaction.
To execute serial tracked manufacturing, the dispatch list enforces users to report production
transactions, by specific product serials, that are previously associated to work orders.
If inspection is setup for an operation, the inspection will be triggered when the operation transaction
is initiated through Quick Complete or Complete with Details actions.
Unforeseen events on the shop floor can be reported as Production Exceptions. Operators can
specify the type of the exception and describe the issue .
Users can indicate the start or pause for either operation or item serial number by clicking on the
start or pause icon. This would track how long the operation or item serial is worked upon.
Operators can view attachments belonging to sales order header, sales order line, work order
header, work order operation, work order operation materials and work order operation resources, if
they exist. Users can also upload attachments to the work order operations from the dispatch list.

This screenshot depicts how you can search for specific records by using a saved search.
Through a set of commonly used search attributes, the Review Dispatch List page allows users to
search for specific operations, and perform actions on them.
The Review Dispatch List page provides:
• Dispatch list based on the application default search
• Personalized save search
The dispatch list can be configured to run automatically, every time the user logs into the application.
Work Area is a mandatory search attribute. The work area by default is associated to the first record
in alphabetical order, in the Application Default search. Dispatch status is the other search criteria
that is set to Ready in the Application Default search.
REST Services for Dispatch List Work Order Operations:
A REST service is also available for Dispatch List Work Order Operations. Using the
dispatchListWorkOrderOperations resource, you can View (GET) Dispatch List Work Order
Operations. The Manufacturing Work Order Dispatch Lists resource manages the work order
operations for the dispatch list. The application must work on these operations for a work area and
for one or more work centers. It displays counts and optional operations for work orders that are in
Released status or Completed status. For more information, refer to the following link:
https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/fasrp/index.html.

This screenshot highlights the following sections in a Work Order Traveler:
• Supplier Operation Details: Details of supplier operation
• Operation Materials: Details of Work Order Operation Material
The Print Work Order Traveler feature allows you to print the work order traveler during production
execution. The work order traveler contains work order details such as work order information, work
definition details, work order operations, materials, resources and resource instances, and
reservations and attachments. Attachments from the work order, work order operation, work order
operation resource, work order operation item, sales order header and sales order line are included
in this report. For serialization-enabled operations, the work order traveler also consists of product
serial numbers. For outside processing operations, the traveler also captures the supplier details
along with the additional attributes such as outside processing item.
You can modify the Work Order Traveler template to include additional attributes required by the
user. The attributes from work order header, work definition, work order operations, work order
product serial, work order reservations, work order TIA values and attachments can be added to the
work order traveler. The modified template must be provided in the setup for Plant Parameters so
that the system can, by default, use it to print the traveler.
The Work Order Traveler can also printed using a configurable scheduled process.

This screenshot depicts a label printed for a work order.
The Print Product Label feature provides the ability to print product labels during production
execution. The product label prints label content for the product, such as item number, item
description, work order details, and quantity. For serialization-enabled operations, the labels can be
printed for product serial numbers.
The production users can print the product labels during the production process when reviewing
work orders, reviewing the dispatch list, and reporting product completions.
The label template can be modified to include additional attributes from item definition, work order,
operation transaction, serial number, and lot number.
The modified template must be provided in the setup for Plant Parameters so that the system can by
default, use it to print the labels.
It is possible to integrate with third-party label providers. Third-party label providers can subscribe to
business events in Integration Cloud Service(ICS). A new print product label event is raised when
print label actions are performed.

This section discusses how you can report production transactions and collect inspection results.

The Report Operation Transactions feature allows you to report progress at a work order operation
level. You have the option to report the progress of the work order by Quick Complete action in two
clicks, if the transaction does not require additional inputs, or by reviewing the details of transactions
through multiple pages by Complete with Details action.
Progress can be reported for serial tracked operation and non-serial tracked operations from Ready
or Reject dispatch states.
If inspection is setup for the operation, the inspection results are entered first and then the
disposition as complete or reject is decided automatically by the inspection results entered. You can
optionally move the reject to scrap with appropriate privilege.
The typical operation transactions performed by an operator are:
• Completing a quantity at an operation
• Scrapping a quantity at an operation
• Rejecting a quantity at an operation for further review to decide on the disposition action
• Completing a reject quantity if the rejected quantity is decided as acceptable
• Scrapping a reject quantity if the rejected quantity is decided as unacceptable
• If inspections are setup, then the disposition will be decided by the inspection results entered.

If the transaction is an operation completion at the last operation, the product is completed to
inventory.
You can select either the Generate Lot or the Generate Serial button on the Complete with Details
page for the last operation of a work order or during orderless completion. These buttons are
displayed based on the type of item control. If the product is only lot control enabled you only see the
Generate Lot button. If the product is only serial control enabled, you only see the Generate Serial
button.
Additionally, the production operator also has the opportunity to correct any errors by performing a
reverse transaction. Reverse transaction reverses the quantity transacted earlier. But the forward
and reverse transactions are recorded as separate transactions. Reverse transactions can be
performed from Complete, Scrap and Reject dispatch states.
Operation transactions can also be imported through a web service, or by entering the required data
in predefined xlsm templates using file based data import (FBDI).

The Quick Complete and Complete with Details are two modes of reporting progress of work order
on the shop floor. The Quick Complete allows simultaneous reporting of scrapped, rejected, and
completed quantities. Quick Complete can be performed with or without inspections for serial tracked
and non-serial tracked operations.
The Quick Complete action provides the user to complete a transaction in two clicks if all required
details can be defaulted from the work order, and if the transaction does not require lot and serial
numbers for product, or any backflush components. The user cannot make any changes to the
material or resource usages. The user cannot make any changes to the completion location in case
of product completions or reversals.
Multiple transactions, such as complete, scrap, and reject, can be reported in one quick complete
action. To perform a quick complete action for an operation without inspection, the production
operator first queries for the work order operation in the required dispatch state in the dispatch list.
The operator then expands the row by clicking the expansion icon in the first column. The operator
then enters the required quantities or selects the required serials for transaction and clicks Quick
Complete. For operation with inspection, the operator must enter the quantity to inspect or select the
required serials and click Quick Complete.

This screenshot depicts the user action to initiate the Quick Complete transaction for a non-serial
tracked operation without inspection. The quantities for multiple fields are populated.
Quick Complete action for non-serial tracked operation without inspection is initiated by the
production operator, by querying the required record in the dispatch list. You must enter the
quantities in the required fields, and then click Quick Complete.

This screenshot depicts the Review Dispatch List page and highlights that if the operation has a
mandatory inspections setup, then the operation transaction Quick Complete should be initiated
with the quantity for inspection. Inspection is to be done first and based on inspection results the
disposition as complete or reject is automatically decided.

This screenshot depicts the Quick Complete page and highlights that inspection results drive the
disposition. Inspection result collection can be initiated during quick complete action. For this an
inspection plan should be setup and associated with the item for the work order operations. The
inspection plan is automatically triggered if the operator clicks the Quick Complete action after
entering the quantity for inspection. Inspections can be initiated for operation transactions from the
Ready or Reject dispatch states. If the inspection is plan is set for WIP inspection of the assembly for
the work order operation and dispatch state, then you will have to mandatorily collect the inspection
results. You will have to enter the quantity for inspection and then click Quick Complete button. You
cannot enter the quantities for destination dispatch states at the time of transaction initiation unlike
operations without inspections. The quantity in destination dispatch state is governed by the
inspection result values.
The inspection results entered for the inspection characteristics in the inspection plans is compared
with the specification values setup for the inspection characteristics. If the result entered for any of
the inspection characteristic is out of specification limits, then the quantity is rejected at the work
order operation. There is a non-conformance automatically logged for out of specification inspection
results. Otherwise, if the inspection results entered for all the inspection characteristics are within the
preset specification limits, then the quantity is accepted for completion at the work order operation.
You must mandatorily complete the quantities accepted by inspection. You can choose to move the
quantities rejected by inspection to reject for rework or to scrap. You can scrap only if the user has
the required privilege to scrap.
The quantities moved to reject can be reworked and inspected again if so setup. You can setup
separate inspection plans for inspection from ready and reject states.

The user cannot complete the parent transactions without collecting inspection results for the
transaction quantity. If the user collects the inspection results and cancels the transaction without
completing the parent transaction, the inspection results will not be saved and the transaction will be
rolled back.
For any result values that are out of specification limits, a non conformance will be logged
automatically in the background.
Once the transactions are completed, a confirmation message is displayed. If multiple transactions
are initiated, a confirmation message is displayed for each transaction.

This screenshot depicts how the Quick Complete action supports reporting of progress on serial
tracked operations. For serial tracked manufacturing, you can initiate the Quick Complete action for
multiple serials. For operations without inspection, the production operator queries for the required
record in dispatch list, expands the row, selects the required serials for complete, scrap or reject, and
clicks Quick Complete to complete the transaction. For operations with inspection, the operator
selects the required serials for inspection and clicks Quick Complete to initiate inspection. Inspection
results must be collected for individual serials. Disposition of each serial as complete or reject is
based on the inspection results entered. The operator will have to complete or reject the serials
depending on the inspection results entered. The serials rejected by inspection can ne scrapped if
the operator has appropriate privilege.

The Complete with Details action allows the user to view and update transaction details, and input
any lot and serial numbers for products or components. The users can report additional materials
and resources consumed in the operation. The Complete with Details action allows users to either
complete, or scrap or reject, while reporting the operation transaction. The user is guided to navigate
through multiple pages to inspect, review transaction details, report materials and resources, and
review inventory details for product completion and reversals.
The Complete with Details action provides the ability to report transactions for serial tracked
operations. This action allows reporting for only one serial per transaction flow for operations without
inspections and for all serial tracked operations. For non-serial tracked operations with mandatory
inspections, multiple transactions can be reported in one transaction flow.
Non-Serial Tracked Operations
To initiate this action for non-serial tracked operations without inspection, the user must enter the
quantity for either complete, scrap or reject for the work order operation in the dispatch list, and click
Complete with Details. The user is allowed to navigate through multiple pages. The first page allows
the user to review transaction details, and add transaction notes. The next two pages allow the user
to report material, and resources used in the operation. The last page allows users to review and
enter details for reporting product completions into inventory.
If inspection is setup for the operation, then the transaction is initiated from Ready or Reject dispatch
statuses by clicking the Complete with Details after entering the quantity for inspection. Inspection
result collection page opens up first before all the other pages. The production operator will have to
capture inspection result for each quantity separately and the disposition as complete or reject is
automatically decided based on the inspection results entered.

The quantity accepted by inspection must be completed at the operation and the rejected quantity
can be rejected at the operation or moved to scrap if the production operator has the appropriate
privilege to scrap
Serial Tracked Operations
To initiate this action for serial tracked operations with out inspection, the user must select the
required serial number for the work order operation in the dispatch list, and click Complete with
Details. The user is allowed to navigate through multiple pages as above. Only one serial can be
transacted at a time with Complete with Details action.
If inspection is setup for the operation, then the transaction is initiated from Ready or Reject dispatch
statuses by clicking the Complete with Details after selecting the required serial number (one serial
only). Inspection result collection page opens up first before all the other pages. The inspection
result is captured for the serial and the serial is automatically dispositioned as Complete or Reject
based on inspection result entered. If the serial is accepted by inspection, then it must be completed
at the operation else if the serial is rejected by inspection , it can be rejected at the operation or
moved to scrap if the production operator has the appropriate privilege to scrap

This screenshot depicts the Review Dispatch List page. In addition, it shows how for operations
without inspection, the Complete with Details action is initiated from the dispatch list by querying for
the required record, and entering the quantity for one of the dispatch states, such as, Complete,
Scrap or Reject, and click Complete with Details.
The Complete with Details action is disabled if quantities are entered in multiple dispatch states,
such as, Complete and Scrap or Complete and Reject. This is because the Complete with Details
action creates only one operation transaction in a transaction cycle for operations without
inspections.
If the operation has a mandatory inspection, the quantity to be inspected should be entered to initiate
the transaction. The disposition as complete or reject will be based on the inspection result entered.
Inspections can be setup only from Ready or Reject dispatch statuses only. Complete with Details
action can create multiple operation transactions in a transaction cycle for operations with
inspections.

This screenshot depicts the Inspect train stop that allows you to enter inspection results and is
displayed only if the transaction has inspection. You can click Complete with Details, to be guided to
navigate, and complete the transaction. The navigation flow has a maximum of five train stops. The
“Inspect” train stop will appear only if there is a mandatory inspection setup for the operation and if
the transaction is initiated from Ready or Reject dispatch status. It will be the first train stop.
The “Backflush Materials” and “Autotransact Resources” train stops appear, based on the setup
in plant parameters, and the “Inventory” train stop appears only if the operation is the last operation
in work order operations.
Inspect Train Stop: You will have to mandatorily enter the inspection results for each quantity
separately if the operation has a mandatory inspection setup. Based on the inspection results
entered, the quantity is accepted or rejected.

This screenshot depicts the Product train stop that allows you to review transaction details, enter
transaction note and additional information.
Product train stop: The production operator reviews the transaction details and provides other
details, such as enters a transaction note, provides additional information as required, and specifies
the option to print labels. Attachments belonging to the work order and sales order can be viewed.
Also, new work order operation level attachments can be uploaded if required. After completing the
required entries, the user clicks Next to navigate to the next train stop.
For operations with mandatory inspection, the quantity that pass inspection is entered as complete
and cannot be updated . The quantity that fails inspection is by default treated as reject and can be
optionally scrapped if the operator has appropriate privilege. For this the reject quantity should be
decreased and the scarp quantity is increased by the same amount.

This screenshot depicts the Material train stop that allows you to report material consumed in the
operation.
Backflush Materials train stop: This train stop allows the user to enter or update the component
details, such as component lot number, serial number, adjust component and resource usages,
supply subinventory, and locator.
Handheld scanners can also be used to scan and input component numbers, lot numbers, and serial
numbers. The applicable operation pull and assembly pull components are populated by default.
However, the user can update applicable operation pull and assembly pull components if they are
set up.
The user can click Back to navigate to the previous train stop. However, the user cannot edit the
contents in the page, except the transaction note.
If inspection results have been collected, this train stop will display all the backflush components for
complete, scrap and/or reject transactions.
Click Next to navigate to the next train stop.
Autotransact Resources train stop: This train stop allows the user to enter or update the resource
usage details. The resources set up as automatic in the work order are defaulted, and the usage
rates can be updated if so set up.
If inspection results have been collected, this train stop will display all the automatic resources for
complete, scrap and/or reject transactions.
The display of this train stop is governed by the setup of plant parameters, as explained in the
previous slide.

Click Next to navigate to the next train stop. If the operation is an intermediate operation in the work
order operations, then this train stop is the last train stop, and the transaction is completed by
clicking Save. If the transaction is saved, the user is navigated back to the dispatch list, and a
confirmation message is displayed.
The display of these two train stops is dependent on the setup of the plant parameter, Allow Quantity
Changes During Backflush. Valid values for this parameter are None, Materials, Resources, or Both.
The following explains the meanings for these values:
None: Neither the Backflush Materials nor Autotransact Resources train stop will appear. When the
value is None, you cannot modify the component or resource usage quantities or transact new
components or resources during this transaction.
Materials: Only the Backflush Materials train stop will appear. When the value is Materials, you can
modify the component usage quantities and transact new components during this transaction, but
you cannot modify resources.
Resources: Only the Autotransact Resources train stop will appear. When the value is Resources,
you can modify the resource usage quantities and transact new resources during this transaction,
but you cannot modify components.
Both (Default Value): Both the Backflush Materials and Autotransact Resources train stops will
appear. When the value is Both, you can modify the component and resource usage quantities and
transact new components and resources during this transaction.
Note: If the system is not able to determine the backflush material details such as lot and serial
numbers, then the Backflush Materials train stop will appear regardless of the parameter value.
Inventory train stop: This train stop is the last train stop and is displayed only if the current
operation is the last operation in the work order operations. Users can enter lot and serial numbers
for products, capture lot and serial attributes, and complete the product in multiple subinventories.
If inspection results have been collected, then only the quantity for completion will be displayed in
this train stop.
Click Save to complete the transaction from this train stop. The user is navigated back to the
dispatch list, and a confirmation message is displayed.

This screenshot depicts the confirmation message that is displayed on the Review Dispatch List
page if the transaction is successful.

This screenshot depicts the Complete with Details action that supports serial tracked operations with
and without inspection. Only one serial can be transacted in a transaction flow and only one
operation transaction is created. For operations with inspection, the production operator will have to
complete or reject the serial depending on the inspection results entered. The production operator
can choose to scrap if the serial is rejected by inspection with appropriate privilege..
For serial tracked operations, the Complete with Details action is the same as for non serial tracked
operation, except that the transaction is in the context of a single serial number, and is displayed in
the header. If the transaction is initiated from Ready or Reject status and the operation has a
mandatory inspection, then serial is completed or rejected based on inspection result entered.
All the other features and functionalities across train stop are similar to non serial tracked operation.
The last train stop Inventory has a single row, as only one serial can be completed in one inventory
location.

These screenshots depict the Create Inspection and Inspections tasks. In addition, they highlight the
Inspection History task.
The production operator can collect inspection results for a work order operation in standalone mode
by clicking the Create Inspection task in the Manufacturing Overview page.
The production operator can view the inspection results collected during transactions by clicking the
Inspections task in manufacturing overview page. Inspection results can be searched within the
organization for an assembly, work order and work order operation, inspection dates etc. The search
results for each instance of result collection will be presented in a row.
The production operator can view the inspection results collected during operation transactions and
also results collected in standalone mode but will be able to edit only those results which were
collected in standalone mode. The results collected in context of a parent transaction cannot be
edited once committed.
The operator can view the inspection results collected during transactions for a work order by
clicking the Inspection History in the History tab in work orders page. The operator can view the
results collected for the work order operations. The results include those collected during
transactions and also those collected against the work order operation in standalone mode.

This screenshot depicts the Report Material Transactions page that allows the production operator to
issue materials from inventory to the work order operation. It also allows to return the issued
materials back to Inventory. It also allows negative issues or negative returns to handle negative
material requirements. For Serial Tracked Manufacturing, where production is tracked by serial
numbers, the materials can be issued or returned in reference to the serial units.
In the All data entry mode, the operator can report materials by selecting from defaulted list of
material requirements specified the work order operation with the push supply type. The operator
can also choose the manually entered data entry mode, in which the operator can choose not to
default the material requirements specified on the work order, and specify the material transactions
manually. The operator can add additional materials that are specified as material requirements in
the work order.

The operator can enter the To transact quantity, and the serial and lot numbers for the material
based on the material control setup. The subinventory and optionally locator are defaulted based on
system setup, and can be overridden by the operator. The material transactions can be reported by
using a handheld scanner. You can scan multiple serial numbers by scanning the component
number once. You can optionally scan component serial attributes for components that are serial-
controlled at issue.
Material transactions can be reported through the Report Materials page accessed from the dispatch
list, or the overview page in the work execution work area.
Material transactions can also be imported through REST service, or through predefined xlsm
templates using FBDI.
REST Services for Work Order Metrics and Work Order Statuses:
• A REST service is also available for Work Order Metrics. Using the workOrdersMetrics resource,
you can View (GET) Work Order Metrics. The Work Orders Metrics resource manages the work
order metrics for the plant.
• A REST service is also available for Work Order Statuses. Using the workOrderStatuses
resource, you can View (GET) Work Order Statuses. The Work Order Statuses resource
manages the work order statuses.

This screenshot depicts the Report Resource Transactions page and highlights the Transaction
Type field that allows you to charge or reverse Resource usage. The Report resource transactions
feature provides the ability for the production operator to manually charge a resource and optionally
a resource instance against a work order operation or to reverse charges earlier made for a resource
and resource instance against a work order operation. It helps to charge a work order operation for
the labor, and equipment resources consumed while performing the operation. The resource
consumed can be according to previously planned and defined in the work order, or any other
additional adhoc resources that were consumed in the course of the operation.
If a resource is charged by mistake or due to error, it can be reversed with another transaction of
type Resource Reverse. Both the charging and reversal are recorded as two separate transactions.
The Report Resource Transactions page can be accessed by clicking the Report Resource
Transactions link in the execution overview page. The user is prompted to enter the work order and
the work order operation sequence. This page can also be accessed from the dispatch list by
clicking the Resource link on a work order operation record.
The page has the work order operation resources set up as Manual by default. The user can update
the default data and add new records.
Resource transactions can also be imported through REST service, or through predefined xlsm
templates using FBDI.

This demonstration shows how a rework work order is created for the assembly, and a defective
component of the assembly is replaced.

In this practice, you report production transactions at an in-house operation and collect inspection
results.

This section discusses how you can manage and execute supplier operations.

This diagram represents a typical example of outside processing where an Original Equipment
Manufacturer (or OEM) performs the first operation in house and ships the machined parts to a
supplier for plating. The supplier performs the plating operation and sends the plated parts to the
OEM. The OEM receives the plated parts and pays the supplier for performing the value added
services. In the entire process, the OEM retains the ownership of the goods that are sent to and
received back from the supplier.
Outside processing is a commonly-observed business process where one or more operations of a
work order are outsourced to a supplier who provides specialized manufacturing services. These
services may vary depending upon the nature of the industry. Typical examples of such specialized
services in discrete manufacturing include heat treatment processes such as annealing, abrasive
blasting processes, industrial painting processes, powder coating processes, and plating processes.
Outside processing is often adopted as a strategic alternative to in-house manufacturing to lower
manufacturing costs due to economies of production, leverage state of the best-in-class
manufacturing technology, augment capacity to overcome production bottlenecks, and more
importantly, focus on core competencies.

This diagram depicts the process flow of outside processing across product offerings in Supply
Chain Management. The first step is to create and release a work order with supplier operations in
Fusion Manufacturing. Work orders are scheduled using the unconstrained logic in Planning
Central/Supply Planning. Once the work order is released, a request is sent to Fusion Supply Chain
Orchestration (SCO) to create a Purchase Requisition. SCO in turn creates a Supply Order and
triggers the creation of a Purchase Requisition in Fusion Self Service Procurement. An Outside
Processing Purchase Order is created in Fusion Purchasing using the details maintained in the
Outside Processing Blanket Agreement. The next step is to execute work order by reporting
quantities as completed at the operation prior to the supplier operation following which, a request is
sent to Fusion Supply Chain Orchestration (SCO) to create a Shipment Line. SCO in turn creates a
Supply Order Line and triggers the creation of a Shipment Line in Fusion Shipping. A Shipment is
manually created for the Shipment Line which is then confirmed and closed. Based on the options
set for the Ship Confirm Rule, the processes to Print Packing Slip and Bill of lading are automatically
launched. The next step is to receive the goods from the supplier in Fusion Receiving and deliver
them to manufacturing. You can optionally create an ASN in Fusion Supplier Portal or Fusion
Receiving which can be used to create a receipt. However, ASN creation is mandatory in case of
consecutive supplier operations. For a non-serialization enabled supplier operation, receipt and
delivery of goods to manufacturing results in automatic completion of quantities at the supplier
operation. Supplier operations are then managed and tracked in Fusion Manufacturing. The receipt,
delivery and operation transactions result in receipt and cost accounting in Fusion Cost
Management.

The following steps explain the process flow of outside processing across product offerings in
Supply Chain Management in a sequential manner:
1. Create and release a work order with supplier operations in Oracle Fusion Manufacturing
Cloud Service. Work orders are scheduled using the unconstrained logic in Oracle Fusion
Planning Central Cloud Service and Supply Planning.
2. When the work order is released, a request is sent to Oracle Orchestration Cloud Service to
create a Purchase Requisition. Oracle Orchestration Cloud Service in turn creates a Supply
Order and triggers the creation of a Purchase Requisition in Self-Service Procurement.
3. An Outside Processing Purchase Order is created in Oracle Fusion Purchasing Cloud
Service using the details maintained in the Outside Processing Blanket Agreement.
4. Execute the work order by reporting quantities as completed at the operation prior to the
supplier operation. A request is then sent to Oracle Orchestration Cloud Service to create a
Shipment Line. Oracle Orchestration Cloud Service in turn creates a Supply Order Line and
triggers the creation of a Shipment Line in Oracle Fusion Shipping.
5. A Shipment is manually created for the Shipment Line in Oracle Fusion Shipping which is
then Confirmed and Closed. Based on the options set for the Ship Confirm Rule, the
processes to Print Packing Slip and Bill of Lading are initiated automatically.
6. The next step is to create an Advance Shipment Notice (ASN) in the Supplier Portal for the
outside processing service item. Goods are received in Oracle Fusion Receiving using the
ASN and delivered to Oracle Fusion Manufacturing Cloud Service. For a supplier operation
that is not serialization enabled, this results in automatic completion of quantities at the
supplier operation.
7. Supplier operations are then managed and tracked in Oracle Fusion Manufacturing Cloud
Service.
8. The receipt, delivery and operation transactions result in receipt and cost accounting in
Oracle Cost Management.
Note: Steps to create shipment line and print shipping documents are optional as indicated in the
diagram. ASN creation is required only in the case of consecutive outside processing scenarios.

This screenshot depicts the Manage Supplier Operations page and highlights the following:
• Dispatch Status
• Exceptions
How are supplier operations monitored and managed in Fusion Manufacturing?
Fusion Manufacturing enables monitoring of supplier operation quantities by dispatch status through
the new Manage Supplier Operations page. In addition to the existing dispatch statuses, a new “In
Process” dispatch status has been introduced to represent quantities at supplier operations that
have been completed at the prior count operation but have not been received yet from the supplier
after processing Once received, the quantities or serials are further managed in the Manage Supplier
Operation page which provides the ability to complete, scrap, reject through the Quick Complete and
Complete with Details actions. The Manage Supplier Operation page also provides visibility into
supplier operation exceptions. In addition, for any supplier operation record, it provides the ability to
navigate to the work order details page and to the supplier operation details page. It also provides
the ability to navigate to the material transactions page to report OEM supplied component usage.
Attachments belonging to the work order, work order operation, work order operation items, sales
order header and sales order line can also be viewed from this page. And lastly, it provides the
ability to print work order traveler and product labels directly from the Manage Supplier Operations
page.

This screenshot depicts the Review Supplier Operation details page and highlights the action to
manage supply exceptions.
In addition, for any given supplier operation, Fusion Manufacturing provides the ability to monitor and
review supplier operation details by displaying the purchasing, shipping and receiving details related
to a supplier operation and providing hyperlinks to review additional details of POs, shipments and
receipts.
It also provides several actions that are conditionally enabled for production supervisors to manage
supply exceptions.

In this practice, you execute a supplier operation with minimal user intervention and report operation
transactions automatically.

This section discusses how you can review product genealogy.

This screenshot depicts the Genealogy Details page for a product. Product Genealogy tracks
manufacturing and inventory transactions starting from the receipt of the lot /serial from the supplier
through the manufacturing process, and to which customers received shipments.
A graphical view shows the genealogy hierarchy depicting the parent child relationships between
components and assembly. You can drill down to view additional details and related information.
During material transaction/Operation Transaction, if the transaction involves lot or serial number of
the assembly/components and the attribute ‘Enable Genealogy Tracking’ is set to ‘Yes’ for the items
– system transfers material transaction details / Operation Transaction along with the related
material transactions to Genealogy. ‘Transfer Manufacturing Transactions to Genealogy’ ESS is
initiated automatically for this.

This screenshot depicts the Transaction History page that allows you to view transaction history of a
specific lot or serial number. The transaction history is displayed in form of map and can be filtered
based on the source and source transaction type.
The details of the Operation and Product completion transaction information for the lot or serial can
also be viewed by clicking on Operation or Product completion hyperlink.

In this practice, you review product genealogy.

This section discusses how you can report orderless transactions.

This screenshot depicts the Report Orderless Transactions feature that allows to report production
activity without having to create work orders. Production operators can report completion or scrap of
an item in reference to a work definition.
The referenced work definition is used to determine the material and resource usages. The work
definition with production priority 1 is defaulted, but can be changed to another work definition to
determine the correct material and resource usages. The operator can conditionally review, add,
delete, and modify the material, and resource requirements (along with resource instances) before
submitting the transaction.
The reported production transactions can be reversed by reporting either Orderless Return or
Return From Scrap transactions. The referenced work definition is used to return the materials back
to inventory. Also, the resource charges are reversed based on the work definition.
Orderless transactions can be reported through the Report Orderless Completion, Scrap, Return or
Return From Scrap tasks, from additional task list the overview page of the work execution work
area. Report Orderless Transactions can also be imported through the Material Transaction Web
Service or material transaction through predefined xlsm templates.

This section discusses how you can review production transactions.

This screenshot depicts the Production Transaction History page. The Review Production
Transaction History feature provides a view of all the production transactions that have been
reported on the shop floor. The View is ordered in reverse chronological order, to allow recent
transactions to be displayed first.
The Review Production Transaction History provides a separate view of production transaction for
work order-based and orderless executions. For Work Order Execution, the material, resource, and
operation transactions can be viewed. For operation transactions, the corresponding backflushed
material and automatically charged resources can be viewed. Additionally, production completions
into inventory can be viewed for operation transactions for the last operation sequence.
For Orderless Execution, the orderless completion, scrap, return or return from scrap transactions
can be viewed. The corresponding backflushed materials, and automatically charged resources can
be viewed for orderless transactions.
The Review Production Transaction History UI allows the user to filter the production transactions
based on transaction date range, item serial number, work order, or item.

Work Order Material Transaction: When you enable electronic signatures and electronic records for
Work Order Material Transaction, the inline process to generate electronic records and capture
electronic signatures is initiated when you submit a material issue or return transaction for approval
through the Report Material Transactions page.
Work Order Operation Transaction: If you enable electronic signatures and electronic records for
Work Order Operation Transaction, the inline process to generate electronic records and capture
electronic signatures is initiated. The process begins when you report quantities or serials as any of the
following:
• Completed
• Scrapped
• Rejected or Reversed to Ready
Note that if multiple transactions, such as complete, scrap, and reject are reported through a single
action, then a single electronic record is generated which contains the details of all the transactions
reported. Also, the process is not initiated when an operation transaction is imported through file-based
data import or web service.
Orderless Transaction: Similarly, if you enable electronic signatures and electronic records for
Orderless Transaction, the inline process to generate electronic records and capture electronic
signatures is initiated. The process begins when you report an orderless completion transaction or an
orderless scrap transaction through the Report Orderless Completion page, or an orderless return or
an orderless return from scrap transaction through the Orderless Return page.

This section discusses how you can report and manage production exceptions.

This diagram depicts the process of reporting and managing exceptions in production. Unforeseen
events on the shop floor can be reported by production operator with details of what is impacting the
planned production. Once the exception is reported, the interested stakeholders would be notified.
Upon receipt of the notification, the production supervisor would analyze if the reported exception
would impact any other work order operations and associate them to the exception. Based on the
nature of the exception, production supervisor can choose to put the impacted operations on hold.
Finally, once the exception is resolved, production supervisor can release the impacted operations
put on hold and close the exception.
REST Services for Production Exceptions:
A REST service is also available for Production Exceptions. Using the productionExceptions
resource, you can View (GET) Production Exceptions. For more information, refer to the following
link: https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/fasrp/index.html.

This screenshot depicts the Report Production Exception page and highlights the Exception Type as
well as the Component fields. The production operator can select the work order operation and
report an exception by specifying the work area, work center, resource or component impacting the
production activity. It is also possible to report a miscellaneous exception by specifying details of
impact on production as part of the exception description. The exception of the type supplier
operation cannot be reported manually and is reported automatically by system to report demand or
supply exceptions.
As part of the predefined configuration, once a production exception is reported, the system notifies
all the users who have edit or view exception privileges as well as having the data role of the plant in
which the exception was reported. The predefined notification configuration can be further configured
by defining the notification rules in the business rule editor provided as part of the Business Process
Management (BPM) tool.

This screenshot depicts the Manage Production Exceptions page. The production supervisor can
monitor the exception for the plant using infotiles. The infotiles would display number of open
exceptions, types of exception, exceptions reported by shift and by severity. Each of the info tiles are
clickable and drills down into additional details that can be viewed and acted on.
The production supervisor can view quickly view the important exception information like type,
description, severity and list of impacted work order operations. The production supervisor can
navigate to Exception Details page to view further details.

These screenshots depict the Exception Details page that the production supervisor can use to
further elaborate the description of an exception or to reclassify the severity. The supervisor would
search for other work order operations that use the resource, resource instance, component, work
area or work center for which exception is reported and associate the impacted work order
operations to the exception. Based on the nature of the exception, the production supervisor can
choose to put the production on hold for the impacted operations. The production supervisor works
to resolve the exception and as needed collaborate with users across the enterprise using Oracle
Social Network. Finally, once the exception is resolved, the production supervisor can release the
impacted operations put on hold and close the exception.

Enable E-Signatures and E-Records for Production Exceptions:
Oracle Electronic Records and Signatures allows you to enable deferred electronic records and
electronic signatures for production exception closure in Oracle Manufacturing Cloud.
The process to generate electronic records and capture electronic signatures is initiated only when a
production exception is submitted for closure either from the Manage Production Exceptions page, or
from the Edit Exception page or from the Work Order Exception tab, or from the Supervisor Mobile
Application pages. The status of the production exception changes to Pending Approval for Closure
after the exception is submitted for closure.
Electronic records are generated and the electronic signatures are captured in a deferred mode before
the production exception is closed.
Notifications are sent to the approvers which can be accessed through the bell notifications in the
oracle cloud application. The approvers can review the electronic records before adding their electronic
signature. Approvers can input their comments, indicate their approval or rejection and sign the
electronic record by entering their password. The approvers also have the visibility to the current status
of the approval process through the approval history region in the inline signature capture page and in
the notifications. Depending upon the outcome of the approval, the production exception is either
closed or rolled back to open status.
The first screenshot depicts that the ERES process is initiated in a deferred mode after the Production
Exception is submitted for closure and the second screenshot depicts an E-Record for Production
Exception.

The electronic record that is automatically generated for a production exception contains the following
information:
• Exception Information
• Attachment Details
• Impacted Work Order Operations
Oracle E-signatures and E-Records also allows you to search and retrieve electronic records in the
electronic records work area using multiple search criteria like the contents of the report title, the
transaction type, organization, signed date and status.

This demonstration shows how you create and resolve a work order exception.

This section discusses how to transfer production transactions to costing.

This screenshot depicts the Transfer Transactions to Costing page. This is an ESS program, which
can be scheduled or run on demand. The manufacturing execution transaction details and work
order status updates are transferred to costing for accurate costing of the work orders. The resource
transactions for only costed resources, all operation transactions data, and work order status
updates are interfaced to costing, from the Oracle Manufacturing Cloud.

This section discusses import of production transactions through predefined templates and external
web services.

It is possible to import the work order transactions, namely material transactions, resource
transactions, and operation transactions using the cloud spreadsheet import mechanism. Predefined
templates for each of the transactions can be downloaded from the File-Based Data Import for
Oracle Supply Chain Management Cloud Chapter in Oracle Help Center, and transaction data can
be entered offline in the spreadsheets.
Correct Work Orders and Transactions for Import: You can view and initiate corrections for work
orders import as well as for operation, resource and material transaction imports that were created
using a file based data import. This feature allows you to view the records that were earlier submitted
for processing using a file based data import but failed processing due to validation errors. These
records are in the “Completed with Errors” status in the interface tables. Note that only those records
that were created through FBDI spreadsheets are available for corrections.

External web services allow the import of material transactions including orderless transactions and
operation transactions. The web service can be invoked with the appropriate payload. Transactions
from multiple plants can be imported in a single upload. The data can optionally be imported in
batches.
SOAP services support for Material and Operation transactions.
REST service support for Material, Resource and Operations transactions.

This section discusses how to close work orders.

This screenshot depicts the criteria to close work orders on the Mass Close Work Orders page. The
user can Close work orders after all activities are completed on a work order. No further updates can
be made on a closed work order. Costing and variances, if any, are posted when the work order is
set to closed status. This is generally a supervisory function performed from the Manage Work
Orders page.
The user can also close work orders by using the scheduled program. The user can search for
multiple work orders using the parameters, and invoke the scheduled program to process the
selected work orders, and close them. If a work order cannot be closed, an appropriate error is
displayed.

15 minutes Practice
30 minutes Total
This section discusses the Oracle Manufacturing Cloud subject areas.

The key features of OTBI in the Oracle Manufacturing Cloud are:
• OTBI offers real time, self-service reporting directly off Oracle Manufacturing Cloud data.
There is no data movement from Fusion Apps to BI application. Every time an analysis is
invoked, it is directly fetches the latest data from Fusion Apps.
• The subject areas supported for this integration support analysis of both In-house
manufacturing and contract manufacturing related work orders and their transactions.
• It provides several Oracle Manufacturing Cloud subject areas, which can be used to build
user-defined analysis. In this lesson, you will learn about these subject areas in detail.
• The dimensions and facts in these subject areas provide visibility to work order management,
work execution transactions, and production exceptions.
• Sample analytics are provided for work orders scheduled today and cycle time performance.

This screenshot depicts the dimensions, facts, and as well as the Design and Output views in the
Work Order Performance Real Time subject area. In addition, it highlights the Design The Work
Order Performance Real Time subject area provides real time information from the work order
objects. Besides work order information, the operation quantities too are stored in the work order
object and hence this subject area can be used for analysis of the metrics related to both work order
management and work order operation transactions. The dimensions in this subject area can be
either from work order level attributes or operation level attributes. The level of abstraction of data in
the facts belonging to this subject area thus depends upon the dimension, which is, work order or
operation. For example, Completed Quantity fact will display completed quantity of Work Order or
Operation, depending upon the dimensions chosen in the analysis.
The following are some of the facts in this subject area:
• Count of work orders
• Execution quantities: Ready, Completed, Scrap, and Rejected quantities
• Work order quantities: Start, Past due backlog, On Hold, Unreleased quantities, and
Reserved quantities
• Work order aging
• Over completion attributes
• Cycle time metrics

The screenshots depict the following:
• The Cycle Time Performance dashboard displays the cycle time statistics (Queue, Run, Idle
times) for an item aggregated on a monthly basis. It allows to drill down to the cycle time
statistics for a specific work order operation or a specific serial number.
• The Work Orders Scheduled Today analysis displays the details of work orders scheduled to
be completed today. It provides a real time view of the quantities reported on the work orders.

This screenshot depicts the dimensions, facts, and the Design and Output views in the Material
Usage Real Time subject area. The Material Usage Real Time subject area provides real time
information of the component transactions taking place in the plant. This subject area can be used to
analyze both component requirements, and components transacted.
Some of the facts in this subject area are Required Quantity, Actual Usage, Issued Quantity,
Returned Quantity, Open Quantity, Negative Issued Quantity, Negative Returned Quantity, On-Hand
balance Quantity.

This screenshot depicts the dimensions, facts, and the Design and Output views in the Resource
Usage Real Time subject area. The Resource Usage Real Time subject area provides real time
information of the resource transactions taking place in the plant. This subject area can be used to
analyze both resource requirements and resources transacted.
Some of the facts in this subject area are Planned Usage, Actual Usage, Usage Variance, and
Usage Variance percentage.

This screenshot depicts the dimensions, facts, and the Design and Output views in the Actual
Production Real Time subject area. The Actual production real time subject area provides real time
information of quantities completed from the last operation into inventory.
This subject area can be used in conjunction with work order real time performance subject area, to
analyze operation completions with work order completions.

The Production Exceptions Real Time subject area allows you to analyze both high level and detailed
level information of production exceptions logged in the shop floor. This is useful to monitor potential
pitfalls which can impact the production output or the health of the plant. In addition, it provides cross
subject area join capabilities with other Manufacturing subject areas through the use of common
dimensions to provide useful insights about the reasons and consequences of the exceptions logged.
Using this subject area you can view metrics related to count of exceptions, age of open exceptions,
cycle time to resolve closed exceptions and impacted work order operations. You can also define
additional user defined aging buckets if the predefined ones in the subject area do not meet the
requirements.

The Manufacturing – Purchased Item Usage Real Time is used to analyze purchased item details in a
work order. Common dimensions have been used to allow you to perform cross subject area analysis
between Manufacturing, Procurement, and Receiving subject areas. The dimensions and metrics in
this subject area allow you to analyze the details of the entire procurement lifecycle consisting of
requisitions, purchase orders, receipts, returns and corrections, and view them in the context of a
Manufacturing work order.

This section discusses how to build dynamic and user-defined reports using Oracle Transactional
Business Intelligence and the Oracle Manufacturing Cloud subject areas.

In this practice, you create an OTBI report using Manufacturing subject areas.


Manufacturing Foundation R19A Student Guide

Uploaded by

Copyright:

Available Formats

Manufacturing Foundation R19A Student Guide

Uploaded by

Document Information

Original Description:

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

Manufacturing Foundation R19A Student Guide

Uploaded by

Copyright:

Available Formats

Schedule: Timing Topic

Oracle SCM Cloud: Manufacturing Foundation 1 - 4

Oracle SCM Cloud: Manufacturing Foundation 1 - 6

Oracle SCM Cloud: Manufacturing Foundation 1 - 7

Oracle SCM Cloud: Manufacturing Foundation 1 - 8

Oracle SCM Cloud: Manufacturing Foundation 1 - 9

Oracle SCM Cloud: Manufacturing Foundation 2 - 3

Oracle SCM Cloud: Manufacturing Foundation 2 - 4

Oracle SCM Cloud: Manufacturing Foundation 2 - 5

Oracle SCM Cloud: Manufacturing Foundation 2 - 6

Oracle SCM Cloud: Manufacturing Foundation 2 - 7

Oracle SCM Cloud: Manufacturing Foundation 2 - 8

Oracle SCM Cloud: Manufacturing Foundation 2 - 9

Oracle SCM Cloud: Manufacturing Foundation 2 - 10

Oracle SCM Cloud: Manufacturing Foundation 2 - 11

Oracle SCM Cloud: Manufacturing Foundation 2 - 12

Oracle SCM Cloud: Manufacturing Foundation 2 - 13

Oracle SCM Cloud: Manufacturing Foundation 2 - 14

Oracle SCM Cloud: Manufacturing Foundation 2 - 15

Oracle SCM Cloud: Manufacturing Foundation 2 - 16

Oracle SCM Cloud: Manufacturing Foundation 2 - 17

Oracle SCM Cloud: Manufacturing Foundation 2 - 18

Oracle SCM Cloud: Manufacturing Foundation 2 - 19

Oracle SCM Cloud: Manufacturing Foundation 2 - 20

Oracle SCM Cloud: Manufacturing Foundation 3 - 3

Oracle SCM Cloud: Manufacturing Foundation 3 - 4

Oracle SCM Cloud: Manufacturing Foundation 3 - 5

Oracle SCM Cloud: Manufacturing Foundation 3 - 6

Oracle SCM Cloud: Manufacturing Foundation 3 - 7

Oracle SCM Cloud: Manufacturing Foundation 3 - 8

Oracle SCM Cloud: Manufacturing Foundation 3 - 9

Oracle SCM Cloud: Manufacturing Foundation 3 - 10

Oracle SCM Cloud: Manufacturing Foundation 3 - 11

Oracle SCM Cloud: Manufacturing Foundation 3 - 12

Oracle SCM Cloud: Manufacturing Foundation 3 - 13

Oracle SCM Cloud: Manufacturing Foundation 3 - 14

Oracle SCM Cloud: Manufacturing Foundation 3 - 15

Oracle SCM Cloud: Manufacturing Foundation 3 - 16

Oracle SCM Cloud: Manufacturing Foundation 3 - 17

Oracle SCM Cloud: Manufacturing Foundation 3 - 18

Oracle SCM Cloud: Manufacturing Foundation 3 - 19

Oracle SCM Cloud: Manufacturing Foundation 3 - 20

Oracle SCM Cloud: Manufacturing Foundation 3 - 21

Oracle SCM Cloud: Manufacturing Foundation 3 - 22

Oracle SCM Cloud: Manufacturing Foundation 3 - 23

Oracle SCM Cloud: Manufacturing Foundation 3 - 24

Oracle SCM Cloud: Manufacturing Foundation 3 - 25

Oracle SCM Cloud: Manufacturing Foundation 3 - 26

Oracle SCM Cloud: Manufacturing Foundation 3 - 33

Oracle SCM Cloud: Manufacturing Foundation 3 - 28

Oracle SCM Cloud: Manufacturing Foundation 3 - 29

Oracle SCM Cloud: Manufacturing Foundation 3 - 30

Oracle SCM Cloud: Manufacturing Foundation 3 - 31

Oracle SCM Cloud: Manufacturing Foundation 3 - 32

Oracle SCM Cloud: Manufacturing Foundation 3 - 33

Oracle SCM Cloud: Manufacturing Foundation 4 - 3

Oracle SCM Cloud: Manufacturing Foundation 4 - 4

Oracle SCM Cloud: Manufacturing Foundation 4 - 5

Oracle SCM Cloud: Manufacturing Foundation 4 - 6