Order Orchestration Enhancements
Order Orchestration: External Application Client Management
With this update, the Manage External Application Access screen now calls Oracle Retail Home APIs, instead of Oracle Identity Cloud Service (IDCS) or Oracle Cloud Infrastructure Identity and Access Management (OCI IAM) APIs, to generate new application clients and secrets, regenerate a secret for an existing client and assign or unassign a scope to an existing client. This enhancement streamlines the client management process and improves security by centralizing client-related operations.
Note:
Oracle Retail Home version 25.1.301.0 or above is required.
Order Orchestration will continue to communicate directly to IDCS or OCI IAM for retrieving new clients and new user creation.
When the 'Refresh Applications' action is triggered, the system now compares the scopes assigned in IDCS or OCI IAM with those stored in Order Orchestration for each application client. If any discrepancies are found, the scopes are automatically updated to match, ensuring consistency. This synchronization process is particularly useful when scopes are manually assigned or unassigned through the Retail Home UI, as it helps to quickly rectify any resulting inconsistencies.
The ability to generate an ‘Xoffice On Prem’ client is no longer available within Order Orchestration. Instead, within the Manage OAuth Client option in Retail Home, create the Client using the ‘Xoffice OnPrem Omni App’ template, if not already created. Once created in Retail Home, click Refresh Applications to update the clients and assign web service access.
Order Orchestration: Vendor User Group Management
With this update, the Identity Cloud User Synchronization job no longer automatically creates the vendor user groups in IDCS or OCI IAM that corresponded to each vendor created in Order Orchestration.
Optionally, create the vendor groups and assign them to the OBCS_Vendor_User role in IDCS or OCI IAM, or assign the Vendor after user creation within the Vendor User Profiles screen under a new “Requires Vendor” option. The “Requires Vendor” column indicates if the user has access to the OBCS_Vendor_User role in IDCS or OCI IAM but was not assigned to a valid vendor upon creation of the user profile.
Previously created vendor user groups will still be available in IDCS or OCI IAM. For new vendors, the vendor user groups will need to be manually created in IDCS or OCI IAM and then assigned to the OBCS_Vendor_User role. The group should be created as ‘OBCS|<environment>|<system>|<vendor>’, where:
-
<environment> is the current environment.
-
<system> is the system code identifying the default vendor system.
-
<vendor> is the code identifying the vendor.
A vendor must be associated to a user to allow the user to log into the Vendor Portal.
Order Orchestration: Store Connect User Group Management
With this update, the Identity Cloud User Synchronization job no longer automatically creates the Store Connect user groups in IDCS or OCI IAM that corresponded to each Store Connect system created in Order Orchestration.
Optionally, create the store connect groups and assign them to the OBCS_Store_User role in IDCS or OCI IAM, or assign the User directly to the OBCS_Store_User role. A new “User does not have access to Store Connect” error message displays in the Store Connect tab of the User screen when the OBCS_Store_User role is not assigned. Once the role is assigned, this error is removed, and “Store Connect” displays under the Access column of the Users list page.
Previously created Store Connect user groups are still available in IDCS or OCI IAM. For new Store Connect systems, the Store Connect user groups need to be manually created in IDCS or OCI IAM and then assigned to the OBCS_Store_User role. The group should be created as ‘STC-<system>’, where <system> is the system code identifying the default Store Connect system.
A store user must be associated to a location to allow the user to log into Store Connect.
Order Orchestration: Web Service Enhancements
With this update, all Locate SOAP web services now support message version 25.2 to enable new logic. See below for specific enhancements.
Pick Reference Duplicate Check
SubmitOrder SOAP v25.2 and REST v2 now support a new pick_reference attribute, for sending an additional value to be used in the duplicate order check logic.
-
When the pick_reference is populated, it is stored in the XOM_ORDER and XOM_ITEM_DUP_CHECK tables and synchronized with Retail Data Store.
-
The duplicate order check logic now includes the System Code, Order Id, Requester Line Number and Pick Reference.
-
If a duplicate is found, the response will include the pick_reference in the description.
See Partial Brokered Line Quantity Updates for when Order Administration populates this attribute.
Eligible Same Day Delivery Locations
The Product Availability REST API has undergone a restructuring to include improvements about eligible Same Day Delivery locations to make your delivery choices more flexible and accessible. Previously, only pickup locations were returned for Store Pickup and Ship for Pickup fulfillment types.
When utilizing the latest API version (2.0, REST) and meeting specific criteria, you receive a customized response that includes a location and product location attributes. The following must be in the request message to qualify for the additional details:
-
fulfillmentType must be DELIVERY.
-
includeLocationDetails must be true.
The API request format remains consistent, requiring essential details such as item code, quantity, and address. However, the ‘pickupLocations’ object has been renamed to ‘locations’, and it has been enriched by providing a list of eligible delivery locations. These locations are thoughtfully sorted by their proximity to your shipping address, making it easy to identify the closest and most convenient options. Additional attributes have been added for each location including availableQuantity, distance, distanceUnit, locationCd, nextPOQuantity, systemCd, storeHours, latitude and longitude.
If there are more than 10 eligible delivery locations, the system presents a maximum of 10, ensuring a concise and manageable selection process.
Note:
The ProductAvailability SOAP API does not include the ability to return Same Day Delivery locations.