Order Orchestration Enhancements
Order Orchestration: Business Time Zone
With this update, Order Orchestration has created new Inbound and Outbound API versions that now include attributes that support ISO 8601 standard date and time with offset formats. The new format allows your business to send in various dates in any time zone, and Order Orchestration will store in UTC and return in UTC.
See below for the logic on how the system handles the different attributes passed. In most messages, the format of the existing attributes has changed from date and time to ISO 8601. Review all changes when updating to the latest version to avoid invalid data being passed. Oracle Retail recommends leveraging the new attributes to be able to define the time zone offset from the external system mapping to avoid mismatch in dates across the applications.
The inbound attributes require ISO 8601 in supported formats of (the .mmm is optional):
- yyyy-mm-ddThh:mi:ss.mmmZ where the Z is Zulu, an abbreviation for UTC.
- yyyy-mm-ddThh:mi:ss.mmm+00:00 where the +00:00 represents a time offset from UTC of 0 hours which is UTC or GMT
- yyyy-mm-ddThh:mi:ss.mmm-06:00 where the -06:00 represents a time offset from UTC of - 6 hours which is US/Central Standard Time
The outbound attributes are in ISO 8601 format with 3 milliseconds (no rounding): yyyy-mm-ddThh:mi:ss.mmmZ where Z is Zulu, an abbreviation for UTC.
SOAP Web Service Enhancements
| SOAP Message | Attributes in request that require ISO 8601 format | Attributes in response in ISO 8601 format |
| Availability Update v25.1 | datetime | datetime |
| Fulfillments v25.1 | datetime |
datetime transaction_date |
| Intransit v25.1 | datetime |
datetime transaction_date |
| Locate Items v25.1 | datetime | datetime |
| Order Search v25.1 | datetime |
Datetime order_date status_date shipment_date **** |
| Order Status Inquiry v25.1 | datetime |
datetime order_date status_date shipment_date **** |
| Order Status List v25.1 | datetime |
datetime order_date status_date shipment_date **** |
| Order Status Update v25.1 |
datetime status_date ** |
datetime |
| Order Update v25.1 | datetime | datetime |
| Product Availability v25.1 | datetime | datetime |
| Product Update v25.1 | datetime | datetime |
| Submit Order v25.1 |
datetime transaction_date *** |
datetime |
** The existing status_date attribute value will be converted using the timezone offset to UTC when persisting in the new 'SHIPPED' column in the XOM_ORDER_ITEM_CARTON and XOM_ORDER_SHIPMENT tables for an intransit and fulfilled status update. When the offset is passed, the system will no longer use the Time Zone on the Tenant screen for additional conversions. For release 23.2 or earlier, the system continues to pass the existing format and logic. If only the date passed and no time, the system will concatenate midnight (00:00:00) as the time and the offset for the Time Zone set in the Tenant screen. Once that date/time with time zone string is created, it will be stored in the database in UTC.
*** The existing transaction_date attribute value will be converted using the timezone offset to UTC when persisting in the ORDER_DATE column in the XOM_ORDER. For 23.2 or earlier, the system continues to pass the existing format and logic where the system assumes it's passed in the Retailers Time Zone configured on the Tenant screen, then it converts that value into UTC.
**** A new shipment_date attribute will be set from the new ‘SHIPPED’ column in the XOM_ORDER_SHIPMENT when present, otherwise from XOM_ORDER_ITEM_CARTON if present. If not present in either table, it will be set from the legacy SHIP_DATE column in UTC. The value will be in ISO 8601 format still.
Rest Web Service Enhancements
| REST Message | Attributes in request that require ISO 8601 format | Attributes in response in ISO 8601 format |
| getInventoryAvailability v2 | datetime | datetime |
| Order Search v2 | shipped *** | |
| Status Update v2 | status_date ** | |
| Status List + Status v2 | shipped *** | shipped *** |
| Email Out v2 | shipmentDateTime **** |
** The existing status_date attribute value will be converted using the timezone offset to UTC when persisting in the new 'SHIPPED' column in the XOM_ORDER_ITEM_CARTON and XOM_ORDER_SHIPMENT tables for an intransit and fulfilled status update. When the offset is passed, the system will no longer use the Time Zone on the Tenant screen for additional conversions.
*** A new shipped attribute (in the StatusListItemDetail element) will be set from the new ‘SHIPPED’ column in the XOM_ORDER_SHIPMENT when present, otherwise from XOM_ORDER_ITEM_CARTON if present. If not present in either table, it will be set from the legacy SHIP_DATE column in UTC. The value will be in ISO 8601 format still.
**** The existing shipmentDateTime attribute will be set from the new ‘SHIPPED’ column in the XOM_ORDER_SHIPMENT when present, otherwise from XOM_ORDER_ITEM_CARTON if present. If not present in either table, it will be set from the legacy SHIP
Order Orchestration: Oracle Maps
With this update, Oracle Maps is now licensed as a base offering and delivered with the Order Management Suite.
To enable, configure the provided URLs into the preference fields on the Tenant-Admin screen in Order Orchestration.
Geocode Address: https://elocation.oracle.com/appidGC000113/geocoder/gcserver
Turn-by-Turn Distance URL: https://elocation.oracle.com/appidGC000113/routeserver/servlet/RouteServerServlet
The About Order Orchestration Cloud Service page in Modern View now includes links to terms and policies for Oracle Maps.
Order Orchestration: Database and Retail Data Store Updates
The Data Dictionaries include changes related to this update of Order Orchestration Cloud Service.
Order Orchestration has added new database columns with a type of TIMESTAMP(6) WITH TIME ZONE to persist dates and times in UTC. Each new column is available through Retail Data Store for custom reporting.
| Database View | Columns Added |
|---|---|
| XOM_ORDER_ITEM_CARTON | SHIPPED |
| XOM_ORDER_SHIPMENT | SHIPPED |