14Manufacturing

This chapter contains the following:

How You Set Up Manufacturing

To set up Oracle Fusion Manufacturing, you perform the setup tasks specified in the Manufacturing and Supply Chain Materials Management offering on the Setup and Maintenance work area.

Manufacturing is an optional functional area in the Manufacturing and Supply Chain Materials Management Offering, and must be selected for implementing Oracle Fusion Manufacturing. The Manufacturing functional area consists of the following hierarchy:

  • Manufacturing Master Data

  • Structures

This topic lists the manufacturing setup tasks under the following three categories:

  • Manufacturing Master Data Functional Area

  • Structures Functional Area

  • Common Setup Tasks

Manufacturing Master Data Functional Area

There are some tasks that may be included in the Manufacturing Master Data functional area, and if the tasks are required or optional. For more information about adding tasks to the Manufacturing Master Data functional area, see Implementing Manufacturing chapter of the Implementing Manufacturing and Supply Chain Materials Management guide.

The following table describes some tasks in the Manufacturing Master Data functional area with their descriptions and whether the tasks are required or optional:

Task Required or Optional Description

Manage Plant Parameters

Required

Configure parameters at a plant level that are relevant to manufacturing setup, work definition, and work execution.

Manage Production Lookups

Optional

Create and maintain lookups that are used in manufacturing setup, work definition, and work execution.

Manage Work Areas

Required

Create and maintain work areas to represent the specific regions in the plant where work activities are executed.

Manage Work Centers

Required

Create and maintain work centers to represent the grouping of resources where work is performed and is composed of resources having similar capabilities.

Manage Production Resources

Optional

Create and maintain resources to model the labor or equipment and to track their usages during production execution.

Manage Manufacturing Plant Data Access for Users

Required

Manage manufacturing plant data access for user provisioned roles.

Note: Although you're required to provide data access to the manufacturing plant, you can follow the common procedure to do so.

The setup tasks specified in the Manufacturing Master Data functional area that don't require specific setup for manufacturing are listed under the Common Tasks section.

Structures Functional Area

None of the setup tasks specified in the Structures functional area require any specific setup for manufacturing. So they're listed under the Common Tasks section.

You can set up Third Party Applications in the Setup and Maintenance work area for IoT Production Monitoring integration. In Oracle Fusion Applications Cloud, use the Setup and Maintenance work area to define the base URL of the IoT application. You can use this data to drill down from the Manufacturing Cloud to the IoT Production Monitoring Cloud.

Note: Item structure is currently supported for only the discrete manufacturing work method.

Common Tasks

Some tasks are included in the Manufacturing Master Data or Structures functional area, but don't require specific setup for manufacturing:

The following table lists the tasks in the Manufacturing Master Data functional area which require no specific setup:

Task Required or Optional Description

Manage Plant Profiles

Required

Review and maintain profile values for manufacturing facilities.

Manage Production Value Sets

Optional

Create and maintain production value sets.

Manage Work Setup Descriptive Flexfields

Optional

Define validation and display properties of the descriptive flexfields for work setup. Descriptive flexfields are used to add user-defined attributes to entities.

Manage Work Execution Descriptive Flexfields

Optional

Define validation and display properties of the descriptive flexfields for work execution. Descriptive flexfields are used to add user-defined attributes to entities.

Manage Enterprise Scheduler Jobs for Manufacturing Applications

Optional

Manage Oracle Enterprise Scheduler jobs and their list of value sources for the Manufacturing applications.

Define Basic Product Structures

Optional

Create and edit structures for the items.

Manage Structure Header Descriptive Flexfields

Optional

Create and edit item structure type descriptive flexfield attributes.

Manage Item Structure Type Details

Optional

Create and edit structure type details.

Manage Structure Component Descriptive Flexfields

Optional

Create and edit item structure component descriptive flexfield attributes.

Genealogy Build Deferred During Execution

Optional

Specify whether the product genealogy is built online immediately or you can decide to defer it.

It has two values of Yes and No with the default value being No. The profile value can be set up only at site level.

These tasks are common to any Oracle Cloud application. Manufacturing doesn't require any specific setup for them, so you can follow the instructions that you use to perform them for any Oracle application. For details about how to perform them, refer to the Implementing Common Features for SCM guide.

Note: None of the setup tasks specified in the Structures functional area require any specific setup for manufacturing. So they're listed under the Common Tasks section.

Enable Genealogy Build Deferred During Execution

To improve the performance of Genealogy, some modifications have been made. A new profile has been introduced. The profile name is Genealogy Build Deferred During Execution (Code: ORA_WIE_DEFER_GENEALOGY_BUILD). You have to specify whether the build of product genealogy is deferred. If it's not deferred, then genealogy builds at the same time as the transaction.

To enable Genealogy Build Deferred During Execution, perform the following steps.

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Task: Manage Administrator Profile Values

  2. In the Profile Option Code field, query for the option Genealogy Build Deferred During Execution (Code: ORA_WIE_DEFER_GENEALOGY_BUILD).

Using this profile, you can specify whether the product genealogy is built online immediately or you can decide to defer it. It has two values, Yes and No, with the default value being No. The profile value can be set up only at site level.

  • If you set the profile value to No, genealogy details are interfaced to the genealogy repository immediately and genealogy builds at the same time as the transaction.

  • If you set the profile value to Yes, genealogy will be not be built immediately. The related transaction records will be available in the interface. You must schedule the Retry in-Error Genealogy Transactions scheduled process at an appropriate time to resubmit the records for processing and build genealogy. After the genealogy is built, the records are removed from the interface.

Enable Audit Trail for Manufacturing Work Orders

If you're an application administrator, you can enable audit trail for manufacturing work orders to comply with US Code of Federal Regulations (CFR 21 Part 11) for electronic record and electronic signature requirements. By doing so, you let your internal and external auditors have more visibility of the work order change history.

Here's how you can enable audit trail for discrete or process manufacturing work orders.

  1. Click Navigator, and then click Setup and Maintenance.

  2. On the Setup page, select the Manufacturing Supply Chain and Materials Management offering.

  3. Search for the Manage Audit Policies task.

  4. On the Manage Audit Policies page, click Configure Business Object Attributes.

  5. On the Configure Business Object Attributes page, select the Common Work Execution product to view the work order object.

  6. Select the check box for the work order objects to enable audit trail.

  7. Select the check boxes for all or any of the child objects for audit. The attributes of that selected object, enabled for audit displays. The key attributes of each object are available by default.

  8. Click Create in the Audited Attributes section which is displayed on the right side of the page to add more attributes.

  9. Click Save if you want to add more attributes to your configuration to enable auditing, or click Save and Close if you're done.

View Audit Reports for Manufacturing Work Orders

Here's how you can view the audit reports for manufacturing work orders and you must have the internal auditor role to view the audit reports.

  1. Click Navigator, and then click Audit Reports.

  2. Select the Common Work Execution product and Work Order business object type and enter the date or date range.

  3. Enter the work order number that needs to be audited in the Description field.

  4. Select Include Child Objects if you want to see the work order child objects in the audit report, and click Search.

Here are the sample values you can enter in the Description field to get the audit report.

Search Text Results

M1-1106

All Work Orders starting with M1-1106 and its child objects.

Work Order:M1-1106

All Work Orders starting with M1-1106 and its child objects.

Work Order:M1-1106:Operation:Testing

All Operations and its child objects with Operation name starting with Testing for Work Order M1-1106.

Work Order:M1-1106:Serial Number:PM

All Product Serial Numbers starting with PM for Work Order M1-1106.

The manufacturing plant parameters are analogous to system parameters and they enable you to specify various functionality of a manufacturing plant. Before setting up the plant parameters, you must set the organization as the manufacturing plant.

Setting a Manufacturing Plant

A manufacturing plant is a type of inventory organization and can be further categorized into: in-house manufacturing plant and contract manufacturing plant.

To set an organization as a manufacturing plant, perform the following steps:

  1. In the Manage Inventory Organizations page, select an existing organization or create a new one from the Search Results region. Then, click the Manage Inventory Organization Parameters button to edit the organization settings.

  2. In the Manage Inventory Organization Parameters page,

    • Select the Organization is a manufacturing plant check box to set an organization as in-house manufacturing plant.

    • Select the Organization represents a contract manufacturer check box to set an organization as contract manufacturing organization.

Note: If the organization is set as a contract manufacturing plant, you must also provide the supplier and supplier site information for the plant.

Setting the Manufacturing Plant Parameters

Once an organization is set as manufacturing plant, you can set the parameters that determine each functionality of the plant.

This topic discusses the manufacturing plant parameters in details. It provides information about the parameters, their acceptable values, and the default values if any.

Plant Details Parameters

The following table discusses the plant details parameter:

Parameters Required Description

Manufacturing Calendar

Yes

Refers to the schedule or calendar to be used in the manufacturing plant.

Note: Changing the Manufacturing calendar or deleting the calendar in the Setup and Maintenance work area can lead to data corruption and unwanted consequences in the work order scheduling and lead time calculations.

Enable Process Manufacturing

No

Specifies if the plant is enabled for process manufacturing, in addition to discrete manufacturing.

Default Work Method

No

Specifies the default work method when the plant is enabled for process manufacturing. The possible values are Discrete Manufacturing and Process Manufacturing. The default plant parameter value is Discrete Manufacturing.

Material Parameters

The following table discusses the material parameters:

Parameters Required Description

Default Supply Subinventory

Yes

For work definitions:

Specifies the default supply subinventory for work definition operation item if there is no supply subinventory defined for the work center or item master.

For work orders:

Specifies the supply subinventory to be used when backflushing components that don't have default values defined at the work order operation item or the inventory item level.

For orderless transactions:

Specifies the supply subinventory to be used when backflushing components that don't have default values defined at the work definition operation item or the inventory item level.

Default Completion Subinventory

Yes

For work orders:

Specifies the completion subinventory to be used for storing the completed product if a default isn't defined at the work order level.

For orderless transactions:

Specifies the completion subinventory to be used for storing the completed product if a default isn't defined at the work definition level.

Default Supply Locator

No

For work definitions:

Specifies the default supply locator for work definition operation item if there is no supply locator defined for the work center or item master.

For work orders:

Specifies the supply locator to be used when backflushing components that don't have default values defined at the work order operation item or the inventory item level.

For orderless transactions:

Specifies the supply locator to be used when backflushing components that don't have default values defined at the work definition operation item or the inventory item level.

Default Completion Locator

No

For work orders:

Specifies the completion locator to be used for storing the completed product if a default isn't defined at the work order level.

For orderless transactions:

Specifies the completion locator to be used for storing the completed product if a default isn't defined at the work definition level.

Default Pick Slip Grouping Rule

No

For work orders:

Specifies the grouping rules that are defaulted from Inventory and are used as the basis to group the pick slips for work order material picking.

Print pick slips

No

For work orders:

Specifies whether or not to print the pick slips that are generated when the Pick Materials for work Orders scheduled process is run and movement request is created to move materials from the warehouse to either directly issue to a work order or to a destination subinventory.

Include pull components for pick release

No

For work orders:

Specifies whether or not to allow materials with the supply type operation pull and assembly pull to be considered for the pick release activity.

Issue push components on pick release

No

For work orders:

Specifies that when a pick slip is confirmed for the work order materials the materials with supply type push will be directly issued to the work order.

Work Definition Parameters

The following table discusses the work definition parameter:

Parameters Required Description

Starting Operation Sequence

No

Specifies the default sequence number for the first operation in a work definition and work order.

The value must be a positive integer.

Operation Sequence Increment

No

Specifies the incremental value by which the sequence of the operation is to be increased in the work definition and work order.

The value must be a positive integer.

Phantom Operation Inheritance

No

Specifies whether the phantom components and resources are inherited at the same operation that the phantom is assigned in the parent item work definition.

The valid values are:

  • Material Only: On selecting this value, when creating the work order, all of the phantom components are inherited at the same operation that the phantom is assigned in the parent item work definition.

  • Material and Resources: On selecting this value, when creating the work order, all of the phantom components and resources are inherited at the same operation that the phantom is assigned in the parent item work definition.

The default value is Material Only.

Work Execution Parameters

The following table discusses the work execution parameter:

Parameters Required Description

Work Order Prefix

No

Specifies the prefix to use when autogenerating the work order names when creating the work orders.

A maximum length of 30 characters is allowed.

Work Order Starting Number

Yes

Specifies the initial number to pass in to the document sequence which is created when a record is saved.

The value must be a positive integer greater than zero. The default value is 1000.

This field becomes read only after the work order document sequence for the plant is created.

Default Overcompletion Tolerance Percentage

No

Specifies the percentage of assemblies that you can over complete on work orders if not defined at the work order level.

The value must be between 1 and 100. The default value is Null.

Note: For process manufacturing, the tolerance is applicable for the Operation quantity.

Default Transaction Mode

No

Specifies whether the materials and resources are defaulted from the work order operation when reporting the material or resource transactions.

The valid values are:

  • All: On selecting this value, all the components and resources that are associated to the work order operation are defaulted and you can transact against them.

  • Entered: On selecting this value, the components and resources that are associated to the work order operation aren't defaulted and you're required to enter the specific component or the resource to transact.

The default value is All.

Default Transaction Quantity

No

Specifies whether the transaction quantity is to be defaulted as that of the required quantity during the material or resource transactions in a work order. However, you're allowed to make changes to the defaulted quantity.

The valid values are:

  • None: On selecting this value, the transaction quantity isn't defaulted as that of the required quantity during the material or resource transactions in a work order.

  • Material: On selecting this value, the transaction quantity is defaulted as that of the required quantity during the material transactions in a work order.

  • Resources: On selecting this value, the transaction quantity is defaulted as that of the required quantity during the resource transactions in a work order.

  • Both: On selecting this value, the transaction quantity is defaulted as that of the required quantity during the material and resource transactions in a work order.

The default value is Both.

Allow Quantity Changes During Backflush

No

Specifies whether changing the transaction quantity is allowed or not.

The valid values are:

  • None: On selecting this value, during backflushing, you can't modify the transaction quantity of the pull components required in an operation and can't report the consumption of the ad hoc material. During automatic charging, you can't modify the charge quantity of the automatic resources required in an operation and can't report the usage of the ad hoc resources.

  • Material: On selecting this value, during backflushing, you can modify the transaction quantity of the pull components required in an operation and can report the consumption of the ad hoc material. During automatic charging, you can't modify the charge quantity of the automatic resources required in an operation and can't report the usage of the ad hoc resources.

  • Resources: On selecting this value, during backflushing, you can't modify the transaction quantity of the pull components required in an operation and can't report the consumption of the ad hoc material. During automatic charging, you can modify the charge quantity of the automatic resources required in an operation and can report the usage of the ad hoc resources.

  • Both: On selecting this value, during backflushing, you can modify the transaction quantity of the pull components required at an operation and can report the consumption of the ad hoc material. During automatic charging, you can modify the charge quantity of the automatic resources required at an operation and can report usage of ad hoc resources.

The default value is None.

Default Work Order Traveler Template

No

Specifies the name of the template to be used for printing the work order traveler or the labels for the plant.

You may use your own BI publisher templates by specifying the file path and file name of your templates in this parameter. If the parameter is left blank, the default template defined in the BI publisher report definition settings is used for all the plants.

Note: You can find separate default templates for discrete and process manufacturing work orders.

A maximum string length of 400 characters is allowed.

Default Label Template

No

Specifies the name of the template to be used for printing the work order traveler or the labels for the plant.

You may use your own BI publisher templates by specifying the file path and file name of your templates in this parameter. If the parameter is left blank, the default template defined in the BI publisher report definition settings is used for all the plants.

A maximum string length of 400 characters is allowed.

Print product labels using external applications

No

Indicates whether product labels are printed using external printing applications. When selected, the native printing functionality into PDF is suppressed and a print product label business event is generated. External printing applications can listen to the business event to generate labels externally.

Include component yield in material requirements

No

Indicates whether the component yield is factored into the work order material requirements and the component quantities during the material transactions.

You deselect this parameter to avoid rounding the decimal quantities. The rounding can inflate transaction quantities causing inaccurate representation of requirements.

Automatically associate serial numbers during work order import

No

Indicates whether the serial numbers are to be automatically generated and associated when importing a work order.

Allow direct purchases for work orders

No

Indicates whether the direct purchases for work orders are allowed or not. The check box is checked by default for maintenance organizations. The check box is unchecked by default for manufacturing organizations and must be checked to enable the parameter.

Capture Level for Serialization-Enabled Operations

No

Level at which start or pause events are captured for serialization-enabled operations. The valid values are as follows:

  • Operation: When you select this value, start or pause events are captured for serialization-enabled operations at an operation level. This is a default option.

  • Item Serial: When you select this value, start or pause events are captured at individual serial units for serialization-enabled operations.

Trigger Purchase Requisition

No

Timing of creation of the purchase requisition for outside processing. The valid values are as follows:

  • At Work Order Release: Purchase Requisition is created at the time of releasing a work order.

  • At Operation: Purchase Requisition is created at the time of completing quantities at an operation prior to a Supplier Operation. This is the default value.

Material Reporting Level for Serialization-Enabled Operations

No

Level at which operators report materials for serialization-enabled operations. The valid values are as follows:

  • Operation: When you select this value, material reporting would be enabled only at the operation level. This is a default option.

  • Item Serial: When you select this value, material reporting would be enabled at individual serial units for serialization-enabled operations.

Lot Selection During Backflush

No

Specifies whether lots should be manually entered or defaulted during backflush. This is applicable for both Report Operation Transactions (Complete with Details) as well as Report Orderless Completion user flows.

The valid values are:

  • Manual: Lots aren't defaulted and need to be manually entered. This is the default setting.

  • Lot FIFO: Lots are defaulted using the receipt date or first in first out (FIFO) basis.

  • Lot FEFO: Lots are defaulted using the expiration date or first expiration first out (FEFO) basis.

Considerations for Setting Up Lookups for Manufacturing

Lookups in applications are used to represent a set of codes and their translated meanings. For instruction on setting up lookups that are common to any Oracle application, refer to the Implementing Common Features for SCM guide, Define Applications Core Configuration chapter.

In addition to the common lookups, Oracle Fusion Manufacturing uses some specific lookups.

The following table lists the lookups specific to Oracle Fusion Manufacturing and descriptions of the lookup codes which you can populate accordingly:

Lookup Name Lookup Code Description

Resource Class

ORA_WIS_RESOURCE_CLASS

Enables you to group resources into resource group for the planning activities.

Work Center Resource Group

ORA_WIS_WC_RESOURCE_GROUP

Enables you to group resources for the work center planning activities.

Work Order Operation Transaction Reason Codes

ORA_WIE_REASON_CODE

Captures the reason codes for scrap and reject transactions.

Work Order Sub Type

ORA_WIE_WO_SUB_TYPE

Captures the work order subtype that describes the specific nature of work being performed. The predefined values are Standard Production, Prototype, Repair, Pilot Lot, and Test Lot. You can add additional lookup values as needed.

Work Definition Operation Resource Activity

ORA_WIS_RESOURCE_ACTIVITY

Captures the activity name of the work definition operation resource. The predefined values are Setup, Run, and Tear Down. You can add additional lookup values as needed.

How You Manage Work Areas

A work area is the specific region in a manufacturing plant where the production activities are executed. In other words, a work area identifies a physical, geographical or logical grouping of work centers.

At least one work area must be defined for a manufacturing plant. However, a plant can have one or more work areas defined within it. A work area consists of one or more work centers within it. A production operator can report material, resource, and operation transactions performed at work centers that belong to a specific work area.

The Manage Work Areas page in the Work Definition work area serves as a starting point to create, edit, and delete the work areas. To access the Manage Work Areas page, based on your security privilege, you can do either of the following:

  • In the Work Definition work area, in the Tasks pane, click the Manage Work Areas link in the Plant Setup category.

  • in the Setup and Maintenance work area, use the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Manufacturing Master Data

    • Task: Manage Work Areas

Creating, Editing, and Deleting a Work Area

You create a work area by providing a unique name and code for the work area.

A work area is deactivated or reactivated by updating the Inactive On field. When a work area is deactivated, it is not available for further use until it is reactivated.

You can delete or deactivate a work area only if no work center is associated with it.

Note: You can query, create, update, and delete a work area using a REST API.

Work centers are specific production units that consist of people or equipment with similar capabilities. Each work center is associated with a valid work area and can be used for capacity requirement planning and detailed scheduling.

The Manage Work Centers page in the Work Definition work area serves as a starting point to perform the following tasks:

  • You can create, edit, and delete work centers.

  • You can add resources to a work center and allocate resources to different shifts.

  • You can view and manage exceptions associated to the resources.

However, based on your security privileges, you may have to manually add the Manage Work Centers task in the Setup and Maintenance work area, using the following:

  • Offering: Manufacturing and Supply Chain Materials Management

  • Functional Area: Manufacturing Master Data

  • Task: Manage Work Centers

Creating, Editing, and Deleting a Work Center

You create a work center by providing a unique name and code for the work center, and a valid work area to which the work center is associated.

A work center is deactivated or reactivated by updating the Inactive On field.

You cannot delete a work center if:

  • There is any resource associated with the work center.

  • The work center is being referenced in work definition operation.

  • The work center is being referenced in work order operation.

Note: You can query, create, update, and delete a work center using a REST API.

Adding Resources to a Work Center and Allocating Resources to a Shift

After creating a work center, you can add resources to it and then allocate shift hours to each resource.

The following table lists all the fields on the Manage Work Centers page and the descriptions of those fields to help you choose the required value for each field.

Field Description

Resource

The unique identifier of the resource. This is a required field.

Inactive On

The date on which the resource becomes inactive.

Default Units Available

Number of resource units available in a work center. This is a required field.

Available 24 Hours

Indicates whether a resource is available 24 hours a day. A resource that is not available 24 hours is available only during the shifts assigned to it.

Check Capable To Promise

Indicates whether the Global Order Promising engine considers the capacity of this resource during order promising.

Utilization

The percentage of the resource time available for the task. This is a required field.

Efficiency

The percentage of the time a resource takes to complete a task. This is a required field.

Utilization and Efficiency Percentages:

The utilization and efficiency percentages are by default set to 100 percent. 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 is required to be done using resource LATHE1 starting from 9 AM on a specific work order, and if its efficiency is 50 percent, and utilization is 50 percent, then the scheduler will determine the end time for this resource as 5 PM. This is calculated as 2/ (0.5*0.5) = 8 hours.( the efficiency percentage of the resource and the utilization percentage of the resource is multiplied to get a value. Then the number of hours required to be done by the resource is divided by the derived value to determine the number of hours from the start time of a resource.)

Resource Allocation:

A resource is available in shifts if the Available 24 Hours field is not selected. When a shift-based resource is associated to a work center, the default units of the resource are automatically assigned to all the shifts of the plant. You can update the availability of resource units across the shifts as required.

For example, consider that you have defined two 8 hour shift for the work center WC1: Day Shift and Night Shift. You associate two units each of four resources R1, R2, R3, and R4 to the work center WC1. The following table shows the various possibilities of associating shifts to resources in a work center and the ways to implement the solutions:

Scenario Implementation

You want the resource R1 available for 24 hours a day.

Consideration: You have not associated the resource R1 to the work center WC1 yet.

Solution: Select the Available 24 Hours check box when associating the resource R1 to the work center WC1. Now, the two units of resource R1 are available 24 hours a day and you cannot assign any shift for it.

You want two units of the resource R2 available for the Day Shift only.

Consideration: You have already associated the resource R2 to work center WC1 with Available 24 Hours check box deselected.

Solution: In the Resource Availability region, in the Day Shift column, enter 2 against the resource R2. Now, the two units of resource R2 is available for Day Shift. For the Night Shift, the resource R2 has zero or Null value.

You want one unit of the resource R3 available for Day Shift and one unit of resource R3 available for Night Shift.

Consideration: You have already associated the resource R3 to work center WC1 with Available 24 Hours check box deselected.

Solution: In the Resource Availability region, in the Day Shift column, enter 1 against the resource R3 and in the Night Shift column, enter 1 against the resource R3. Now, one unit of resource R3 is available for the Day Shift and one unit of resource R3 is available for the Night Shift.

You want all the units of resource R4 available for both the Day Shift and Night Shift.

Consideration: You have already associated the resource R4 to work center WC1 with Available 24 Hours check box deselected.

Solution: In the Resource Availability region, in the Day Shift column, enter 2 against the resource R4 and in the Night Shift column, enter 2 against the resource R4. Now, two units of resource R4 is available for both the Day Shift and the Night Shift.

Viewing and Managing Resource Exceptions

You use the work center resource calendar to view and manage the exceptions related to the resources. In case of a conflict, the exceptions granted in the work center resource calendar override the exceptions granted in production calendar.

If you're a production controller or supervisor, you can define and update work order statuses to support enterprise-specific business processes. To do so, use the Manage Work Order Statuses page. Here are two ways to find the page:

  • In the Tasks pane of the Setup and Maintenance work area, click the Manage Work Order Statuses task.

  • In the Setup and Maintenance work area, use this path:

  • Offering: Manufacturing and Supply Chain Materials Management

  • Functional Area: Manufacturing Master Data

  • Task: Manage Manufacturing and Maintenance Work Order Statuses

A work order status can be either predefined or user-defined. Here are the predefined statuses:

  • Unreleased

  • Released

  • On Hold

  • Completed

  • Closed

  • Canceled

Define a New Work Order Status

To define a new status, click the Add icon. You must provide a unique name and code for the status, and associate it to a system status. For example, you can define the new status Materials_Unrel, and associate it to the system status Unreleased. This helps you sort, manage, and report work orders more effectively.

Note: You must name the new status in a way that the user understands which system status it's associated to. You can add a prefix or a suffix of the system status. For example, you can use the name UNREL_MATERIAL_UNRELEASED to indicate that the new status is associated to the system status Unreleased.

Edit a User-Defined Work Order Status

You can only update the Name and Description attributes for both system statuses and user-defined statuses. For a user-defined status, you can't update the Code and System Status attributes.

Note: It's recommended to not update the name of the system status. However, if you want to, you must do it in a way that the user can understand and associate it to the original name of the system status.

Resource Instances

Resource instances are granular representations of a resource in the Manufacturing application. One or more resource instances can be associated to a resource. You can identify a resource by a unique code known as the identifier, and a name.

You can also optionally assign a primary work center to the resource instance to identify the department or location that the resource instance primarily works in.

Tip: Assigning a primary work center to a resource instance helps in quick assignment of the resource instance in work orders and work execution transactions.

You can deactivate or reactivate a resource instance by updating the Inactive On field. When a resource instance is deactivated, it's not available for further use until reactivated. You can delete a resource instance only if it's not used in work execution.

Associate Labor Resource Instances

A labor resource instance represents the names of actual people working in the manufacturing shop floor. A labor resource instance can be optionally associated to a person record available in the Oracle Trading Community Architecture. Such associations are unique within a plant.

Note: Oracle Trading Community Architecture represents a repository of person and organization parties identified through their party usages. Manufacturing allows the subset of Oracle Trading Community Architecture person party records to assign person type resource instances.

Person types in Oracle Trading Community Architecture that can be associated to a resource instance and can be any of the following:

  • Employee

  • Contingent Worker

  • Partner Contact

You can define persons of types Employees or Contingent Workers in Oracle Human Capital Management (HCM) and are automatically propagated to the Oracle Trading Community Architecture through the HCM- Oracle Trading Community Architecture auto-sync process.

You can set up persons of type Partner Contact in the Oracle CRM application, which are automatically available in the Oracle Trading Community Architecture.

Associate Equipment Resource Instances

An equipment resource instance represents the names of actual machines being used in the manufacturing shop floor. An equipment resource instance can optionally associated to an Asset Number defined in Maintenance Cloud. Such associations are unique within a plant.

Assets must be defined in a location corresponding to the plant and a location type work center in order to be eligible for association to the equipment resource instance.

Use the IoT Insights icon provided in the Equipment Resource Instances region, to drill down to the Machine Summary view in IoT Production Monitoring Cloud to view machine performance, real time sensor data, and insights into analytics, anomalies, predictions, and trends.

Set Up IoT Production Monitoring Integration

You can set up Third Party Applications in the Setup and Maintenance work area for IoT Production Monitoring integration.

To set up IoT Production Monitoring integration, you must opt in to enable this feature.

  1. In Oracle Fusion Applications Cloud, use the Setup and Maintenance work area to set up Third Party Applications. Create a third party application called IoT Production Monitoring which identifies the IoT Production Monitoring cloud instance that Manufacturing Cloud will integrate with.

  2. In the IoT Production Monitoring Cloud, go to Configuration, Settings, and set up the end point URL and other details required to integrate with Manufacturing Cloud.

Note: IoT integration currently supports drill down for only discrete manufacturing work orders and the equipment resource instances referenced in those work orders.

The resources are the labors, equipment, and tools allocated to a work center. Resources can be categorized into two types: Labor and Equipment.

The Manage Resources page in the Work Definition work area serves as a starting point to search, create, edit, and delete the resources.

However, based on your security privileges, you can also access the Manage Production Resources task in the Setup and Maintenance work area, by using the following:

  • Offering: Manufacturing and Supply Chain Materials Management

  • Functional Area: Manufacturing Master Data

  • Task: Manage Production Resources

Create, Edit, and Delete Resources

You must create a resource with unique name and code. Additionally, you must define the resource type and usage UOM of the resource at the time of creation.

You cannot change the usage UOM of a resource once associated with a work center. You cannot edit the resource type when a resource instance is associated. However, you can edit all other resource attributes at any time. You can schedule a resource in a work definition and work orders only if the usage UOM belongs to the UOM class as defined in the profile SCM Common: Default Service Duration class.

Note: The usage UOM field indicates the unit of measure for the planned and actual usage of a resource.

A resource is deactivated or reactivated by updating the Inactive On field. When a resource is deactivated, it is not available for further use until reactivated. You can delete a resource only if the resource is not assigned to any work center.

Note: You can query, create, update, and delete a production resource using a REST API.

Resource Instances

Resource instances are granular representations of a resource in the Manufacturing application. One or more resource instances can be associated to a resource. You can identify a resource by a unique code known as the identifier, and a name.

You can also optionally assign a primary work center to the resource instance to identify the department or location that the resource instance primarily works in.

Tip: Assigning a primary work center to a resource instance helps in quick assignment of the resource instance in work orders and work execution transactions.

You can deactivate or reactivate a resource instance by updating the Inactive On field. When a resource instance is deactivated, it is not available for further use until reactivated. You can delete a resource instance only if it is not used in work execution.

Associate Labor Resource Instances

A labor resource instance represents the names of actual people working in the manufacturing shop floor. A labor resource instance can be optionally associated to a person record available in the Oracle Trading Community Architecture. Such associations are unique within a plant.

Note: Oracle Trading Community Architecture represents a repository of person and organization parties identified through their party usages. Manufacturing allows the subset of Oracle Trading Community Architecture person party records to assign person type resource instances.

Person types in Oracle Trading Community Architecture that can be associated to a resource instance and can be any of the following:

  • Employee

  • Contingent Worker

  • Partner Contact

You can define persons of types Employees or Contingent Workers in Oracle Human Capital Management (HCM) and are automatically propagated to the Oracle Trading Community Architecture through the HCM- Oracle Trading Community Architecture auto-sync process.

You can set up persons of type Partner Contact in the Oracle CRM application, which are automatically available in the Oracle Trading Community Architecture.

Associate Equipment Resource Instances

An equipment resource instance represents the names of actual machines being used in the manufacturing shop floor. An equipment resource instance can optionally associated to an Asset Number defined in Maintenance Cloud. Such associations are unique within a plant.

Assets must be defined in a location corresponding to the plant and a location type work center in order to be eligible for association to the equipment resource instance.

Use the IoT Insights icon provided in the Equipment Resource Instances region, to drill down to the Machine Summary view in IoT Production Monitoring Cloud to view machine performance, real time sensor data, and insights into analytics, anomalies, predictions, and trends.

Set Up IoT Production Monitoring Integration

You can set up Third Party Applications in the Setup and Maintenance work area for IoT Production Monitoring integration.

To set up IoT Production Monitoring integration, you must opt in to enable this feature.

  1. In Oracle Fusion Applications Cloud, use the Setup and Maintenance work area to set up Third Party Applications. Create a third party application called IoT Production Monitoring which identifies the IoT Production Monitoring cloud instance that Manufacturing Cloud will integrate with.

  2. In the IoT Production Monitoring Cloud, go to Configuration, Settings, and set up the end point URL and other details required to integrate with Manufacturing Cloud.

Note: IoT integration currently supports drill down for only discrete manufacturing work orders and the equipment resource instances referenced in those work orders.

This section explains the details for Oracle Fusion Manufacturing business objects that can be enabled in Oracle Social Network to collaborate as social objects.

In the Setup and Maintenance work area, use the Manage Oracle Social Network Objects for Supply Chain Management task in the Manufacturing and Supply Chain Materials Management offering to configure the manufacturing business objects so that they're enabled for Oracle Social Network integration.

The following table lists the attribute details for Common Work Setup module and Work Definition business object:

Attribute Attribute Details

Item

Work definition item, as set up in the item organization

Description

Item description

Structure Name

Item structure name

Name

Work definition name

Version

Work definition version

Start Date

Work definition version start date

End Date

Work definition version end date

Production Priority

Production priority of the work definition

The following table lists the attribute details for Common Work Execution module and Work Order business object:

Attribute Attribute Details

Work Order

Work order number

Start Date

Work order start date

Completion Date

Scheduled completion date of the work order

Actual Completion Date

Actual completion date of the work order

Status

Work order status

Item

Work order assembly item number

Description

Assembly item description

Quantity

work order quantity

UOM

Unit of measure of work order quantity

Customer

Customer name, as applicable, for the work order

The following table lists the attribute details for Common Work Execution module and Exception business object:

Attribute Attribute Details

Exception Number

Unique identifier of the production exception

Reported By

User reporting the production exception

Reported On

Date on which the production exception was reported

Expected Resolution Date

Expected date for the production exception to be resolved

Expected Downtime in Minutes

Expected time duration when the production activity is stopped or likely to be stopped as a result of the reported exception

Description

User description of the production exception

Exception Type

User determined classification of the production exception

Resource

Resource for which production exception is reported

Component

Component for which the production exception is reported

Work Center

Work center for which the production exception is reported

Work Area

Work area for which the production exception is reported

Exception Status

Status of the production exception, either Open or Closed

Severity

User determined severity of the production exception and the following severity values are predefined:

  • Critical

  • High

  • Medium

  • Low

You can share all the attributes for a given business object, or selectively enable the individual attributes, so that only a few selected attributes are available on the social object wall.

Note: For more information about how to share a business object, refer to the Social Network chapter in the Oracle Applications Cloud Using Common Features guide.
Note: For manufacturing scenarios involving external users such as contract manufacturers, refer to the Collaborating Through Social Networking for Outside Users chapter in the Oracle Cloud Using Oracle Social Network guide.

How You Configure Human Tasks for Manufacturing

This topic explains how you set up the human task associated with the Oracle Fusion Manufacturing business objects.

You must use the Manage Task Configurations for Supply Chain Management task from the Setup and Maintenance work area to configure the human tasks:

The following table lists the human tasks you must configure:

Human Task Name Description

QualityIssueHumanTask

Human task to notify users for production exceptions.

StructureChangeFYIHumanTask

FYI Human Task Flow to notify users of item structure changes completed in the Product Information Management work area.

Note: For more information about configuring human tasks, refer to the chapter, Configuring Human Tasks of the Developing Business Processes with Oracle Business Process Management Studio guide. This guide is intended for process developers who use the Business Process Studio application to create and implement business processes including the configuring of human tasks.