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.

Submit Rejected Deposits (SRDP): This menu option will be removed from Classic View in a future update. The Submit Rejected Deposits option in Modern View should be used instead.

Features Deprecated and Removed in this Release

  • Basic inbound authentication: Basic authentication is no longer supported for inbound web service messages. OAuth must be used instead. Instead of using Work with Web Service Authentication (WWSA) in Classic View, you should use the Manage External Application Access option in Modern View to generate a client ID, obtain the client secret, and define web service access.

  • SOAP Messages: SOAP inbound messages are no longer supported. REST must be used instead.

    Note:

    If you are using the inbound return API (RETURN_IN) from Xstore to Order Administration, you need to upgrade Xstore to a version that supports REST and OAuth:

    • 17.0.5

    • 18.0.4

    • 19.0.3

    • 20.0.2

    • 21.0.0

  • REST Message versions:

    • CWEmailOut: Versions earlier than 13.0 are no longer available. New version 13.0 no longer includes the opm_credit_card tag and includes instead the card_token tag.

    • CWInvoiceOut: Versions earlier than 7.0 are no longer available. New version 7.0 no longer includes the ipm_credit_card_nbr and instead includes the card_token tag.

    • CWOrderIn: Versions earlier than 12.0 are no longer available. New version 12.0 no longer includes the cc_number or already_tokenized tags, but instead includes the new card_token, psp_payment_scheme, and psp_customer_token tags.

    • CWOrderOut: Versions earlier than 12.0 are no longer available. New version 12.0 no longer includes the credit_card_nbr tag, but instead includes the new card_token tag.

  • Payment processing: The following payment processing options are no longer supported. The EFTConnect module can be used instead.

    • CyberSource Point-to-Point integration and Decision Manager Update: The EFTConnect module now supports integration with CyberSource, including Decision Manager. See Oracle Retail EFTConnect for details.

      If you have been using CyberSource Point-to-Point, you can implement and use the same merchant account through EFTConnect. Any tokenized credit cards numbers will be retained.

      As a result of this deprecation, options and features such as the following have been removed:

      • You can no longer create an authorization service with a Service Code of CYB (WASV).

      • The CYBDMUP (CyberSource Decision Manager Update) periodic function has been removed.

      • Properties related to the CyberSource Point-to-Point integration have been removed. See Properties for a list of removed properties.

    • External Payment Service for credit card processing: The EFTConnect module must now be used instead.

      If you have been using the External Payment Service for credit cards, you can implement and use the same merchant account through EFTConnect. Any tokenized credit cards numbers will be retained.

      Note:

      You can continue to use the External Payment Service for stored value cards.

    More information: See Technical Changes and Removed Features for listings of removed integration layer processes, menu options, functions, properties, reports, system control values, and secured features, as well as additional renamed or disabled options.

  • FTP: The use of secure FTP is no longer supported for the following outbound batch file processes. A file storage or file transfer service must be used instead.

    • Order Broker integration: Sending Product, Product Location, and Incremental Inventory imports information to Order Broker.

    • POSLog: Sending POSLog files to Customer Engagement.

      Note:

      You must be on a release of Customer Engagement that supports the File Transfer Service (FTS).

    • RTLOG: Sending the RTLOG files to the Sales Audit Module of the Oracle Retail Merchandising Foundation.

    See Externalize File Movement for details on removed or disabled properties or options related to the removal of support for secure FTP.

  • Encryption: With the implementation of the EFTConnect module, Order Administration no longer processes, stores, or transmits credit card data, so encryption is no longer used or required. All tokenized cards will be migrated.

  • PREORDER Periodic Function: The PREORDER periodic function has been removed. The Active PO Processing (ACTPO) periodic function should be used instead.

  • E-Commerce Static Data Tables (ESTF): This menu option is no longer used and will be removed in a future update. If you need to move static files to a third-party system, you can use Oracle Analytics Custom Reports or the Retail Data Store. See the reporting guides on My Oracle Support (ID 2149144.1) or the Retail Data Store for more information.

For a full list of declared deprecated features, please visit these locations on My Oracle Support (MOS):