Document History

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

Date	Update Version	Notes
21 SEP 2018	Update 18C	Delivered new features in update 18C.
20 APR 2018	Update 18B	Delivered new features in update 18B.
19 JAN 2018	Update 18A	Delivered new features in update 18A.

Update 18C

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 SEP 2018		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)

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 Go to 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.

Feature Summary

Manufacturing

Integrate with External Label Printing Systems Using Business Events

Oracle Manufacturing Cloud provides web services and business events to enable integration with external systems, such as manufacturing execution systems, shop floor devices, mobile devices, and third-party label printing applications.

Specific business and industry requirements drive customers to use specialized label printing applications which cater to specific label printing needs such as compliance labeling. Your organization may need to print labels of various sizes, layout, and content for different items. Also, there can be a need to provide specific data formats for specialized printing equipment, or to choose specific printers.

Up until this update, you were able to print a label from the Manage Work Orders page in the Work Execution work area, from the Review Dispatch List page, or during operation completion, either in a pdf format, or integrate with third-party label printing solutions at the start of the production.

With this update, you are now able to print product labels when products are completed into inventory.

External label printing applications can subscribe to the event in Integration Cloud Service(ICS). In addition to the data published, you can retrieve the additional data requirements for label printing using the Inventory Transaction REST service as well as the Work Order REST service. You can then pass on the information to the label printing application where the layout would be determined, and then sent to a printer. 

Steps to Enable

To enable this feature, follow these steps:

1. In the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials Management offering.
2. On the Setup: Manufacturing and Supply Chain Materials Management page, select the Manufacturing Master Data functional area.
3. Select the task Manage Plant Parameters.
4. For the manufacturing organization that you want to enable this feature for, select the check box Print product labels using external applications.

Tips And Considerations

Oracle Manufacturing Cloud provides standard functionality to print product labels in PDF format. Business events and REST services are provided to enable integration with external label printing applications. You must evaluate which option will work best based on the business requirements for label printing.

Role Information

• Job Role Name and Code:
  • Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Enable Deferred Electronic Records and Electronic Signatures for Production Exceptions

Companies in regulated industries must keep detailed records of their product manufacturing processes in accordance with the United States Food and Drug Administration (FDA) regulation on electronic records and signatures, called the 21 Code of Federal Regulations Part 11. Oracle E-Signatures and E-Records is a configurable framework for securely capturing, storing, retrieving, and printing electronic records and signatures.

With this update, you can close a manufacturing exception through the user interface, a REST service, or the mobile application. When an exception is closed, an electronic record is created and it supports the deferred capture of an electronic signature.

A new transaction Production Exception Closure is introduced to enable or disable electronic signatures for exceptions. If electronic records and electronic signatures are enabled, the exception status reflects the current status in the approval process which works in conjunction with the approval workflow.

When you are ready to close a production exception, you will submit the exception for approval rather than directly closing it. This sends notifications to the approvers to review the electronic record and capture the electronic signatures. The exception is held in a pending approval status until all approvals are complete.

The following screenshot shows the approval page for a production exception closure:

Production Exception Closure- Approval Page

The electronic records created for the production exceptions are stored in a secured document repository and cannot be modified or deleted. You can search the electronic records based on any of the transactional information displayed in the electronic record to retrieve and print an electronic record.

The following screenshot shows an electronic record for a production exception closure:

Electronic Record for Production Exceptions

Steps to Enable

The following are the prerequisites for using this feature:

• Enable the Capture Electronic Records and Electronic Signatures for Supply Chain Management Transactions feature in the Facilities functional area in the Manufacturing Supply Chain and Material Management Offering.
• Determine and configure electronic signatures for each inventory organization using the Configure E-Signature Preferences task in the Setup and Maintenance work area to enable e-records and capture electronic signatures for manufacturing.
• Define configurable business process rules in Oracle Business Process Management using the Manage Task Configurations for Supply Chain Management task, and the Manage Approval Groups task in the Setup and Maintenance work area to determine the approvers for each transaction.

Role Information

To use this feature, the following role is required:

• Privilege Name and Code:
  • Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV)
• Job Role Name and Code:
  • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

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

• Privilege Name and Code:
  • Determine Transactions Requiring Electronic Signature (EDR_DETERMINE_ESIGNATURES_TRANSACTIONS_PRIV)
• Job Role Name and Code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Import Work Definitions Through File-Based Data Import

With this update, you can import a high volume of manufacturing work definitions using file-based data import (FBDI) to facilitate the implementation of Oracle Manufacturing Cloud, and manage change management scenarios. The work definition import process allows you to load a high volume of new and updated work definitions for both standard items and assemble-to-order model items. For standard items, you can import standard, rework, and transform work definition types, and for assemble-to-order model items, you can import standard work definition type; you cannot create rework and transform work definition types for assemble-to-order model items.

The following attributes and their details can be imported Using the Work definition import template and a scheduled process:

• work definitions
• operations
• operation items for standard items
• operation items for assemble-to-order model items
• operation resources
• operation alternate resources

For assemble-to-order model work definitions, you can import the operation items, where the item can be from any level in the exploded assemble-to-order model item structure. To uniquely identify the operation item, you must specify the component start date and component hierarchy, which represents the hierarchical relationship of the component to the top-level assemble-to-order model.

NOTE: The definition of operation applicability rules based on selected options and transactional item attributes for assemble-to-order model work definitions is supported only through the user interface.

As FBDI supports a one-way import into the cloud, you must enter the work definitions in the spreadsheet template before initiating the import process. For mass update scenarios, you can query the work definitions through ADFdi, or print the work definition report, and then copy and modify the data in the work definition FBDI template for import. You can view the successfully imported work definitions in the Work Definition page. If import errors occur, you can purge unsuccessful records in the interface tables, correct the data in the work definition FBDI template, and repeat the import process.

The following diagram illustrates the task flow involved in the import work definitions process:

Work Definition File-Based Data Import Process

Leveraging this file-based data import capability enables faster implementation and allows change management of work definitions for manufacturing in a high volume.

The following is a screenshot of the Work Definition FBDI template where you enter the work definition header details:

Work Definition FBDI Template

The following is a screenshot of the Import Work Definitions scheduled process. Batches that are successfully loaded are available for your selection:

Import Work Definitions Scheduled Process

Steps to Enable

Download and review the latest Work Definitions import template in the File-Based Data Import for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center. To import data using the template, follow the instructions in the Loading Data into Tables: Explained topic.

Tips And Considerations

The component hierarchy is a required attribute in the operation items for assemble-to-order model worksheet (WIS_WD_DETAILS_INT-ATO CMP) in the work definition FBDI template.

To obtain the component hierarchy, you can perform the following:

1. Using file-based data import, create the ATO model work definition headers.
2. Using the Operation Items- Multilevel ATO worksheet in ADFdi, download the multilevel item structure, one ATO model at a time. Note that the download limit is 2000 rows.
3. Copy the component hierarchy of the operation items that you want to import from ADFdi to FBDI, excluding the component itself.
4. In FBDI, select Find and Replace to replace the delimiter before importing. In ADFdi, the delimiter used is a '.', and in FBDI, the delimiter used is a '>'. There should be no space before the delimiter '>', and there should be a space after the delimiter '>'.

In the following example, the component OP41 is under OC4. OC4 is under OC1, and OC1 is under ATO10. The component hierarchy is as follows:

• In ADFdi: ATO10.OC1.OC4.OP41
• In FBDI: ATO10> OC1> OC4

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)

Enable Audit Trail for Work Orders

