This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Module | Feature | Notes |
---|---|---|---|
16 SEP 2022 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
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.
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.
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, Update, and Get Inspection Characteristics Using a REST Service |
||||||
Create Problem Reports and Corrective Actions Directly from Engineering Items |
||||||
Enable Deferred Electronic Records and Electronic Signatures for Manufacturing Work Order Release |
||||||
Correct REST API Transaction Errors Using the ADFdi Interface |
||||||
Qualify Operators When Assigning Work or Reporting Labor Usage |
||||||
Synchronize Process Manufacturing Work Orders with IoT Production Monitoring |
||||||
Manage Production Calendar Shift Exceptions Using a REST service |
||||||
Create, Update, and Get Inspection Characteristics Using a REST Service
Companies need an efficient way to set up quality inspection characteristics, so that they can be used in inspection plans or directly added to inspections to facilitate the reporting of results. Once inspection characteristics are defined, they may also need a way to get inspection characteristic details to integrate with an external system or device for test measurement or data collection. Now you can use an Oracle REST API to manage and view inspection characteristics stored in Oracle Fusion Cloud Quality Management to enable these integration scenarios.
Use the Inspection Characteristics REST service to do the following:
- Create or update an inspection characteristic for any source object and data type supported, including the value set if applicable
- Add and delete attachments to an inspection characteristic
- Associate an inspection characteristic with one or more characteristic groups
- Enable or disable an inspection characteristic
- Get inspection characteristics and their details
With the Inspection Characteristics REST service, you can streamline the initial data load or ongoing updates to inspection characteristics and easily share this information with an external system or through a mobile or connected device.
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.
Tips And Considerations
-
You can consider taking the opportunity for data cleansing and data synchronization before using this REST service to migrate or integrate inspection characteristics, since they serve as the basis for inspection plans and inspection results.
-
You can update an inspection characteristic under certain conditions. Refer to the Considerations for Updating Inspection Characteristics in the Oracle Help Center.
-
You can't delete an inspection characteristic using a REST service. Instead, you can use this REST service to disable an inspection characteristic.
-
You can leverage the Visual Builder Cloud Service add-in for Excel with the Inspection Characteristics REST service to mass load inspection characteristics through a spreadsheet. Refer to the Oracle Visual Builder Add-in for Excel available in the Oracle Help Center.
Key Resources
- Watch Create, Update, and Get Inspection Characteristics Using a REST Service Readiness Training
- Refer to Inspection Characteristics in the Oracle Help Center for more information about creating, updating, and disabling inspection characteristics.
- See REST API for Oracle Fusion Cloud SCM on the Oracle Help Center. In the REST documentation, the Inspection Characteristics resource is available in the Manufacturing section.
Role And Privileges
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 Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
- Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Edit Characteristics (QA_EDIT_CHARACTERISTICS)
Create Problem Reports and Corrective Actions Directly from Engineering Items
With this update, you can:
- Create a problem report and corrective action from an engineering item
- Create a corrective action from a problem report.
You can now access these two new actions directly from the Actions menu of an engineering item:
- Create Problem Report
- Create Corrective Action
And one new action directly from the Actions menu of a problem report:
- Create Corrective Action
These new actions are available for both internal users as well as supplier users.
Create a Problem Report and a Corrective Action from an Engineering Item
Here's what happens when you create a problem report or a corrective action from an engineering item:
- The object opens in a new dynamic tab within the Product Development work area for editing for an internal user.
- For a supplier user, the page reloads with the newly created object.
- It's automatically linked to the item and added to its Quality tab.
- Organization data is carried over from the item.
Create a Corrective Action from Problem Report
Here's what happens when you create the corrective action from a problem report:
- You get additional options of copying over the descriptive flexfields, attachments, relationships, and tasks from the problem report. For affected objects, you get the option to copy over the affected objects and their descriptive flexfields to the newly created corrective action.
- The object opens in a new dynamic tab within the Product Development work area for editing for an internal user.
- For a supplier user, the page reloads with the newly created object.
- It's automatically linked to the problem report in the relationships tab.
- Organization data is carried over from the problem report.
This feature enables users who don't often access the Quality Management work area to create problem reports and corrective actions directly from the engineering item record in the Product Development work area. A visible link is created automatically between the problem report or corrective action and the item. When creating a corrective action from a problem report details are easily copied through a selection of options.
Easy access to the Create actions simplifies training and drives efficiencies in reporting quality events as they occur.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Oracle Fusion Cloud SCM: Using Product Development guide, available on the Oracle Help Center.
Role And Privileges
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 along with the following privileges can access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Users who are given any of these functional privileges can view items.
- View Item (EGP_VIEW_ITEM_PRIV)
- Manage Item (EGP_MANAGE_ITEM_PRIV)
For Internal Users:
- Problem Report:
- Create Change Order (EGO_CREATE_CHANGE_ORDER_PRIV)
- View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV)
- Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)
- Corrective and Preventive Action:
- Create Change Order (EGO_CREATE_CHANGE_ORDER_PRIV)
- View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
- Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)
To provide granular View or Manage access to the user for problem reports and corrective actions, you must provide the Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) privilege along with the object-specific View or Manage privileges.
To view the Product Development work area, you must have the Monitor Product Development privilege (ACA_MONITOR_PRODUCT_DEVELOPMENT_PRIV).
For Supplier Users:
- Problem Report:
- Create Change Order (EGO_CREATE_CHANGE_ORDER_PRIV)
- View Problem Report in Supplier Portal (ACA_VIEW_PROBLEM_REPORT_SUPPLIER_PORTAL_PRIV)
- Manage Supplier Problem Report (ACA_MANAGE_SUPPLIER_PROBLEM_REPORTS_PRIV)
- Corrective and Preventive Action:
- Create Change Order (EGO_CREATE_CHANGE_ORDER_PRIV)
- View Corrective Action in Supplier Portal (ACA_VIEW_CORRECTIVE_ACTION_SUPPLIER_PORTAL_PRIV)
- Manage Supplier Corrective Actions (ACA_MANAGE_SUPPLIER_CORRECTIVE_ACTIONS_PRIV)
To provide granular View or Manage access to the user for problem reports and corrective actions, you must provide the Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) privilege along with the object-specific View or Manage privileges.
If you're using a user-defined role, then the role must be assigned a data security policy with the following predefined condition to have access to the item change.
-
Predefined condition: "Access the item change for table EGO_ENGINEERING_CHANGES_B for the item changes they created"
Selected Quality Management Bug Fixes in This Update
This update includes some bug fixes that can change the way Oracle Quality Management works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.
Copy Relationships
In previous updates, when you saved a problem report as a change order, the relationships weren’t copied over, even if you selected the option to copy relationships.
With this update, the issue is fixed.
Oracle reference: 34109293
Steps to Enable
You don't need to do anything to enable this feature.
Enable Deferred Electronic Records and Electronic Signatures for Manufacturing Work Order Release
Companies in regulated industries must keep detailed records of their product manufacturing processes in accordance with the United States Food and Drug Administration (FDA) regulation on electronic records and signatures called 21 Code of Federal Regulations (CFR) Part 11. Oracle E-Signatures and E-Records is a configurable framework for securely capturing, storing, retrieving, and printing electronic records and signatures.
While production transactions for materials, operations, outputs, and orderless transactions are supported with e-records and e-signatures today, there is no formal approval process before releasing a work order. With this feature, you can enforce the generation of an e-record and capture of e-signatures when a work order is initially changed to the Released status through the following pages:
- Edit Work Order
- Manage Work Orders
The manufacturing work order e-record contains the following information as applicable in the work order:
- Work order header and details
- Transactional item attributes if it is a configured product
- Preassigned product lot and serial details
- Project details
- Operation details, including operation items, operation outputs, operation resources, and documents
- Material reservations
- Production exceptions
- Attachment details
E-Record for Work Order Release
Using a deferred approval process with notifications, the work order is held in a Pending Approval status until the approvals are obtained. Depending upon the outcome of the approval, the work order is saved in the Approved status or rolled back to the previous status.
Work Order in Pending Approval Status
Notification for Approval of Electronic Record
Controlling the release of a work order through the e-record and e-signature process ensures adherence to specifications and procedures before starting internal or external production.
Watch a Demo.
Steps to Enable
- To enable electronic records and capture electronic signatures for manufacturing, you must determine and configure electronic signatures for each inventory organization using the Configure Electronic Signature Preferences task in the Setup and Maintenance work area. The transaction to be configured is Manufacturing Work Order Approval.
- After you enable electronic signatures, you should also define configurable business process rules in Oracle Business Process Management using the Manage Task Configurations for Supply Chain Management task, and the Manage Approval Groups task in the Setup and Maintenance work area to determine the approvers for each transaction. The task to be configured is WorkOrderDeferredApproval.
Tips And Considerations
- You can enable e-records and e-signatures for discrete manufacturing and process manufacturing work orders separately from maintenance work orders. You can also configure different approval rules based on the work method.
- You can submit a work order for approval when the initially changing to a user-defined status that is associated with the system status of Released.
- You can't update a work order in Pending Approval status through the UI, File Based Data Import (FBDI), or REST. You must wait for the approval process to complete as approved or rejected before making further changes.
- You can't create work orders in the Released status through the UI if e-records and e-signatures are enabled for the organization. However, you can create work orders in the Released status through FBDI and REST.
- You can't submit a work order that has been previously released for e-record and e-signature approval again. Instead, you can enable audit trail to track work order changes.
- You can't release and pick a work order in a single action when e-records and e-signatures is enabled. Instead, you can release a work order and submit it for approval before picking materials.
- You can't release a work order for e-record and e-signature approval through FBDI, REST, the Material Availability Assignments page, the Edit Production Exception page, or the Production Supervisor Mobile application.
- You can't prevent changes to material reservations for work orders in Pending Approval status. However, you can manually coordinate when material reservation changes in Inventory need to be implemented for the affected work order before initiating the e-record and e-signature approval process.
- You can't configure the suppression of the e-signature approval based on specific conditions. However, you can configure an automatic, conditional approval based on approval rules.
Key Resources
- Watch Enable Deferred Electronic Records and Electronic Signatures for Manufacturing Work Order Release Readiness Training
- Refer to Implementing E-Signatures and E-Records and Using E-Signatures and E-Records in the Oracle Help Center
Role And Privileges
- Users who are assigned any of these predefined job roles can access this feature:
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
- Users who are assigned a configured job role that contains these privileges can access this feature:
- Manage Work Order Headers (WIP_MANAGE_WORK_ORDER_HEADERS_PRIV)
Work orders are created through supply chain planning, maintenance programs, or are manually created by users. In either case, the work order dates, operation dates, and resource dates are scheduled using the unconstrained scheduling method. When work order dates or quantities are manually updated, the work orders are automatically forward scheduled or backward scheduled through the unconstrained scheduling method.
However, due to needs in both maintenance and manufacturing business scenarios, some work orders need to have gaps between, or overlapping of operation duration, or resource duration.
For example, if a maintenance operation involves painting, or a manufacturing operation requires heat treatment, the next operation can only start after drying or cooling time, respectively. This requires the next operation to start after a gap once the previous operation is completed.
Before this update, work orders were always scheduled automatically with no gap or overlap using the user interface. With this update, you can now schedule work orders manually to enable gap or overlap between operations or resources.
Here are the capabilities supported in this feature:
- Set up work order for manual scheduling
- Manually schedule work orders
- Manual update of work order start and completion dates
- Manual update of work order operation start and completion dates
- Manual update of work order resource start and completion dates
Set up work order for manual scheduling
The scheduling method is displayed at the work order header for both maintenance and manufacturing work orders. You can select one of the following two values:
- Default Scheduling
- User or External Scheduling
Edit Work Order> General Information> Details
Manually schedule work orders
- Manual update of work order start and completion dates
You can manually update the start and completion dates of the work order. The unconstrained scheduling won't be invoked if your scheduling method is User or External Scheduling.
- Manual update of work order operation start and completion dates
You can manually update the start and completion dates of the work order operations. The unconstrained scheduling won't be invoked if your scheduling method is User or External Scheduling. However, the work order start and completion dates will be synchronized with the earliest operation start date and the latest completion date, if they are outside the work order start and completion date.
- Manual update of work order resource start and completion dates
You can manually update the start and completion dates of the work order resources. The unconstrained scheduling won't be invoked if your scheduling method is User or External Scheduling. However, the work order operation start and completion dates and the work order start and completion dates will be synchronized with the earliest resource start date and the latest resource completion date, if they are outside the work order or operation dates.
Oracle Fusion Cloud Supply Planning, including Production Scheduling will consider manually scheduled work orders during scheduling. If Oracle Supply Planning, including Production Scheduling update the work order dates, Oracle Fusion Cloud Manufacturing will honor the recommendations.
Using the manual scheduling of work orders, you can better manage real time requirements of shop floor scheduling, to meet your business needs.
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 23B
Tips And Considerations
The Firm indicator would be automatically selected if the scheduling method is changed to User or external scheduling method. However, it can be optionally deselected.
This enhancement is supported in the User interface only. FBDI and REST will continue to support the existing behavior.
Key Resources
Role And Privileges
- Users who are assigned any of these predefined job roles can access this feature:
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
Correct REST API Transaction Errors Using the ADFdi Interface
With Oracle Fusion Cloud Manufacturing, you can create work orders and report work order transactions in several ways.
You can create work orders and report work order transactions using the user interface, REST services, or the file-based data import process.
Prior to this update, using the ADFdi user interface you could correct the transactions that resulted in errors for import transactions that were created through file-based data import.
With this update, you can now correct these transactions from the user interface for both file based data import as well as REST services. The following transactions can be corrected:
- Work order operation transaction
- Work order material transaction
- Work order resource transaction
Select the Correct Work Orders and Transactions for Import task in the Work Execution work area to correct the transactions that have returned errors or to complete the records that are incomplete.
On the Correct Work Orders and Transactions for Import page, you can use a combination of filters to narrow your search. You can filter for a specific type of transaction, such as work order materials, operations, or resources. You can also filter on criteria such as the import batch code, import batch status, or even a specific import batch ID.
The following screenshot displays the Correct Work Orders and Transactions for Import page.
Correct Work Orders and Transactions for Import UI
Correct Work Order Operation Transactions ADFdi Spreadsheet with details of error
The ADFdi spreadsheet correction feature provides you the flexibility to make corrections to transactions imported through FBDI or REST service, quickly from a single user interface.
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
Tips And Considerations
Consider the following details before enabling the opt-in:
- You must not have hybrid mode of error handling. For example, when you decide to resubmit error REST calls, you must do so for all errors. You must not resubmit some error REST calls and ignore in some other cases.
- When you get REST call errors and you decide to resubmit error REST calls from the calling program, you must not enable the opt-in, because it might create duplicate transactions.
- When you get REST call errors and you decided not to resubmit error REST calls from the calling program, you must enable the opt-in and must resubmit the transactions.
Key Resources
Role And Privileges
- Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
Qualify Operators When Assigning Work or Reporting Labor Usage
Companies often have separate processes and systems for maintaining operator skills or training records and executing operations, which could pose a potential risk in ensuring that their operators are properly trained before performing their work. With this feature, you can verify that an operator is qualified to perform a manufacturing or maintenance operation based on the specified job profile.
For initial setup, you can leverage Oracle Fusion Cloud Talent Management, part of Oracle Cloud Human Capital Management (HCM), to define job profiles for specific job requirements and track an employee talent profile for competencies with corresponding proficiency levels and certifications. Then, you can require that an operator must meet the specific job requirements by associating the job profile to a standard operation resource, a manufacturing or maintenance work definition operation resource, or directly to a manufacturing or maintenance work order operation resource.
Create job profile in HCM with required skills and qualifications
Associate Job Profile to an Operation Resource
This qualification check is enforced when assigning work to an operator or reporting labor usage as follows:
-
You can confirm the operator's qualifications when assigning a labor resource instance to a manufacturing or maintenance work order operation. In the event that the operator does not qualify during the assignment to a work order operation, you receive a warning and can proceed or replace with another qualified operator.
Supervisor is Warned If Unqualified Operators are Assigned
-
You can confirm the operator's qualifications when reporting an operation or resource transaction using the labor resource instance. During operation completion or resource charging, you can't proceed with an unqualified operator and need to reassign to a qualified operator.
Resource Transaction Requires an Operator to Qualify Against the Job Profile Associated to the Resource
File-based data import (FBDI) changes:
You can associate the job profile to standard operation resource, work definition operation resource, and work order operation resource using file-based data import. A new column called Job Profile Code has been added to the respective FBDI templates. You can't report operation completion if an operation resource has an associated job profile because resources and resource instances can't be reported for operation transactions through FBDI. To report completion for such operations through FBDI, you can set the resource charge type to Manual and use the Work Order Resource Transaction Import.
REST API changes:
You can associate the job profile to standard operation resource, work definition operation resource, and work order operation resource using REST service. REST payload accepts Job Profile Code and Profile ID. You can't report operation completion if an operation resource has an associated job profile because resources and resource instances can't be reported for operation transactions through REST. To report completion for such operations through REST, you can set the resource charge type to Manual and use the Work Order Resource Transaction REST service.
ADFdi Changes:
ADFdi Changes: You can associate the job profile to Standard operation resource and Work definition operation resource through ADF desktop integration service (ADFdi). Job Profile Name and Profile Code are both exposed in the templates with code being given precedence.
Built-in, operational checks for compliance with training and job requirements reduces the likelihood of noncompliance, defects, or failures in manufacturing and maintenance operations while adhering to standard operating procedures and regulatory requirements. For additional information, please refer to talent management documentation under resources section.
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 23B
To use this feature Talent profiles must be enabled in Oracle fusion cloud Human Capital Management. After enabling the profiles, talent profile content sections, content items, and rating models must be created and made available for use in job profile and employee profile.
Tips And Considerations
- You can define the qualifications required for a manufacturing or maintenance operation using model profiles in Oracle Profile Management within Oracle Talent Management, part of Oracle HCM.
- You can associate a job profile to an operation resource for any work order type and work methods of discrete manufacturing and process manufacturing, and also for maintenance orders. You can't associate it with an outside processing operation or in a contract manufacturing work order
- You can add an active job profile to a standard operation, work definition operation, or work order operation through the UI and other ways including REST, File Based Data Import (FBDI), and Application Development Framework Desktop Integration (ADFdi) as supported by the work method.
- You can associate a job profile to a work definition operation resource to apply the same job requirements to all of its labor resource instances during work order assignment and operation or resource transaction reporting. If an operator is qualified to do more than one type of work, then you can create different job profiles that align with the different operations.
- You can create a new work definition version to track changes in the job profile that contains the job requirements associated with an operation. Enabling e-records and e-signatures for manufacturing work definitions can automatically enforce a new work definition version for any further changes using an approval process.
- You can delete the job profile associated to a work definition operation to disable the qualification check required in the work order and during work execution.
- You can enforce the qualification check when reporting operation or resource transactions through the UI, REST, and FBDI.
- You can't leverage an external system for the qualification check, since only the integrated check with HCM is supported.
- You can't use the Quick Complete process on the Review Dispatch List page when a work order has a job profile required for any of its operation resources.
- You can't override skill validation during resource transaction reporting. Qualifications of the assigned labor resource instance is checked against the job profile requirements. The user who is logged into report the transactions is not used for verification.
Key Resources
- To understand more about how to create job profiles and manage employee talent profiles, please refer to Talent Management documentation which is part of Oracle Fusion Cloud Human Capital Management (HCM)
Role And Privileges
- Users who are assigned these predefined job roles can automatically access this feature:
- Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
- Users who are assigned this job role can create job profiles with required qualifications since they need to access functionality from Oracle Fusion Cloud Human Capital Management (HCM)
- Human Resources Specialist (ORA_PER_HUMAN_RESOURCE_SPECIALIST_JOB)
Synchronize Process Manufacturing Work Orders with IoT Production Monitoring
Process manufacturers are increasingly augmenting their plants with Internet of Things (IoT)-enabled sensors and devices as part of a digital transformation strategy for more predictive and adaptive processes. With this update, you can synchronize process manufacturing work orders for real-time production monitoring and actionable insights through connected equipment resource instances using the prebuilt integration between Oracle Fusion Cloud Manufacturing and Production Monitoring, part of the Oracle Fusion Cloud IoT Intelligent Applications.
In IoT Production Monitoring, you can monitor the execution of a specific process manufacturing work order to detect predictions, trends, and anomalies based on Artificial Intelligence and Machine Learning algorithms. In addition, you can automate the completion of the batch quantity at an operation and any outputs including the primary product, co-products, and by-products. By leveraging the existing capabilities between Manufacturing and IoT Production Monitoring for discrete manufacturing work orders, you can now monitor synchronization of process manufacturing work orders, view IoT dashboard metrics on the Work Execution landing page and drill directly to the IoT Factory Dashboard, and navigate from equipment resource instances and process manufacturing work orders to view IoT insights.
Routing View of Process Work Orders in IoT Production Monitoring
With this seamless integration, process manufacturers can effectively implement process automation and predictive analytics as competitive differentiators.
Steps to Enable
The steps to integrate Manufacturing Cloud with IoT Production Monitoring are the same as the existing procedure. Here are the steps to enable this feature:
- In the Functional Setup Manager, navigate to Manage Setup Content and then Manage Integration of Additional Applications. Create a new entry with IoT Production Monitoring as the application name. You must set the Security Policy to oracle/wss_http_token_over_ssl_client_policy. The credentials you provide must be a valid user in IoT Production Monitoring with necessary privileges.
Manage Integration of Additional Applications
- Using the Manage Plant Parameter task in Functional Setup Manager, select the check box for the Enable synchronization to IoT Production Monitoring parameter for a process manufacturing enabled organization.
Manage Plant Parameters
- In IoT Production Monitoring Cloud > Settings > Integrations > Oracle Manufacturing Cloud Service, you can set up the end point URL and other details required to integrate with the Manufacturing application. The end point URL must be in the format https://<oraclecloud server name>/fscmRestApi/resources/latest and the username specified should have the necessary privileges to invoke Manufacturing Cloud REST APIs to update work order status and perform work execution transactions.
IoT Production Monitoring: Integration Settings
Tips And Considerations
- The synchronization of process manufacturing work orders is similar to the synchronization of discrete manufacturing work orders. Refer to the documentation on How You Synchronize Discrete Work Orders and How You Manage Synchronization Errors for more information.
- You can't automatically report lot and serial numbers for outputs using this integration at this time.
Key Resources
- Watch TOI of 20B feature Synchronize Resource Details and Work Order Details from Manufacturing to IoT Production Monitoring
Role And Privileges
- Users provisioned with the following job role will automatically be able to use this feature:
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
Manage Production Calendar Shift Exceptions Using a REST service
Use the Production Calendar Shift Exceptions REST service to:
- Create new shift exceptions
- Update future effective shift exceptions
- Get shift exception details
- Delete future effective shift exceptions
This service allows you to quickly create changes to the manufacturing production calendar.
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
- Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation, available on the Oracle Help Center.
Role And Privileges
To use this feature, the following privileges or role is required:
- Privilege Name and Code: Manage Plant Shift Exception - RCS_MANAGE_PLANT_SHIFT_EXCEPTION_PRIV
- Privilege Name and Code: Manage Production Calendar - RCS_MANAGE_PRODUCTION_CALENDAR_PRIV
- Privilege Name and Code: Manage Work Center Resource Exception - RCS_WORK_CENTER_RES_EXCEPTION_PRIV
- Privilege Name and Code: Manage Work Center Resource Calendar - RCS_WORK_CENTER_RES_CALENDAR_PRIV
Manage Work Center Resource Exceptions Using a REST service
Use the Work Center Resource Exceptions REST service to:
- Create new work center resource exceptions
- Update future effective work center resource exceptions
- Get work center resource exception details
- Delete future effective work center resource exceptions
This service allows you to quickly create changes to the working time for one or a set of work center resources.
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
- Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation, available on the Oracle Help Center.
Role And Privileges
To use this feature, the following privileges or role is required:
- Privilege Name and Code: Manage Work Center Resource Calendar - RCS_WORK_CENTER_RES_CALENDAR_PRIV
- Privilege Name and Code: Manage Work Center Resource Exception - RCS_WORK_CENTER_RES_EXCEPTION_PRIV
- Privilege Name and Code: Manage Production Calendar - RCS_MANAGE_PRODUCTION_CALENDAR_PRIV
- Privilege Name and Code: Manage Plant Shift Exception- RCS_MANAGE_PLANT_SHIFT_EXCEPTION_PRIV