Update 21A

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	Product	Feature	Notes
18 DEC 2020			Created initial document.

Overview

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

SECURITY AND NEW FEATURES

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

If you have created job roles, then you can use this information to add new privileges to those roles as needed. For details about how to compare your configured job roles to predefined job roles and add security artifacts to your configured job roles, see the Security Console and Roles and Role Assignments chapters in the Oracle SCM Cloud: Securing SCM guide on the Oracle Help Center.

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.

Pre-Update and Post-Update Tasks

Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle SCM Cloud: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

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

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

1. Click Navigator > My Enterprise > Offerings.
2. On the Offerings page, select your offering, and then click Opt In Features.
3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

Opt In Expiration

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

Feature Summary

Cross-Product Enhancements

Link to SCM Application Pages Using Deep Links

In this update, Oracle Supply Chain Management Cloud delivers new deep links that provide easy navigation directly to application pages without using the menu structure. You can use these links in a variety of ways, such as in business intelligence reports, notifications, and third-party application pages.

New deep links in the update are listed by product:

• Supply Chain Collaboration
  • Manage Supply Collaboration Network (COLLABORATION_RELATIONSHIP,EDIT)

• Inventory Management
  • Review Completed Transactions
  • Inventory Pending Transactions
  • SSP Manage Receipts
  • View Receipts
  • Manage Lots
  • Manage Serial Numbers
  • Create ASN
  • Manage Movement Requests
  • Create ASBN
  • Manage Inbound Shipments - Shipment
  • Manage Inbound Shipments - Purchase Order
  • Receive Expected Shipments - Purchase Order
  • Receive Expected Shipments - ASN
  • Receive Expected Shipments - Transfer Order
  • Receive Expected Shipments - In-Transit Shipment
  • Receive Expected Shipments - RMA
  • Manage Transfer Order
  • Manage Shipment Lines
  • Edit Shipment

• Channel Revenue Management
  • Manage Customer Claims (CUSTOMER_CLAIM,NONE)
  • Customer Claim (CUSTOMER_CLAIM,EDIT)

• Manufacturing
  • Work Order (WIE_WORK_ORDER, VIEW)
  • Work Order (WIE_WORK_ORDER, EDIT)
  • Exception (WIE_PRODUCTION_EXCEPTION,EDIT)
  • Work Definition (WIS_WORK_DEFINITION,EDIT)
  • Edit Resource (WIS_RESOURCE,EDIT)

When you add deep links to reports or third-party application pages, users can simply click those links to go directly to the application pages they need to use, without any additional clicks or navigation. When a user clicks a deep link, that user's security assignment is honored; that is, users can access application pages only if they're assigned a job role that allows them access.

Steps to Enable

You can find all of the available deep links in the Deep Links work area. Some deep links, such as those assigned the NONE action, are ready to use as is. Other deep links, such as those assigned the EDIT action, require you to edit the link details before you can add the deep link to a report or third-party application page. Refer to the documentation listed in the Key Resources section for details and instructions.

Key Resources

For details about how to work with deep links, refer to these books on the Oracle Help Center:

• Oracle Applications Cloud: Configuring and Extending Applications
• Oracle SCM Cloud: Implementing Common Features for SCM

Role Information

You have a couple of options for giving people access to the Deep Links work area, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles are automatically able to access the Deep Links work area:

• Application Developer (FND_APPLICATION_DEVELOPER_JOB)
• Application Implementation Administrator (ORA_ASM_APPLICATION_IMPLEMENTATION_ABSTRACT)
• Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
• Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
• Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Users who are assigned configured job roles that contain this privilege are able to access the Deep Links work area:

• View Administration Link (FND_VIEW_ADMIN_LINK_PRIV)

If you're using deep links specifically for reports, here are the privileges you need:

• For Business Intelligence Publisher:
  • BI Author Role (BIAuthor)
  • BI Consumer Role (BIConsumer)
  • BI Administrator (BIAdministrator)

• For Oracle Transactional Business Intelligence (OTBI):
  • BI Author Role (BIAuthor)
  • BI Consumer Role (BIConsumer)

Manufacturing

Enable Dual Units of Measure in Manufacturing and Maintenance

There is a segment of manufacturers that produce products that vary in a specific attribute, such as weight, volume, concentration, or purity, that is tracked separately from how they are stocked. For example, a product is stocked by count in cases, but costed by weight in pounds. This capability is often referred to as catchweight in the consumer packaged goods industry or dual units of measure (UOM) in other manufacturing industries. These manufacturers require production tracking simultaneously in a stocking UOM and the equivalent, variable UOM, beyond the fixed UOM conversions supported today.

You can now report materials and products in dual UOMs through the following discrete and/or process manufacturing transactions that update on-hand inventory and conditionally genealogy, if items are enabled with lot control and genealogy tracking:

• Manual material issue and return

• Backflush material issue and return using quick complete or complete with details

• Product completion and return using quick complete or complete with details of the last operation on a discrete manufacturing work order

• Output completion and return using quick complete or complete with details at the corresponding operation on a process manufacturing work order

• Manual output completion and return on a process manufacturing work order

• Orderless completion and return

• Complete supplier operation with an outside processing item

• Material issue and return in a contract manufacturing organization

• Product completion and return in a contract manufacturing organization

• Tracking purchasing and receiving details and receipt correction and return for a purchased item directly tied to a work order

Backflush Material Issue using Complete with Details

Report Output Completion

Based on the item setup for dual UOM tracking, the relationship between the primary and secondary quantities can be either fixed or variable within a deviation tolerance for each manufacturing transaction.

• When the item's UOM defaulting control is set to fixed, you enter the transaction quantity in the primary or transactional UOM, which is automatically converted to the secondary quantity in the secondary UOM based on the standard or item-specific UOM conversion

• When the item's UOM defaulting control is set to default, you can enter the transaction quantity in the primary or transactional UOM and override the secondary quantity that is defaulted from the standard or item-specific UOM conversion

• When the item's UOM defaulting control is set to no default, you can enter the transaction quantity in the primary or transactional UOM and enter the secondary quantity in the secondary UOM

You can perform these manufacturing transactions in dual UOMs using the user interface, File-based Data Import, ADFdi for import error correction, and REST services. You can also view these manufacturing transactions in dual UOMs through the production transaction history, e-records for material, operation, and output transactions, and the Manufacturing subject areas in Oracle Transactional Business Intelligence.

In addition, you can search for and view the complete genealogy for lot-controlled items tracked in dual UOMs, spanning raw materials to the finished product. For a selected lot, you can view its on-hand, issued, and shipped quantities in dual UOMs and view the transaction history of inventory and manufacturing transactions completed in dual UOMs.

Watch a Demo

With production reporting and lot genealogy in dual UOMs, you can better track the variability inherent in materials and products for improved inventory visibility and costing accuracy, based on the actual quantity instead of the standard quantity in catchweight and other manufacturing industries.

Steps to Enable

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

Offering: Manufacturing and Supply Chain Materials Management  No Longer Optional From: Update 21C

Tips And Considerations

• UOMs must be defined prior to creating UOM standard conversions and items. Items must be defined prior to creating UOM interclass or intraclass conversions. Refer to Implementing Common Features for SCM for more information about units of measure and conversions in Oracle Supply Chain Management Cloud Common Configuration.

• Items must be defined with Primary and Secondary Tracking Unit of Measure in order to perform manufacturing transactions in dual UOMs and Enable Genealogy Tracking for lot genealogy visibility. Additional item attributes related to Unit of Measure can be defined, including primary UOM, secondary UOM, defaulting control of fixed, default, or no default, and positive and negative deviation factors.

• An Assemble-to-Order (ATO) model can be defined with dual UOMs. The resulting configured item inherits the dual UOM attributes of the base model, and is executed in Manufacturing similar to a standard item.

• In some use cases, another transactional UOM can be specified for a material quantity in a discrete manufacturing and additionally an output quantity in a process manufacturing work definition. The transactional UOM is inherited in manufacturing transactions for reporting convenience as long as it is convertible to the base UOM in the UOM class of the item's primary UOM. The secondary UOM defaults from the item definition and cannot be updated during manufacturing transactions.

• If a work definition operation item or operation output has been defined with the secondary UOM as their transactional UOM, it is recommended that they are revised to use the primary UOM as their transactional UOM.

• Lot-specific UOM conversions are not created based on inventory or manufacturing transactions.

• The production report for contract manufacturing that is accessed from the Supplier Portal, Supply Chain Orchestration, and Supply Chain Collaboration work areas does not support material issue and product completion transactions in dual UOMs. Instead you can perform these transactions in the manufacturing user interfaces and through REST services.

• Unconstrained and constrained-based supply planning as well as reservations and picking of work order materials occur in the primary UOM.

• Cost planning and cost accounting can be performed in either the primary or secondary UOM for an item based on its cost profile.

• Refer to the Enable Dual Units of Measure in Manufacturing and Maintenance feature under Maintenance Cloud for more information about dual UOM-enabled items in maintenance transactions and the asset pages.

Key Resources

• Watch Enable Dual Units of Measure in Manufacturing and Maintenance Readiness Training

Role Information

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
• Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Review Dispatch List (WIP_REVIEW_DISPATCH_LIST_PRIV)
• Report Material Transactions (WIP_REPORT_MATERIAL_TRANSACTIONS_PRIV)
• Report Operation Transactions (WIP_REPORT_OPERATION_TRANSACTIONS_PRIV)
• Report Orderless Transactions (WIP_REPORT_ORDERLESS_TRANSACTIONS_PRIV)
• Manage Supplier Operations (WIP_MANAGE_SUPPLIER_OPERATIONS_PRIV)
• Review Supplier Operation Details (WIP_REVIEW_SUPPLIER_OPERATION_DETAILS_PRIV)
• Review Production Transaction History (WIP_REVIEW_PRODUCTION_TRANSACTION_HIST_PRIV)
• Review Product Genealogy (CSE_REVIEW_PRODUCT_GENEALOGY_PRIV)

Schedule Work Orders of Multiple Year Duration

Companies plan and schedule their production based on customer demand and the lead time for manufacturing. In most cases, the lead time for production is from hours to days to weeks. However, in certain types of products, the lead time can be long ranging up to a few years.

Until this update, you were only able to create work orders with a maximum lead time of 12 months. You could create these work orders from Oracle Supply Planning Cloud or manually in Oracle Manufacturing Cloud.

With this update, using a plant parameter "Maximum Scheduling Duration in months", you can set the duration to any value between 3 to 48 months. Based on the plant parameter, the work orders are created with lead times up to 48 months, provided the plant calendars are defined for the requisite period. You can now use the native unconstrained scheduler to schedule the work orders without having to build integrations with third party scheduling tools.

Manage Plant Parameters

Watch a Use Case Scenario Demo

This update helps plan and schedule work orders for a long duration using the configurable scheduling horizon.

Steps to Enable

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

Tips And Considerations

Some of the considerations to be kept in mind are:

1. By default, new and existing manufacturing plants are created with a parameter value of 12 months. You can modify them as desired.
2. This parameter does not influence manufacturing lead time calculations scheduled process.

Key Resources

• Watch Schedule Work Orders of Multiple Year Duration Use Case Demo

Role Information

You can use the seeded Production Supervisor role to schedule work orders using this feature.

View Inventory Lot Split, Lot Merge, and Lot Translation in Genealogy

When dealing with goods that are under lot control, there are numerous events that might require you to break, combine, or transform some or all of the goods in a specific lot. For example, a weather event causes damage to your warehouse and spoils only a portion of a lot. The damaged portion of the lot is still usable for some, but not all, of your manufacturing processes. Thus, you need to split this quantity from the original lot and assign new lot numbers to ensure your goods are designated properly for future use. Similarly, maybe you regularly combine multiple lots into a single vat before use in downstream processes. When you merge all of these lots into a single vat, you assign a new and unique lot number. Finally, in some industries, a chemical reaction process might require that you change the assigned lot number of an item when the process is complete. For example, let’s say you complete a work order for item 123 into lot A. After two weeks, the reaction process is complete, and the lot should change to lot B. This change indicates that the item is ready for the next step. The item itself hasn’t changed, and the additional overhead of a work order just to change the lot number isn’t desired. Additionally, you need the lot history retained. In these scenarios, a work order isn’t required. Now you can perform lot splits, merges, and translations within Oracle Inventory Management Cloud using REST APIs or file-based data import (FBDI).

For historical traceability, you can track the lot genealogy data from the lot splits, merges, and translations and view these lot genealogy records through the Review Product Genealogy page. In genealogy details, the parent-child genealogy relationships for a specific lot are displayed visually using directional arrows and new filters for lot composition and lot where used, so you can trace forwards and backwards between the source lot and resultant lots. In the transaction history, you can filter the timeline for these inventory transactions by type and click through to review the lot split, merge, or translate transaction details.

Genealogy Details - Lot Split

Genealogy Timeline - Lot Split

The new split, merge, or translate lots feature lets you change lots dynamically and track its genealogy, without the additional overhead of creating a work order or performing extraneous inventory transactions.

Steps to Enable

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

Tips And Considerations

• Refer to the Perform Lot Split, Merge, and Translate Using REST APIs and FBDI feature under Inventory Management for more information.

• You cannot use the Product Genealogy REST APIs and FBDI to import lot genealogy data resulting from inventory lot split, merge, and translate transactions.

• You can view lot split, merge, and translate transactions in the Inventory Transactions Real Time subject area, but not the Product Genealogy subject areas in Oracle Transactional Business Intelligence.

Role Information

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

• Privilege Name and Code: 
  • Get Product Genealogy by Service (CSE_GET_PRODUCT_GENEALOGY_BY_SERVICE_PRIV)
  • Manage Product Genealogy by Service (CSE_MANAGE_PRODUCT_GENEALOGY_BY_SERVICE_PRIV)

• Job Role Name and Code: 
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)

Quality Management

Add Relationships Between Problem Reports and Corrective Actions

Create bi-directional relationships between Problem Reports and Corrective Actions from the Relationships tab of these objects. You can also use the Relationships tab of other objects in Product Development, Innovation Management, and Quality Management to add Problem Reports and Corrective Actions as related objects.

When you add a relationship, you can use simple search or advanced search to find the Problem Report or Corrective Action that you want.

Add Problem Report and Corrective Action from Relationships Tab

Organization details provided in the search results help you identify the correct object.

Search for Problem Reports

Relationships you create are listed along with its organization in the Relationships table.

Relationship Table for Problem Report Shows Corrective Action and Related Problem Report

Relationship Table for Change Order Shows Corrective Action and Related Problem Report

Relate objects to group similar product issues, identify patterns, and get a complete picture of impacted objects to ensure proper resolution. 

Steps to Enable

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

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Quality Analyst Job Role (ORA_ENQ_QUALITY_ANALYST_JOB)

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV) or Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

• Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)

Additionally, you need to create a data policy with the following condition:

• Access the item change for table EGO_ENGINEERING_CHANGES_B for the item changes they have access to.

Cancel Workflows for Quality Issues and Actions

Cancel workflows for quality issues or actions that are created by accident or are no longer relevant. Use the Cancel action on an object to close its workflow and remove it from the infolets on the Overview page.

New Cancel Action in Actions Menu

Confirmation Dialog for Cancel Action

Cancellation Recorded in Quality Action Workflow Summary

Cancel workflows that were created in error, or are no longer required, so that you can keep your focus on relevant quality issues and actions.

Steps to Enable

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
• Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• ENQ_CANCEL_QUALITY_ISSUE (for quality issues)
• ENQ_CANCEL_QUALITY_ACTION (for quality actions)

Control Quality Object Creation with New Privilege

Use two different privileges to control who can create a quality object, and who can edit it. A new Create privilege lets you create, but not edit, quality objects. The Manage privilege lets you create and also edit quality objects.

Create Quality Issue Dialog

Enable non-quality personnel from other functional groups like production, development, or field service to create and view a quality issue or action. If you assign these users only the Create privilege, they can't edit or manage the object after creation.

Steps to Enable

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
• Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

All other roles, who can only create and not manage issues and actions, must be assigned the following new CREATE privileges:

• ENQ_CREATE_QUALITY_ISSUE
• ENQ_CREATE_QUALITY_ACTION

Enforce Sampling Inspection for a Work in Process Plan in Manufacturing

Today you can enforce the inspection of 100% of the consecutive units produced while completing a manufacturing work order operation. After the inspection is done, you can report on the operation quantity completed, rejected, or scrapped based on the number of units with accepted or rejected inspection results, respectively. However, once a manufacturer has produced a number of units with consistent good quality, they may not be able to test every product due to high volume production or the cost and cycle time of inspection.

With this feature, you can now select representative samples out of a discrete or process manufacturing work order operation quantity to determine the quality of a nonserialized work in process (WIP). WIP sampling is supported through the Review Dispatch List page and the Inspection Results REST services.

