Update 20B

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
20 MAR 2020		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.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business.  Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions:

Access the Opt In page from 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 Go to Opt In for any feature you want to opt in
4. On the Edit Features page, select the Enable option for the feature, and then click Done

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Manufacturing

Upload Manufacturing Work Definition and Work Definition Operation Attachments Using a SOAP Service

Manufacturers who migrate from or integrate with an external application require an efficient way to associate specific attachments with a work definition. For example, work instructions can be captured as an attachment file, text, or URL to provide key additional information for producing an item or performing a specific operation.

Currently, the tools for uploading or downloading work definitions, such as REST services, file-based data import (FBDI), and Application Development Framework Desktop Integration (ADFdi), do not allow you to include attachments when processing work definitions.

With this update, you can use the ERP Object Attachment SOAP service to perform the automatic, mass upload of attachments for discrete and process manufacturing work definitions. You can specify the input parameters for the payload of this service to upload attachments to existing work definitions at the header or operation levels.

By using a service-based approach to upload manufacturing work definition and work definition operation attachments, the initial data load from an external source system or ongoing updates to work definitions can be streamlined into Oracle Manufacturing Cloud.

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

Steps to Enable

To get started, refer to the SOAP service definition provided in the Oracle Financials Cloud SOAP Web Services for Financials guide, available from the Oracle Help Center.

• Chapter: Business Object Services
• Section: ERP Object Attachment Service

Here are the specifics for uptaking the ERP Object Attachment SOAP service for the manufacturing business entities work definition and work definition operation.

REQUEST PAYLOAD 

Here's a table with request payload information.

Element Name	Type	Description
entityName	String	Valid business entity names are: WORK_DEFINITION, WORK_DEFINITON_OPERATION.
categoryName	String	Document Category Name associated with the business entity.
allowDuplicate	String	Whether duplicate is allowed. Valid values are: Yes, No.
attachmentRows		List of elements, each containing the details of the attachment to upload. The details include the user keys, attachment type, and title.

attachmentRows ATTRIBUTES FOR WORK DEFINITION HEADER

Here's a table with attachmentRows Attributes for Work Definition Header information.

Attribute Name	Type	Description
UserKeyA	String	Organization Code.
UserKeyB	String	Item Number.
UserKeyC	String	Work Definition Internal Name.
UserKeyD	String	Keep this key with value #NULL.
UserKeyE	String	Keep this key with value #NULL.
AttachmentType	String	Valid values are: FILE, TEXT, URL.
Title	String	The title of the attachment.
Content	String	The following is an example. Your content may be different. URL: https://www.google.com Text: Use Lathe L123. File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR WORK DEFINITION OPERATION

Here's a table with attachmentRows Attributes for Work Definition Operation information.

Attribute Name	Type	Description
UserKeyA	String	Organization Code.
UserKeyA	String	Item Number.
UserKeyA	String	Work Definition Internal Name.
UserKeyA	String	Version Number.
UserKeyA	String	Operation Sequence Number.
AttachmentType	String	Valid values are: FILE, TEXT, URL.
Title	String	The title of the attachment.
Content	String	The following is an example. Your content may be different. URL: https://www.google.com Text: Use Lathe L123. File: Encode the source data to a Base64 string (Base64 encoding).

Sample Payload for Work Definition Header

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">

<soapenv:Header/>

<soapenv:Body>

<typ:uploadAttachment>

<typ:entityName>WORK_DEFINITION</typ:entityName>

<typ:categoryName>MISC</typ:categoryName>

<typ:allowDuplicate>Yes</typ:allowDuplicate>

<!--Zero or more repetitions:-->

<typ:attachmentRows>

<!--Optional:-->

<erp:UserKeyA>M1</erp:UserKeyA>

<!--Optional:-->

<erp:UserKeyB>AS54888</erp:UserKeyB>

<!--Optional:-->

<erp:UserKeyC>ORA_MAIN</erp:UserKeyC>

<!--Optional:-->

<erp:UserKeyD>?</erp:UserKeyD>

<!--Optional:-->

<erp:UserKeyE>?</erp:UserKeyE>

<!--Optional:-->

<erp:AttachmentType>TEXT</erp:AttachmentType>

<!--Optional:-->

<erp:Title>File1</erp:Title>

<!--Optional:-->

<erp:Content>Use Lathe L123.</erp:Content>

</typ:attachmentRows>

</typ:uploadAttachment>

</soapenv:Body>

</soapenv:Envelope>

Sample Payload for Work Definition Operation

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">

<soapenv:Header/>

<soapenv:Body>

<typ:uploadAttachment>

<typ:entityName>WORK_DEFINITION_OPERATION</typ:entityName>

<typ:categoryName>MISC</typ:categoryName>

<typ:allowDuplicate>Yes</typ:allowDuplicate>

<!--Zero or more repetitions:-->

<typ:attachmentRows>

<!--Optional:-->

<erp:UserKeyA>M1</erp:UserKeyA>

<!--Optional:-->

<erp:UserKeyB>AS54888</erp:UserKeyB>

<!--Optional:-->

<erp:UserKeyC>ORA_MAIN</erp:UserKeyC>

<!--Optional:-->

<erp:UserKeyD>1</erp:UserKeyD>

<!--Optional:-->

<erp:UserKeyE>10</erp:UserKeyE>

<!--Optional:-->

<erp:AttachmentType>TEXT</erp:AttachmentType>

<!--Optional:-->

<erp:Title>Att001</erp:Title>

<!--Optional:-->

<erp:Content>Use Lathe L123.</erp:Content>

</typ:attachmentRows>

</typ:uploadAttachment>

</soapenv:Body>

</soapenv:Envelope>

Tips And Considerations

The content for attachment of type FILE must be provided in the Base64 encoding.

Role Information

• Privilege Name and Code:
  • FSCM Load Interface Administration (ORA_FUN_FSCM_LOAD_INTERFACE_ADMIN_DUTY)
  • Manage Work Definitions (WIS_MANAGE_WORK_DEFINITIONS_PRIV)

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

Enable Audit Trail for Work Order Changes Through Import and Automated Updates

Currently you can enable audit for any data changes made through the UI for a manufacturing work order and its child objects. In this update, you can also capture audit trail for manufacturing work orders and its child objects created and updated through import or other automated processes, including file-based data import (FBDI), Supply Chain Orchestration, Supply Planning, or work order transactions. Any work order updates resulting from operation, material, and resource transactions are also monitored through auditing, because the changes are automated without explicit user intervention or action. Audit trail for work orders includes changes to the following:

• work order attributes, including project and country of origin
• work order operations
• product serial numbers
• operation materials including lot and serial numbers
• operation resources and resource instances
• operation outputs
• attachments at any level

With built-in capabilities to support audit trail for work order creation and updates made through any method, you can ensure compliance with the US Code of Federal Regulations (21 CFR Part 11) for work order audit requirements.

The following screenshot displays the audited attributes that can be configured for auditing Work Order Attachments.

Steps to Enable

To enable this feature, follow the same steps that is done for enabling Audit Trail for Manufacturing Work Orders feature .

1. Click the 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 to navigate to the Configure Business Object attributes page.
5. Select the common work execution product to view the work order object. You have to enable the work order object to enable audit
6. You can select all or any of the child objects for audit. After you select an object for audit the attributes of that object, enabled for audit, are displayed. The key attributes of each object are available by default. Click Add to add more attributes or remove any existing attributes.
7. Click Done.

Tips And Considerations

You can also selectively enable audit trail for attachments for a manufacturing work order and its child objects if you have already enabled audit trail for manufacturing work orders in a prior update.

Key Resources

• Oracle Supply Chain Management Cloud: Using E-Signatures and E-Records Guide available on the Oracle Help Center.

• Oracle Manufacturing Cloud: Enable Audit Trail for Manufacturing Work Orders Guide available on the Oracle Help Center.

Role Information

To use this feature, the following role is required:

• Job Role Name and Code:
  • Internal Auditor (ORA_FND_INTERNAL AUDITOR)

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

• Job Role Name and Code:
  • Application Administrator ORA_FND_APPLICATION_ADMINISTRATOR)

Execute Rework Work Orders with Manual Control

Customer requirements, quality requirements, and sometimes production constraints require rework of finished products.  To perform rework on the finished assembly or product, you need to issue the finished assembly to production and perform the repair or rework. However, certain business processes require returning the assembly back to inventory without performing any repair or rework action.

For example, you have a rework work order for a quantity of 10, and you send all the 10 assemblies to your outside processing supplier for rework.  Because you are using a rework work order, you have to issue these assembly components to the work order. During shipment, one of the assembly is damaged. You now need to either reduce the work order quantity to 9 or return 1 quantity of the assembly that was issued.

Until this update, the assembly  was automatically issued to the work order when the work order was released. You could not intervene in the issue or return of the assemblies. Also, you couldn't update the work order quantity.

With this update, you can not only return the assembly  but you can also update the work order quantity.

There are four aspects to a rework order assembly :

• Manually Issue the Assembly 
• Return Assembly 
• Update Rework Work Order Quantity
• Cancel Rework Work Order

MANUALLY ISSUE THE ASSEMBLY

You have the option to manually issue the assembly  to the work order. Based on a plant level setup, you can either have the assembly  issued automatically at the time of releasing the work order or issue it manually.  You can perform partial issue or the full quantity issue of the assembly component.

When performing the issue, you can also choose the revision of the item that you want to issue.

When you edit the work order, you can also edit the supply subinventory and locator of the assembly.

Manually Issue the Assembly 

RETURN ASSEMBLY

If you performed a manual issue of the assembly , you can now perform return transactions for the assembly.

You can return these assemblies, even if they are an in-house operation or a supplier operation.

If the assemblies are serial controlled,  you can return only the serials that have been issued to the work order.

Any change to the work order quantity will propagate to the outside processing operation as well.

Return the Assembly

UPDATE REWORK WORK ORDER QUANTITY 

If you performed a manual issue of the assembly , you can now change the quantity of a rework work order. You can either reduce or increase the quantity in the released status.

Update Rework Work Order Quantity

CANCEL REWORK WORK ORDER 

If you performed a manual issue of the assembly , you can now cancel a rework work order. Like any other work order, you can cancel a rework work order at any time, even after releasing and performing some transactions.

Cancel Rework Work Order

Watch a Demo

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: Update 20D

The enablement for Execute Rework Work Orders with Manual Control is achieved by enabling Opt-in option. This Opt-in has an expiration revision of 20D. Enable the Opt-in for the feature using Functional Setup Manager, Manufacturing and Supply Chain Materials Management offering and Manufacturing Master data functional area.

Then using Manage Plant Parameters task in Functional Setup Manager, enable the Plant parameter 'Manually issue assembly to rework work order' for the desired manufacturing plant.

Manage Plant Parameter

Tips And Considerations

Before enabling this feature, you should review the rework business process for the manufacturing plant. Once enabled, additional validations are done that may not allow the plant parameter “Manually issue assembly to rework work order" to be disabled. While you enable the plant parameter, it also enables several other capabilities like returning the assembly , cancel the rework work order for the rework process for the organization..

Key Resources

• Watch Execute Rework Work Order with Manual Control Readiness Training

Role Information

The feature can be accessed using Production Supervisor and Production Operator job roles.

Synchronize Resource Details and Work Order Details from Manufacturing to IoT Production Monitoring

The Oracle Internet of Things (IoT) Production Monitoring Cloud can be deployed in manufacturing environments to monitor production flow and equipment health. IoT Production Monitoring detects statistical and pattern anomalies and makes 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.