Enable audit trail for manufacturing work orders and its child objects to comply with US Code of Federal Regulations (CFR 21 Part 11) for electronic record and electronic signature requirements. You can enable  audit trail for any attribute in a work order, work order operation, operation material, operation resource, resource instance, operation material lot and serial numbers, and work order serial numbers.

After audit trail is enabled, any changes to the work order are automatically tracked in the audit tables. The creation or updates done through the manage work orders page or edit work orders page in the work execution work area or through the Work Order REST services are tracked in the audit tables. You can search and retrieve the audit history in the Audit Reports work area.

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

The following screenshot shows the audit report for changes done to a work order.

You search and retrieve the changes to the work order objects in the audit reports page in the audit reports work area. Here, you can search by a date range and optionally you can filter your search results by user. You can also restrict your search for a specific even type like create, update or delete. To search for work order changes, you have to select the Common Work Execution product and work order business object type. You can use the description to search for a specific work order or a child object of a work order. You can see the different options to search for work order change records in the demo section of this training. You can also export the search results for detailed analysis.

The following screenshots shows the search attributes for Audit Report.

Any updates done through file based data import (FBDI) are not audit tracked in this update.

Steps to Enable

To enable this feature, do the following: 

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.

Key Resources

• Oracle SCM Cloud: Using E-Signatures and E-Records 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)

Calculate and Roll Up Cumulative Manufacturing and Cumulative Total Lead Times

With new product introductions and upgrades, changes in production efficiencies, or supplier changes, the cumulative lead times of manufactured items require timely updates to ensure accurate and realistic order promising. With this feature, the cumulative manufacturing and cumulative total lead times for a range of items or for item categories can be automatically calculated when you run a scheduled process. The cumulative lead times represent the rolled up lead times from the underlying make and buy items in a multilevel item structure.

As part of the cumulative lead time calculation, the following are calculated:

• Cumulative manufacturing lead time
• Cumulative total lead time

The cumulative manufacturing lead time represents the total time required to make an item if you had all raw materials in stock, but had to make all subassemblies level by level. This is calculated by rolling up the single-level manufacturing lead time of each make item from the lowest level to the highest level.

The cumulative total lead time represents the total time required to make an item if no inventory existed, and you had to order all the raw materials and make all subassemblies level by level. For a buy item, it is calculated by adding the preprocessing, processing, and postprocessing lead times. For a make item, it is calculated by rolling up the total lead times of make and buy items from the lowest level to the highest level.

The existing scheduled process for calculating lead times has been enhanced in this update. You can choose to run the program in different scopes which are as follows:

• Calculate Manufacturing Lead Times
• Calculate Cumulative Lead times
• Calculate Manufacturing and Cumulative Lead Times

The calculated values of the lead times are displayed as part of the output file of the scheduled process. The calculated values are automatically updated in the item definition after the calculation.

With this update, the cumulative manufacturing lead times and the cumulative total lead times are factored into the available-to-promise rules for more accurate sales order promising.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

Consider the following:

• Cumulative lead time calculations do not apply to assemble-to-order model items and configured items.
• Cumulative lead time calculations are automatically updated in the item definition if it is a definition organization, and not a reference organization.

Role Information

• Privilege Name and Code:
  • Calculate Manufacturing Lead Times (WIS_CALCULATE_MANUFACTURING_LEAD_TIMES_PRIV)
• Job Role Name and Code:
  • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)

Correct Work Orders and Transactions for Import

With Oracle Manufacturing Cloud, you can create work orders and complete work order transactions in several ways.

You can create work orders and complete work order transactions using the user interface, REST services, or the file-based data import process.

Prior to this update, for the import transactions that were created through file-based data import and resulted in errors, you could only purge them using a scheduled process. You then had to recreate the transactions using the file-based data import template.

With this update, you can now correct these transactions from the user interface as well. The following transactions can be corrected:

•  Work order import
•  Work order operation transaction import
•  Work order material transaction import
•  Work order resource transaction import

NOTE: You can only correct the transactions that were created through the file-based data import process through the Correct Work Orders and Transactions for Import task . If the transactions were performed through the user interface or through REST services, you cannot correct them from this task.

Choose the task Correct Work Orders and Transactions for Import in the Work Execution work area to correct the transactions that have returned errors or to complete the records that are incomplete.

On the Correct Work Orders and Transactions for Import page, you can use a combination of filters to narrow your search. You can filter for a specific type of transaction, such as work orders, materials, operations, or resources. The default filter criteria is set to work orders import. You can also filter on additional criteria such as the import batch code, import batch status, or even a specific import batch ID.

You can then choose a specific row and choose the action Manage in Spreadsheet. Based on the type of transaction you chose, an ADFdi spreadsheet opens. There are four different ADFdi spreadsheet templates, each for a particular type of transaction.

The following screenshot displays the Correct Work Orders and Transactions for Import page.

Correct Work Orders and Transactions for Import Task

The ADFdi spreadsheet will prompt you to provide your login credentials before you can start working on it. The spreadsheet displays all the errors related to the row you selected on the user interface for you to make the corrections. After you make the corrections, you can change the status of the row to Ready. You can then submit the ADFdi spreadsheet by clicking Upload to correct the transactions that returned errors.

The following screenshot shows the ADFdi spreadsheet template for the Correct Work Orders Import transaction:

Correct Work Orders for Import ADFdi Spreadsheet

The ADFdi spreadsheet correction provides you the flexibility to make corrections for your transactions quickly from a single user interface.

Steps to Enable

No steps are required to enable this feature.

Role Information

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

• Privilege Name and Code:
  • Import Work Orders (WIP_IMPORT_WORK_ORDERS_PRIV)
• Job Role Name and Code:
  • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

Users provisioned with the Production Supervisor role will automatically be able to correct work orders and transactions for import.

Use Resource Instances in Manufacturing and Maintenance

Production resources, such as equipment and labor, are an integral part of manufacturing activities. They can be used to track actual time spent for production against standards, and enables accurate product costing.

A resource instance is a granular representation of a production resource that identifies the specific equipment or person working on production or maintenance activities. For example, in a machining work center there may be three lathes that are identical in model, production capacity, machine specifications, and usage cost. Each of these lathes is a resource instance and can be uniquely identified using the equipment serial number. Similarly, you may have a labor resource called lathe operator. There may be several people in the workforce that have the same skills and labor rates to be a lathe operator and are uniquely identified as individuals by name as resource instances.

In addition to having better visibility and utilization of labor and equipment resource instances, you can also report resource usages against specific resource instances so that you can analyze resource utilization and cost them accordingly.

Prior to this update, you could only define a resource and classify it as equipment or labor and report usage against the resource. With this update, you can report usage and production or maintenance exceptions against a resource instance.

FEATURE DETAILS

•  Define Labor and Equipment Resource Instances
•  Assign Resource Instances to Work Order Operations
•  Charge Resource Instances in Work Execution
•  Report Production or Maintenance Exceptions
•  Analyze Resource Instances

DEFINE LABOR AND EQUIPMENT RESOURCE INSTANCES 

You can define labor resource instances that represent a specific person working on the shop floor or in maintenance activities. You may have different types of labor resources like employees, contingent workers, or partner contacts. You can define the employees and contingent workers using Oracle Human Capital Management (HCM) Cloud, and then associate them with the defined resource instance.

You can define equipment resource instances that represent the name of an actual machine on a shop floor. For example, two machines available on the shop floor are Lathe-1 and Lathe-2, and you define them as two resource instances of a Lathe resource. You can optionally associate a resource instance to an asset number in the asset master.

You can define these resource instances using the user interface or using REST services.

The following is a screenshot that shows how to define labor resource instances on the Edit Resource page:

Labor Resource Instance Definition

ASSIGN RESOURCE INSTANCES TO WORK ORDER OPERATIONS 

As a Production Supervisor or Maintenance Manager, you can optionally assign as many resource instances to a work order operation resource. This helps you identify the actual people or machines used in execution of production or maintenance activities.

You can track the actual usage at the resource level or a resource instance level, based on the level at which resource transactions are reported.

You can assign these resource instances using the user interface, REST services, or the file-based data import (FBDI) process.

CHARGE RESOURCE INSTANCES IN WORK EXECUTION 

As a Production Operator or Maintenance Technician, you can record resource transactions with resource instance details while manually charging resources, performing orderless completions, or reporting operation completions for automatically charged resources.

When reporting a resource transaction at a resource level, the required quantity reflects the exact quantity required based on the work order.

However, when reporting at the resource instance level, the required quantity is zero, because it is not possible to split the required quantity against each instance. However, you can report any quantity against the instances. You can also review resource instance information for the resources on the Production Transactions History page.

You can report these resource transactions at the instance level using the user interface, REST services, or the file-based data import (FBDI) process.

The following is a screenshot of the Report Resource Transactions page where you can charge at the resource instance level:

Report Resource Transactions

REPORT PRODUCTION EXCEPTIONS 

When you report a production or maintenance exception of type resource, you can capture the specific resource that has an exception. You can now additionally capture the instance of the resource that has an exception. The resource exception notification includes the resource details as well as the resource instance details.

ANALYZE RESOURCE INSTANCES 

When you report resource transactions at an instance level, you can analyze the resource usage in real time using Oracle Transactional Business Intelligence (OTBI).  You can use the resource instance as a dimension and perform detailed analysis in conjunction with asset dimension in Oracle Maintenance Cloud as well as person detail dimension in Oracle Human Capital Management Cloud.

You can also review the details of resource instances in the Work Order Traveler.

Steps to Enable

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

Before using this feature, you can optionally set up the following.

• Set up assets to be linked to Equipment resource instances:
  • If Maintenance Management is installed, create your assets using the Manage Assets task.
  • If Maintenance Management is not installed, use the functional area Manufacturing Master Data, and perform the following tasks to import your assets:
    • Download Asset Import Template
    • Upload Asset Data
    • Load Interface File for Asset Import
    • Import Assets
• Set up persons to be linked to Labor resource instances:
  • If Oracle Human Capital Management Cloud is installed, perform the following tasks to set up the person records for employees and contingent workers:
    • Hire an Employee
    • Add a Contingent Worker
  • If Oracle Human Capital Management Cloud is not installed, use the functional area Customers, and perform the following tasks to import your person records directly to the Trading Community Architecture (TCA):
    • Import Person and Organization

Tips And Considerations

Consider the following:

• When you define asset numbers for maintenance, ensure that the location organization is the manufacturing plant and the location type is work center.
• When you set up resource instances, you can optionally associate them to a primary work center. This facilitates quick assignment of resource instances in work orders and work execution transactions.

Role Information

Define Labor and Equipment resource instances

• Privilege Name and Code:
  • Manage Production Resources (WIS_MANAGE_PRODUCTION_RESOURCES_PRIV)  
• Job Role Name and Code:
  • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)

Assign Resource Instances to work order operations

• Privilege Name and Code: 
  • Manage Work Order Operations (WIP_MANAGE_WORK_ORDER_OPERATIONS_PRIV)  
• Job Role Name and Code:
  • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB???????

Charge Resource Instances in Work Execution

• Privilege Name and Code: 
  • Report Resource Transactions (WIP_REPORT_RESOURCE_TRANSACTIONS_PRIV)
  • Report Orderless Transactions (WIP_REPORT_ORDERLESS_TRANSACTIONS_PRIV)
  • Review Dispatch List (WIP_REVIEW_DISPATCH_LIST_PRIV) ???????
• Job Role Name and Code:
  • Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)???????

Report Production Exceptions

• Privilege Name and Code: 
  • Report Production Exceptions (WIP_REPORT_PRODUCTION_EXCEPTIONS_PRIV) ???????
• Job Role Name and Code:
  • Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Update Work Order Released Date and Closed Date

Prior to this update, you could not update the released date and closed date of a work order. With this update, you can update the released date and closed date of a work order to a date earlier than the current application date.

UPDATE RELEASED DATE OF A WORK ORDER 

When an organization initially imports work order data from the legacy system into Oracle Manufacturing Cloud at the start of any implementation, it helps in maintenance of historical data. However, after the initial import, your organization may need to update the released date of certain work orders to a previous date than the current date in the application so that it reflects the actual work order dates.

You can now update the released date of a work order in the General Information tab on the Edit Work Order page.

The following is a screenshot of the General Information tab on the Edit Work Order page:

Update Released Date of a Work Order

NOTE: You cannot update the released date for contract manufacturing work orders.

UPDATE CLOSED DATE OF A WORK ORDER 

Your organization may need to post material and resource transactions of a work order to a previous date than the current application date after the work order is closed. This can be the case when there is a requirement to align the actual work order closure with the original closed date, and reflect the costing transactions for the previous date.

You can now update the closing date of a work order in the General Information tab on the Edit Work Order page. You can also select multiple work orders to set them to closed status from the Mass Actions menu on the Manage Work Orders page, and change the closed date for all the selected work orders. In case the work order is already closed and processed, you can reopen the work order, perform any transactions, and close the work order again with the closing date set to a previous date.

The following is a screenshot of the General Information tab on the Edit Work Order page:

Update Closed Date of a Work Order

The following is a screenshot of the Mass Actions menu on the Manage Work Orders page:

Update Work Order Closed Date fom Mass Action

NOTE: You cannot update the closed date for contract manufacturing work orders.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

Consider the following validations when you update the released date or closed date of a work order:

• You cannot update the released date to a future date, or a date later than the first transaction date in the work order.
• You cannot update the closed date to a date prior than the last transaction in the work order.
• You cannot update the closed date of work orders that you close through the scheduled process.
• You can update the released date and the closed date of work orders using FBDI and REST services.

Role Information

• Privilege Name and Code:
  • No new privilege required.
• Job Role Name and Code:
  • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

Users provisioned with the Production Supervisor role will automatically be able to update the released date and closed date of the work orders.

E-Signatures and E-Records

Review E-Record and E-Signature Details Inline

Review electronic record and electronic signature details for inline approvals in a PDF file on the E-Signature page.

Users reviewing an electronic record before adding their electronic signatures need not click on a link to open or download the electronic record. The application displays electronic records on the E-Signature page.

The Electronic Record area on the E-Signature page that displays the electronic record in a PDF file allows users to navigate, search, zoom, and download the electronic record. For inline signature transactions, the electronic record is displayed inline in approval notifications too.

The following screenshot shows the electronic record in the E-Signature page.

Steps to Enable

No steps are required to enable this feature.

Key Resources

• Oracle SCM Cloud: Using E-Signatures and E-Records Guide, available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV)  
• Job Role Name and Code:
  • All roles provisioned with the Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV) privilege. Existing roles applicable to the supply chain management transactions that use e-signatures and e-records are provisioned by default.  
• Privilege Name and Code:
  • View Electronic Records and Signatures (EDR_VIEW_RECORDS_ESIGNATURES_PRIV)  
