| Oracle® Retail Xstore Office Cloud Service Administration Guide Release 18.1 F20380-02 |
|
 Previous |
 Next |
| Oracle® Retail Xstore Office Cloud Service Administration Guide Release 18.1 F20380-02 |
|
Previous |
Next |
This chapter describes possible integrations with Xstore Office.
Several integrations are possible, especially those sending data from Xstore Office using the broadcaster framework. For more information about broadcasters, see the information on Xstore Office Broadcaster System in the Oracle Retail Xstore Suite Implementation and Security Guide.
For cloud, broadcasters can be configured from the Xadmin UI. For more information on how to configure broadcasters, see the Broadcaster Management section in the Oracle Retail Xstore Office/Xstore Office Cloud Service User Guide.
Xstore Office sends information to Oracle Retail Customer Engagement (ORCE formerly Relate) via Broadcaster integration. It uses either ORCE custom authorization or OAuth2. The XSCS client (Xstore/Xcenter) will have to be granted the correct scope(s) defined in ORCE.
Xstore Office also uses SFTP to pull files from ORCE. The status is updated to POLL_FILE_STATUS and files extracted into the auto file-transfer directory.
Xstore Office sends information to Oracle Retail XBRi Loss Prevention (XBRi) via Broadcaster integration. It uses either XBRi custom authorization or OAuth2. The XBRi broadcaster will be configured via the Broadcaster UI.
Xstore Office sends product (ITM_ITEM) and inventory (INV_STOCK_LEDGER_ACCT) data to Oracle Retail Order Broker (OROB formerly Locate) via OROB's REST file service and uses basic auth for authentication.
Alternatively, Xstore Office can be configured to use SFTP to send to OROB using an SSH public/private key mechanism.
For 18.0, direct integration to Oracle Retail Order Management System (OROMS formerly Serenade) has been removed from Xstore Office. Instead, direct integration to OROMS happens from Xstore directly.
For more information about the integrations to Oracle Retail Merchandise Operations Management (MOM), refer to the Oracle Retail Xstore Suite 18.0/Merchandising Foundation Cloud Service 16.0.030 and Pricing Cloud Service 16.0.030 Implementation Guide.
Additional third-party integrations that need retail transaction data from Xcenter can access the Broadcaster REST Service to retrieve POSLogs. See the Oracle Retail Xstore Suite Services Guide for details on this service endpoint.
The Omnichannel Cloud Data Service is a repository for the merchandising and pricing data used by Oracle Retail Omnichannel Applications, such as Xstore POS and Customer Engagement.
OCDS is part of the Oracle Retail Integration Cloud Service along with other supporting infrastructure technologies used by Oracle Retail Enterprise Applications, including the Oracle Retail Bulk Data Integration (BDI) and Oracle Retail Integration Bus (RIB).
OCDS receives merchandising foundation data from Oracle Retail Merchandising Foundation Cloud Service (RMFCS). The initial load of the merchandising foundation data is communicated to OCDS from RMFCS using BDI, after which incremental updates are received by OCDS through RIB messages.
Merchandising foundation data includes:
Merchandise Hierarchy
Organizational Hierarchy
Store and Warehouse Locations
Differentiators and Dimensions
Items
VAT Tax Rules and Item Associations
Initial Prices
OCDS receives pricing data from the Oracle Retail Pricing Cloud Service (RPCS). Regular and clearance price changes and promotions are communicated from RPCS using BDI.
Omnichannel applications request data from OCDS by calling RESTful Web Services. Applications can request all data for a data type or only new, deleted, or changed data in OCDS since a point in time. Omnichannel applications typically call OCDS at regular intervals. For example, a typical request to OCDS from an Ommichannel application could be, ”What merchandise hierarchy data has changed since yesterday at midnight?”.
