1 Feature Summary

This chapter describes the feature enhancements in this release.

Noteworthy Enhancements

This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Supplier Evaluation Cloud Service 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.

Note:

Where new fields, User Interface (UI) changes, or glossary entries are introduced as part of a change, the portal owner may need to apply their own translations of the core system text.

Column Definitions

  • Feature: Provides a description of the feature being delivered.

  • Module Impacted: Identifies the module impacted associated with the feature, if any.

  • Scale: Identifies the size of the feature. Options are:

    • Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

    • Medium: These UI or process-based features are typically comprised of field, validation, or program changes. Therefore, the potential impact to users is moderate.

    • Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

  • Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.

  • Customer Action Required: You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.

Table 1-1 Noteworthy Enhancements

Feature Module Impacted Scale Delivered Customer Action Required?
JET UI Site Form <BETA>

Supplier

Medium

No

Enable JET UI forms.
Site Reference Attachment Linking Supplier Small Yes Update reference type glossary items if the attachment field is to be mandatory.
Partner Supplier Type Supplier Medium Yes, if the Merch module is active.

Enable JET UI forms.

Update system parameters if MFCS integration is required.

Modification to MFCS Supplier and Site Integration Supplier Small Yes Update new system parameters.

JET UI Site Form <BETA>

This release includes the Site form as part of the transition of forms to the new JET UI design. This is BETA release of the form and additional updates will be included within upcoming releases. Two notable areas that will be included later are Process Links and Linked Site sections.

With JET UI enabled, the new JET UI Site form can be enabled with the JET UI Forms Enabled system parameter; or individual users can enable the forms using the new Preview JET UI Forms setting in their User Preferences.

Note:

This enhancement applies to environments that have the JET UI enabled.

The Site Details page contains several tabs covering key information for the site.

The Main Details provides the sites main information, including contact details and technologist details.

Main Details screen

The Sourcing Details includes production details, billing details and grower details.

Sourcing Details screen

The References includes a table of references used by the site.

References screen

The Scores page contains the Score Details tab which the Evaluation Scores for the site and a summary of the records used to generate the scores.

Scores screen

The Contacts page provides a list view of contacts configured for the site.

Contacts Details screen

The Associated Records page provides a number of list view for associated record types through the available tabs.

Associated Records screen

Site Reference Attachment Linking

This is an enhancement to the Site References table on the Site form so that it is now possible to associate a row in the reference table with one or more attachments that have been saved against the Site record.

Where a row in the table needs to be evidenced by a certificate or other document, this will facilitate that.

Additionally, the Reference Type Glossary has been updated so that for each reference type it is now possible to configure whether the attachment is mandatory or not.

Note:

This enhancement applies to environments that have the JET UI enabled.

Partner Supplier Type

This feature introduces support for Partner suppliers, enabling retailers to manage and evaluate non-direct supply chain contributors such as fabric and component manufacturers. Partner suppliers and their sites can be created, integrated through MFCS, and linked to other suppliers to represent extended supply chain relationships.

While they share core functionality with standard suppliers, Partner suppliers are excluded from active record metrics and cannot be assigned as primary sources for products. A new Processes field is also available on site records to capture the activities performed at each site for reporting purposes.

Users can also convert existing suppliers into Partner suppliers and filter or report on them using the new Partner designation. Partner suppliers can be created in both Classic and JET UI; however, supplier connections and conversion from regular to Partner suppliers are supported in the JET UI only.

Note:

This feature is only available in portals where the MERCH module is enabled.

Modification to MFCS Supplier and Site Integration

This enhancement introduces additional control over the integration of suppliers and sites from MFCS into ORSE.

A new configuration option allows integration to be conditioned based on the presence of a specific non-primary address type in MFCS. When enabled, only suppliers and sites that have the configured address type populated with a valid contact email will be eligible for integration. This provides retailers with greater control over which suppliers and sites are integrated, as well as the timing of their integration.

If the new configuration is not enabled, the integration will continue to function as before, automatically synchronizing all active suppliers and sites from MFCS.

Note:

If the non-primary address option is enabled but the Address Type ID is not configured, no suppliers or sites will be integrated.

Post Release Tasks & Impact on Existing Installation

The following post release tasks and impact on an existing installation must be taken into account as part of this release.

Note:

See the Noteworthy Resolved Issues document for 26.1.201.0 for additional post release tasks.

Database Update Scripts

There are no database update scripts included for this release.

System Text

The following features include new system text:

  • JET UI Site Form <BETA>
  • Site Reference Attachment Linking
  • Partner Supplier Type
  • Modification to MFCS Supplier and Site Integration

System text records are added automatically during the release process, however any translation overrides must be added manually, by the retailer administrator.

Post Release Configuration and Testing

The following feature has post release configuration and testing requirements:

  • Site Reference Attachment Linking
  • Partner Supplier Type
  • Modification to MFCS Supplier and Site Integration
Site Reference Attachment Linking
  • If reference types are required to be mandatory, then set the new mandatory flag on each of the reference types where that is required.
  • Verify that the Site then validates the reference types appropriately when added against a Site record.
  • Reports

    The Site Reference query has been updated to include the “Linked Attachments” field to allow reporting on this new information.

  • Site Extract and RDS

    The RDS tables which include Site data have been updated to include the “Linked Attachments” field.

Partner Supplier Type

To enable full use of Partner supplier functionality, the following actions may be required:

  1. Configure MFCS Partner Integration (if applicable)

    If MFCS integration is to be used, system administrators must configure the Partner Integration (Inbound) system parameters, including:

    • Partner Integration Enabled (set to Enabled)
    • Integration Interval (mins)
    • Do not run Integration before / after (optional run window)
    • Messages per Call
    • Invoicing System (mandatory before enabling integration)
  2. Define Default Values for Integrated Records

    Set default values used during Partner supplier and site creation using integration:

    • Supplier Administrator Role
    • Default Technologist
    • Default Supplier Type
    • Default Site Type
    • Default Business Unit
    • Default Business Category
  3. Configure Integration Conditions (Optional)

    To control which Partner records are integrated:

    • Use Non-Primary Address
    • Address Type ID
  4. Review Integration Behaviour Settings

    Configure optional behaviour settings:

    • Auto Delist in SE for Inactive MFCS Status
    • MFCS Active Description in ORSE
    • MFCS Inactive Description in ORSE
  5. Monitor and Maintain Integration

    Administrators should monitor and maintain integration using:

    • Last Run (with Reset option if required)
    • Number of days to keep Inbound Message Queue data
    • Batch job logs and messages for errors or failures

    Note:

    No additional configuration is required to manually create or manage Partner suppliers within the application. Existing roles and permissions are used to control access to Partner functionality.
  • Allocate and update permissions as needed for Partner Suppliers:

    New Partner: Supplier & Site Creator authority profile.

    Convert to Partner: Oracle Authorized Administrator authority profile.

    Select / Remove Partner Connections:

    • Supplier users: Supplier Administrator or Site Administrator authority profile.
    • Retailer users: Supplier & Site Editor authority profile.
  • Testing Guidance

    Validate the creation and management of Partner suppliers and sites, including the ability to convert existing suppliers to the Partner designation. Confirm that Partner-specific behaviour is enforced, such as exclusion from product assignment and active record metrics.

    Where applicable, validate the creation and management of Partner connections between sites, and confirm that Partner suppliers can be correctly filtered and reported on. If MFCS integration is in use, include validation of Partner supplier creation and updates by using the integration.

  • Reports

    A new Partner Connections Report (CR118) is provided to detail sites (conventional and partner) with their partner connections.

    The Partner flags from supplier and sites, and Processes from the site record will be available on the following report queries:

    • Assessment Tabular Responses
    • Audit
    • Audit Status History
    • Audit/Visit Scores Latest/Completed
    • Contact Role
    • Evaluation Site Summary Scores available
    • Policy Document Acceptance
    • Site
    • Site Assessment Scores All
    • Site Assessment Scores Latest/Completed
    • Site Assessments
    • Site Audit Summary
    • Site Reference
    • Site Status History
    • Supplier
  • Extract and RDS

    • Supplier and Site extracts and RDS views will include the Partner flag.
    • Site Partner connections will be available in RDS views.
Modification to MFCS Supplier and Site Integration

Configuration of the following system parameters is required to use this feature:

  • Use Non-Primary Address
  • Address Type ID
  • Testing Guidance

    Validate that supplier and site integration behaves as expected under both configurations. Confirm that, by default, all active suppliers and sites are integrated, and that when the non-primary address option is enabled, only suppliers and sites with the configured address type and valid contact email are integrated.

    Also validate behaviour when the Address Type ID is not configured, ensuring that no suppliers or sites are integrated, and confirm that the correct address and contact details are applied to integrated records.

Application Program Interfaces (APIs)

The following API is affected by this release. Consider if changes need to be made to any external systems that call the API.

  • Site REST API: The Site Reference Attachment Linking feature adds “Linked Attachments” from the Reference table.

Enabling Identity Management Notifications

As an IDCS or OCI IAM Administrator, verify that Notifications are enabled in the corresponding Stage / Production tenant.

Enabling User Roles

If they do not already exist, configure the Power User, Account Administrator, Assistant Technologist, and Site Inspector user roles, and assign to the appropriate users.

The instructions for downloading and uploading the amended Permissions spreadsheet are as follows:

  1. Log in as an Oracle Authorized Administrator user and go to Company > Admin > Roles & Permissions.

  2. Open the Permissions page.

  3. Download the active spreadsheet by selecting the row with true in the Active Permissions column, click Download Selected, and save locally.

  4. Edit the downloaded spreadsheet, make the changes described above, then save the spreadsheet.

  5. Upload the edited spreadsheet by clicking Upload Permissions, select the spreadsheet, and click Ok.

  6. Apply the changes by selecting the uploaded spreadsheet row, click Process Selected, and then click Ok to confirm.