1 Overview
This document describes integration between the Xstore suite of solutions and the Merchandising Cloud Services of solutions. For Merchandising, this document covers functionality supported in both the on premise and cloud service versions of the following products:
On Premise Solution | Cloud Service Solution |
---|---|
Oracle Retail Merchandising System (RMS) |
Oracle Retail Merchandising Foundation Cloud Service (RMFCS) |
Oracle Retail Sales Audit (ReSA) |
Oracle Retail Merchandising Foundation Cloud Service (RMFCS) |
Oracle Retail Pricing (RP) |
Oracle Retail Pricing Cloud Service (RPCS) |
For the Xstore Suite, this document covers functionality supported in the following products:
On Premise Solution | Cloud Service Solution |
---|---|
Oracle Retail Xstore Office |
Oracle Retail Xstore Office Cloud Service (XOCS) |
Oracle Retail Xstore Point of Service |
NA |
The integration of the Merchandising Cloud Services and the Xstore Suite consists of two major data flows:
-
Inbound: Merchandising and pricing information is consumed by Xstore Office where data is loaded into the Xcenter database and files are automatically distributed for data loading into Xstore databases.
-
Point of Service transactions from Oracle Retail Xstore Point of Service flow to Xstore Office for transformation and distribution to the Merchandising Foundation Cloud Service Sales Audit module.
In combination, these data flows represent the round trip of data between the stores and headquarters. New items, other foundation data, and prices from headquarters are communicated to Xstore. Sales and returns from Xstore are communicated to Merchandising, where these transactions impact inventory. Merchandising further integrates summarized sales and inventory information from Xstore to other Oracle Retail applications, such as Planning and Analytics.
Inbound: Integration Options with Xstore Office
The inbound Xstore Suite integration from Merchandising is achieved using platform specific integration interfaces. Table 1-1 lists important details about the integration options available to the two Xstore Office deployment topologies: Cloud vs On-Premise. The inbound Xstore Office integration interfaces are:
-
RMFCS/RPCS web services – Xstore Office requests merchandising and pricing data directly from Merchandising and Pricing Cloud Services
-
OCDS web services - Xstore Office requests merchandising and pricing data from OCDS, which is a data hub.
-
RMFCS/RPCS flat file export – Merchandising and pricing data exported from RMFCS and RPCS can be imported into Xstore Office using momzip archive files.
Table 1-1 Inbound Xstore Suite Merchandising Integration Matrix
Xstore Office | Merchandising and Pricing System Data | ||
---|---|---|---|
Direct Web Services(1) | OCDS(2) | Flat File(3) | |
Cloud |
Yes |
Yes |
Yes |
On-Premise |
YesFoot 4 |
Yes |
Yes |
Footnote 1 Introduced in v21 of MFCS /RPCS
Footnote 2 OCDS is only available with MFCS v19x. It was replaced with Direct Web Services in v21+.
Footnote 3 RPCS flat file export does not support export of promotions
Footnote 4 OAuth credentials to be obtained from Oracle Retail Home
Outbound: Integration Options with Xstore Office
The outbound Xstore Suite integration to the Merchandising Foundation Cloud Service Sales Audit module is achieved with two options.
-
Using RTLog flat files generated by RTLog generator. Depending on Xstore suite and Sales Audit deployment topologies, different file delivery options are supported including SFTP, FTS, REST download, or publishing to file system folder.
-
Using direct Sales Audit REST service integration. RTLog generator is not involved.
Table below lists important details about the integration options available to the two Xstore Office deployment topologies: Cloud vs On-Premise.
Table 1-2 Outbound Xstore Suite Merchandising Integration Matrix
Xstore Office | Merchandising Foundation Cloud Service Sales Audit | ||||
---|---|---|---|---|---|
Sales Audit (REST) | SFTP | FTS | File Download (REST) | Publish to File System Folder | |
Cloud |
YesFoot 5 |
YesFoot 6 |
YesFoot 7 |
Yes |
No |
On-Premise |
YesFoot 8 |
No |
YesFoot 9 |
No |
Yes |
Footnote 5
XOCS integration with Sales Audit REST API only available in RMFCS V21+
Footnote 6
XOCS integration with SFTP is only available in RMFCS V19
Footnote 7
XOCS integration with FTS only available in RMFCS V21+
Footnote 8
Xstore Office On-Premise integration with Sales Audit REST API only available in RMFCS V21+.
OAuth credentials to be obtained from Oracle Retail Home.Footnote 9
Xstore Office On-Premise integration with FTS only available in RMFCS V21+
. OAuth credentials to be obtained from Oracle Retail Home.The details of the integration are covered in the remaining sections of this guide:
-
Data Flow from Merchandising to Xstore: This chapter describes the flow of data from the Merchandising applications to the Xstore Suite.
-
Transaction Flow from Xstore to Sales Audit: This chapter describes the flow of transactions from Xstore Point of Service to Sales Audit.
-
Webservice Integration Configuration: This chapter provides information on the configuration changes that can be made for the integration.
-
Integration Considerations: This chapter covers functional and technical points about the integration that need to be taken into consideration when implementing the integration.
-
RTLog Generator On-Premise: This chapter covers how to install, deploy, and configure the RTLog Generator application.
-
RTLog Generator Cloud: This chapter covers the RTLog Generator Cloud.
-
Appendix: Xstore to Sales Audit Mapping Details: This appendix provides tables that describe the mappings.
-
Appendix: Flat File Mapping: This appendix describe the flat file mapping.
Xstore Office [On-Prem Only]: OAuth Credentials
The direct service MFCS integration, Sales Audit REST integration, and RTLog FTS integration require the use of OAuth client credentials in order for Xstore Office to communicate with MFCS/Sales Audit. Credentials should be obtained through the use of Oracle Retail Home. Once obtained, the Client ID, Client Secret, and Scope, should be submitted into Xstore Office using Xadmin's Credentials Manager.
Figure 1-1 Credentials Storage
![Credentials Storage Page Credentials Storage Page](img/credentials_storage.png)