1 Feature Summary

The enhancements below are included in this release.

Noteworthy Enhancements

This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Order Management Suite 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.

Column Definitions

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

• Module Impacted: Identifies the module 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 on 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.

Feature	Module Impacted	Scale	Delivered	Customer Action Required?
New and Updated Features
Order Administration Cloud Service
Modern View Customer Enhancements	Order Administration – Modern View	Large	Yes	No
Modern View Contact Center Order Search Enhancement	Order Administration – Modern View	Small	Yes	No
Advance Capture Overpayment Credit Invoice Enhancement	Order Administration - Payments	Small	Yes	No
Order Administration Item Number Length Expansion	Order Administration	Small	Yes	No
Tax Compliance Enhancements	Order Administration - Taxation	Medium	Yes	No`
Merchandising Warehouse Cross Reference and RTLog Mapping	Order Administration – Sales Audit Integration	Small	No	Yes
Enhanced Warehouse and Location Selection for Returns	Order Administration – Modern View	Small	Yes	No
Item Import Filtering by Location Identifier for Enterprise Foundation Integrations	Order Administration – Merchandising Integration	Small	No	Yes
ReSA RTLog Deduplication for Consolidated Invoicing	Order Administration – Sales Audit Integration	Small	Yes	No
Order Purge Enhancements	Order Administration	Small	Yes	No
Job Management	Order Administration - Jobs	Small	Yes	No
Updates to Menu and Setting Names	Order Administration	Small	Yes	No
IDCS Scope Restriction Readiness - Steps for External Integrations	Order Administration – Web Services	Small	No	Yes
Customer Web Service Enhancements	Order Administration – Web Services	Small	No	Yes
Database and Retail Data Store Updates	Order Administration	Small	Yes	No
Order Orchestration Cloud Service
Documentation Links	Order Orchestration	Small	Yes	No
Oracle Digital Assistant (ODA)	Order Orchestration	Small	No	Yes
IDCS Scope Restriction Readiness - Steps for External Integrations	Order Orchestration – Web Services	Small	No	Yes
Database and Retail Data Store Updates	Order Orchestration	Small	Yes	No

Order Administration Enhancements

Order Administration: Modern View Customer Enhancements

With this update, the Modern View Customer delivers a range of enhancements focused on improving usability, transparency, and efficiency for customer management. These changes simplify workflows, centralize key information, and empower users with more control and clarity in the customer management processes.

Refresh

A new Refresh button on the Customer page provides instant updates, ensuring the most current data is always displayed without the user having to reopen the page.

Additional Data

An Additional Data tab has been added to centralize customer-related fields, offering streamlined access and edit capabilities based on user permissions. New fields have been added that were previously only available through Classic View customer pages.

• Associate Price: Select to identify the customer as an associate.

  • Associate Price is available only when selected to display in the Work with Contact Center Field Display (WWCC) menu option.

  • The Change Associate Customer? In Cust Sold (B10) secured feature controls whether you can change the value. If allow, field is enabled; if exclude, the field is in display only.

  • Removed from the Create/Edit Customer, Order Entry Customer Information, Order Entry Edit Ship To (Primary Address), Order Summary Edit Ship To and Edit Sold To pages.

• Automatically Cancel Backorders: Select to automatically cancel backorders. Renamed the field label from Auto Cancel B/O in Classic View Customer page

• Birth Date (Birth Month/Day): Grouped edit for Birth Month and Birth Day; displays only when ORCE Customer Integration (L37) system control value is INTERACT.

• Bypass Reservation: Select to bypass reservation for the customer

• Call Code: Values are defined in Work with the Mail/Call Code (WMCC) menu option.

• Commercial: Select to set as a commercial customer.

• Current Mail Type: Values are Buyer, Catalog Request, List Rental, Recipient and Suspect or Prospect.

• Current Source: Values are defined in Work with Source Codes (WSRC) menu option where Display in O/E is set to Yes, and Restricted is set to No. A valid source code can be manually entered and saved when Restricted is set to No.

• Custom Data: Grouped edit for Custom Data 1 to 4.

• Custom Type: Renamed the field label from ‘Type’ in Classic View Customer page. Renamed from 'User fields 1 - 4' in Classic View Customer.

• Customer Class: Values are defined in Work with Customer Classes (WCCL) menu option.

  • Also available through the Create/Edit Customer pages.

  • Customer Class is available only when selected to display in the Work with Contact Center Field Display (WWCC) menu option.

  • A value is required when the Require Customer Class (H85) system control value is selected.

  • The Maintenance of the Customer Class Field (B07) secured feature controls whether you can change the value. If allow, the field is enabled; if exclude, the field is in display only.

• Customer Discount Percent:

  • Customer Discount Percent is available only when selected to display in the Work with Contact Center Field Display (WWCC) menu option.

  • The Access Customer Pricing/Discount Fields (J13) secured feature controls whether you can change the value. If allow, the field is enabled; if exclude, the field is in display only.

  • Removed from the Create/Edit Customer pages.

• Do Not Fax: Select to allow a fax to be sent to the customer.

  • Do Not Fax is available only when the Third Phone Number Type (L53) system control value is set to FAX.

• Email Opt-In: Values are Email order and promotion information, Email order information only, Do not email and Do not ask for email address.

  • Also available through the Create/Edit Customer pages.

  • Updates both the customer sold to and the primary customer sold to email records.

• Fraud Check: Values are Hold, Bypass and Fraud.

  • Removed from the Create/Edit Customer pages.

  • The Maintenance of Hold/Fraud/Bypass Flag (A57) secured feature controls whether you can change the value. If allow, the field is enabled; if exclude, the field is in display only.

• Inactive: Select to set as an inactive customer.

• Language: Values are defined in Work with Language Codes (WLAN) menu option.

• Mail: Select to send the customer future catalogs

  • Also available through the Create/Edit Customer pages.

• Mail Code: Values are defined in Work with Mail/Call Code (WMCC) menu option.

• Original Mail Type: Values are Buyer, Catalog Request, List Rental, Recipient and Suspect or Prospect. Display only field.

• Original Source: Values are defined in the Work with Source Codes (WSRC) menu option where Display in O/E is set to Yes, and Restricted is set to No. A valid source code can be manually entered and saved when Restricted is set to No.

• Price Column:

  • Price Column is available only when selected to display in the Work with Contact Center Field Display (WWCC) menu option.

  • The Access Customer Pricing/Discount Fields (J13) secured feature controls whether you can change the value. If allow, the field is enabled; If exclude access, the field is in read-only.

  • Removed from the Create/Edit Customer pages.

• Price Group: Values are defined in Work with Customer Price Group (WCPG) menu option.

  • Price Group is available only when selected to display in the Work with Contact Center Field Display (WWCC) menu option.

  • The Access Customer Pricing/Discount Fields (J13) secured feature controls whether you can change the value. If allow, the field is enabled; If exclude access, the field is in read-only.

  • Removed from the Create/Edit Customer pages.

• Rent: Select to rent the customer’s name.

  • Also available through the Create/Edit Customer pages.

• Reserve Warehouse: Values are defined in Work with Warehouses (WWHS) menu option where Allocatable is set to Yes.

• Sales Representative: Values are defined in Working with Sales Representative (WSLS) menu option.

  • Sales Representative is available only when selected to display in the Work with Contact Center Field Display (WWCC) menu option.

• Seed: Set to Yes when this is a seeded customer.

  Only available as display only.

• Suppress Sales Representative Email Notifications: Select to send the Outbound Email XML Message (CWEmailOut) to the Sales Representative associated to the customer.

• Track Item History: Values are No Item Tracking, Sold To Tracking Only, Sold To + Ship To Tracking.

Note:

A user must have ALLOW or DISPLAY access to the Allow Edit of Customer Additional Data in Modern View (J15) secured feature to access the Additional Data tab in the Customer page.

Address History

The Address History feature has been introduced for both Customer and Address Book records, enabling users to easily review historical changes to the specific name, address and phone information. This includes all previous addresses, with the user and the date it was updated, along with what area of the application the change was made through.

Changes made to the Prefix, Suffix, Company Name and Country now write an address history record for the Customer.

Previously this was only available through the Classic View Display Address Changes screens accessed through the Work with Customer (WCST) Customer Address Change History screen and the Customer Ship To > Prev Address screen.

Alternate Customer Numbers

To provide a more transparent view of customer identification, the Customer page now displays the following customer numbers in the Customer Information Panel:

• Customer Engagement Customer ID:

  • Available only when the ORCE Customer Integration (L37) system control value is INTERACT. If the customer has not been synchronized to Customer Engagement, a value of ‘None’ is displayed.

• Order Administration Customer ID:

  • Available only when ORCE Customer Integration (L37) system control value is INTERACT. When Customer Engagement is not enabled, the customer id in the title is always the Order Administration Customer ID.

• Primary Alternate Number:

  • The Primary Alternate Number field is now more visible, relocated to the left navigation panel of the Customer page, above the Frequent Purchases section.

    • The field label can be customized by populating a value in the Alternate Customer Number Label Description (H95) system control value.

    • Primary Alternate Customer is available only when Alternate Customer is selected to display in the Work with Contact Center Field Display (WWCC) menu option.

    • If an Alternate Number has not been defined as Primary, a value of ‘None’ is displayed.

  • An alternate customer number can be assigned as Primary through the Alternate Numbers drawer.

    • Click the Star icon next to a record to set as primary. When the primary is changed, this immediately updates the customer record.

    • Click the Delete icon to remove an alternate number. If also the primary, the Primary Alternate Customer is updated to display ‘None’ on the Customer page.

    • The Change Alternate Customer # in Cust Sold (B11) secured feature controls whether you can set, update, or delete a primary number. If allow, the primary can be updated or deleted; otherwise, the star icon is not available, and an error is displayed for delete. Non-primary numbers can be deleted regardless of this setting.

Customer Actions

Users can now access and manage customer actions directly from the Modern View Customer page. The drawer allows for the viewing, addition, and management of customer issues in a streamlined interface.

Previously this was only available through Classic View screens accessed through Work with Customer (WCST) Customer Actions or Work with Customer Action Notes (WCAN).

Add/Edit Actions and Notes: Users can create new customer actions and add detailed notes. The edit functionality allows modification of action details, reasons, assignees, and associated notes, with all changes validated for required fields such as action description and reason.

Status Management: Customer actions now have clear status progression, with the ability to move actions from Open to In Process to Resolved via dropdown selections. Once marked Resolved, no further changes to status are permitted, and the record becomes read-only.

Assignee Dropdown: Actions can be assigned to any user with access to the company. The assignee field is editable unless the action is resolved, at which point it becomes read-only.

Authority Controls: Editing and deleting notes/actions is only permitted for users with the appropriate secured feature authority. All users can view actions and notes by default.

• Change Customer Action Notes Description (A93)

  • Controls: Ability to edit the "Action Description" field within a Customer Action. When this permission is excluded, users cannot update the action description. When allowed, users can edit the description for actions in “Open” or “In Process” status. The field is always disabled for resolved actions.

• Delete Customer Action Notes (A96)

  • Controls: Access to delete a Customer Action from the main Customer Actions drawer. The “Delete” option is visible only if the action status is "Open" or "In Process." Deletion is restricted for resolved actions.

• Change Customer Action Notes Status/Work in Process (A97)

  • Controls: Grants users the ability to change the status of a Customer Action to “In Process.” In the main Customer Actions drawer, users will only see the "In Process" option when the action is currently "Open." The status dropdown in the details drawer aligns to these rules; if access is excluded, attempts to change status will prompt an error and disable confirmation.

• Change Customer Action Notes Status/Resolve (A98)

  • Controls: Authorization to resolve a Customer Action. The "Resolve" option will only display in the main drawer or details screen if the action is “Open” or “In Process.” For users without this authority, the "Resolve" control is disabled.

• Add Customer Action Detail Notes (A94)

  • Controls: Permission to add a note within the Add Customer Action and Notes process. Users without this authority will not see the "+ Add Note" button in the notes table.

• Change Customer Action Detail Notes (A95)

  • Controls: Permission to edit or delete notes associated with a Customer Action. When excluded, the edit and delete options in the notes table are hidden. When allowed, users can edit and remove notes as needed.

Catalog History

The Catalog History feature has been introduced, enabling users to easily review offer mailings directly from the Customer page. Previously this was only available through Classic View in the Customer Mail History screen.

Catalog History is available only when selected to display in the Work with Contact Center Field Display (WWCC) menu option.

Duplicate Address Check

When creating a new Address Book record, the system now checks for a duplicate record using the Standard Match Code logic defined in Setting Up Match Codes (MMCH) menu option.

If a duplicate is found, the system will open a drawer where you can continue creating the address book record or select to update a matching record that already exists.

Note:

Note: The Duplicate Customers Found window has been redesigned as a drawer for alignment with the new Duplicate Address Book Entry Found.

Items

Order Quantity is now available on the Items tab of the Customer page to allow a user to quickly identify how many units of that item was ordered.

Order Administration: Modern View Contact Center Order Search Enhancement

Order Search functionality has been improved to now filter orders by entering an "Order Date" where the system returns results for all orders on or before the specified date (not just those matching exactly). The search displays up to the 500 most recent orders in descending order of date.

If the results exceed 500 records, users will see the message: "Maximum records exceeded. Showing 1-500. Please refine your search." This update replaces the previous generic error and ensures combined search criteria are processed correctly.

Order Administration: Advance Capture Overpayment Credit Invoice Enhancement

When an Advance Capture Overpayment Credit invoice is generated (whether during order creation, cancellation, or refund release), a new Order Activity message is written to the order_transaction_history table and displayed through the Modern View Order Activity tab.

The message will display as: "Advance capture overpayment credit invoice #<invoice_number> generated."

The enhancement allows for clear identification of overpayment transactions and ensures consistency with other invoice types.

Order Administration: Item Number Length Expansion

With this update, enhancements have continued to support the increase of the Item Number and Retail Reference Number field lengths.

Retail Reference Number

The Retail Reference Number now supports up to 25 numeric digits. Previously, this was limited to 18.

System Control Values

The Default SVC Refund Item Number (I73) system control value has been expanded from 10 to 25 positions. This includes updates to the field within the Stored Value Card Processing Values (I71) system control value screen.

The Item for Non-Merchandise Amounts (L38) system control value has been expanded from 10 to 25 positions. This includes updates to the field within the ORCE Integration Values (L52) system control value screen from 12 to 25 positions.

Import Files

Item number has been expanded in the following import processes:

• Upload Price Code File (PRICECDUPLOAD): The ITM Number field now supports up to 25 alphanumeric characters (previously 12), accommodating a broader range of item identifiers. This applies to the Price Code Detail (PCD) record type.

• Upload Customer Price Group Exclusion (CUSTPGEUP): The Item field now allows up to 25 alphanumeric characters, enabling support for longer item numbers and ensuring compatibility with multi-byte characters (for example, Arabic, Chinese).

• Upload Set Component File (INSCUP): Both the Master Item and Component Item fields now support up to 25 alphanumeric characters for applicable set types (S, VG, VI), expanding flexibility for set and component management.

The integration between Order Administration and Order Orchestration has been enhanced to support expanded item numbers of up to 25 characters, including robust handling for items with associated SKUs. The enhancements introduce the use of the tilde (~) delimiter to consistently separate the item number from SKU elements within item identifiers across integration files and interfaces.

Key highlights:

• Item numbers are no longer padded to a set length or separated by spaces; instead, tildes are used only where needed to delineate SKU elements.

• All relevant service messages and import/export files now support this new tilde-delimited format.

• The item match logic within Order Administration has been updated to recognize the new format, ensuring a more accurate synchronization of product information and order processing.

Item Number Expansion with Order Orchestration

Alerts: There is a maximum item ID length limitation of 35 characters in Order Orchestration. Ensure that, when using SKUs, the total length does not exceed 35 characters (including tildes) to avoid integration errors.

Existing records should be updated or recreated as needed to match the new format; legacy data may not be compatible for item matching.

Example:

• Previously: ITEMNUMBER12 SKU1 SKU2 SKU3 (with spaces)

• Now: ITEMNUMBER12~SKU1~SKU2~SKU3

• If only SKU2 exists: ITEMNUMBER12~~SKU2

• If there are no SKUs: ITEMNUMBER12

These changes improve flexibility in the item master structures and ensure reliable item mapping and order processing across both Order Administration and Order Orchestration modules.

Order Administration: Tax Compliance Enhancements

Order Tax Override Enhancements

Enhancements to the logic for handling tax overrides at both the item and ship-to (freight) levels have been made. These changes improve tax compliance and bring item-level logic in line with freight tax logic, ensuring more accurate and predictable handling of tax override scenarios across all channels using the Order API, ChannelAdvisor, Order Orchestration Fulfillment orders and Modern View Order Entry.

Anytime the TAX_AMOUNT is supplied at the item level of the Order API, regardless of the tax override flag, the API sets the order detail tax to that amount, and marks the override field as 'Y' for transparency and audit control.

For partial tax override scenarios, the Order API is intelligent enough to detect when only part of the tax is being overridden, whether it happens at the item or freight level. In those cases, the relevant override indicators are always set to 'Y', even if the calculated tax values are zeroed out elsewhere.

• Use Case 1: A TAX_AMOUNT is provided at item level, but the override flag is omitted. The API sets the tax for the item and clearly flags the item as overridden. Meanwhile, the freight tax is zeroed out and flagged as overridden at the Ship To level.

• Use Case 2: A partial override is done by only filling the freight tax override and leaving items untaxed. The API sets the freight tax, flags it as overridden, and zeros out the item tax with the appropriate override flags set.

With these changes, we’re ensuring tax data always matches your XML, override status is explicit, and downstream financial controls are robust and clear.

No new tags have been added to the CWOrderIn XML, and backward compatibility is maintained.

Handling New Lines on Tax Override Orders

Enhancements to order tax processing have been made, ensuring compliance when new lines are added to orders initially submitted with tax override values. Now, when additional order lines are inserted during maintenance (such as exchanges, returns, or general order updates), Order Administration triggers a Quotation Request to the configured tax service (for example, Vertex) for the new line(s) only.

The resulting tax amounts are applied exclusively to the new lines and marked as overrides, while the original tax override status and the existing Retail Delivery Fee (RDF) flat tax indicators on the order remain unchanged. This ensures accurate, compliant tax assessment on new items without impacting previously overridden tax information, supporting scenarios for Minnesota and Colorado Retail Delivery Fees.

Customer Tax Code

As part of ongoing efforts to improve consistency and compliance in tax processing, this update introduces several important enhancements to the handling of tax codes within the Modern View Contact Center pages and across related APIs.

• Standardized Tax Code Drop-Downs: The ‘Tax Code’ field has been made uniform across all Modern View Contact Center screens, including Customer Tax Details, Order Entry (Shipping Tab), Order Summary (Edit Ship To), and Classic View WCST screens.

• Only the following options are available:

• Blank (default)

• Exempt

• GST Only

• PST Only

• Resale

• Non-Taxable and Standard Tax options have been removed to eliminate confusion and enforce compliance.

• Default Tax Code for New Records: When creating new Customer Sold-To records via UI or through APIs (Order Entry, Order API, WCST, Channel Advisor, Order Broker), the Tax Code defaults to Blank unless a valid tax exemption is specified (GST Only, PST Only, Resale with Tax ID, Exempt with Tax ID).

• API Updates: Updates to the Customer and Order APIs ensure that the Tax Code on new or edited records is only saved if it matches an allowed value. Invalid tax codes are not persisted.

• Tax ID Validation: For Exempt and Resale tax codes, entry of a valid Tax ID is now required for data integrity.

External Tax Service Integration: When using external tax services, exemption handling defers to the external provider based on customer class and selected tax code. Improved logic ensures consistent application of tax rules in all scenarios.

Note:

Existing customer records have been updated using a database script to ensure historic data aligns with new standards.

• Records previously set to Standard Tax is set to Blank.

• Records previously set to Non-Taxable is set to Exempt only if a Tax ID is present, otherwise set to Blank.

Order Administration: Merchandising Warehouse Cross Reference and RTLog Mapping

A new Merchandising Warehouse cross reference field has been introduced in the Warehouse record, allowing entry of a numeric warehouse code up to 10 digits to support integration with the Retail Merchandising Foundation Cloud Service (RMFCS) and Sales Audit (ReSA) modules. This field, accessible in the warehouse maintenance (WWHS) screens, can be used to map Oracle Administration warehouse codes to their corresponding physical warehouse codes in external merchandising and audit systems—resolving prior mismatches and failures associated with code length differences.

The enhancement directly impacts the generation of the ReSA RTLog file, which relies on accurate mapping of warehouse information during return transactions. Specifically:

• For returns that affect inventory, the RTLog TITEM transaction will now carry the cross-referenced Merchandising Warehouse code as the Return Warehouse when it is populated (non-zero), ensuring proper alignment with RMFCS and ReSA expectations.

• For returns that do not affect inventory, if ReSA Warehouse for Non-Inventory Returns (M56) is populated and the Merchandising Warehouse cross reference is populated, the RTLog will use this value and if blank, the warehouse code. If ReSA Warehouse for Non- Inventory Returns is blank, Default Warehouse (A04) system control value is used and the Merchandising Warehouse cross reference is populated, the RTLog will use this value; otherwise, it defaults to the Order Administration warehouse code.

• The change ensures continued compatibility with existing processes: if the cross-reference field is left blank or zero, the system reverts to previous logic using the Order Administration warehouse code.

Operationally, this enhancement only affects the RTLog file (all supported formats), with no changes to external invoice message layouts. Users should ensure that any new or updated warehouse records include the proper cross reference code for seamless downstream processing.

Order Administration: Enhanced Warehouse and Location Selection for Returns

The process for selecting warehouse and location during line-level returns has been improved on two Modern View Contact Center screens: the Return Order Line screen (accessed by selecting "Return" for an order line in Order Summary), and the Add Unverified Return Item screen (by entering a negative quantity in Order Entry for an item).

Key enhancements include:

• Dynamic Defaults: The Warehouse and Warehouse Location fields now proactively update their values based on the selected Return Disposition Code. If the code indicates inventory should not be affected, these fields are disabled. If inventory is to be affected, the fields will default to the item's primary warehouse/location (if defined) or to the values defined on the Return Disposition Code.

• User Flexibility: Users can select any warehouse (including options such as ‘Damage’ Warehouse) and see the Warehouse Location list immediately refreshed to include all valid locations for that warehouse and item.

  • Users may manually type in a valid location not otherwise displayed. The system ensures that any manually entered location is valid for the chosen warehouse. If an invalid location is entered, an error message is displayed, and the return is not processed.

• Real-Time Updates: Any change to the Return Disposition Code or Warehouse immediately updates the Warehouse and Location lists, supporting accurate and efficient returns processing.

Order Administration: Item Import Filtering by Location Identifier for Enterprise Foundation Integrations

A new enhancement introduces item and item image import filtering by Location Identifier for both Merchandising Omnichannel Web Services and Omnichannel Cloud Data Service (OCDS) integrations.

Both integrations leverage the OCDSITM periodic function, but which one is used depends on the system configuration. See the documentation for each import system control value for more information:

• OCDS Item URL (M45) 

• OCDS Item Image URL (M47) 

A new OCDS Filter Items by Location Identifier (M93) system control value controls whether items and item images imported are filtered based on a specified OCDS RMS Location Identifier (M52) system control value. When enabled, both item and image imports are limited to those associated with the defined location, ensuring that only relevant product data is loaded for targeted locations. When filtering is disabled, the import process continues to load the full product catalog and all associated images.

This enhancement provides greater flexibility and control to retailers, supporting more efficient imports and streamlined merchandising for both integration approaches.

Note:

Existing item data are not cleaned up as part of this process. If items are initially imported without the filter, they will need to be purged through other processes such as MPSK (Purging SKUs). If using MPSK, the item status must be populated first to find the qualifying records for purge.

Merchandise Hierarchy is the only URL that does not support the filtering by ‘nodelevel’ and ‘nodeid’, so that will not have any changes, and all records is imported.

Order Administration: ReSA RTLog Deduplication for Consolidated Invoicing

The deduplication logic during ReSA RTLog file generation to support consolidated invoicing has been updated to ensure more accurate reporting and processing by preventing duplicate transactions from being sent to ReSA, leading to cleaner data for financial and sales auditing.

Previously, deduplication evaluated the transaction_number field, which created challenges when multiple invoice transactions for the same order were generated, each with a sequential transaction number.

With this change, the RTLog process now identifies and removes duplicate SALE and RETURN transactions using the Reference_Number_31 (invoice number) field within the THEAD record. When consolidated invoicing is enabled (system control value B49 = Y), the INT_RESALOG staging table may temporarily contain multiple transactions for the same invoice, each with a different set of shipped lines. The enhanced logic ensures that only the invoice transaction containing all consolidated invoice lines is retained in the final RTLog.

Notably, PREPAY transactions are excluded from this deduplication process, as it is valid for multiple PREPAY transactions to exist for a single order within an RTLog file.

This update does not impact downstream message layouts, and all existing integrations for non-invoice transactions remain unaffected.

Order Administration: Order Purge Enhancements

The order purge processes now include additional related tables. This ensures associated records, such as tax response details, promotion and discount details, and return courier package and delivery information are correctly purged alongside orders.

The following purge routines have been updated: Order Purge by date or number of days (MPOR), Purging of individual orders (MORP), Purging Suspended Orders (PSOR), the periodic PURGEOR function, and the Order Cleanup (ORDCLNUP) function.

These enhancements prevent stranded records and ensure that all relevant data tied to an order is removed when an order meets purge eligibility criteria. Eligibility criteria continues to include requirements that orders must be closed or cancelled, with no recent activity, and have no pending returns or refunds.

Order Administration: Job Management

With this update, important improvements for jobs have been included to improve the safety, traceability, and correctness of job handling across critical queues, especially for batch operations.

Prevention of Job Rerouting from PICKGEN Queue: Jobs currently in the PICKGEN queue can no longer be rerouted to other queues. Any attempt to move such jobs prompts an error message, ensuring that jobs remain within the correct processing path.

Enforcement of Queue Order During Pauses: If a job in the PICKGEN queue is paused (such as during pod repaving), jobs queued behind it will not move forward or start running. The paused job is treated as if it is still running, maintaining the expected processing sequence and supporting the rule that only one PICKGEN job runs at a time.

Improved Audit Logging: Each time a job is manually moved from one queue to another via the My Jobs screen, a log message is generated. The message includes the job number, name, user who performed the move, and both the source and destination queues. This provides better visibility and supports troubleshooting for queue management activities.

Order Administration: Updates to Menu and Setting Names

To make the User Interface clearer and easier to use, several menu option names and descriptions have been updated. These changes remove unnecessary words and provide more accurate explanations.

• The "SCV Reversal" periodic function was renamed to "Card Authorization Reversal":

  • The SCVREV periodic function now has a clearer name to show it handles authorization reversals for credit, debit and stored value cards, not just stored value cards.

• "Manage Held Orders" renamed to "Held Orders":

  • The Modern View menu and related screen titles now simply read "Held Orders" making navigation more straightforward.

• "Manage Rejected Deposits" renamed to "Rejected Deposits":

  • The Modern View menu and related screen titles now simply read "Rejected Deposits" making navigation more straightforward.

• SCV B49 Narrative updated:

  • The description for the Consolidated Invoice (B49) system control value now accurately explains: “Controls whether items billed on the same business day will consolidate into a single invoice.”

Order Administration: IDCS Scope Restriction Readiness - Steps for External Integrations

IDCS or OCI IAM has announced restricting the use of urn:opc:idm:__myscopes__ which will require individual services to have their own predefined scopes.

REST services exposed externally by Order Administration require authentication from IDCS or OCI IAM, which is obtained by providing the IDCS OAuth Client ID and Secret along with a scope. In most cases, unless a service has a predefined scope, the scope urn:opc:idm:__myscopes__ is used. This scope grants broad access to all scopes associated with the specified OAUTH Client ID. 

Customers currently using urn:opc:idm:__myscopes__ are advised to switch to the existing scope rgbu:omscs:order-rw-<ENV_NAME> to avoid potential disruption. This advisory encourages customers to make this change proactively, ahead of the planned updates from IDCS or OCI IAM, to minimize any impact.

Order Administration: Customer Web Service Enhancements

With this update, Order Administration has created new web services available for external merchant applications.

• The Order Read/Write or Order Read Only scope is required for calling these services. Assign a Client ID access to this scope through the Manage External Application Access screen in Modern View.

Customer Services

The following options have been added to the Customer Services, for a specific customer record, where the data is also now available through the Order Administration: Modern View Customer Enhancements

• Get and Update additional data values.

• Get catalog history records.

• Check for duplicate address book records and allow the duplicate to be updated or return a list of matches.

• Create, Update and Delete of customer state and province exemptions.

• Get, Create, Update, Delete and Bulk Updates for customer actions and associated notes.

For more information, see the Order Administration Web Services Guide.

Order Administration: Database and Retail Data Store Updates

The Data Dictionaries include changes related to this update of Order Administration Cloud Service.

Order Administration has added new database columns with a type of TIMESTAMP(6) WITH TIME ZONE to persist dates and times in UTC related to Customer Actions and Notes, along with the Brokered Line Updates. Created and Updated By fields have also been added for tracking the user who performed the customer action update.

Database View	Columns Added
CUSTOMER_ACTION	CREATED, ASSIGNED, RESOLVED, UPDATED, CREATED BY, UPDATED_BY, ID
CUSTOMER_ACTION_NOTE	CREATED, UPDATED, CREATED BY, UPDATED_BY, ID
CUSTOMER_ACTION_REASON	CREATED, UPDATED, CREATED_BY, UPDATED_BY
ORDER_BROKER	UPDATED
WAREHOUSE	MERCH_WAREHOUSE

Order Orchestration Enhancements

Order Orchestration: Documentation Links

With this update, the Documentation section on the Home Page has been updated to guide users directly to the Order Management Suite Cloud Service main documentation library on the Oracle Help Center. Additionally, the "Documentation" menu option has been removed from the Order Orchestration Classic View UI.

This ensures users always access the most current product documentation.

Online help links accessed through icons in the upper right (Classic View and Modern View UIs) remain unchanged and continues to open the Order Orchestration Online Help.

Order Orchestration: Oracle Digital Assistant (ODA)

With this update, Order Orchestration is now integrated with Oracle Digital Assistant (ODA). The Oracle Digital Assistant (ODA) is an AI-powered platform that enables users to interact with various business applications and services through natural conversations via chat interfaces. This integration provides users with an intuitive and conversational self-service alternative to find information, workflows, and assistance in a single, unified approach, enhancing the overall self-service experience.

ODA leverages the existing Order Orchestration Guides to provide a response to user requests or questions.

If ODA cannot resolve your request, consult the documentation, or log a service request to get additional support.

Enabling ODA in Order Orchestration

A new property, "Use Oracle Digital Assistant", is now available in the Tenant and Tenant-Admin settings of Order Orchestration Cloud Service (OOCS). When enabled, the ODA widget icon will display in Modern View. The "Oracle Digital Assistant URL" property in the Tenant screen is also required for proper configuration. If these settings are disabled or left blank, the ODA icon does not appear.

For configuration issues or questions, please log a service request (SR) for Oracle assistance.

Accessing ODA in Modern View

To access ODA, click the conversation icon located at the lower left of any Modern View screen within Order Orchestration. The ODA functionality is only available in Modern View and is not present in Classic View.

Order Orchestration: IDCS Scope Restriction Readiness - Steps for External Integrations

IDCS or OCI IAM has announced restricting the use of urn:opc:idm:__myscopes__ which will require individual services to have their own predefined scopes.

REST and SOAP services exposed externally by Order Orchestration require authentication from IDCS or OCI IAM, which is obtained by providing the IDCS OAuth Client ID and Secret along with a scope. In most cases, unless a service has a predefined scope, the scope urn:opc:idm:__myscopes__ is used. This scope grants broad access to all scopes associated with the specified OAUTH Client ID. 

Customers currently using urn:opc:idm:__myscopes__ are advised to switch to the existing scope rgbu:obcs:order-rw-<ENV_NAME> to avoid potential disruption. This advisory encourages customers to make this change proactively, ahead of the planned updates from IDCS or OCI IAM, to minimize any impact.

Order Orchestration: Database and Retail Data Store Updates

The Data Dictionaries include changes related to this update of Order Orchestration Cloud Service.