• Job Role Name and Code:
  • Compliance Business Analyst (ORA_EDR_COMPLIANCE_BUSINESS_ANALYST_JOB

Capture User Name with E-Signature

Capture user name and password while generating an e-signature for inline and deferred transactions. During the signing process, you are now required to enter the user name along with the password for two distinct identification components of the e-signature.

The US Food and Drug Administration’s (FDA) 21 CFR Part 11 requires employing at least two distinct identification components such as the identification code and password when obtaining an e-signature.

Starting with this update, signers should enter their user name in addition to the password when adding e-signature to a transaction. Both the user name and the password of the signer is validated before recording their approval or rejection of the electronic record. Error messages are displayed if either the user name or the password does not match with that of the signer.

The user name is captured for electronic records approved through the inline signature page and also when the electronic records are captured through approval notifications.

The following screenshot shows the capture of both user name and password when approving an operation transaction.

Steps to Enable

No steps are required to enable this feature.

Key Resources

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

Role Information

• Privilege Name and Code:
  • Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV)  
• Job Role Name and Code:
  • All roles provisioned with the Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV) privilege. Existing roles applicable to the supply chain management transactions that use e-signatures and e-records are provisioned by default.  
• Privilege Name and Code:
  • View Electronic Records and Signatures (EDR_VIEW_RECORDS_ESIGNATURES_PRIV)  
• Job Role Name and Code:
  • Compliance Business Analyst (ORA_EDR_COMPLIANCE_BUSINESS_ANALYST_JOB

Print E-Signature History in E-Record

Include e-signatures and comments from each reviewer at the end of an electronic record report.

The Signature Manifestations section of the US Food and Drug Administration’s (FDA) 21 CFR Part 11 mandates that the signed electronic records shall contain information associated with the signing that clearly indicates all of the following:

• The printed name of the signer.
• The date and time when the signature was executed.
• The meaning (such as review, approval, responsibility, or authorship) associated with the signature.

The Electronic Record Signature History section is now automatically added to the electronic records stored in the application after they are either approved or rejected. The signature history prints the name of the signer, the signature meaning, response, signed date, and the comments entered, if any, when the electronic signature is added.

Printing the electronic signatures in the electronic records results in compliance with the US Food and Drug Administration’s (FDA) 21 CFR Part 11 regulations for storing electronic records. Electronic signatures are linked to their respective electronic records to ensure that the signatures cannot be excised, copied, or otherwise transferred to falsify an electronic record.

The following screenshot shows the electronic signature history in an electronic record for a work order operation transaction.

Steps to Enable

No steps are required to enable this feature.

Key Resources

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

Role Information

• Privilege Name and Code:
  • Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV)  
• Job Role Name and Code:
  • All roles provisioned with the Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV) privilege. Existing roles applicable to the supply chain management transactions that use e-signatures and e-records are provisioned by default.  
• Privilege Name and Code:
  • View Electronic Records and Signatures (EDR_VIEW_RECORDS_ESIGNATURES_PRIV)  
• Job Role Name and Code:
  • Compliance Business Analyst (ORA_EDR_COMPLIANCE_BUSINESS_ANALYST_JOB

Quality Management

Configure Inspection Actions

Quality Engineers require a methodical approach to implement post-inspection activities and procedures based on the outcome of quality inspection for a particular item, supplier, resource, or business process such as incoming, in process, and final inspection. With configurable inspection actions, you can configure the If-Then decision rules of what actions the user or application should take to ensure compliance with standard quality procedures. As part of an inspection plan, you can visualize and define action rules based on the inspection plan specifications. When results entered for one or more inspection characteristics match the action rule conditions, the corresponding action is triggered. With inspection data, proper follow-up procedure, and disposition you can ensure adherence to the highest quality standards.

Configurable inspection actions will allow you to:

• Change the material status of a lot, serial, or subinventory
• Create a nonconformance issue
• Display alert messages
• Trigger a quality inspection business event that can be extended through PaaS integration to call a web service
• Send a workflow notification to a specified recipient
• View the noted history of actions triggered

Manage Inspection Action Rules

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

The setup of action rules in the Inspection Plan UI is optional.

Save the inspection plan specifications before configuring the inspection action rules.

You can define one or more inspection actions per inspection characteristic.

You can re-implement the automatic generation of nonconformance data using configurable inspection action rules.

NOTE:  You can create and modify inspection actions only from the Inspection Plans UI. You cannot create or update them using the Manage Quality Inspection Plans REST services.

Role Information

• Privilege Name and Code:
  • Edit Inspection Plans (QA_EDIT_INSPECTION_PLANS)  
• Job Role Name and Code:
  • Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)

Manage Quality Inspection Plans Using a REST Service

Oracle Quality Management Cloud provides web services to enable integration with external systems, such as an external quality management system, shop floor devices, or mobile devices. With this update, you can now create and update quality inspection plans.

Use the Inspection Plan REST service to do the following:

• Get quality inspection plan details, specifications, and inspection criteria
• Create and update quality inspection plans details
• Create, update, and delete quality inspection plan specifications
• Create, update, and delete quality inspection plan criteria
• Create and delete attachments at any of the following levels:
  • Inspection plan details
  • Inspection plan specifications

This REST service helps streamline the management of inspection plans by automating the initial load of inspection plans, synchronizing inspection plan changes, and sharing inspection plans with external systems.

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation, available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • Edit Inspection Plans (QA_EDIT_INSPECTION_PLANS)
• Job Role Name and Code:
  • Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)

Manage Data Security Across Issues and Actions

The new Security panel on Issues and Actions enables you to restrict data visibility and access to each object. You can add specific users and roles in the Security panel of an object to make sure only these users and roles are able to access these issues and actions. Creators and assignees have automatic access to their issues or actions.

Security Panel on a Quality Issue

Steps to Enable

Since data security has been enabled in order to protect issues and actions from being seen by unprivileged users, some additional setup steps are required. Each user role, such as a Quality Analyst, must have data security grants assigned to access issues and actions.

Perform the following steps to enable this feature:

1. Open the Security Console.
2. Search for and edit all the roles that should be able to access issues and actions.
3. On the Data Security Policy tab of the Role Definition, grant access to the ENQ_ISSUES_B and ENQ_ACTIONS_B DB resources by instance set.

Configuring Access to Quality Issues and Actions in the Security Console

In addition, for every user who needs to add new entries to the Security panel of the quality issue and quality action, the respective user role should be able to modify the Security table.

To enable this:

1. Search for and edit all the roles that should be able to add new entries to the Security tab of a quality issue or quality action.
2. On the Data Security Policy tab of the Role Definition, you need to grant access to the FND_OBJECTS resources by instance set, for quality issues and for quality actions (two entries).

Configuring Rights to Add Entries in the Security Panel of Quality Actions and Issues

Tips And Considerations

In order to make these "private" issues and actions "public" again, remove all users and roles from the Security panel. Once you do this, all other users with privileges can see the issues and actions again.

Display Manufacturing Resource Instance

When raising a resource production exception in Manufacturing, you can define a more granular representation of a resource instance.  This resource instance is stored and displayed along with the affected manufacturing resource on the quality issue that was created as a production exception.

With the addition of resource instance details on the Affected Objects page of quality issues or actions, and visibility of this information within Oracle Transactional Business Intelligence analysis, you can quickly assess which child of a resource is contributing most to production exceptions, and requires immediate attention.

Resource Instance Details Displayed

Steps to Enable

No steps are required to enable this feature.

Mandate Signature Password upon Workflow Approval

In some industries, a prescribed set of workflow approval transactions for quality issues or actions require greater granularity of electronic signatures. You can enable an advanced signature capture option that mandates the need for a user ID and a password supporting the strict compliance requirements for regulated industries, such as Life Sciences, to maintain the audit history and traceability of signatures.

User Name and Password Required Fields for Approval

Steps to Enable

Set the signature policy of the workflow approval task to Password Required.

Set Up Signature Policy As Password Required

Extend Quality Issues and Actions Using Application Composer

Oracle Quality Management Cloud currently allows you to configure existing ready-to-use objects such as adding user-defined attributes. New extensibility capabilities now available through Oracle Application Composer greatly expand the ability to configure Quality Management's standard issues and actions objects. You can modify and enhance existing business processes using:

• New Attribute Types: DCL, Checkbox, Percentage, Date Time, and Long Text
• Dynamic Field Layouts: Group attributes based on criteria that align with your processes
• Tabs: Show or hide and reorder tabs based on criteria, and add URL tabs
• Buttons and Actions: Add user-defined actions and buttons

Application Composer leverages a set of standard design patterns and wizards to remove the complexity of making user-defined changes, allowing you to focus on the application changes required for your business.

Configuring Buttons and Actions Using Application Composer

Newly Configured Action Displayed in Actions Menu

Steps to Enable

For details about configuring Quality Issues and Actions objects using Applications Composer, refer to the Oracle Applications Cloud: Configuring and Extending guide, available on the Oracle Help Center.

Update 18B

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 APR 2018		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.

Customers Upgrading from Release 12

If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.

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 Go to 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.

Feature Summary

Manufacturing

Integrate with External Label Printing Systems Using Business Events

Oracle Manufacturing Cloud provides web services and business events to enable integration with external systems, such as manufacturing execution systems, shop floor devices, mobile devices, and third-party label printing applications. With this update, a new business event has been added for label printing.

Up until this update, you were able to print a label from the Manage Work Orders page, from the dispatch list, or during operation completion. This would automatically generate a label template with details in a pdf format. You could directly print this pdf through a printer.

With this update, a new capability has been added to integrate with third-party label printing solutions at the start of production.

Based on an application parameter, you can either continue printing using the existing pdf capability, or you can choose to send data to a third-party label printing application.

You can print labels from the following pages in the Work Execution work area:

• Manage Work Orders
• Dispatch List
• Operation Completion – Complete with Details

The action to print labels triggers the Print Product Label business event.  You can then use Oracle Integration Cloud Service to subscribe to this business event, initiate a REST service call to retrieve additional data required for the label, and pass it on to the label printing application.

The third-party label printing application finalizes the template and layout, and prints the label.

Steps to Enable

To enable this feature, follow these steps:

1. In the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials Management offering.
2. On the Setup: Manufacturing and Supply Chain Materials Management page, select the Manufacturing Master Data functional area.
3. Select the task Manage Plant Parameters.
4. For the manufacturing organization that you want to enable this feature for, select the check box Print product labels using external applications.

Tips And Considerations

It must be noted that with this update, you can print labels at the start of production and not at product completion.

Role Information

• Job Role Name and Code: Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Generate Lot and Serial Numbers at Product Completion

Many products produced on the shop floor are serial control enabled or lot control enabled for traceability purpose. Products have serial or lot control enabled at different stages. Some products are identified as predefined, where the serial numbers are created and assigned to the item ahead of the production transactions. Some products are identified as serial control enabled at receipt or lot control enabled for which the serial or lot numbers are generated at the time of inventory receipt or during production completion and put away to inventory.

Until this update, when you completed a work order for products that were identified as serial control enabled at receipt or lot control enabled , you had to either choose the serial or lot from a list of values of pregenerated lot or serial numbers, or type or scan in the lot or serial number. You would either enter a new serial or lot number by typing a serial or lot number, or choose from a list of previously created serial or lot numbers.

With this update, you can select either the Generate Lot or the Generate Serial button on the Complete with Details page for the last operation of a work order or during orderless completion. These buttons will be displayed based on the type of item control.

• If the product is only lot control enabled you only see the Generate Lot button.
• If the product is only serial control enabled, you only see the Generate Serial button.

GENERATE LOT NUMBERS

For lot control enabled products, you can generate new lot numbers by selecting the Generate Lot button. At the time of completing an operation, you are provided with one table row with the quantity of the work order already defaulted.  If you need to generate a single lot, you can select the Generate Lot button. However, if you have more than one lot to be generated, you must modify the quantity in the first row as the quantity of the first lot. A new row with the remaining quantity of the work order is automatically populated. You can highlight both these rows and select the Generate Lot number button once. The application automatically generates two new lot numbers for this product.

GENERATE SERIAL NUMBERS

For products that are serial control enabled at receipt during production, you can generate new serial numbers by selecting the Generate Serial button. At the time of completing the operation, you are provided with as many table rows of the quantity of the product as are being completed. For example, if you are completing a serial control enabled product for a quantity of 10, you will see 10 rows for which you can populate the serial numbers for the product. You can highlight the rows for which you want to generate the serial number, and then select the Generate Serial button. The application generates new serial numbers for the product for these rows.

The following screenshot shows the Inventory train stop on the Complete with Details page where you can perform the action of generating lot and serial numbers.

Automatic Lot and Serial Number Generation While Performing Complete with Details Action

Steps to Enable

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

The following parameters must be set up in item definition:

• The product should be set up as lot control enabled in your inventory organization for you to generate lot numbers automatically during product completion transactions.
• The product should be set up as serial control enabled and the serial generation attribute must be specified as At Receipt in your inventory organization for you to generate serial numbers automatically during product completion transactions.

No additional setup steps are required in Oracle Manufacturing Cloud.

Role Information

Users provisioned with the Production Operator role will automatically be able to generate the lot and serial numbers during product completion.

• Privilege Name and Code: No special privilege required.
• Job Role Name and Code: Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB).

Delete a Work Definition

In your enterprise, a work definition may be created by mistake and prior to this update, there was no way to undo the creation of a work definition. For instance, if a work definition was created manually without an item structure, you had to first create a new work definition with the corrected data, then change the production and costing priorities to make sure that planning, work execution, and costing did not use the incorrect work definition.

With this feature, you can now delete a work definition that was created through either a manual or an automatic process and has not been referenced in work orders or published in cost scenarios.  Deletion removes the work definition and all of its versions from visibility in planning, work execution, and costing.  You can correct a data entry mistake and create a new work definition by reusing the work definition name and item as intended.  As a result, you have more flexibility in making sure work definitions are accurately defined.

The following is a screenshot of the warning message upon deleting a work definition:

Delete a Work Definition

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.

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)

Integrate and Extend Manufacturing Using REST Services

Manage Electronic Signature Organizations Using a REST Service

Use the Electronic Signature Preferences REST service to retrieve electronic signature preferences for supply chain management transactions from the setup.

You can use the Electronic Signature Preferences REST API in external applications to retrieve the e-signature preferences for supply chain transactions. You can query the REST API using organization or transaction type as input. Since, transaction type is a child resource, you can use an e-signature transaction type to query the e-signature used for the transaction type in an organization or all organizations.

The following figure shows a sample payload for the Electronic Signature Preferences REST service.

Sample Payload of the Electronic Signature Preferences REST Service

Steps to Enable

No steps are required to enable this feature.

Key Resources

• Refer to the REST APIs for Oracle SCM Cloud documentation available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • Get Electronic Signature Preferences by Service (EDR_GET_ESIGNATURE_PREF_SERVICE)
• Job Role Name and Code:
  • Compliance Business Analyst (ORA_EDR_COMPLIANCE_BUSINESS_ANALYST)

Manage Workday Patterns Using a REST Service

Oracle provides web services to enable and simplify integration with external systems, and to support data creation and maintenance for large volumes.

Use the Workday Patterns REST service to do the following:

• Create a time, duration, or elapsed workday pattern.
• Assign shifts to the workday pattern to represent working and nonworking time.
• Get the shift details when you need the details of a schedule that uses the shift in a workday pattern.

Steps to Enable

No steps are required to enable this feature.

Key Resources

• Refer to the REST APIs for Oracle SCM Cloud documentation available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • View Workday Patterns (RCS_VIEW_SCHEDULES_WEB_SERVICE_PRIV
  • Create and Update Workday Patterns (RCS_MANAGE_SCHEDULES_WEB_SERVICE_PRIV)
• Job Role Name and Code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Manage Shifts Using a REST Service

Oracle provides web services to enable and simplify integration with external systems, and to support data creation and maintenance for large volumes.

Use the Shifts REST service to do the following:

• Create a time, duration, or elapsed shift.
• Create or update details for time shifts modeling flexible or punch clock based working time.
• Get shift details when you need the details of a schedule that uses the shift in a workday pattern.

Steps to Enable

No steps are required to enable this feature.

Key Resources

• Refer to the REST APIs for Oracle SCM Cloud documentation available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • View Shifts (RCS_VIEW_SCHEDULES_WEB_SERVICE_PRIV)
  • Create and Update Shifts (RCS_MANAGE_SCHEDULES_WEB_SERVICE_PRIV)
• Job Role Name and Code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Manage Schedule Exceptions Using a REST Service

Oracle provides web services to enable and simplify integration with external systems, and to support data creation and maintenance for large volumes.

Use the Schedule Exceptions REST service to do the following:

• Create a schedule exception to model additional working or nonworking time. A schedule exception may be assigned to any number of schedules.

Steps to Enable

No steps are required to enable this feature.

Key Resources

• Refer to the REST APIs for Oracle SCM Cloud documentation available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • View Schedule Exceptions (RCS_VIEW_SCHEDULES_WEB_SERVICE_PRIV)
  • Create and Update Schedule Exceptions (RCS_MANAGE_SCHEDULES_WEB_SERVICE_PRIV)
• Job Role Name and Code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Manage Schedules Using a REST Service

Oracle provides web services to enable and simplify integration with external systems, and to support data creation and maintenance for large volumes.

Use the Schedules REST service to do the following:

• Create a time, duration, or elapsed schedule.
• Assign workday patterns to the schedule to represent working and nonworking time for a defined period of time.
• Assign schedule exceptions to the schedule to add additional working and nonworking time which supersedes the workday pattern.

Steps to Enable

No steps are required to enable this feature.

Key Resources

• Refer to the REST APIs for Oracle SCM Cloud documentation available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • View Schedules (RCS_VIEW_SCHEDULES_WEB_SERVICE_PRIV)
  • Create and Update Schedules (RCS_MANAGE_SCHEDULES_WEB_SERVICE_PRIV)
• Job Role Name and Code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Update 18A

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
19 JAN 2018		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.

Customers Upgrading from Release 12

If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.

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.

Feature Summary

Manufacturing

Create Automatic Work Definitions Using a Scheduled Process

Prior to this update, an automatic work definition was created individually for an item through the user interface of the item structure (that is, bill of materials) in order to facilitate production reporting and costing. These automatic work definitions simplify the manufacturing setups and item structure change management needed for execution without the need for manual intervention and overrides. However, it quickly becomes a tedious task to generate work definitions for each item in a set of items using the user interface.

With this feature, you can specify a set of parameters that filter the organization, user item type, item category, and range of items in order to run a scheduled process that creates an automatic work definition for each item. This scheduled process uses the primary item structure for the selected standard items and the standard operation marked as the default for automatic work definitions to generate the primary work definition with production priority of 1. After running the scheduled process, you can view an output file of the automatic work definitions that are either generated successfully or fails with errors which you can address and rerun the scheduled process. You can also schedule the process to run periodically in order to create automatic work definitions for new items that you create. As a result, this scheduled process streamlines the data setup for a large number of automatic work definitions in order to quickly transact and cost items such as pick-to-order kits that do not require detailed shop floor control.

The following is a screenshot of the Create Automatic Work Definitions scheduled process:

Create Automatic Work Definitions Scheduled Process

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.

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)

Enable Deferred Electronic Records and Electronic Signatures for Manufacturing Work Definitions

Companies in regulated industries must keep detailed records of their product manufacturing processes in accordance with the United States Food and Drug Administration (FDA) regulation on electronic records and signatures called 21 Code of Federal Regulations (CFR) Part 11. Oracle E-Signatures and E-Records is a configurable framework for securely capturing, storing, retrieving, and printing electronic records and signatures.

With this update, the manual creation and update of manufacturing work definitions through the user interface support the creation of an electronic record and the deferred capture of an electronic signature. With electronic records and electronic signatures enabled, the work definition version status now displays as the current status of its approval process that works in conjunction with the approval workflow. A new work definition version is defined only when the version is in draft status.

The following screenshot illustrates an example of a work definition version in draft status that you can submit for approval:

Edit Work Definition Details Page Displaying a Draft Work Definition Version

You must submit the work definition version for approval in order to send the notifications to the approvers to review the electronic record and capture the electronic signatures. The new work definition version is held in a pending approval status until all approvals are complete.

The following screenshot illustrates the workflow approval notification for a work definition version that you submitted for an approval. The notification allows the approver to review the electronic record and capture the electronic signature for an approval or rejection of the work definition changes:

Workflow Approval Notification for Approving the Work Definition Version

When approval is granted, the work definition version cannot be modified. If you must make subsequent changes to an approved work definition including its operations, materials, and resources, you must create a new draft version with a new operation to reflect the changes and submit it for approval again. Only approved work definitions are visible to planning, work execution, and costing.

The following screenshot shows the Edit Work Definition visualization user interface where you can edit the draft work definition version to perform changes to the work definition:

Edit Work Definition Details Page with a New Operation

The work definition electronic records that are created are stored in a secured document repository and cannot be modified or deleted. You can search the electronic records based on any of the transactional information displayed in the electronic record in order to retrieve and print an electronic record.

Steps to Enable

You must opt in to and enable the Capture Electronic Records and Electronic Signatures for SCM Transactions feature. For instructions, refer to the Optional Uptake of New Features section of this document.

To enable e-records and capture electronic signatures for manufacturing, you must determine and configure electronic signatures for each inventory organization using the Configure E-Signature Preferences task in the Setup and Maintenance work area.

After you enable electronic signatures for a transaction, you should also define configurable business process rules in Oracle Business Process Management using the Manage Task Configurations for Supply Chain Management task, and the Manage Approval Groups task in the Setup and Maintenance work area to determine the approvers for each transaction.

Role Information

To configure electronic signature preferences and set up approval rules for work definition management:

• Privilege Name and Code: Determine Transactions Requiring Electronic Signature (EDR_DETERMINE_ESIGNATURES_TRANSACTIONS_PRIV)
• Job Role Name and Code: Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

To initiate the e-records and e-signatures process upon submitting a work definition for approval:

• Privilege Name and Code: Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV)
• Job Role Name and Code: Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)

Create and Update ATO Model Work Definitions with Expanded Levels in Spreadsheet

Prior to this update, as a manufacturing engineer you could use the Application Development Framework Desktop Integration (ADFdi) spreadsheet to upload and download assemble-to-order (ATO) model work definitions to gain visibility into the first level of the model structure in order to assign items to operations. However, any operation assignments at lower levels in the model structure had to be done through the user interface for a single work definition. As a result, extra steps to individually define and maintain ATO model work definitions made it difficult to verify setups and perform mass changes.

With this update, you can build complete work definitions for ATO model items in the ADFdi spreadsheet with an expanded view of option classes and phantoms in the model structure. When you create a work definition, you can specify the ATO model item and its primary item structure in addition to the sequence of operations required to build the work definition.

In a new spreadsheet tab, you can now view all of the levels of the option class and phantom structures, including the hierarchy from a component to the top-parent item. This helps you in building the operation-item assignments for an ATO model work definition and provides you the same flexibility in assigning items to operations as in the user interface. You can assign an item from any level in the item structure (such as child ATO model, option class, option, phantom, or mandatory component) to a work definition operation. For example, lower-level components, for instance options, can inherit their operation assignment based on their parent’s assignment, for instance option class.

Additionally, you can also search for ATO model work definitions and operations that use a specific material and perform a mass update, such as replacing an option that appears under different option classes.

The ability to create and update the expanded levels of ATO model work definitions using the ADFdi spreadsheet enables more accurate data setups and easier change management for the work definitions of product configurations which are created through the configure-to-order (CTO) business process.

 It must be noted that you can define operation applicability rules based on selected options and transactional item attributes (TIAs) only through the user interface.

The following is a screenshot of the worksheet within the Manage Work Definitions spreadsheet where you can create and update ATO model work definitions with expanded levels:

Operation Items - Multilevel ATO Tab

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

The following must be considered:

• After defining the header and operations for the multilevel ATO model work definition, you can query with search parameters like Organization and Item to view the Component Hierarchy, Level, and Assignment Status in addition to other details in the Operation Items- Multilevel ATO tab of the spreadsheet.
• You can also use these details to assign the components from different levels to appropriate work order operations. 
• After uploading the details, you can requery to check the assignment status at all levels. 

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)

Pick Materials for Work Orders

In Oracle Manufacturing Cloud and Oracle Maintenance Cloud, material is manually issued from a subinventory to the work order or is backflushed from the inventory based on the material assigned to the work order. Prior to this update, there was no way to pick and stage material for production. In industries with long lead times or many common materials, there is a need to move material from the warehouse or a common stock subinventory to a shop floor supply subinventory based on the jobs that are scheduled for production in the near future.

Companies that backflush material commonly mark this supply subinventory as nonreservable and not available-to-promise supply to prevent production material from being used for other purposes, while giving cost accountants a convenient way to report on the value of the material that is staged for production but not yet issued to work orders. Companies that require a manual transaction to charge material to the job often have the picking process issue the material directly to the work order, saving their shop floor operators from having to perform a second manual transaction.

In the warehouse, the physical picking process is the same whether the demand is a work order, a shipment, or a movement request, and it is often performed by the same personnel. With this update, enhancements to the products allow you to pick work orders from Oracle Inventory Management Cloud. There are four aspects to the enhancements:

• Request Work Order Material Picking
• Execute Picking in the Warehouse
• View Allocated Quantity and Picked Quantity in Manufacturing
• Manage Work Order Changes

REQUEST WORK ORDER MATERIAL PICKING

Initiate the picking task to ensure material-tracking and timely availability of materials during production. You can initiate this process from the Manage Work Orders task and the Manage Material Availability Assignments task.

You can also schedule the picking task periodically to generate the picking request.

• Schedule Picking from the Pick Materials for Work Orders Task In some companies, the person requesting for picking of work orders may be different from the person managing the work orders. In such cases, the Pick Materials for Work Orders task in the Work Execution and in the Inventory work areas allows you to choose parameters based on which you want to request for picking of materials. The parameters allow you to specify the following:
  • Organization: Set the context for your picking.
  • Work method: Pick components for manufacturing or for maintenance work orders.
  • Work order type: Choose one or many of the work order types such as standard, nonstandard, rework, transform, and maintenance work orders. 
  • Hours ahead: Pick components that have a requirement date within the hours ahead that you specify from the time of submitting the pick request.
  • Pick all components of a work order: Pick all components for a work order only when all the quantities for all the components of that work order are available.

The pick slip grouping rule and the pick slip printing attributes default from the plant parameters you have specified, but they can also be overridden.

You can select the Pick Materials action to initiate the scheduled process. The scheduled process creates a movement request to move the components to the appropriate shop floor location.

Pick Materials for Work Orders Scheduled Process

• Schedule Picking from the Manage Work Orders Task and the Material Availability Assignments Task

In many companies, the person that is managing and releasing work orders to the shop floor is the same person that initiates the pick process to stage material for production. In such cases, you can directly release and pick components from either the Manage Work Orders task or the Material Availability Assignments task in the Work Execution work area.

You can select one or more work orders and select the Release and Pick action. You are asked to confirm the pick slip grouping rule that should be used, whether or not you want to print the pick slip, and if you want to force each work order to be picked completely.

After you submit the request, the application will release all unreleased work orders for production and submit the background process to generate a pick request for all components that are eligible for picking based on the inventory picking rule, plant parameters, and the picking status.

You can also select the Release and Pick action to repick an order that was already released and is partially picked.

The scheduled process generates a movement request to move the components to the applicable shop floor location.

Picking from Manage Work Orders Page

Picking from Material Availability Assignments Page

EXECUTE PICKING IN THE WAREHOUSE

When you initiate picking in Manufacturing, a manufacturing movement request is created in Inventory. Manufacturing passes the pick slip grouping rule, the print pick slip parameter, the pick complete indicator, as well as indicates for each component whether the component will be issued directly to the work order or moved to the supply subinventory, based on the supply type of the component and the manufacturing plant parameters.

After the material movement request is created, Inventory reserves and picks material using the scheduled process Print Movement Request Pick Slip Report.

The pick slip is generated using the pick slip grouping rule assigned in Manufacturing. The pick slip grouping rule allows you to group pick slips in the warehouse and by a variety of pick slip attributes such as work order number, work area, work center, and push or pull activity. 

Using the Confirm Pick page in Inventory, you can optionally select pick slips by pick slip type shopfloor to confirm the details of the picked material, to move the material to the destination subinventory defined on the work order, and to update inventory balances. 

After pick confirm, the application will either issue materials or move materials based on values passed from Manufacturing.

The allocation for the lines eligible for partial picking is done based on the on-hand quantity available for the component. The work order is eligible for pick release after the partial pick has been performed for a work order component. Manufacturing sets the work order pick release status to Pick Partial based on what Inventory was able to pick.

VIEW ALLOCATED QUANTITY AND PICKED QUANTITY IN MANUFACTURING

You can view the allocated and picked quantities for each material of the work order in the following pages:

• Work Order Operation Items
• Material Availability Details

Allocated and Picked Quantity in Edit Operation Items

Allocated and Picked Quantity in Material Availability Details

MANAGE WORK ORDER CHANGES

The application allows you to monitor and manage changes to work orders and the picking process in the following manner:

• If a work order is canceled, closed, or unreleased after the picking process has been performed, but before the move order is transacted, the application automatically cancels the move order.
• If the work order quantity is increased, you can resubmit the order for picking and the application will create a pick request only for the additional quantity required.
• If the work order quantity is reduced, you will be informed if the materials have already been picked for a higher quantity.

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.

Also, the following plant-level parameters have been added to control the default behavior of the work order picking process for a given facility, and give you the ability to do the following:

• Default Pick Slip Grouping Rule: Specify which picking rule you want to use as a default when you are initiating work order picking
• Print pick slips: Determine whether the system will print pick slips by default.
• Include pull components for pick release: Determine whether to include backflushed materials in the picking process.
• Issue push components on pick release: Determine if you want to automatically issue push material to the job during picking or just move the material to the supply subinventory specified on the work order.

          Manage Plant Parameters

Role Information

With this update, a new functional privilege for work order picking has been added and can be assigned to any manufacturing or inventory user.  Users with that responsibility will have access to this feature.

• Privilege Name and Code: Pick Components for Work Orders (WIP_MANAGE_WORK_ORDER_COMPONENT_PICKING_PRIV)
• Privilege Name and Code: Print Movement Request Pick Slip Report (INV_PRINT_MOVEMENT_REQUEST_PICK_SLIP_REPORT_PRIV)
• Job Role Name and Code: Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

Integrate with External Systems with Additional REST Services

Oracle Manufacturing Cloud provides web services to enable integration with external systems, such as manufacturing execution systems, shop floor devices, and mobile devices. With this update, the following services have been added or updated:

REST SERVICE FOR CREATE WORK ORDER

Prior to this update, you could create a standard, rework, or transform work order by using the default or alternate work definition using REST services. With this update, the REST service has been updated to support the following additional capabilities:

• Create a nonstandard work order without any reference to the work definition.
• Create, update, or delete an operation for any type of work order.
• Create, update, or delete an operation material for any type of work order.
• Create, update, or delete an operation resource for any type of work order.
• Simultaneously create, update and delete work order operations, operation materials and operation resources in a single REST service call using a batch request
• Create, update, or delete work order descriptive flexfields at any of the following levels:
  • Work order header
  • Work order operation
  • Work order operation material
  • Work order operation resource

REST SERVICE FOR STANDARD OPERATIONS

If you are using an external application, you may want to GET the details of standard operations to use with third-party applications. With this update, you can GET the following information for standard operations:

• Standard operation header details
• List of resources and resource details associated with the standard operation
• List of alternate resources for a resource assigned to each operation and details of alternate resources associated with the primary resource
• Attachments associated with the standard operation header and standard operation resource
• Descriptive flexfields of the standard operation header and standard operation resource

REST SERVICE FOR WORK DEFINITION

If you are using an external product development application and want to integrate with Oracle Manufacturing Cloud, you are able to use the GET Work definition REST service. Prior to this update, you were able to GET only the work definition header. With this update, you can GET the following additional information for work definitions:

• Header details
• Operations
• Operation materials
• Substitute materials for a work definition operation material
• Operation resources
• Alternate resources for a work definition operation resource
• Attachments associated with work definition header, operation, operation materials, and operation resources
• Descriptive flexfields of a work definition operation, operation material, and operation resource

It must be noted that you are able to get the details for a standard item only.

Steps to Enable

No steps are required to enable this feature.

Role Information

Following are the privileges required to use this feature:

• REST Service for Create Work Order

  • Privilege Code: WIP_UPDATE_WORK_ORDERS_SERVICE

  • Privilege Name: Allows you to create and update work orders using a service.

• REST Service for Standard Operations

  • Privilege Code: WIS_GET_STANDARD_OPERATIONS_SERVICE
  • Privilege Name: Allows retrieval of standard operation information using a service.

• REST Service for Work Definition

  • Privilege Code: WIS_GET_WORK_DEFINITIONS_SERVICE
  • Privilege Name: Allows retrieval of work definition information using a service.

Following Job Roles have the above privileges:

• Production Supervisor

  • WIP_UPDATE_WORK_ORDERS_SERVICE

• Manufacturing Engineer

  • WIS_GET_STANDARD_OPERATIONS_SERVICE

  • WIS_GET_WORK_DEFINITIONS_SERVICE

Import Product Genealogy Data for Initial Data Upload

Serial-controlled and lot-controlled products and components that are produced internally in an organization can be tracked by the product genealogy solution. With this update, when you implement Oracle Supply Chain Management Cloud, you can also import the component structure and historical transactions of a product serial number or lot from your external legacy systems. This will enable the complete traceability of your products from legacy systems to your transactional applications.

Leveraging file-based data import from Oracle Supply Chain Management Cloud, the product genealogy import process allows you to create the product instances for serial-controlled or lot-controlled products, build the structure relationships between assemblies and components, and load related historical transactions into the genealogy repository.

The following screenshot traces the tasks involved in the import process:

Product Genealogy Import Process

You can view the successfully imported product instances, structures, and historical transactions on the Review Product Genealogy page.

Steps to Enable

The following setups must be completed to use this feature:

• For each product and component that you want to import, specify the following attributes while defining items in the Product Information Management work area:
  • Select Enable Genealogy Tracking as Yes.
  • Select Lot Control as Full lot control if you want to track genealogy for lot-controlled products.
  • Select Serial Generation as required except for the option No serial number control if you want to track genealogy for serial-controlled products.

• A valid external source system is required for import. As a prerequisite, you must define one or more external source systems in Customer Data Model.

Tips And Considerations

The following points must be considered:

• You can optionally create components and build multi-level component structures in the same batch. Identify your genealogy instances by the Import Record Number attribute.
• For a  product that is lot-controlled only, the combination of item number and lot number is not unique for a genealogy instance. You must specify the Genealogy Instance Identifier attribute to update such a product instance.

Key Resources

• For more information on this feature, refer to the File-Based Data Import for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

• Privilege Name and Code: Import Product Genealogy (CSE_IMPORT_PRODUCT_GENEALOGY)
• Job Role Name and Code: Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR)

Create Product Genealogy Analyses and Reports Using Oracle Transactional Business Intelligence

The product genealogy solution provides you with tracking capabilities for serial-tracked and lot-tracked products and components. However, companies also have a need to generate user-defined reports for product genealogy for multiple purposes, such as tracing reports that capture information about where they need to find where a defective material was used, or for submission of detailed work order information to various regulatory agencies or even a customer. Typically these reports will trace the entire history of a product from receipt of materials through manufacturing to the delivery of the product to the customer.

With this update, Oracle Transactional Business Intelligence (OTBI) provides the tools to easily generate your own reports to satisfy all of your genealogy reporting requirements.

The following subject areas have been introduced:

• Product Genealogy – Genealogy Instance Real Time: This subject area provides real time information on genealogy instance identifying attributes, current location, and related details.
• Product Genealogy – Genealogy Structure Real Time: This subject area provides real time visibility into genealogy component structures. Each structure is a list of components associated to a parent assembly as built.
• Product Genealogy – Genealogy Transaction Real Time: This subject area provides real time information on genealogy transactions.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

In the subject area Product Genealogy – Genealogy Instance Real Time, the main dimension is Genealogy Instance Details. It includes the identifying attributes such as item, serial number, lot number, the current location, related parties, and documents. This dimension is shared by subject areas Product Genealogy – Genealogy Structure Real Time and Product Genealogy – Genealogy Transaction Real Time, enabling you to include genealogy instance details when reporting on structures or transactions.

You can change the column labels instead of using the default attribute names in your report to make it more functionally relevant to your enterprise.

Role Information

• Business Intelligence Duty Role Name and Code: Product Genealogy Transaction Analysis Duty (FBI_PRODUCT_GENEALOGY_TRANSACTION_ANALYSIS_DUTY) 
• Job Role Name and Code: Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR)