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 |
---|---|---|---|
09 FEB 2022 | Manufacturing | Preassign Output Lot Numbers to Work Orders | Updated document. Revised feature information. |
19 MAR 2021 | Created initial document. |
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:
- Click Navigator > My Enterprise > New Features.
- 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.
- 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.
- 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:
- Click Navigator > My Enterprise > Offerings.
- On the Offerings page, select your offering, and then click Opt In Features.
- On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
- 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.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
---|---|---|---|---|---|---|
Feature |
Report |
UI or |
UI or |
|
||
Create Supply in Back-to-Back Flows for Sales Orders That Include Project Details |
||||||
View Product Genealogy and Assets with Country of Origin or Project and Task Information |
||||||
Enable Dual Units of Measure in Process Manufacturing Work Definitions and Work Orders |
||||||
Update Lot Origination Date, Hold Until Date, and Expiration Date During Production |
||||||
Define Sample Quantity and Unit of Measure for Use in Ad Hoc Inspections |
||||||
Manage Security for Quality Issues and Actions Using REST APIs |
||||||
Project-Driven Supply Chain is an end-to-end, integrated solution across the Oracle Supply Chain Management and Oracle Project Management Cloud applications. This solution is designed to support various business processes of manufacturing and asset-intensive companies.
You can use the Project-Driven Supply Chain solution to manage your supply chain processes in the context of projects without creating separate organizations for each project. You can also capture supply chain costs as project expenditures.
Create Supply in Back-to-Back Flows for Sales Orders That Include Project Details
Use this feature to make sure the project expenditures that you see in inventory are accurate. If you create a sales order that includes project details in Order Management, then Supply Chain Orchestration will include your project details on the purchase order, transfer order, or work order. You can then receive or finish the item in project-specific inventory in your back-to-back flows.
Here's how it works.
- You create a sales order in Order Management cloud that includes project details.
- Order Management sends a supply request that includes project details to Supply Chain Orchestration.
- Supply Chain Orchestration gets a supply recommendation from Global Order Promising according to the sourcing rules that you set up for your back-to-back fulfillment for the item.
- Supply Chain Orchestration uses the supply recommendation to create a supply order.
- Supply Chain Orchestration sends a request to create supply for a purchase order, transfer order, work order, or on-hand reservation.
- Order Management sends the sales order details to Inventory Management.
- Inventory Management creates shipment lines to fulfill the item.
- Your back-to-back fulfillment uses a buy, make, transfer, or on-hand flow to create supply.
There are some unique differences for each of these flows.
Buy
- Supply Chain Orchestration creates a purchase requisition that includes project details from the sales order.
- Oracle Procurement converts the requisition into a purchase order with project details.
- Inventory Management receives the item and adds it to inventory that's specific for the project.
- You can't update the project attributes on a back-to-back purchase order.
Make
- Supply Chain Orchestration creates a back-to-back work order that includes project details form the sales order.
- Manufacturing completes the production and adds the item to the inventory that's specific for the project.
- You can't update the project and task on the work order that's reserved for the sales order, but you can update other project attributes for a work order that isn't released.
Transfer
- Supply Chain Orchestration sends a back-to-back transfer order request that includes project details from the sales order to Inventory Management.
- Inventory Management creates a transfer order that includes the project details, then interfaces the transfer order details to the warehouse.
- The warehouse manager uses the project details that are on the transfer order to identify the project-specific inventory to fulfill the item, then picks and ships the item.
- You can't update project attributes on the transfer order.
On-hand
- You can use the on-hand flow when on-hand supply is available in the fulfillment warehouse that you use for the back-to-back item.
- Global Order Promising sends a recommendation to Supply Chain Orchestration to reserve on-hand supply if on-hand inventory is found in the fulfillment warehouse.
- Supply Chain Orchestration uses project details from the sales order to reserve on-hand supply for the back-to-back order.
Inventory Management reserves the on-hand supply.
Use this feature to make sure the project expenditures that you see in inventory are accurate. Your purchase order, transfer order, or work order can now include project details from the sales order. Inventory Management uses these details to fulfill the item from inventory that's specific for the project, so you can accurately apply the cost that you incur for carrying inventory to each project.
If you don't use this feature, then Inventory Management uses common inventory to fulfill the item, and costs get averaged for all items that are in common inventory regardless of whether they are part of a project. This situation can result in project expenditures that aren't accurate because costs aren't specific to the project, and it might affect your project margins.
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 21D
Tips And Considerations
- Global Order Promising doesn't consider project details.
- Use the Supply Chain Availability promising mode when you set up your available-to-promise (ATP) rule for each item that you fulfill in a back-to-back flow.
- Consider excluding on-hand supply for your back-to-back item. This will help to avoid a reservation failure for your project-specific inventory.
Key Resources
- For more information on this feature, refer to the following guide, available on the Oracle Help Center:
- Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management
- Watch Execute Project-Specific Back-to-Back Fulfillment Release Training
Role Information
Users with any of the following predefined job roles are automatically able to participate in the project-driven supply chain process:
- Project Administrator (ORA_PJF_PROJECT_ADMINISTRATOR_JOB)
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
- Order Entry Specialist (ORA_FOM_ORDER_ENTRY_SPECIALIST_JOB)
- Order Manager (ORA_DOO_ORDER_MANAGER_JOB)
- Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)
- Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
- Inventory Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
- Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
- Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
- Buyer (ORA_PO_BUYER_JOB)Cost Accountant (ORA_CST_COST_ACCOUNTANT)
- Project Accountant (ORA_PJF_PROJECT_ACCOUNTANT_JOB)
- Project Manager (ORA_PJF_PROJECT_MANAGER_JOB)
- Project Billing Specialist (ORA_PJF_PROJECT_BILLING_SPECIALIST_JOB)
If you're maintaining your own configured job roles: no new privileges were introduced to support the Execution of Project-Specific Back-to-Back Fulfillment feature.
Search and View Product Genealogy with Parent Lot
When producing finished goods that are lot controlled, several companies need to group the material under a single lot, namely the parent lot. While the parent lot identifies the overall lot, the child lots are produced over a period of time and in manageable quantities.
You can now search for lots in product genealogy records based on the associated parent lot when the item is child lot enabled. You can view the parent lot in the lot information in addition to the transaction history of inventory transactions, discrete manufacturing work order operation transactions, and process manufacturing work order output transactions.
Genealogy Search Panel
Genealogy Information Dialog
As a result, you have greater visibility of parent lot information when viewing lot genealogy records.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Refer to the 20D feature Capture Parent Lot at Work Order Product Completion in Manufacturing Cloud for more information.
- Parent lot is not available in the Genealogy OTBI, but can be added through a cross-join with the appropriate Manufacturing OTBI and Inventory OTBI subject areas.
Role Information
- Users who are assigned any of these predefined job roles will be able to access this feature automatically:
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
- Users who are assigned configured job roles that contain these privileges will be able to access this feature:
- Review Product Genealogy (CSE_REVIEW_PRODUCT_GENEALOGY_PRIV)
View Product Genealogy and Assets with Country of Origin or Project and Task Information
In today's globally connected supply chain, knowing the country of origin of goods you import or export is critical for both internal and external reporting requirements. You also need the ability to perform your supply chain activities in context of projects whenever you have to produce contract-specific goods and services of a specific quality on a specified schedule and budget.
You can now search for lots and serials in product genealogy based on its country of origin or project and task, when country of origin or project-driven supply chain tracking are enabled for the applicable inventory organizations. You can view lot on-hand inventory balances, work order issued details, and customer sales order shipped details striped by these inventory attributes. In the genealogy transaction history for a specific lot or serial number, you can view a timeline of the inventory and manufacturing transactions and click a link to transaction details that specify the country of origin or project and task.
Review Product Genealogy UI
With product genealogy tracking by country of origin or project and task, you can maintain tight traceability of imported and exported goods as well as project-striped inventory and manufacturing.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
In the Information dialog box, the Country of Origin, Project, and Task columns are not displayed by default. You may have to manually add these columns to the table to view this information.
Key Resources
- For more information on the Project-Driven Supply Chain solution, refer to the Implementing Manufacturing and Supply Chain Materials Management guide (Oracle Help Center > Oracle Supply Chain Management Cloud).
-
For more information on Country Of Origin, refer to the Implementing Inventory Management guide (Oracle Help Center > Oracle Supply Chain Management Cloud).
Role Information
- Users who are assigned any of these predefined job roles will be able to access this feature automatically:
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
- Users who are assigned configured job roles that contain these privileges will be able to access this feature:
- Review Product Genealogy (CSE_REVIEW_PRODUCT_GENEALOGY_PRIV)
Enable Dual Units of Measure in Process Manufacturing Work Definitions and Work Orders
Certain manufacturing industries require dual units of measure (UOM) to track inventory in a stocking UOM and cost in a different valuation UOM, where the conversion between these UOMs can be fixed or variable depending on the item. Prior to this update, you could report the actual quantity in material and output transactions in both the primary and secondary UOMs. However, this flexibility did not extend to the work definition and work order, in which you specify the required quantity for an operation item or output in its primary UOM or another transactional UOM that is convertible to the primary UOM.
Using this feature, you can enter process manufacturing work definition and work order operation items and outputs in either the primary or secondary UOM. This allows you to view the equivalent secondary or primary quantity that is calculated based on the standard or item-specific UOM conversion.
Work Definition - Operation Item
Work Definition - Operation Output
Work Order - Operation Items
Work Order - Operation Outputs
The work definition and work order save only the primary quantity, and will recalculate and display the secondary quantity every time you view it in the Work Definition page, Work Order page, through REST services, and in OTBI. You can view the item and output quantities in dual UOMs to understand the planned values for actual material issue and output completion transaction reporting.
Watch a Demo
This flexibility and visibility in process manufacturing work definitions and work orders make it easier to create work definitions and work orders, using whichever UOM is most familiar.
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 21D
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 enter process manufacturing work definition and work order operation items and outputs in either the primary or secondary UOM. 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.
- Using the UI to create and update process manufacturing work definition and work order items and outputs in the primary UOM automatically displays the calculated quantity in the secondary UOM based on the item-specific or standard UOM conversion. Similarly, entering in the secondary UOM automatically displays the calculated quantity in the primary UOM.
- Regardless whether the defaulting control of the item is fixed, default, or no default, you cannot override the calculated primary or secondary quantity when entering process manufacturing work definition and work order operation items and outputs.
- You cannot simultaneously enter both the primary and secondary quantities in process manufacturing work definitions and work orders.
- In some use cases, another transactional UOM can be specified for a material quantity and 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 in a process manufacturing work definition and work order.
- Using file-based data import and REST services to create and update process manufacturing work definition and work order operation items and outputs dynamically maps the current attributes for quantity and UOM to either the primary quantity and primary UOM or secondary quantity and secondary UOM based on the item definition. The GET methods for the process manufacturing work definition and work order REST services retrieve the quantity and UOM separately for primary vs. secondary.
- The work definition report and work definition e-record continue to display the primary or transactional quantities.
- Work order creation, constrained-based supply planning, 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 Manufacturing Cloud in Update 21A for more information about reporting manufacturing transactions in dual UOMs.
Key Resources
Role Information
- Manufacturing Engineer
- Production Supervisor
Update Lot Origination Date, Hold Until Date, and Expiration Date During Production
Industries that have lot controlled products need to manage lot expiration and origination dates. This is even more critical with regulated industries. There may be a time lag between the creation of a lot number and the actual date of production of the lot thereby having the need to update the lot origination date to reflect the exact date of manufacture.
Until this update, whenever you generated a lot number in Inventory or Manufacturing, you were only able to update the lot origination date or lot hold until date using "Manage Lots" in Inventory.
With this update, you'll be able to update the lot origination date and lot hold until dates at the time of product completion in production. Updating the lot origination date at the time of product completion automatically updates the lot expiration date.
Lot Control Dates in Work Execution
Provides the flexibility to update lot control dates and manage accurate transaction records.
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 21D
Tips And Considerations
The expiration date and hold until date are defaulted based on the organization item setup.
Key Resources
- Watch Enhancements to Output Lot Management in Work Execution Readiness Training.
Role Information
- Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
Default Lot Number for Work Order Product Completion
Organizations use lot control for finished products to enable track and trace capability. Some organizations preassign the lot number of the products to be produced before the start of production and some organizations generate the lot numbers at the time of product completion. To simplify tracking, many organizations use the work order number as the lot number of the finished product being manufactured.
Until now, you were not able to automatically have the work order number as the product lot number.
With this feature, you are now able to default and use the work order number as the output product lot number.
You can set the plant parameter "Default lot number for production completion" to "work order number." Based on this setup, the system will automatically default the work order number as the lot number at the time of product completion. For process manufacturing work orders, the work order number is defaulted for the primary product. However, the user has the choice to use the default number or override the lot number during the transaction.
If you have also enabled the “Preassign Lot” indicator in work definition, the work order number is preassigned as the lot number at the time of work order creation.
Having the work order number as the product lot number enables traceability, especially for regulatory industries.
Steps to Enable
Plant Parameter
Default value is 'No default'; select 'Work order number' to default the work order number as the product lot number.
Tips And Considerations
Defaulting the work order number as the output product lot number is applicable with system generated as well as user specified work order number.
Key Resources
- Watch Enhancements to Output Lot Management in Work Execution 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)
Preassign Output Lot Numbers to Work Orders
Some manufacturers require that their product lots be defined ahead of production in order to facilitate product labeling and audit requirements for material tracking. The lot numbers are generated and assigned to specific work orders before the actual production starts. Until now, the lot number was only assigned when completing the product into inventory.
With this feature, you can preassign one or more lot numbers for a product in a manufacturing work order.
There are four aspects to this update:
- Setup
- Preassign lots at work order creation
- Complete products using the preassigned lots
- Preassigned lots in production reports
SETUP
Use the Preassign Lots indicator in work definitions for lot-controlled items to define which work definitions must have lots preassigned during work order creation and work execution. For automatic work definitions, the Preassign Lots indicator is selected, and can’t be changed.
Discrete Work Definition
Process Work Definition
PREASSIGN LOTS AT WORK ORDER CREATION
Based on your work definition settings, you will now see the “Lot Numbers” tab when you create the work order. You can preassign one or more lot numbers for the product.
For preassigning the lot numbers, you can generate the lot number, choose an existing lot from the list of values or specify your own user defined lot number.
You are also able to preassign the parent lot number, if the item is child lot enabled.
Discrete Work Order
For Process manufacturing work orders, if you have the "Preassign Lots" indicator enabled for the work definition, you will need to preassign the lots for the primary product. You can optionally preassign the lot numbers for other products and byproducts.
If you have also enabled the plant parameter “Default lot number for product completion”, the work order number will be automatically preassigned at the time of work order creation. For discrete manufacturing work orders, the work order number is defaulted as the lot number for the finished product and for process manufacturing work orders, the work order number is defaulted as the lot number for the primary product.
Process Work Order
You will be able to disassociate a preassigned lot number that hasn’t been used for product completion transactions. Once you have completed a product transaction for a specific preassigned lot number, you won’t be able to disassociate the lot number.
You are able to preassign product lot numbers for discrete manufacturing standard, non standard , transform work orders and process manufacturing work orders. You are able to preassign lots for work orders in unreleased, released and hold status.
COMPLETE PRODUCTS USING THE PREASSIGNED LOTS
After you have preassigned the lots to the work order, you will be able to complete only to the preassigned lots. The list of values will show only the lots that have been preassigned to the work order.
The preassigned lot number will be defaulted at the time of product completion, if you have preassigned only one lot number. If you have preassigned more than one lot number, you will be able to choose from the list of values at the time of product completion.
Work Order Product Completion
For product return transactions, you are able to return to any of the preassigned lot numbers.
Product Completion
You will be able to choose the preassigned lot number for performing ad hoc inspection transactions.
PREASSIGNED LOTS IN PRODUCTION REPORTS
Work order traveler and labels will display the preassigned lot numbers.
Traveler Report
You are able to preassign the lots using user interface, REST services and file-based data import.
Watch a Demo
Preassigning of the product lots to a work order can help accurately track product lots, their transaction history, and genealogy relationships throughout the production process.
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 21D
Tips And Considerations
- The values for the Parent Lot Number and Lot Expiration Date attributes aren't defaulted so must be manually specified. What's applicable for these attributes is dependent on the item setup for child lot control and user-defined expiration date.
- For automatic work definitions, the Preassign Lots indicator is selected and can’t be changed. Prior to reporting product completion transactions, you must preassign lot numbers in work orders that are based on the automatic work definition.
Key Resources
Role Information
- Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Manufacturing Engineer (ORA_WIE_MANUFACTURING_ENGINEER_JOB)
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
Define Sample Quantity and Unit of Measure for Use in Ad Hoc Inspections
Certain industries with a large number of transactions require batch inspection using physical samples rather than a visual inspection of individual units. These samples are drawn from a batch of material, for example inventory lot or manufacturing work order, and analyzed against specifications to determine its quality, usage, or next steps based on the test results. Each sample size is specified as a quantity in a unit of measure (UOM) that aligns with the item being inventoried or produced. Today, the inspection quantity is interpreted as the number of samples in an ad hoc inspection, and each sample represents one unit of the item.
In addition to the inspection quantity, you can specify the sample quantity and UOM as part of the definition of an inspection level to assign to an inspection plan and use for ad hoc inventory or work in process inspection using the UI. In the inspection level, you can also select the sample quantity UOM as a more granular, alternate UOM than the transactional UOM used in receiving, inventory, and manufacturing to facilitate sampling procedures and avoid a decimal quantity. For example, the inspector takes 2 samples of 10 milligrams for each sample against the mixing operation in a process manufacturing work order, which tracks production in kilograms. To enable this sampling setup, you define an inspection level based on a fixed count of 2 samples with a quantity per sample of 10 mg.
Inspection Level with Quantity per Sample
When performing an ad hoc inventory or work in process inspection using the Enter Inspection Details page, you can view the required sampling information, including the inspection quantity as the number of samples, quantity per sample and UOM, and total sample quantity and UOM. The acceptance and rejection of inspection results from the samples evaluated against the inspection plan specifications help determine the disposition and actions for the item and optionally lot.
Ad Hoc Inspection with Sample Quantities
Watch a Demo
With a clear definition of sample quantities and units of measure, you can better communicate and adhere to the appropriate sampling procedures for quality analysis.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- There is no change to the inspection quantity and UOM fields and the logic that determines the number of samples.
- You cannot use the quantity per sample and unit of measure without using an inspection plan and inspection level.
- You can leave the quantity per sample and UOM blank and enable sampling in the inspection level in order to inspect a sample size of discrete units.
- The sample quantity covers the material required to perform all of the inspection characteristics defined in the inspection plan.
- The physical tracking of the sample quantity in inventory or against a manufacturing work order is not supported with this feature.
Key Resources
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 this predefined job role are automatically able to access this feature:
- Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
- Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Edit Inspection Levels (QA_EDIT_INSPECTION_LEVELS)
Display Similar Interface for Quality and Change Objects
The edit page of a quality issue or action now displays a side panel view with additional tabs similar to the edit pages of change objects. The new side tabs replace the infotiles for Workflow, Affected Objects, Related Objects, and Similar Issues.

Quality Issue with Side Tabs
Streamline the layout and icon look and feel across Product Management Cloud to keep the user experience consistent and predictable.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Product Management No Longer Optional From: Update 21D
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 the quality issue and quality action pages with the updated user interface:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
Inspect a Preassigned Lot to a Work Order in Manufacturing
Before production, some manufacturers generate the product lot number that represents a specific production date or work order and track all production activities, including inspection, against this lot to facilitate product and quality sample labeling, master batch record, and lot traceability requirements. Previously, the step that enforces inline work in process (WIP) inspection at an operation precedes the product lot identification and completion into inventory. Only an ad hoc WIP inspection could capture the lot number after it is completed from the work order.
Now you can perform an ad hoc WIP inspection against a preassigned output lot at the operation where it is completed, as supported through the Enter Inspection Details page and REST services. You can inspect the preassigned lot for a product in a discrete manufacturing work order, and additionally for a co-product or by-product in a process manufacturing work order. Through inspection plan actions, the inspected lot can also be dispositioned with a new material status or extended through a business event and PaaS to initiate other lot actions.
Ad Hoc WIP Inspection with Preassigned Lots
As a result, ad hoc WIP inspection for a lot that is preassigned to the work order improves the lot traceability between manufacturing and inspection activities.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- You can preassign one or more lots and optionally its parent lot for a product in a discrete manufacturing work order or for any output in a process manufacturing work order.
- You can perform an inline WIP inspection against a preassigned lot at the last operation in the work order.
- Refer to the Preassign Output Lot Numbers to Work Orders feature under Manufacturing Cloud in Update 21B for more information about preassigning lots at work order creation and completing products using the preassigned lots.
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)
Manage Security for Quality Issues and Actions Using REST APIs
Add or remove users and roles from the Security tab of quality issues and actions using REST APIs. A new Security child resource is now added to the existing Quality Actions and Quality Issues REST resources.
Sample call to add the user product_manager to the Security tab:
curl -v -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -u <user>:<pwd> -X POST -d '{ "GranteeType" : "USER", "GranteeName" : "PRODUCT_MANAGER"}' https://<server>/fscmRestApi/resources/11.13.18.05/qualityActions/300100186703417/child/Security
Response showing that the user product_manager was added successfully:
{"GranteeType" : "USER","GranteeName" : "PRODUCT_MANAGER","LastUpdateDate" : "2020-11-11T02:32:36.426+00:00","LastUpdatedBy" : "QUALITY_ANALYST","CreatedBy" : "QUALITY_ANALYST","CreationDate" : "2020-11-11T02:32:36+00:00", ....
Once you add a user to the Security tab, the object becomes private and can only be accessed by users on the list.
Grant access to quality issues and quality actions from an external client, from Application Composer Groovy, or during legacy data import through REST. You can now add users and roles to the Security tab based on specific attribute values of the quality issue or action.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Review the changes to the Quality Issues and Quality Actions services, and update your REST client as desired.
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 the Security tab settings for quality issues and actions through REST:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
Use Object Hyperlinks to View Related Objects
Navigate between quality objects and configured objects (objects created using Application Composer). You can do this from a Dynamic Choice List attribute or from a subtab link.
Link to Quality Issue on Configured Object Subtab
Quality Issue Opened from Subtab Link
Likewise, you can navigate to the details of an Application Composer configured object from a quality issue or quality action.
Link to Configured Object from Quality Issue
Configured Object Opened from Link on Quality Issue
Watch a Demo
Experience seamless navigation between objects created in Application Composer and quality issues or quality actions. Extend the value delivered by your quality management organization to include additional processes such as risk reduction or new product introduction and qualification, using objects created in Application Composer.
Steps to Enable
To use this feature, you must first opt in to its parent feature: Display Similar Interface for Quality and Change Objects
Tips And Considerations
- When you navigate from a custom object to a quality issue or action, the object opens in a new dialog.
- When you navigate from a quality issue or action to a custom object, the object opens in a dynamic tab.
Key Resources
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)
- Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Quality action:
- Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)
- Review Corrective Action (ENQ_REVIEW_QUALITY_ACTION_PRIV)
- Quality issue:
- Manage Quality Issue(ACA_MANAGE_CORRECTIVE_ACTION_PRIV)
- Review Quality Issue (ENQ_MANAGE_QUALITY_ISSUE_PRIV)
- Custom object:
- Custom Objects Administration: ORA_CRM_EXTN_ROLE and
- Read access to custom object at a minimum.
- Quality action: