February Maintenance Pack for 20A
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 |
---|---|---|
28 FEB 2020 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Features Delivered Enabled
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. |
Action is Needed 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 |
|
||
Upload Manufacturing Work Definition and Work Definition Operation Attachments Using a SOAP Service |
Upload Manufacturing Work Definition and Work Definition Operation Attachments Using a SOAP Service
Manufacturers who migrate from or integrate with an external application require an efficient way to associate specific attachments with a work definition. For example, work instructions can be captured as an attachment file, text, or URL to provide key additional information for producing an item or performing a specific operation.
Currently, the tools for uploading or downloading work definitions, such as REST services, file-based data import (FBDI), and Application Development Framework Desktop Integration (ADFdi), don't allow you to include attachments when processing work definitions.
With this update, you can use the ERP Object Attachment SOAP service to perform the automatic, mass upload of attachments for discrete and process manufacturing work definitions. You can specify the input parameters for the payload of this service to upload attachments to existing work definitions at the header or operation levels.
By using a service-based approach to upload manufacturing work definitions and work definition operation attachments, the initial data load from an external source system or ongoing updates to work definitions can be streamlined into Oracle Manufacturing Cloud.
NOTE: This feature was also made available in a monthly update of 19D.
Steps to Enable
To get started, refer to the SOAP service definition provided in the Oracle Financials Cloud SOAP Web Services for Financials guide, available from the Oracle Help Center.
- Chapter: Business Object Services
- Section: ERP Object Attachment Service
Here are the specifics for uptaking the ERP Object Attachment SOAP service for the manufacturing business entities work definition and work definition operation.
Request Payload
Here's a table with request payload information.
Element Name | Type | Description |
---|---|---|
entityName |
String | Valid business entity names are: WORK_DEFINITION, WORK_DEFINITON_OPERATION. |
categoryName |
String | Document Category Name associated with the business entity. |
allowDuplicate |
String | Whether duplicate is allowed. Valid values are: Yes, No. |
attachmentRows |
List of elements, each containing the details of the attachment to upload. The details include the user keys, attachment type, and title. |
attachmentRows Attributes for Work Definition Header
Here's a table with attachmentRows Attributes for Work Definition Header information.
Attribute Name | Type | Description |
---|---|---|
UserKeyA |
String | Organization Code. |
UserKeyB |
String |
Item Number. |
UserKeyC |
String |
Work Definition Internal Name. |
UserKeyD |
String |
Keep this key with value #NULL. |
UserKeyE |
String |
Keep this key with value #NULL. |
AttachmentType |
String |
Valid values are: FILE, TEXT, URL. |
Title | String |
The title of the attachment. |
Content | String |
The following is an example. Your content may be different. URL: https://www.google.com Text: Use Lathe L123. File: Encode the source data to a Base64 string (Base64 encoding). |
attachmentRows Attributes for Work Definition Operation
Here's a table with attachmentRows Attributes for Work Definition Operation information.
Attribute Name | Type | Description |
---|---|---|
UserKeyA |
String | Organization Code. |
UserKeyB |
String | Item Number. |
UserKeyC |
String | Work Definition Internal Name. |
UserKeyD |
String | Version Number. |
UserKeyE |
String | Operation Sequence Number. |
Attachment Type | String | Valid values are: FILE, TEXT, URL. |
Title | String | The title of the attachment. |
Content | String | The following is an example. Your content may be different. URL: https://www.google.com Text: Use Lathe L123. File: Encode the source data to a Base64 string (Base64 encoding). |
Sample Payload for Work Definition Header
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
<soapenv:Header/>
<soapenv:Body>
<typ:uploadAttachment>
<typ:entityName>WORK_DEFINITION</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>M1</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>AS54888</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>ORA_MAIN</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>?</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>?</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>File1</erp:Title>
<!--Optional:-->
<erp:Content>Use Lathe L123.</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>
Sample Payload for Work Definition Operation
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
<soapenv:Header/>
<soapenv:Body>
<typ:uploadAttachment>
<typ:entityName>WORK_DEFINITION_OPERATION</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>M1</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>AS54888</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>ORA_MAIN</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>1</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>10</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>Att001</erp:Title>
<!--Optional:-->
<erp:Content>Use Lathe L123.</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>
Tips And Considerations
The content for attachment of type FILE must be provided in the Base64 encoding.
Role Information
- Privilege Name and Code:
- FSCM Load Interface Administration (ORA_FUN_FSCM_LOAD_INTERFACE_ADMIN_DUTY)
- Manage Work Definitions (WIS_MANAGE_WORK_DEFINITIONS_PRIV)
- Job Role Name and Code:
- Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
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 DEC 2019 | 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.
Give Us Feedback
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
Optional Uptake of New Features (Opt In)
Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users in a couple of ways:
Access the Opt In page from the New Features Work Area
- Click the Navigator, and then click New Features (under the My Enterprise heading)
- On the New Features page, select the offering that includes new features you’d like to review
- Click Go to Opt In for any feature you want to opt in
- On the Edit Features page, select the Enable option for the feature, and then click Done
or... Access the Opt In page from the Setup and Maintenance Work Area
- Click the Navigator, and then click Setup and Maintenance
- On the Setup page, select your offering, and then click Change Feature Opt In
- On the Opt In page, click the Edit Features icon for any area that includes features you want to opt in
- 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.
- Click Done.
Opt In Expiration
Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.
Column Definitions:
Features Delivered Enabled
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.
You 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. If you’re a manufacturing or a service company delivering goods and services on a project, you also want to invoice your customers based on terms of the contract, rather than the cost of goods and services.
Project-Driven Supply Chain is an end-to-end, integrated solution across supply chain and project management cloud applications. This solution supports business processes of both manufacturing and asset-intensive companies.
- Manufacturers can enhance their market share and profitability by offering servitized sales of differentiated products.
- Contract manufacturers can increase their margins by serving multiple contracts from the same plant without having to maintain project-specific organizations.
- Asset-intensive companies can use this solution to control project risks when building assets and also comply with regulatory requirements.
You can use the Project-Driven Supply Chain solution to manage your supply chain operations without having to create separate organizations for each project and capture supply chain costs as project expenditures.
In this update, the Project-Driven Supply Chain solution is comprised of 11 features. The first nine features are part of the Oracle Supply Chain Management Cloud applications, and the last two features are part of the Oracle Project Management Cloud applications:
- Segregate and Manage Project-Specific Inventory
- Receive Project-Specific Supply
- Pick Project-Specific Inventory
- Ship Project-Specific Inventory
- Transfer Project-Specific Inventory
- Purchase Project-Specific Inventory
- Execute Project-Specific Manufacturing
- Perform Project-Specific Maintenance
- Execute Project-Striped Supply Chain Without Project Financials
- Capture Project-Driven Supply Chain Material and Manufacturing Costs (Oracle Project Management Cloud feature)
- Capture and Capitalize Project-Driven Supply Chain Asset Maintenance Costs (Oracle Project Management Cloud feature)
The ability to plan and execute supply chain operations by project enables your business to serve more than one project from the same set of plants and warehouses while maintaining project-specific material visibility and project-specific costing. The Project-Driven Supply Chain solution also enables you to track your overall schedule and budget and comply with the terms of contracts.
The Project-Driven Supply Chain features in Oracle Manufacturing Cloud are described in this document.
Execute Project-Specific Manufacturing
When you use a manufacturing plant and its resources to serve multiple projects, executing each work order in context of a project is essential to ensure that the right material and resources are used and manufacturing costs are allocated to the right project. You also want to ensure that only the eligible raw material and subassemblies are used in project-specific manufacturing work orders and completed products are put away into project-specific inventory.
With this feature, you can:
- Create project-specific manufacturing work orders
- Issue components and subassemblies from common and project-specific inventory to the work order
- Complete the work orders into project inventory
- Send work order transactions, along with their costs, to the project
- Purchase outside processing services for completing work order operations
- Report project-specific orderless transactions
With this feature, you can compartmentalize your manufacturing operations to serve multiple projects from a common set of resources in a plant. It enables you to service multiple customers on projects, manufacture products that require deal-specific research and development or services, or manufacture assets for corporate use.
Here's what the project-specific manufacturing execution flow looks like:
- Create a manufacturing work order with project details. (Navigation: Work Execution > Manage Work Orders > Edit Work Order)
Create Project-Specific Work Order
- Issue material for a work order from either common or project-specific inventory. (Navigation: Work Execution > Report Material Transactions)
Report Material Transactions for a Project-Specific Work Order
- Complete products into project inventory and review the completed transaction. (Navigation: Work Execution > Review Dispatch List, Navigation: Inventory Management > Review Completed Transactions)
Complete Products Into Project-Specific Inventory
Review Completed Transaction Details
- Review and send manufacturing costs to projects. (Navigation: Supply Chain Execution> Cost Accounting > Review Cost Accounting Distributions)
Review Manufacturing Costs with Project Details
- Review and manage costs in projects. (Navigation: Projects > Costs > Manage Project Costs)
Review and Manage Project Costs
You can import costed and accounted transactions from supply chain as project expenditures into Oracle Project Management Cloud (PPM) and view there via the Manage Project Costs UI. If the cost incurred against the project is a billable cost, you can bill your customer based on the percentage of completion or milestones achieved on the project. If it is a capitalizable cost, your can proceed to execute the capitalization flow. You may choose to also allocate costs to other projects, project tasks or accounts as appropriate. For additional details refer to Whats New document for the Capture Project-Driven Supply Chain Material and Manufacturing Costs and Capture and Capitalize Project-Driven Supply Chain Asset Maintenance Costs features the Oracle Portfolio Management Cloud What's New, update 20A.
Watch Demos of:
- The Manufacturing Flow
- The Inventory Management Flow
- The Cost Accounting Flow
- The Project Portfolio Management Flow
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
Feature: Project-Driven Supply Chain
After you opt in, you must perform additional steps to enable project-driven supply chain. For instructions, refer to the Steps to Enable section in the Segregate and Manage Project-Specific Inventory feature, available in the Oracle Inventory Management Cloud What's New, update 20A.
Tips And Considerations
If your business doesn't require project-specific manufacturing costs to be sent to project financials, then define project types in Project Management and identify the which project types to exclude from cost collections in Supply Chain Management.
- For instructions, refer to the Steps to Enable section in the Execute Project-Striped Supply Chain Without Project Financials feature, available in Oracle Inventory Management Cloud What's New, update 20A.
If your business requires manufacturing costs to be sent to project financials, and you have a need to use item or resource specific expenditure types, then define and set up default expenditure types for items and resources.
The following screenshots show the set up of default expenditure types for items and resources:
Set Up Default Expenditure Type for Items
Set Up Default Expenditure Type for Resources
For ease in picking material for project-specific manufacturing work orders, consider defining pick slip grouping rules by project number and task number.
And finally, based on your business requirements, you can create project-specific accounting distributions using project attributes that are available as accounting sources.
Key Resources
For more information on this feature, refer to the following guides, available on the Oracle Help Center:
- Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management
- Oracle Supply Chain Management Cloud: Using Manufacturing
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)
- Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
- Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)
- Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
- Buyer (ORA_PO_BUYER_JOB)
- Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
- Inventory Manager (ORA_INV_WAREHOUSE_MANAGER_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 Execute Project-Specific Manufacturing feature.
Execute Project-Striped Supply Chain Without Project Financials
When you perform supply chain operations across multiple contracts, you may need to segregate your supply chain inventory and activities by project simply to avoid commingling of materials and other costs. In these cases, you do not need to maintain budgets, commitments, costs, and revenue in a project entity. You manage your supply chain cost within supply chain and invoice from order management upon shipment.
With this feature, you can:
- Segregate and value inventory by project and task.
- Perform inventory and warehouse operations by project and task.
- Procure material by project and task.
- Manufacture by project and task.
- Maintain assets by project and task.
- Manage all supply chain costs in supply chain without sending them to projects.
- Generate invoices from supply chain.
This feature will enable you to compartmentalize your supply chain operations to serve multiple projects from a common set of resources in an organization.
You can set up and project types for exclusion from cost collection. Using project types that are excluded from cost collection does the following:
- Project expenditure is not interfaced to Oracle Project Management Cloud from Oracle Cost Management Cloud.
- Commitment is not recorded in Oracle Project Management Cloud.
- Accounting of cost of goods sold happens within Cost Management and is not issued to the project. (If the project type associated to the project is not excluded from cost collection, then a debit is recorded using a new accounting line type called Project Clearing, to facilitate charging the shipment cost as expenditure to the project.)
You can set project and task as additional valuation structure attributes to track costs and value inventory balances. Project information is visible while reviewing cost accounting distributions and in cost accounting subject areas within Oracle Transactional Business Intelligence. Project attributes can be used as an accounting source in subledger accounting based on your business need.
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
Feature: Project-Driven Supply Chain
After you opt in, you must perform additional steps to enable project-driven supply chain. For instructions, refer to the Steps to Enable section in the Segregate and Manage Project-Specific Inventory feature, available in the Oracle Inventory Management Cloud What's New, update 20A.
In addition, you may want to exclude specific project types from cost collection. To do so, perform these steps:
- In the Setup and Maintenance work area, go to the Manage Project Type Cost Exclusions task.
- Offering: Manufacturing and Supply Chain Materials Management
- Functional Area: Facilities
- Task: Manage Project Type Cost Exclusions
-
Select the project types you want to exclude from cost collection and move them to the Cost Excluded list.
Manage Project Type Cost Exclusions
3. Click Save and Close.
Tips And Considerations
- If you enable project-based tracking, setup your valuation structure in cost management to include project and task to enable tracking inventory values by project and task.
- Set up new cost profiles with a valuation structure that includes project and task. You cannot modify existing cost profiles with the new valuation structure. If your setup of a new cost profile includes a valuation structure that contains project and task, you can update the new cost profile on your item cost profiles only if the item cost profile is not already used in transactions.
Key Resources
- For more information, refer to Oracle Supply Chain Management Cloud: Using Supply Chain Cost Management, available on the Oracle Help Center:
Role Information
Users with the following predefined job role are automatically able to participate in the project-driven supply chain process:
- Cost Accountant (ORA_CST_COST_ACCOUNTANT)
If you're maintaining your own configured job roles: no new privileges were introduced to support the Execute Project-Striped Supply Chain Without Financials feature.
Add Operations to Work Orders in Released Status
Production processes go through a standard sequence of operations to produce a finished product. However, sometimes capacity changes, quality issues or changes in demand may warrant changes to the standard sequence. For example, if a quality issue is found after a product is completed to inventory, you may want to move the item back to the original work order that produced it, add an operation for rework, and then complete it back to inventory. Or, when a customer requirement changes or a customer cancels an order, you may need to add some additional operations to an open work order to adjust to the change in demand.
Until now, you were able to add only an optional operation to a work order in released status.
With this update, you can now add a count point, or an automatically transact operation to a work order in released status.
- You can add an in-house operation or an outside processing operation.
- You can add a serial-tracked operation.
- You can add a standard or nonstandard operation.
- You can add a new operation either as a first operation, intermediate operation, or the last operation.
- If you need to add a new operation prior to an existing completed operation, you need to reverse the full quantity of the operation to ready status and then add the new operation prior to that operation.
- If you need to add an outside processing operation immediately before an existing outside processing operation, you need to ensure the subsequent outside processing operation has the generate shipment indicator disabled and the supplier details are provided.
- After you complete the last operation partially or fully, you will not be able to add any operation after that operation.
- If you complete a work order and still need to add operation, you can reverse the last operation to ready status and can add an operation prior to the last operation.
The addition of a new operation does not automatically reschedule the work order. You must initiate midpoint rescheduling to update the new start and end dates of the work order.
Adding a new operation to a released work order provides shop floor control and enables complete traceability. You can also accurately track additional costs incurred due to a canceled sales order.
To add operations to a released work order, you use the Add Operation icon, the + icon.
New Operation Added Using the '+' Icon
Ready quantity (10 Each) moved from the previous operation sequence 20 to the newly added count point operation at operation sequence 1.
Ready Quantity Shown at the Newly Added First Count Point Operation
You can also add supplier operation before or after an existing supplier operation. If you need to add an outside processing operation, you must ensure that the subsequent outside processing operation has the generate shipment check box disabled, and the supplier details are provided. Also, you can't add a new count point or automatically transact operations between consecutive supplier operations.
New Supplier Operations Added to the Work Order
You can add new operations to a serial tracked work order in released status. If the newly added operation is prior to the serial start operation, it will not be serial tracked. If the newly added operation is after the serial start operation, it will always be serial tracked.
New Operations Added to the Serial Tracked Work Order
Watch Demos:
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 20C
Tips And Considerations
New operations can be added to all types of work orders in released status. This is supported through UI and REST services only.
Key Resources
Role Information
Users with the following existing responsibility can use this feature.
- Job Role Name and Code:
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
Country of Origin in Supply Chain Management
Establish and maintain the country of origin of items within your enterprise systems and throughout the supply chain lifecycle.
Track Country of Origin During Production
In today's globally connected supply chain, you can import material for use in manufacturing processes, import finished goods that you then sell to your customer, or export products for use in other enterprise's downstream operations. In any of these scenarios, knowing the country of origin for goods you import or export to is critical for both internal and external reporting requirements.
You can now specify the country of origin during the following manufacturing transactions:
- manual material issue or returns
- backflush material issues or returns using detailed complete
- product completion and returns using detailed complete of the last operation on a discrete work order
- product output completions and returns on a process manufacturing work order
- orderless completions and returns
Track Country of Origin During Production Transactions
When you quick complete an operation, all the components that are backflushed will be issued without a country of origin.
You can perform these transactions using the user interface, FBDI, and REST services.
Specifying the country of origin when performing manufacturing transactions, aids reporting compliance on import and export documents. Customers can also now report country of origin when using trade agreements or other trade programs, and identify risk in supply chain sourcing as tariffs change.
Watch a Demo
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Manufacturing and Supply Chain Materials Management
Feature Name: Country of Origin in Supply Chain Management
After you opt in, you must also enable individual inventory organizations to track by country of origin. For instructions, refer to the Steps to Enable section in the Report and Track Country of Origin for Inventory Transactions and On-Hand Balances feature, available in the Oracle Inventory Management Cloud What's New, update 20A.
Key Resources
Role Information
Users who are provisioned with the following job roles will automatically be able to use this feature:
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
Include Additional Attributes for Quality Objects in REST Services and Groovy Expressions
Include additional attributes for quality issues and quality actions when you work with REST services and Application Composer. In addition to ID, you can now use a user-friendly name and code for Workflow Template, Status, Organization, and Type. With REST or Groovy, these attributes can be read or written to execute event triggers such as changing a workflow status.
Steps to Enable
You don't need to do anything to enable this feature.
Generate Configuration Report to View Configuration
Application Composer supports configurations such as additions or enhancements to core features, or Groovy code that executes events such as validation rules or triggers to other objects or fields. In Metadata Manager, click Generate Configuration Report to view a summary of configurations made to layout details against a published sandbox. Reports can be exported to HTML or Excel and are user and time stamped.
Use the Configuration Report to view configuration modifications across the following:
- Standard and Custom Objects
- Global Functions
- Custom Relationships
- Standard Fields or Custom Fields
- Validations,
- Object Functions
- Triggers
- Object Workflows
- Dynamic Layouts
You can use this detailed report to help create an efficient and consistent implementation experience, with quicker navigation to resolve issues created with groovy scripts or other configurations.
Configuration Report Showing Custom Fields Added to Requirements
Steps to Enable
You don't need to do anything to enable this feature.
Increase Sampling Size to 100% Inspection for a Receipt Line
When acceptance sampling is employed to reduce the cost of incoming inspection for a good supplier, organizations want the flexibility to determine when the entire receipt is deemed acceptable or unacceptable based on the initial sample(s) as well as the option to continue inspecting the rest of the received material. With this feature, you can switch from sampling to 100% inspection of a receipt line if a visual check or inconclusive results indicate that further inspection is required. By inspecting every unit received, you can separate defective or nonconforming material by splitting the receipt line into the accepted quantity to put away into inventory and the rejected quantity to return to supplier or quarantine for material review. This capability enables your organization to tighten incoming quality control to fully inspect materials with high value or higher probability of defects, while minimizing the risk of accepting bad materials or rejecting good materials from suppliers.
A new "Inspect All" button has been added to the Inspection Results page:
Inspect All Button
The button will appear if you are performing an inspection against an inspection plan where sampling is enabled. Once you press the button, additional samples will be created so that the number of samples will be equal to the receipt line quantity. You will then be able to enter results values against all of the material received on that line.
The Inspect All functionality is also supported through the use of the Inspection Events REST service.
Watch a Demo
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
NOTE: This feature is not enabled for high volume receipts, where the receipt line quantity is greater than 800.
Key Resources
Role Information
To use this feature, the following roles are required:
- Job Role Name and Code:
- Receiving Agent (ORA_RCV_RECEIVING_AGENT)
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
Inspect Inventory Prior to Serial Number Generation
To minimize the cost of serialization, some companies choose to serialize each unit of an item at the point of use and want the flexibility to skip serial number entry at inspection and require it later when performing material transactions. With this feature, you can now inspect material in inventory without specifying serial numbers for the units inspected if the method of serial generation requires entry at sales order, transfer order or work order issue. Once serialization occurs, you can also record serial numbers for inventory inspection to track the quality of each individual serial number. As a result, the quality inspection process becomes more adaptive to support the serialization strategy at your company.
Samples and Serials radio buttons have been added to the Enter Inspection Details page:
Samples or Serials Radio Buttons
These buttons will be made available when you create an Inventory or Ad Hoc Work In Process inspection of an item with a serial generation value set to “Entry at sales order, transfer order, or work order issue” and “Entry at inventory pick.” You can specify if results should be entered against samples or serial numbers based on whether serial numbers have been assigned to the material.
This new functionality is also supported through the use of the Inspection Events REST service.
Watch a Demo
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
To use this feature, the following roles are required:
- Job Role Name and Code:
- Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
Mark Inspection Characteristic as Optional or Default Specification Target Value for Result Entry
For inspections with a long list of characteristics and high number of samples, it is time-consuming for quality inspectors to enter results for every characteristic in order to progress the inspection samples from pending to accept or reject. Whereas, certain test scenarios only require a subset of inspection characteristics to determine conformance to quality specifications, while the rest of the inspection characteristics are either skipped or entered selectively.
With this feature, you can now identify which inspection characteristics are considered optional for results entry or default their result value from the specification target in the inspection plan. With optional characteristics, you can define the full list of quality specifications in an inspection plan and distinguish the mandatory vs. non-mandatory set of requirements. This flexibility allows you to conditionally enter results and evaluate them to determine the inspection disposition of acceptance and/or rejection. In addition, results defaulted from the specifications help streamline data entry of pass/fail data by allowing you to override specific results to record failures.
As a result, data collection against the inspection plan and across samples becomes a quicker task of required and exception reporting, reducing the overall cost related to inspection activities.
"Optional" and "Default Target Value" checkboxes have been added on the Inspection Plan Specifications page:
Optional and Default Target Values Checkboxes
In addition, Select All and Deselect All actions are available from the Actions menu for both the optional and default target value checkboxes.
If you check the "Optional" checkbox for a characteristic, the sample disposition can be determined and the inspection completed even if you have not entered a value has been entered for that characteristic. If you do enter a result value for an optional characteristic, the value will be included in the determination of the sample disposition.
If you check the "Default Target Value" checkbox for a characteristics, the specification target value will be used as a default when you are entering result values during an inspection. All defaulted result values will be marked as pass, but you will be able to override the defaulted value and the value entered will be used to determine pass or fail.
The optional and default target value flags are also supported through the use of the Inspection Plan and Inspection Events REST services.
Watch a Demo
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
To use this feature, the following role is required:
- Job Role Name and Code:
- Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
Set Up Quality Object Types in Setup and Maintenance Work Area
Set up quality object types directly from the Setup and Maintenance work area. You now have all major configuration tasks for quality management in the same place, and you can also migrate your data configuration from one environment to another with ease.
To configure quality object types, use the two additional tasks appearing in the Quality Issue and Action Management functional area, under the Product Management offering:
- Manage Quality Issue Types
- Manage Quality Action Types
New Tasks in Quality Issue and Action Management Functional Area
Steps to Enable
To create and enable new Quality Issue and Quality Action types, go to the Setup and Maintenance work area, select the Product Management offering, and then click the Quality Issue and Action Management functional area. Then click either the Manage Quality Issue Types link to create and manage quality issues, or click the Manage Quality Action Types link to create and manage quality actions.
Key Resources
Use the Audit Report to View Changes to Quality Issue Attributes and Attachments
Provide an audit trail for any changes made to a quality issue. This is an important function of quality system controls for regulated industries. You can access the audit report through the side panel on the right. In the report, you can see all changes to attributes or attachments of a quality issue, including production exceptions. The report records changes made through the user interface and through REST services, along with details of who performed each change and when. The audit report promotes accountability, enables traceability, and provides adherence to regulatory compliance across quality issue transactions.
Steps to Enable
To configure the attributes in audit trail:
- Navigate to the Manage Audit Policies task in the Setup and Maintenance work area.
- Click the Configure Business Object Attributes button.
- From the Product list, select Quality Issue and Action Management.
Tips And Considerations
You can access the audit reports through the Manage Audit Report user interface. Please see Audit Lifecycle Feature: AuditTrail for an introduction of the Audit framework.
Key Resources
Role Information
To use this feature, the following roles and privileges are required:
- Job Role Name and Code:
- Application Administrator
- Internal Auditor
- Quality Analyst
- Privilege Name and Code:
- Manage Audit Policies (FND_MANAGE_AUDIT_POLICIES_PRIV)
- Manage Audit Reports (FND_VIEW_AUDIT_HISTORY_PRIV)
- Manage Audit Reports (ORA_FND_INTERNAL_AUDITOR_JOB)
View Quality Issues and Actions for an Item in the Product Information Management Work Area
View quality issues and quality actions related to an item from the Manage Items > Edit Item page in the Product Information Management work area. You can now directly and easily access quality issues and actions for an item in the context of the organization from the additional quality tab of the item page. You can also view the quality issues and actions of a child organization item.
Quality Issues and Actions for Child Organization Item
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Quality issues and actions are only displayed if an affected object for the issue or action is for the same item organization combination.
Key Resources
Role Information
To use this feature, the following privilege and role is required:
- Job Role Name and Code:
- Product Manager (ORA_EGP_PRODUCT_MANAGER)
- Privilege Name and Code:
- View Item (EGP_VIEW_ITEM_PRIV)
Integrate and Extend Quality Management Using REST Services
Expand REST Services to Manage Relationships for a Quality Issue or Quality Action
REST services enable external applications to access the quality issue and quality action relationships. You can link to other related objects like ideas, requirements, and change orders, to create a digital thread that weaves an integrated view of other processes related to a quality issue or action.
The new services include:
- Quality Issues > Relationships
- Quality Actions > Relationships
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.
Key Resources
Expand REST for User-Defined Quality Issue or Quality Action Number
Quality processes may require the transfer of data from legacy or other systems to Oracle Quality Management Cloud. You can now add the quality issue and quality action number through REST APIs, when required, if the respective number generation method per type allows it.
If the Type attribute is set to:
- User-Defined Number - the number attribute is mandatory through REST.
- Sequence-Generated Number - the number attribute is a read-only through REST.
The updated REST APIs include:
- Quality Issues > Create an issue
- Quality Actions > Create an 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.
Key Resources