1 Feature Summary

Oracle Retail Supply Chain Collaboration Cloud Service 26.2.401.0 is a Critical Update.

Oracle Retail Supply Chain Collaboration Cloud Service includes the following modules:

  • Oracle Retail Supply Chain Hub

  • Oracle Retail Supplier Evaluation

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 Supply Chain Collaboration 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: Identifies whether the feature is Enabled or Disabled upon initial delivery.

  • 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?
Supplier Evaluation: Modification to MFCS Item Integration

SE: Item Integration

Small

No

Configuration

Health Checks for POM Integration SCH: Data Administration Small No POM Configuration

Supplier Evaluation: Modification to MFCS Item Integration

Item Integration failure messages accumulating.

The MFCS Item integration can now be configured to selectively identify which Items should be integrated, providing greater control over the scope and timing of Item synchronization.

A new Custom Flex Attribute (CFA)-based integration option allows administrators to configure a specific CFA and value in MFCS as the criteria for Item integration. When enabled, only Approved Items with the configured CFA value are eligible for synchronization to ORSE. When the option is not enabled, the existing behavior remains unchanged, and Approved Items continue to be automatically integrated.

Items that do not meet the configured CFA criteria are skipped without generating an inbound integration failure batch job message. A server log message is generated to indicate that the Item was skipped.

Health Checks for POM Integration

The Health Checks capability in Data Administration has been extended to validate selected configurations in the Merchandising Foundation Cloud Service (MFCS) Process Orchestration and Monitoring (POM) schedule relating to cost, item, and purchase order induction integration. These additional checks help administrators identify schedule configuration issues that could affect integration processing.

Post Release Tasks and Impact on Existing Installations

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

Database Update Scripts

There are no database update scripts included for this release.

Post Release Configuration and Testing

The following features have post release configuration and testing requirements:

  • Modifications to MFCS Item Integration
  • Health Checks for POM Integration
Modifications to MFCS Item Integration
  • Application Changes

    The MFCS Item Integration configuration has been enhanced to support the use of a Custom Flex Attribute (CFA) to control which MFCS Items are eligible for integration.

    The following system parameters are added to the Item Integration (Inbound) field set on the MFCS Integration tab:

    • Use CFA - Enables CFA-based Item integration. This option is disabled by default.
    • CFA Entity - Identifies the MFCS entity against which the CFA is configured. This defaults to ITEM_MASTER and cannot be edited.
    • CFA Attribute View Column Name - Specifies the CFA attribute to use when determining Item eligibility.
    • CFA Value - Specifies the value that an Item must have for the configured CFA to be eligible for integration.

    When Use CFA is disabled, the existing integration behavior continues, and Approved Items are automatically synchronized from MFCS to the application.

    When Use CFA is enabled, the integration evaluates the configured CFA Attribute and CFA Value for each Item. The CFA Attribute name must exactly match the attribute name received in the MFCS payload. The CFA Value comparison is an exact text match but is case-insensitive.

    Items that meet the configured criteria are processed using the existing Item integration functionality. Items that do not meet the criteria are skipped and do not generate an Inbound Integration failure batch job message. A server log message is generated to indicate that the Item was skipped.

    The existing Item eligibility requirements continue to apply. Only Items that are Approved in MFCS and are at Style or SKU level can be created through the integration.

  • Impact on Existing Installations

    This enhancement is automatically available when upgrading an existing installation.

    The existing MFCS Item integration behavior is not changed by the upgrade as the new Use CFA system parameter is disabled by default. Unless this parameter is enabled, Approved Items continue to be automatically synchronized from MFCS to SE using the existing integration behavior.

    Existing customers using the MFCS Item integration should include the integration in their upgrade testing.

  • Configuration

    No configuration changes are required to continue using the existing MFCS Item integration behavior.

    To use the new CFA-based Item integration functionality, complete the following post release configuration:

    1. Configure the required Custom Flex Attribute (CFA) in MFCS: The CFA used for Item integration must be configured against the Item Header entity.
    2. Configure the CFA integration parameters: In the Item Integration (Inbound) field set on the MFCS Integration tab, configure the CFA Attribute and the CFA Value that will determine which Items are eligible for integration.
    3. Enable the CFA-based integration: Select the Use CFA system parameter to activate the new integration behavior.
  • Testing Guidance
    • Verify the configuration before relying on the new integration behavior: Once Use CFA is enabled, the existing automatic integration behavior is overridden. If the required CFA configuration or CFA Value has not been completed, Items will be skipped rather than automatically integrated.
    • Test the MFCS Item integration: Confirm that Approved Items meeting the configured CFA criteria are synchronized to SE and that Items that do not meet the criteria are skipped as expected.
Health Checks for POM Integration
  • Testing Guidance

    Run health checks manually through Data Administration and confirm that the additional MFCS POM schedule validations are executed.

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.