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 |
|---|---|---|---|
| 13 JUN 2023 | 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.
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 |
|
||
Download All Attachments for a Selected Document or Trace
This feature enables you to download all the attachments pinned with a transaction document for a specific business flow step or for the entire business flow trace with a single click. Instead of downloading each attachment separately, the bulk export feature offers greater flexibility to download all the attachments in a single zip archive for every single version of the document/trace or for the entire version history.
Some of the key benefits of this feature are:
- Optimized user experience: Exporting all attachments in a single archive provides greater control to instantly retrieve and track historical data locally as needed thereby optimizing the overall application user experience.
- Effective file organization: All the files are exported in a zip format with a well-organized directory structure with a directory for each document and its associated versions.
- Detailed summary report: A separate CSV file containing a complete download summary of the zip archive, such as document name, document number, the business flow and flow step for which it was submitted, document version, and so on.
- Access control: Use permission based access to allow or restrict users from viewing and downloading attachments pertaining to the most recent version or for the entire version history.
- Track export status: Provides efficient tracking functionality to check the export activity status and subsequently download the archived files to your local system.
Steps to Enable
You don't need to do anything to enable this feature.
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 |
|---|---|---|---|
| 18 MAY 2023 | 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.
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 |
|
||
Support for Unidirectional Reference Keys In Metadata Template |
||||||
Support for Unidirectional Reference Keys In Metadata Template
Currently, when you create internal references between transaction documents, in the document metadata template, you use the ledgerKey of the document as a primary key for defining document correlations. This approach throws the following challenges:
- If the exact document ledgerKey value is not known, then document correlations are formed by using the bi-directional reference model where each document is back referenced to itself.
- Bi-directional references create recursive correlations between documents and add a higher level of complexity for a large number of documents across business flows.
To create fine-grained correlations between documents, a unidirectional reference model is now available that enables you to create exact internal correlations. For this purpose, you can now define referenceKeys for each document that is to be referenced by other documents.
For example, to create correlations between Sales Order and Purchase Order documents, first, in the Purchase Order metadata document, add a referenceKey to the Purchase Order document, which is a reference definition used by the Sales Order document, and then in the Sales Order metadata template, in the documentCrossRef object definition, define a Purchase Order document name as referenceKey(s)to create a direct reference to the Purchase Order document without creating any back reference to itself.
The key benefits of this enhancement are:
- One-way references to address the bi-directional recursion limitation.
- Simplified metadata template definition for creating internal references. For example, the usage of referenceKeys instead of references field to define correlations.
- No dependency on the document/ledger keys to define correlations.
Steps to Enable
You don't need to do anything to enable this feature.
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 |
|---|---|---|---|
| 17 APR 2023 | 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.
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 |
|
||
Use Filter Based Search to Retrieve Items and Documents Data |
||||||
Use Filter Based Search to Retrieve Items and Documents Data
The Items and Documents dashboard in Oracle Intelligent Track and Trace now supports Filter based search to query through a large amount of data and then narrow down the search results by applying predefined filters, such as to retrieve a list of items based on a specific lot size, batch number, or reference document, etc.
You can apply multiple filters on the available columns to search documents that satisfy the given criteria, such as a document submitted and received on a specific date and time, a document variant that matches the exact string, or a document that is not received for a specific business flow, etc.
Filter based search overcomes the limitations of free text search and further enriches the overall application usability experience that helps you scope and refine your search results as needed.
Some of the key benefits of filter-based search are:
- Add filters to multiple columns at once.
- Select one or more filter values to narrow down your search results.
- Change the scope of your search by using different filter values.
- Use various identity operators to refine your search.
- Export the search results in a CSV or Excel format.
Steps to Enable
You don't need to do anything to enable this feature.