When defining an inspection level, you can specify sampling based on a percentage of the quantity produced, a fixed count of samples, or based on the statistical standards for Acceptance Quality Limit (AQL). In percentage-based sampling, any inspection failure can reject the entire quantity being completed at that operation. In AQL inspection, the system statistically determines the number of samples from the quantity produced and the maximum number of rejected units allowed in order to qualify for acceptance. You can associate a sampling-enabled inspection level with a mandatory WIP inspection plan to enforce inline WIP sampling.

Defining a Work In Process Inspection Plan with User Defined Inspection Level

During the inline WIP inspection process, you can complete the full or partial work order quantity at an operation using the Quick Complete or Complete with Details flows on the Review Dispatch List page. The quantity being completed at the operation is used to determine the number of samples based on the inspection level required by the WIP inspection plan. Then you can select this number of units at random for sampling and inspection to proceed with the operation transaction.

Inline Work In Process Inspection with Sampling

After results are entered for the required samples, the inspection is accepted or rejected based on either acceptance sampling logic for percentage-based and fixed count sampling or AQL standards and is applied to the entire quantity produced at the operation. If an initial sample failure is reported in percentage-based or fixed count sampling, you can also increase to 100% inspection to inspect the rest of the quantity. Saving the inspection results also drives the corresponding operation transactions for completed and rejected quantities. With the appropriate privilege, you can move the rejected quantity to scrap for disposal.

Watch a Demo

WIP sampling combined with flexible WIP inspection levels help manufacturers reduce the cost and scope of inspection to reach reliable conclusions about their product quality.

Steps to Enable

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

Tips And Considerations

• WIP sampling can also be used with fixed count sampling. Refer to the Perform Sampling Inspection with a Fixed Count Inspection Level feature for more information.

• For discrete manufacturing work orders, inline WIP sampling can apply to work in process at an intermediate operation or the product at the last operation. The accepted quantity from inspection matches the product completion quantity at the last operation.

• For process manufacturing work orders, inline WIP sampling can apply to work in process at any operation, where the inspection quantity is considered representative of the batch quantity being completed at the operation. Ad hoc WIP inspection is recommended for inspecting the primary product, co-product, or by-product in process manufacturing.

• Similar to the existing inline WIP inspection process, WIP sampling is enforced prior to product or output completion when a lot number is assigned.

• The Inspect All feature increases percentage-based and fixed sampling to 100% inspection and does not apply to AQL sampling inspection.

• Inline WIP sampling does not apply to serial-controlled items or serial-tracked operations.

• Ad hoc WIP inspection allows the number of samples to be specified, so WIP inspection levels do not apply.

• The rejection rate of WIP inspections displayed in the Work Execution and Quality Management overview page infolet is based on the number of samples rejected out of the total samples and is unaffected by WIP sampling.

• You can analyze sampling-based WIP inspections in OTBI to help determine when you can manually switch inspection levels based on the historical detection of defects.

Key Resources

• Watch Enforce Sampling Inspection for a Work in Process Plan in Manufacturing Readiness Training
• Using Quality Management guide on the Oracle Help Center. 

Role Information

You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
• Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
• Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Edit Inspection Results (QA_EDIT_INSPECTION_RESULTS)

Perform Sampling Inspection with a Fixed Count Inspection Level

As an alternative to sampling based on a percentage sampling size or Acceptable Quality Limit, some companies need the flexibility to define a sample count that doesn't change based on quantities being received or produced. For example, a large work order only requires two samples for lab analysis and destructive testing purposes. Now you can define an inspection level based on a fixed count of samples and apply it to a mandatory receiving or work in process inspection plan. This type of sampling plan specifies the sampling size as a fixed count regardless of the receipt line quantity or work order quantity.

Fixed Count Inspection Level

During the inline inspection process, you take the predefined number of samples and test them based on acceptance sampling, which rejects the inspection quantity as soon as one defect is found with a rejected result. If the inspection results are inconclusive, you can also choose to increase the sampling size to 100% inspection of the remaining quantity being received or produced to further separate accepted and rejected quantities.

Sampling Inspection with a Fixed Count Inspection Level

Watch a Demo

With fixed count sampling, you can enforce the proper sampling size and procedure for your business, thereby reducing the costs associated with more samples and minimizing disruptions to operations.

Steps to Enable

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

Tips And Considerations

• Fixed count sampling can also be used with work in process sampling. Refer to the Enforce Sampling Inspection for a Work in Process Plan in Manufacturing feature for more information.

• Ad hoc inventory and work in process inspection allows the number of samples to be specified, so sampling-enabled inspection levels do not apply.

Key Resources

• Watch Perform Sampling Inspection with a Fixed Count Inspection Level Readiness Training

Role Information

You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
• Receiving Agent (ORA_RCV_RECEIVING_AGENT)
• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
• Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
• Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Edit Inspection Results (QA_EDIT_INSPECTION_RESULTS)

View Audit Details and Comments for Quality Issues and Actions in Side Panel

Use the side panel view on a quality issue or action to view audit details. You can see details for the object attributes that are configured for inclusion in the audit. Comments now appear in a side panel, instead of a dialog.

History Side Tab

Comments Side Panel

Watch a Demo

HISTORY SIDE PANEL 

Gain instant access to audit details for a specific issue or action without having to navigate to the audit reports. You can easily track when it was created, updated, or deleted.

COMMENTS SIDE PANEL

Collaborate quickly and effectively to facilitate important quality processes. Use the Comments side panel to communicate issue details, share possible root cause and resolution, and clarify tasks. The side panel shows you a consolidated, uncluttered view of all the user comments for a quality issue or quality action.

Steps to Enable

You must enable auditing of quality issues and actions to see audit log entries in the History side panel.

Key Resources

• Watch Audit and Comment Enhancements Readiness Training

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
• Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

View Inventory Lot Split, Lot Merge, and Lot Translation in Genealogy

When dealing with goods that are under lot control, there are numerous events that might require you to break, combine, or transform some or all of the goods in a specific lot. For example, a weather event causes damage to your warehouse and spoils only a portion of a lot. The damaged portion of the lot is still usable for some, but not all, of your manufacturing processes. Thus, you need to split this quantity from the original lot and assign new lot numbers to ensure your goods are designated properly for future use. Similarly, maybe you regularly combine multiple lots into a single vat before use in downstream processes. When you merge all of these lots into a single vat, you assign a new and unique lot number. Finally, in some industries, a chemical reaction process might require that you change the assigned lot number of an item when the process is complete. For example, let’s say you complete a work order for item 123 into lot A. After two weeks, the reaction process is complete, and the lot should change to lot B. This change indicates that the item is ready for the next step. The item itself hasn’t changed, and the additional overhead of a work order just to change the lot number isn’t desired. Additionally, you need the lot history retained. In these scenarios, a work order isn’t required. Now you can perform lot splits, merges, and translations within Oracle Inventory Management Cloud using REST APIs or file-based data import (FBDI).

For historical traceability, you can track the lot genealogy data from the lot splits, merges, and translations and view these lot genealogy records through the Review Product Genealogy page. In genealogy details, the parent-child genealogy relationships for a specific lot are displayed visually using directional arrows and new filters for lot composition and lot where used, so you can trace forwards and backwards between the source lot and resultant lots. In the transaction history, you can filter the timeline for these inventory transactions by type and click through to review the lot split, merge, or translate transaction details.

Genealogy Details - Lot Split

Genealogy Timeline - Lot Split

The new split, merge, or translate lots feature lets you change lots dynamically and track its genealogy, without the additional overhead of creating a work order or performing extraneous inventory transactions.

Steps to Enable

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

Tips And Considerations

• Refer to the Perform Lot Split, Merge, and Translate Using REST APIs and FBDI feature under Inventory Management for more information.

• You cannot use the Product Genealogy REST APIs and FBDI to import lot genealogy data resulting from inventory lot split, merge, and translate transactions.

• You can view lot split, merge, and translate transactions in the Inventory Transactions Real Time subject area, but not the Product Genealogy subject areas in Oracle Transactional Business Intelligence.

Role Information

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

• Privilege Name and Code: 
  • Get Product Genealogy by Service (CSE_GET_PRODUCT_GENEALOGY_BY_SERVICE_PRIV)
  • Manage Product Genealogy by Service (CSE_MANAGE_PRODUCT_GENEALOGY_BY_SERVICE_PRIV)

• Job Role Name and Code: 
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)