June Maintenance Pack for 19B

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
21 JUN 2019		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Feature Summary

Manufacturing

Search for Work Definitions Based on Item Effectivity Using ADFDI

Today a manufacturing engineer can search for work definition operation items based on a specified work definition as of date that corresponds to a work definition version in the Application Development Framework Desktop Integration (ADFdi) spreadsheet. The search results return all of the item structure components and assigned operation items that are effective within the start and end dates of the work definition version.  As a result, it is challenging to distinguish the past, current, and future states of the work definition on a specific date.

With this update, you can search for work definition operation items and further restrict the search results based on the past, current, and future, or current, or current and future date effectivity as of the current date, or a specified work definition as of date. This search filter can expedite the identification of new or updated components that may have been implemented through a change order. You can also display past, current, and future effective components to coordinate their assignment to a work definition operation by looking at their operation sequences and material sequences within an operation.

Searching for work definitions based on the date effectivity of operation items in ADFdi helps you quickly identify the components assigned and unassigned to operations to facilitate change management scenarios, and verify work definition setups for accurate work order creation.

The new Display Effectivity search field is available in the following worksheets: Operation Items - Standard, Operation Items - ATO Model, and Operation Items- Multilevel ATO. The following is a screenshot of the Operation Items- Multilevel ATO worksheet in which a new Display Effectivity search field is available with 3 effectivity options:

Search Field Display Effectivity in ADFdi

NOTE: This feature was also made available in a monthly update of 19A.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

If you don't specify work definition as-of date, the work definition version start date is used to determine what is past, current, and future effective. In this case, since the version start date is used to determine effectivity, you will not get past effective components.

Role Information

• Privilege Name and Code:
  • Manage Work Definitions (WIS_MANAGE_WORK_DEFINITIONS_PRIV)

• Job Role Name and Code:
  • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)

Update 19B

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
22 MAR 2019		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Optional Uptake of New Features (Opt In)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt-in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt-in using the New Features work area:

1. Click the Navigator, and then click New Features (under the My Enterprise heading).
2. On the New Features page, select the offering that includes new features you’d like to review.
3. Click Opt-In for any feature that you want to opt-in to.
4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt-in using the Setup and Maintenance work area:

1. Click the Navigator, and then click Setup and Maintenance.
2. On the Setup page, select your offering, and then click Change Feature Opt-In.
3. On the Opt-In page, click the Edit Features icon.
4. On the Edit Features page, select the Enable option for any feature you want to opt-in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close. 
5. Click Done.

OPT-IN EXPIRATION

Some features include an opt-in expiration update, after which they are no longer optional. If you have not opted in to the feature by the expiration update, it will automatically be enabled for you in that update.

Click here to review details of all Oracle Applications Cloud features with an upcoming opt-in expiration update.

Feature Summary

Manufacturing

Validate Material Issue During Production

Production operators issue materials on the shop floor to complete production activities.  They often scan the item and quantities to issue the materials. Occasionally, mistakes are made, and an operator enters or scans the wrong item or quantity.

Until now, no option was available to validate that the material an operator issues is defined as required push material on the work order. As a result, any operator can issue ad hoc materials, over-issue materials, or issue bulk materials - either on purpose or unintentionally.

With this enhancement, you are now able to control the material issue to ensure error-free updates to production work orders of the following types: standard, nonstandard, rework, and transform. You set this control by selecting one of two values -- Allow or Do not allow -- for a new operation-level setting named Additional Manual Material Issue.  

VALIDATION AT MATERIAL ISSUE

After operation-level control for the material issue is set up, the production operator can issue the push materials only as per the set controls.

If you allow additional manual material issue, the operator can issue push materials more than the required quantity and issue additional materials that are not listed in the work order. Also, the operator can issue materials other than the Push supply type - for example, Bulk.

Additional Manual Material Issue Validation

If the Additional Manual Material Issue is set to Do not allow, the operator can issue only Push materials listed on the work order for a quantity equal to or less than the required quantity. The operator cannot issue above the required quantity, or issue anything other than the materials listed on the work order.

In all cases, the operator can always issue less than the required quantity to ensure that the production can progress whenever materials are short in quantity.

You can use the user interface pages, file-based data import (FBDI), or REST services to perform the transaction and validation.

This option provides poke yoke and error-free material issue and ensures your shop floor operators issue only the required push materials. When you combine this with the Validate Operation Completion During Production feature, you can ensure that all materials are issued exactly as defined on the work order.

Watch a Demo

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

After you opt in, you can set up operation-level control on the following pages:

• Manage Standard Operations (Work Definition work area)
• Manage Work Definition Operations (Work Definition work area)
• Manage Work Order Operations (Work Execution work area)

Additional Manual Material Issue Control Field on the Edit Standard Operation Page

On those pages, you'll see a new operation-level setup: Additional Manual Material Issue.  You can select one of two values: Allow or Do not allow.

Allow additional manual material issue when you want your operators to be able to react to conditions on the shop floor by having the flexibility to issue items that were not defined on the work order, or issue quantities greater than the work order quantity. Do not allow additional manual material issue when you want tight control, and want all changes to be made on the work order and then executed exactly as defined in the work order.

When you set up the control at the standard operations or work definition operations level, it is inherited by the work order operations. When a work order is in Released, Unreleased, Hold, or Complete status, you can edit the control on the work order operation and can set the value on any operations added directly to the work order.

You can perform this setup for an in-house or a supplier operation. Contract Manufacturing work orders do not allow any edits, so values will always default from the work definition.

You can use the user interface pages, file-based data import (FBDI), or REST services to perform this setup.

Key Resources

Watch Validate Material Issue and Operation Completion During Production Readiness Training

Role Information

No additional privileges required. Users who are provisioned with the following job roles will automatically be able to use this feature:

• Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
• Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
• Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Validate Operation Completion During Production

Production processes go through several operations before completing a product and the work order. Required materials can either be manually issued  or backflushed.

After each operation, the backflush materials are automatically issued in the background.

However, there are multiple reasons why manually issued materials may not all be issued at the same time. For example, if the operation has a long duration, and materials are issued continuously throughout the duration. Or, if a material is short and needs to be issued once it becomes available. In both cases, it's easy for the production operator to forget to issue the remaining quantity. Before this enhancement, there was a visual indicator on the dispatch list that indicated that additional material is required, but there was nothing to prevent the operation from completing if all material was not issued. This can cause errors and discrepancies in costing. Tight controls are required to ensure error-free production.

With this enhancement, during every operation completion, the application checks whether all the required Push materials have been issued and whether all exceptions are closed. If not, then the application either provides a warning message or prevents the operation completion. You set this control by selecting one of three values -- Allow, Do not allow, or Allow with warning -- for two new operation-level settings: Completions with Under Issues and Completions with Open Exceptions.

VALIDATION AT OPERATION COMPLETION

After the operation-level controls are set up, the production operator can complete the operations only as per the set controls.

Completions with under issues:

If this control is set to allow, even though the operator had issued push material quantities less than the required quantity, the operator can complete the operation.

If this control is set to allow with warning, if the operator had issued push material quantities less than the required quantity or had not issued some materials, the operator can cancel the transaction and go back and issue the remaining materials, or proceed with the operation completion transaction even though not all push materials were issued.

Under Issues Warning During Operation Completion

If this parameter is set to do not allow, the operator cannot complete the operation without issuing the exact quantity required for the push materials.

Under Issues Error During Operation Completion

There are several nuances of the validation.

Non-Last Operation vs. Last Operation

When the operation is not the last operation, the check for under issue of materials is done only for that operation.

For the last operation, the validation is performed for all the previous operations count point and auto transact operations) and the last operation, to ensure all the materials are issued across the work order.

Nonserial-tracked vs serial-tracked operations

If the operation is not serially tracked, the validation for material quantity is performed at the work order requirement level. The validation for an operation is invoked when all the quantities are completed, for example, if an operation has a quantity of 50 units, during partial completions the validation is not invoked.  However, when the operation completion quantity gets to the total quantity of 50, the validation is invoked.

For serial-tracked operations, whenever a serial is being completed, the validation is invoked to ensure that all material for that serial number has been issued.

Completions with open exceptions:

If this control is set to Allow, even though there are open exceptions assigned to the operation, the operator can complete the operation.

If this control is set to allow with warning, when there are open exceptions assigned to the operation, the operator can cancel the transaction and go back and issue the remaining materials, or proceed with the operation completion transaction even though not all exceptions are closed.

Open Exceptions Warning During Operation Completion

If this control is set to do not allow, the operator cannot complete the operation without closing all the exceptions against the operation.

Open Exceptions Error During Operation Completion

Non-Last Operation vs the Last Operation

When the operation is not the last operation, the check for open exceptions is done only for that operation.

For the last operation, the validation is performed for all the previous operations (count point, as well as auto, transact operations) and the last operation, to ensure there are no open exceptions across the work order.

The exception check is always done at the work order operation level, as exceptions are not logged against a specific assembly serial.

The transactions and validation can be performed using the user interface pages, file-based data import (FBDI), or REST services.

The validation for operation completion feature, along with the validation material issues feature, provides tight shop floor control and ensures poke yoke. Operators will not be able to issue materials outside than that prescribed in the work order, nor miss issuing any push materials. At the same time, you can also ensure that production is not held up in the initial operations due to the shortage of material by having the operation level setup to “warn.”

This prevents human errors, ensures data accuracy and accurate costing of products, and improves operational efficiency.

Watch a Demo

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

After you opt in, you can set up operation-level control on the following pages:

• Manage Standard Operations (Work Definition work area)
• Manage Work Definition Operations (Work Definition work area)
• Manage Work Order Operations (Work Execution work area)

Additional Manual Material Issue Control Field on the Edit Standard Operation Page

On those pages, you'll see a new operation-level setup: Additional Manual Material Issue.  You can select one of two values: Allow or Do not allow.

Allow additional manual material issue when you want your operators to be able to react to conditions on the shop floor by having the flexibility to issue items that were not defined on the work order, or issue quantities greater than the work order quantity. Do not allow additional manual material issue when you want tight control, and want all changes to be made on the work order and then executed exactly as defined in the work order.

When you set up the control at the standard operations or work definition operations level, it is inherited by the work order operations. When a work order is in Released, Unreleased, Hold, or Complete status, you can edit the control on the work order operation and can set the value on any operations added directly to the work order.

You can perform this setup for an in-house or a supplier operation. Contract Manufacturing work orders do not allow any edits, so values will always default from the work definition.

You can use the user interface pages, file-based data import (FBDI), or REST services to perform this setup.

Key Resources

Watch Validate Material Issue and Operation Completion During Production Readiness Training

Role Information

No additional privileges are required. Users wo are provisioned with the following job roles will automatically be able to use this feature:

• Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
• Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
• Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Synchronize Item Structure Quantities to Work Definitions Using a Scheduled Process

As part of the scheduled process for item structure changes to discrete manufacturing work definitions, you review the worklist notification to decide what changes to make in the impacted work definitions. In the case of assemble-to-order (ATO) model items, the scheduled process automates any component quantity changes from the primary item structure to its work definition. However, this synchronization does not apply to standard items, where the updates to the work definitions are implemented manually. As a result, you can create or update the work definition version, edit the existing operation item assignment, create a new operation for item assignment, or choose to leave the work definition as is.

In this update, you can automatically synchronize the changes to a component quantity in the item structure of a standard item with the discrete manufacturing work definitions that reference the item structure. When the scheduled process for “Process Item Structure Changes to Work Definitions” is successfully completed, any updates to the structure component quantities are automatically applied to the work definition operations where the components are already assigned and do not generate a worklist notification.

If a structure component quantity has been split across multiple operations, the worklist notification is sent, so that you can decide how to reflect the change in the impacted work definitions.

As observed in the existing behavior, new structure components added to an item structure are not automatically assigned to a work definition operation by default. You must update the work definition directly by assigning new structure components to the appropriate operation.

In a manufacturing plant that is enabled for electronic record and electronic signature, the synchronization process does not apply, as tracking any change in the operation item quantity would require that a new work definition version and operation are created. This new version can be submitted for approval to control changes to the work definition.

With this feature, the change management process from the product structures to the manufacturing process becomes even more streamlined.

Watch a Demo

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

Tips And Considerations

It is a best practice to schedule the Enterprise Scheduler Service job, Process Item Structure Changes to Work Definitions, on a regular, periodic schedule, as per the business needs.

Key Resources

Watch Synchronize Item Structure Quantities to Work Definitions Using a Scheduled Process Readiness Training

Role Information

• Privilege Name and Code: Existing privileges, as applicable, to the Process Item Structure Changes to Work Definitions scheduled process and the Worklist Notifications:

  • Receive Item Structure Change Worklist Notifications for Work Definitions (WIS_RECEIVE_ITEM_STRUCTURE_CHANGE_NOTIFICATIONS)

  • Process Item Structure Changes to Work Definitions (WIS_PROCESS_ITEM_STRUCTURE_CHANGES_TO_WORK_DEFINITIONS)

• Job Role Name and Code:
  • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)

Update Product Genealogy Without Waiting for a Scheduled Process to Run

Prior to this update, when you transacted lot and serial controlled input or output items with Enable Genealogy Tracking set to Yes, the application immediately ran the scheduled process named Manufacturing Transactions to Genealogy Interface. The genealogy was built after the scheduled process was completed.

When users performed large volume of transactions, the application automatically ran many Manufacturing Transactions to Genealogy Interface scheduled processes to build genealogy automatically. This reduced the performance of the overall application.

Based on customer feedback to improve the performance of the application, a new profile option Genealogy Build Deferred During Execution (Code: ORA_WIE_DEFER_GENEALOGY_BUILD) in Common Work Execution Controls profile category has been introduced.

Genealogy Build Deferred During Execution profile

To update the profile value, after you log in, select Set up and Maintenance. Search for the task Manage Administrator Profile Values and query for the profile.

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.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

If you set the profile value to Yes, it is a best practice to schedule the Retry in-Error Genealogy Transactions scheduled process on a regular, periodic schedule as per the business needs when transaction load on application is low.

Role Information

No new privilege is required.

Monitor Manufacturing Work Orders and Resource Instances with IoT-Enabled Equipment

Today, the Internet of Things (IoT) Production Monitoring Cloud can be deployed in manufacturing environments to monitor production flow and equipment health. IoT Production Monitoring Cloud detects statistical and pattern anomalies and predictions based on equipment sensor attributes, configurable Key Performance Indicators (KPIs) and a rules engine, and built-in Artificial Intelligence (AI) and Machine Learning (ML) models and algorithms. However, the Manufacturing master and production data needs to be mapped through a customer-built integration, or entered directly in IoT. And the production supervisor is required to sign in separately into both applications.

With the pre-built integration and single sign-on between Manufacturing Cloud and IoT Production Monitoring Cloud, you can extend operational visibility into real-time production monitoring and actionable insights by sharing connected equipment resource instances and synchronizing manufacturing work orders. Manufacturing work orders in the released status are automatically synchronized with IoT Production Monitoring Cloud, including information about its plant, products, work centers, equipment resources and their instances.

You can drill down from a specific work order or equipment resource instance in Manufacturing Cloud to view a KPI dashboard and digital twin simulation of the real-time and predicted status of a work order or equipment in IoT Production Monitoring Cloud. Quick access from Manufacturing Cloud to IoT Production Monitoring Cloud insights is provided in multiple pages:

• Manage Work Orders page
• Edit Work Order page, in the History tab
• Edit Resource Instance page 

As a result of anomaly detections and predictive analytics in IoT Production Monitoring Cloud, you can decide what actions to take in Manufacturing Cloud or IoT Production Monitoring Cloud.

Using the IoT Insights button provided in the Manage Work Orders page, drill down to the work order view in IoT Production Monitoring Cloud to view work order details, factory level metrics, and machine level details.

Drill down from Manufacturing Cloud Work Order to IoT Production Monitoring

Work Order View in IoT Production Monitoring

Using the IoT Insights button provided in Resource Instances page, 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.

Drill Down from Equipment Resource Instance to IoT Production Monitoring

Machine Summary View in IoT Production Monitoring

Watch a Demo

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

1. In Fusion Applications Cloud, use Functional Setup Manager to define the base URL of IoT application. This data is used to drill down from Manufacturing Cloud to IoT Production Monitoring cloud.

Create Third-Party Application

2. In IoT Production Monitoring cloud, In Configuration -> Settings, set up the Manufacturing cloud end point URL and other details required to synchronize data from Manufacturing cloud to IoT cloud.

Integration Configuration Setting in IoT Production Monitoring Cloud

Tips And Considerations

In the current update, IoT integration supports drill down only for Discrete Manufacturing work orders and the equipment resource instances referenced in those work orders. Support for process manufacturing work orders is planned for a future update.

Key Resources

You can find additional information on IoT Production Monitoring Cloud at: https://cloud.oracle.com/en_US/iot-production-monitoring-cloud.

Watch Monitor Manufacturing Work Orders and Resource Instances with IoT-Enabled Equipment Readiness Training

Role Information

IoT Insights can be accessed from the following job roles:

• Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
• Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
• Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

Process Manufacturing

Process manufacturing represents a segment of manufacturers in industries, such as consumer packaged goods, in which the finished product cannot be broken down into its ingredients, and the production method requires ways to manage variability that is inherent in materials and processes. In this update, the enhanced capabilities to support batch production with multiple co-products and by-products provide the foundation for mixed-mode manufacturing in the same plant.  These capabilities can help manufacturers – who use standard recipes for producing various batch sizes and products in single or dual units of measure (UOMs) with a fixed conversion – to make the right product at the right time.

Define and Execute Batch Production for Process Manufacturing

Producing bulk, intermediate material that is packaged into finished goods typically requires a hybrid of process and discrete manufacturing capabilities. In particular, batch production moves manufacturing in batch quantities through each stage of the production process instead of moving individual discrete units.  This manufacturing difference presents the following unique requirements that extend beyond the light assembly production that is supported currently:

• You need to define the relationship of inputs and outputs to make a batch instead of defining a hierarchical item structure.

• You need to manage co-products, that are planned, multiple output products resulting from a process, and by-products, that are additional unplanned outputs from a process.

• You need to define and execute recipes on the basis of batch size instead of the number of discrete items.

• You need to define the input size of a batch process, such as packaging production, using the variable output from the previous batch process, such as bulk production, or by scaling a work order to a target batch quantity.

With this update, process manufacturing can operate in the same plant as discrete manufacturing, as determined by the work method for products being produced. This capability enables you to model, track, and cost for materials and processes using the appropriate manufacturing method for each stage of production. As with discrete manufacturing, process manufacturing supports similar capabilities for in-house manufacturing and outside processing of standard products with the option to enable electronic records and electronic signatures for critical business events. You can design your production process with work definitions, manage production with a material availability check and work order picking, execute production with quality inspection and production exceptions, and perform cost rollup and cost accounting. 

The process manufacturing capabilities in Manufacturing Cloud are described as follows:

• Design the production process for process manufacturing
• Manage production for process manufacturing
• Execute production for process manufacturing

DESIGN THE PRODUCTION PROCESS FOR PROCESS MANUFACTURING

• Define a work definition for a process with co-products and by-products. You can create a work definition as a recipe for a unique, named process in a plant in addition to a primary product through the user interface, file-based data import spreadsheets, and REST service. The process can complete multiple co-products and by-products at any in-house or supplier operation.

• Manage work definitions and work orders in batch quantities. Define multiple work definitions in various batch sizes, where the input and output quantities in a work definition and work order are expressed in terms of a batch quantity for the purposes of batch sizing and scaling. The batch quantity moves through operations until work order completion, while process yield loss can be captured as operation scrap.

Create Process Work Definition

Edit Operation Output

MANAGE PRODUCTION FOR PROCESS MANUFACTURING

• Create work orders based on a process or product. You can manually create standard work orders based on a specified process and batch quantity or a product and its quantity through the user interface, file-based data import spreadsheets, and REST service. The application automatically selects the work definition for the primary product with the lowest production priority, which you can override to select another work definition.

• Scale work orders before production. Recalculate work order quantities proportionally based on a critical input, output, or batch quantity prior to work order release through the user interface. Inputs can be scaled as either fixed or variable quantities, whereas outputs can be scaled as variable quantities.

• Analyze co-products and by-products. You can create your own metrics and analyses, such as yield and variance analysis based on the subject areas in Oracle Transactional Business Intelligence for Manufacturing Cloud, which include co-product and by-product transactions.

Create Batch Work Order Based on Process Name or Primary Output

Batch Work Order with Multiple Outputs

Batch Work Order Scaling

EXECUTE PRODUCTION FOR PROCESS MANUFACTURING

• Report co-products and by-products for work orders. You can complete multiple co-products and by-products with lot information into an inventory or expense location through the user interface, file-based data import spreadsheets, and REST service. Product completion can be reported independent of or with operation completion. Unplanned co-products and by-products can also be added directly to a work order or while reporting an output completion transaction.

• Inspect work order co-products and by-products. From the dispatch list, you can create an ad hoc inspection to record quality results against samples of work in process or a primary product, co-product, or by-product in the context of a work order operation through the user interface and REST services.

• Trace end-to-end lot genealogy of co-products and by-products. Visualize and analyze the parent-child relationships between input and output items under lot control, whether generated from in-house receiving, production, and shipping transactions, or imported through a spreadsheet from a supplier.

Report Multiple Output Completion

Inspection of the Output Item

Output Item Lot Genealogy Details

With all these capabilities built in, you can run both process manufacturing and discrete manufacturing in the same plant, which is driven by the manufacturing work definitions and work orders to make products.  This flexibility allows you to determine the best manufacturing method for each stage of production, enabling a more flexible, quicker implementation of mixed-mode manufacturing with the cloud benefits of a configurable and extensible platform and automated upgrades.With all these capabilities built in, you can run both process manufacturing and discrete manufacturing in the same plant, which is driven by the manufacturing work definitions and work orders to make products.  This flexibility allows you to determine the best manufacturing method for each stage of production, enabling a more flexible, quicker implementation of mixed-mode manufacturing with the cloud benefits of a configurable and extensible platform and automated upgrades.

Watch a Demo

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

• Enable Process Manufacturing in Manage Plant Parameters
  • After enabling process manufacturing for the plant, specify the default work method for the manufacturing organization, Discrete Manufacturing / Process Manufacturing in the plant parameter.

Plant Parameter to Enable Process Manufacturing and Set Up Default Work Method

Tips And Considerations

• The Default Work Method controls the default behavior of the user interface, every time the user logs in to create a work definition and work order.

  • Default Work Method is plant specific. If a plant typically runs batch production, set the Default Work Method to Process Manufacturing.

• Use the process manufacturing work method specific File-Based Data Import (FDBI) templates for mass creation of Work Definition, Work Order, Operation Transaction and Material Transactions. For resource transactions, the FBDI template is common for Discrete and Process manufacturing work methods. 

Key Resources

Watch the following Readiness Training:

• Define and Execute Batch Production for Process Manufacturing – Setup and Work Definitions
• Define and Execute Batch Production for Process Manufacturing – Manage and Execute Production 

Role Information

• Privilege Name and Code: No additional privileges required.   
• Users provisioned with the following job roles will automatically be able to use this feature:
  • Job Role Name and Code:
    • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
    • Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
    • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

Perform Cost Rollup for Process Manufacturing Work Definitions

You can now use standard cost rollup for process manufacturing work definitions with multiple outputs. This is also useful if you require a hybrid of discrete and process manufacturing capabilities within the same inventory organization.

When setting up work definitions, you can specify the output item yielded from different operations, and the percentage of costs to be allocated towards those output items. You can also enter the standard cost of an output item as a fixed cost for specific business requirements. The Costing Batch Output Size parameter allows you to plan your costs accurately by reflecting your typical production batch size.

The Rollup Costs process will calculate the cost of output items with active work definitions, based on the cost allocation defined in the work definition operations.

You can use the View Rolled-up Costs page to understand the cost calculations for each output item.

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

Feature Name: Define and Execute Batch Production for Process Manufacturing

Key Resources

• Using Supply Chain Cost Management guide, available on the Oracle Help Center.

Role Information

• Job Role Name and Code:
  • Cost Accountant (ORA_CST_COST_ACCOUNTANT)

Cost Account Process Manufacturing Work Orders

You can use Cost Accounting to calculate the costs for process manufacturing work orders, and to create the accounting entries. The Review Work Order Costs page now displays the input costs of material and resource transactions for process manufacturing work orders.

The following screen capture illustrates the feature and its benefits.

Review Work Order Costs

The product costs are calculated based on the cost allocation factors defined in the work definition for Primary Product, Co-Products, and By-Products.

All product completions processed before a work order is closed use an estimated cost based on the Provisional Completion option chosen in the item cost profile. Once a work order is closed, and based on the cost allocation factors, the actual costs incurred on the work order are used to calculate the actual product costs. The formula used for products that have a percentage based cost allocation factor is as follows:

(Total costs accumulated through this operation – Scrap Reported in this operation)*Cost Allocation Factor) / Quantity Produced

If the cost allocation factor is set to Fixed, then the standard cost of the item is used to cost the provisional completions. You must create a standard cost for the output item when you set the cost allocation factor to Fixed.

The costs accumulated through the operation where the scrap is reported are used to value the scrap, based on the following formula:

Scrap costs = (Total costs accumulated through this operation)*(Scrap Quantity/Batch Quantity)

The following screen capture illustrates the feature and its benefits.

Product Costs and Cost Allocation Factors

A new variance type called Yield Variance has been introduced to support process manufacturing work orders. Yield variance is calculated as the output correlated to the batch quantity instead of the quantities of inputs directly. The formula for calculating the yield variance is as follows:

Yield Variance = (Actual reported quantity - Planned scaled quantity) * Standard cost of product

The following screen capture illustrates the feature and its benefits.

Variance Details

Watch a Demo

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

Feature Name: Define and Execute Batch Production for Process Manufacturing

Tips And Considerations

If the cost allocation factor is set to Fixed, set up a standard cost for the item.

Key Resources

Watch Support Process Manufacturing in Cost Accounting Readiness Training

For more information about this feature, see the Oracle SCM Cloud: Using Supply Chain Cost Management guide available on the Oracle Help Center.

Role Information

• Privilege Name and Code: Create Cost Distributions (CST_CREATE_COST_DISTRIBUTIONS)
• Job Role Name and Code: Cost Accountant(ORA_CST_COST_ACCOUNTANT)

Supply Chain Management Common Components

Extend End Dates on Existing Schedules

Enables you to extend an existing schedule by providing a new end date further in the future. Your existing schedule detail data for working and non-working time is kept, and the additional information representing the change of date is appended to this set of data.

Steps to Enable

Use the Opt-In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

Use Side Tabs on Manage Plant Parameters User Interface

Side tabs are available to reorganize the plant parameter fields. This layout better supports future product growth, and also reduces the crowding of attributes on the page.

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.10.0

Quality Management

Configure Object Number for Quality Issues and Quality Actions

Configure how the object number is generated for each type of quality issue or action. You can enable a user to type in a number manually or autogenerate the next number in the sequence.

When you set up quality issue and action types, you can choose one of the following options for number generation:

• Inherited from Parent: Inherits the number generation method from the parent object
• User-defined: Lets the user type in a number at the time of object creation
• Sequence-generated: Autogenerates a number based on a specified sequence and increment

Configure Number Generation Method During Object Type Setup

Number Generation During Object Creation

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

The number generation schemas and the next number to be used per type will remain the same after updating to 19B. It is still recommended to note down the next number in the sequence for each quality issue and action type, and double-check this after the system update.

NOTE: Avoid setting the number generation method for exceptions and nonconformances to user-defined or inherited from parent. These settings may be used only for legacy data import. In general, it is recommended to always set the number generation method to sequence-generated.

Key Resources

Watch More Flexibility and Configurability Quality Issue and Action Management Readiness Training

Role Information

To set up this feature, the following privilege or role is required:

• Job Role Name and Code: 
  • Supply Chain Administrator (ORA_MSC_SUPPLY_CHAIN_ADMIN)

Create Quality Issues and Quality Actions Through Groovy Scripting

Quality Management consists of a series of steps designed to improve problem assessment and process standardization. Use Application Composer to standardize and progress quality processes.

You can execute groovy scripting from the Actions menu and automatically create new quality issue or action objects from any other object enabled by Application Composer.  You can also enhance efficiency and data consistency because the Name and Type values from the existing object are carried over to the newly created object.

Steps to Enable

No steps are required to enable this feature.

Key Resources

Watch More Flexibility and Configurability Quality Issue and Action Management Readiness Training

Delete a Quality Issue or Quality Action in Draft Status

Under certain conditions, you may need to delete quality issues and quality actions (with the exception of manufacturing production exceptions and inspection nonconformances) while they are in Draft status.

When you click the Delete action in the Actions menu, a warning message prompts you to confirm the deletion. Along with the quality issue and quality action, all affected and related objects and attachments are deleted.

Use this feature to delete quality issues and quality actions that may have been created by accident or are redundant duplicates.  Your quality administrator can also remove issues and actions that are no longer valid.

New Delete Action in Actions Menu

Warning Prevents Accidental Deletion

Steps to Enable

No steps are required to enable this feature.

Send Notification for Quality Issues and Quality Actions to Improve Collaboration

Quality Management requires real-time collaboration across cross-functional users.  Use the Send Notification action for quality issues and quality actions to send an FYI notification with a personalized message to stakeholders. Stakeholders can view the notifications from the notification bell icon.

You can use this feature to share an issue or action with additional users without leaving the application. Your users can be sent an FYI, or a specific request to assist in resolving issues or actions.

The following screenshots show this feature:

Send Notification from Actions Menu

Add Personalized Message to Stakeholders

Watch a Demo

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

When you send a notification, ensure that the recipient has the appropriate privileges to view the issue or action. 

Key Resources

Watch More Flexibility and Configurability Quality Issue and Action Management Readiness Training

Use Application Composer Attributes to Define Quality Issues and Actions

Data collection is a key input and output of the Quality Management process. Extend the definition of Quality Issues or Quality Actions with extensible attributes in Application Composer to capture relevant data such as findings, test results or operational data to improve downstream activity and continuous improvement.

With this update, you can use an increased number of attributes:

• Date, or date and time attributes: 50
• Text, check box, and fixed or dynamic choice list attributes: 350
• Number, currency, and percentage attributes: 200

Additional Extensible Attributes in Application Composer

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

Oracle Transactional Business Intelligence (OTBI) coverage for these new attributes will be available in 19C.

Key Resources

Watch More Flexibility and Configurability Quality Issue and Action Management Readiness Training

Use Advanced Search to Add Users in Quality Issue or Quality Action Workflows

Depending on the implementation, user names can be cryptic, challenging the ability to quickly assign workflow approvers to quality issues and quality actions. The Advanced Search feature enables more options to find and assign approvers. 

Apart from standard search operators such as Starts With, Ends With, Equals, Contains, and so on, you can use additional fields such as Email Address or Name, to pick approvers. When the exact system user name is not known, the advanced search makes it easier to find and invite the required users to approve a quality issue or quality action.   

Additional Fields in Advanced Search

Steps to Enable

No steps are required to enable this feature.

Key Resources

Watch More Flexibility and Configurability Quality Issue and Action Management Readiness Training