Until this update, the prebuilt integration between Oracle Manufacturing Cloud and IoT Production Monitoring pulled manufacturing master data and work order details into IoT Production Monitoring at predefined intervals.

With this update, you can synchronize multiple manufacturing entities with IoT Production Monitoring in real time using a push mechanism. You can now decide which specific plants need to be synchronized with IoT Production Monitoring, by enabling the plant parameter Enable synchronization to IoT Production Monitoring. When you create or update production master data, such as resources and resource instances, the data is automatically synchronized in real time with IoT Production Monitoring. Also, when a discrete manufacturing work order or its operations, resources, or resource instances are created or updated, the corresponding work order is synchronized in real time with IoT Production Monitoring.

Work Order Details That Was Synchronized to IoT Production Monitoring

You can view the summary and details of errors encountered during synchronization. You can then resolve them manually by selecting specific records, or automatically by a scheduled process.

Monitor and Resubmit IoT Synchronization Errors

Scheduled Process: Synchronize with IoT Production Monitoring

With real time synchronization of work order data from Manufacturing Cloud to IoT Production Monitoring Cloud, you get accurate and automatic reporting of production quantities and collection of other sensor parameters. This real time integration eliminates integration errors and performance issues otherwise encountered with pulling work order details in batch mode.

Watch a Demo

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: Update 20D

Here are the steps to enable this feature:

1. In the Functional Setup Manager, navigate to Manage Setup Content and then Manage Integration of Additional Applications. Create a new entry with IoT Production Monitoring as the application name. You must set the Security Policy t to oracle/wss_http_token_over_ssl_client_policy. The credentials you provide must be a valid user in IoT Production Monitoring.

Manage Integration of Additional Applications

2. Using the Manage Plant Parameter task in Functional Setup Manager, select the check box for the Enable synchronization to IoT Production Monitoring parameter.

Manage Plant Parameters

To enable an existing manufacturing plant for IoT Integration, you must run the Synchronize with IoT Production Monitoring scheduled process once, by selecting the Initial Data Synchronization mode. Running the program in this mode will prepare your plant for IoT integration by synchronizing existing data, such as active resources, active resource instances, and open work orders to IoT Production Monitoring Cloud.

Tips And Considerations

In update 20B, synchronization of process manufacturing work order is not supported. This is planned for a future update.

Key Resources

• Watch Synchronize Resource Details and Work Order Details from Manufacturing to IoT Production Monitoring Readiness Training

Role Information

Users provisioned with the following job role will automatically be able to use this feature:

• Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

The privileges governing this feature are:

• Review Manufacturing IoT Synchronization Errors (WIP_IOT_REVIEW_ERRORS_PRIV)
• Synchronize Manufacturing Details to IoT (WIP_IOT_SYNC_SUBMIT_PRIV)
• Synchronize Work Orders to IoT (WIP_IOT_WO_SYNC_SUBMIT_PRIV)

Perform Negative Issue Transactions Using Enhanced Capabilities in Rework and Transform Work Orders

Companies sometimes need to rework a finished product or a customer returned product to meet quality requirements. During this process, the operator removes existing material that needs replacement. To remove material, the operator performs a negative issue transaction in a rework or a transform work order and additionally provides serial numbers when the material to be removed is serial controlled.

So far you were able to perform a negative issue of a serial controlled material only if that serial number was previously issued to another work order in the same plant. However, this causes an issue, when the rework or transform process is performed in a different plant than the plant that originally produced the finished goods.

With this update, you can choose a previously issued serial number, provide a new serial number, or complete the negative issue transaction without providing a serial number based on the serial control type of the material.

MATERIALS SERIALIZED AT RECEIPT

Negative Issue for Material Serialized at Receipt

While performing a negative material issue transaction, the serial number will be required and the LOV will continue to show all serial numbers that had previously been issued to any work order in that plant. However, you can scan or enter a new serial number that is not on that list. When the transaction is submitted, genealogy is updated and the material is put into inventory with the serial number provided.

MATERIALS SERIALIZED AT ISSUE 

Negative Issue for Material Serialized at Issue

While performing a negative material issue transaction for materials serialized at issue, you can optionally provide a serial number based on a plant parameter Allow negative issue without serial number. When the transaction is submitted, the material is put into inventory without a serial number.

Watch a Demo

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Watch Perform Negative Issue Transactions Using Enhanced Capabilities in Rework and Transform Work Orders Readiness Training

Role Information

Users who are provisioned with the following job roles will automatically be able to use this feature:

• Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Quality Management

Configure Default Assignee for Quality Issues and Actions

Standardize quality issue and quality action resolution processes by automatically setting the value of a key field to a default process owner in your organization.  You can configure a user as the default assignee for an object type during type setup in the Setup and Maintenance work area. This user is then automatically added as the assignee when you create an object of that object type, using any of the following actions:

• Create Quality Issue or Create Quality Action in the Quality Management work area
• Create actions from the item page in Product Development
• Save As action
• Create Quality Action from a quality issue
• Object creation through REST APIs

New Default Assignee Field in Edit Type Page

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Watch Clipboard and Notification Enhancements Readiness Training

Role Information

To use this feature, the following roles and privileges are required:

• Job Role Name and Code:
  • Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Open Organization Item Details Within Quality Management

Enrich user analysis and decision processes with quicker access to relevant item information. You can now open child organization item details in a dynamic tab within the Quality Management work area. If the item is added as an affected object for the issue or action, you can open the item from the Affected Objects tab.

The following screenshot shows an affected item from a non-default master organization or child organization on the quality issue. You can click on the item hyperlink to open it.

Affected Item Offering a Hyperlink to the Item Screen

The item page opens in a new dynamic tab within the Quality Management work area.

Edit Item Detail Screen Opened in Quality Management Work Area

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

You must have the necessary privileges on the item to open it from the Quality Management work area.

Key Resources

• Watch Clipboard and Notification Enhancements Readiness Training

Role Information

To use this feature, the following roles and privileges are required:

• Job Role Name and Code:
  • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
  • Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

Specify Date Range Filters for Quality Issues and Actions

Fine-tune quality issue and quality action searches with new saved search filters. Use operators such as Before, After, Contains, Starts With, and more for every attribute. You can also search across a particular date range to narrow down your search results.

New Search Filter with Operators

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Watch Clipboard and Notification Enhancements Readiness Training

Role Information

To use this feature, the following roles and privileges are required:

• Job Role Name and Code:
  • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
  • Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

Use Clipboard in Quality Management

Access the clipboard to drag and drop favorites and recent items into the Affected Objects tab or the Relationships tab of quality issues and quality actions.  You can avoid multiple or redundant searches, improve productivity, and enjoy a seamless user experience while you work with quality objects. 

Clipboard entries are shared across the clipboards in other Product Management work areas such as Product Development. Here's a screenshot of the clipboard showing copied items, along with favorites and recent items.

Clipboard Panel in Quality Management Work Area

You'll find new Copy and Paste buttons in the Affected Objects tab to copy items to the clipboard or paste items from the clipboard.

Copy and Paste Buttons on Affected Objects

Watch a Demo

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: Product Management  No Longer Optional From: Update 20D

Key Resources

• Watch Clipboard and Notification Enhancements Readiness Training

Role Information

To use this feature, the following roles and privileges are required:

• Job Role Name and Code:
  • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
  • Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

In addition, users with these roles must have the Monitor Item Work Area privilege.

View Issues or Actions in Approval Status Within Infolets

Use the infolets on the Quality Management landing page to view all your issues and actions, including those that are in Approval status. Infolets such as My Open Issues, My Open Actions, Open Issues by Severity, and My Open Issues by Age, now include issues and actions in Approval status.

 Issues and Actions in Approval Status Now Show Up in Infolets

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Watch Clipboard and Notification Enhancements Readiness Training

Role Information

To use this feature, the following roles and privileges are required:

• Job Role Name and Code:
  • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
  • Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)