Release 24.1.3
Revision History
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 18 MAR 2024 | Created initial document. |
Overview
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.
Feature Summary
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 |
|
||
Role Based Viewer Access to All Trading Partners in a Business Flow Step |
||||||
Intelligent Track and Trace
Intelligent Track and Trace
Role Based Viewer Access to All Trading Partners in a Business Flow Step
Currently, when you configure Business Flows, you define Viewers of each flow step individually based on the associated Trading Partner ID. When more and more trading partners get associated with the business, adding them separately becomes tedious, and all logged-in trading partner users may not have viewing access to all the documents, other than the ones for which they are the default viewers.
To address this limitation, you now have the flexibility to set up trading partner users as viewers by selecting either one or both the options:
- Define Viewers by selecting business roles
- Define Viewers by selecting trading partners
This enhancement refines and extends the scope to define Viewers based on Trading Partners selection and/or based on specific Business Role. The other benefits entail:
- Reduced configuration overhead: Viewers to each step can automatically be applied based on the selected roles.
- Adaptability: Allows your organization to adapt quickly to changes when new customers join the organization or when roles are changed. Viewing requirements can be quickly updated by selecting appropriate roles.
- Role-based access: Group users belonging to a specific business role will be the viewers to access their primary or secondary documents instead of defining each viewer separately.
Steps to Enable
You don't need to do anything to enable this feature.
UI Enhancements for Trading Partners Configuration
The trading partner configuration in Intelligent Track and Trace is now enhanced to provide an improved UI experience while inviting and managing participating and endorsing trading partners. The new visual design simplifies the end-user experience to manage all trading partner configuration tasks from the User Management section.
Moving the trading partner configuration under the User Management section offers better flexibility and ease of navigation. It provides a logical flow of tasks you need to execute and control for activities related to user management.
The new UI design provides the following benefits:
- Trading Partners summary: A dedicated tab under the User Management section that covers trading partner attributes, such as roles, status, user quota, etc.
- Trading Partners Edit and Invite pages: Dedicated action drawers where all the details about trading partner information can be entered concisely under respective heads.
- New Locations page: To provide trading partner location, the enhanced UI location page contains trading partner details, a map (with one marker per location), and a list of primary and secondary locations of a particular trading partner.
Steps to Enable
You don't need to do anything to enable this feature.