1. Release Readiness Guide
  2. Deprecation Advisory

4 Deprecation Advisory

As part of the continuous delivery model for cloud services, features and technical components of a solution may be removed or replaced to enhance the security, performance, and overall quality of the cloud service. When this occurs, the deprecation of a feature or component will be announced in advance, allowing customers sufficient time to anticipate the change and transition to any enhanced replacement feature/component. After the deprecation is announced, the deprecated feature or component will remain in the solution until the planned removal date and will not be enhanced or made compatible with other new features.

For more information about deprecated functionality in this product, see the following document on My Oracle Support: Oracle Retail Order Broker Cloud Service Deprecation Advisory (2670295.1).

New Order Polling Schedule for Store Connect: The New Order Polling Schedule tab has been removed from the Store Connect Preferences screen. The Minutes and Times options are no longer supported. Orders assigned to Store Connect locations will now go into Polled status immediately, and any orders that were previously in NEW_ORDER status and not yet polled will go into Polled status immediately with this update.

Removal of SFTP for Imports and Exports: With this update, Secure FTP is no longer supported for any imports and exports including:

  • Product Import

  • Incremental Inventory Import

  • Fulfilled Inventory Export

  • Inventory Quantity Export

  • Sales Order Data Extract

The Data Folder settings at the Tenant-Admin screen have been removed.

Any existing sFTP directories or files will be gone once the upgrade is applied. Ensure all files have been processed before the upgrade is done.

Prior to applying this update, ensure all import and export files have been processed and File Storage API is configured where applicable.

Note:

The Proximity, Vendor Invoice and Vendor Shipment uploads available through the user interface were previously updated to support file storage only.

Retail Pickup and Ship To Store Orders: With this update, retail pickup and ship to store orders are no longer supported. Related changes include:

  • Any organization that was not already set to use ship for pickup orders is automatically reset.

  • Any existing retail pickup or ship to store orders are automatically converted to ship for pickup orders:

    • For a converted retail pickup order, the pickup location is the same as the originating (source) location.

    • For a converted ship to store order, the sourced location is the same as the originating (placed) location.

  • Screens no longer display retail pickup or ship to store order types as selection criteria.

  • Any existing probability rules based on retail pickup or ship to store orders are no longer used.

  • If a web service request (SubmitOrder, LocateItems, or ProductAvailability) references retail pickup or ship to store, a message such as the following is returned: response_cd="1008" response_description="Invalid or missing fulfillment type, (fulfillment_type) is required.”

Important:

Considerations for update, if ship-for-pickup orders were not previously enabled in your organization:

  • Integrating systems must support ship-for-pickup: Do not upgrade to 21.0 if any integrating systems do not support a third location besides the originating (placed) location and the pickup location.

  • Existing orders permanently converted: When ship-for-pickup orders are enabled, all retail pickup and ship-to-store orders are converted to ship-for-pickup orders, and cannot be changed back.

  • Reset fulfillment options: After ship-for-pickup orders are enabled, you need to use the Preferences screen to set the options at the Fulfillment tab, including the Sourcing Distance, and select eligible sourcing and pickup locations. You can also use the Order Broker Preference Overrides screens to set up overrides.

  • Reschedule reports: After converting an existing organization to support ship-for-pickup orders, you should recreate any currently scheduled Order Status or Unfulfillable reports.

  • Ship-to-store orders and Store Connect use:

    If you previously processed ship-to-store orders and use Store Connect, these orders will be converted to ship-for-pickup orders, which cannot be fulfilled through the Store Connect user interface.

  • Close reason codes or SHIP2STORE carrier:

    These are related to ship-to-store orders, and are no longer implemented. You can flag these as inactive or delete them.

Store Connect HTML Email Templates: With this update, the ability to specify an HTML Email Notification Template has been removed.  If the template was populated prior to this update and the email is set to generate HTML, Order Broker will continue to send emails using that template. If you are not currently configured for sending HTML emails or you need to disable email notifications, contact your Oracle Representative. It is recommended to move to the Outbound Email API if customization is required.

Note:

If you did not previously have a bilingual template selected for the Shipment Notification Email, Pickup Ready Notification Email, or Pickup Ready Reminder Email at the Store Connect Preferences screen, you can no longer select a bilingual template for these emails.