3 Transaction Flow from Xstore to ReSA

Xstore is the source of Point of Sale (POS) transactions, including but not limited to the following:

• Sales

• Returns

• Voids

• Cash management transactions

• Many store activity transactions

All transactions produced in Xstore are sent to ReSA. ReSA processing is primarily concerned with transactions that alter inventory or contain payment. ReSA loads other types of Xstore transactions (such as entering training mode, gift registry creation, and so on) into an OTHER transaction type for full visibility and to avoid gaps in the transactions sequence, but will not out of the box perform any audit functions on these OTHER types of transactions.

ReSA validates Xstore transactions that impact inventory (such as sales, returns, and customer orders) and exports the information to RMS to record the full financial and inventory impact.

Conceptual Data Flow

Figure 3-1 illustrates the transaction flow from Xstore to ReSA.

Figure 3-1 Xstore to ReSA Transaction Flow

The following steps describe the flow shown in Figure 3-1:

1. All Xstore registers replicate, or persist, all transactions to Xcenter. Note that this includes both customer related transactions (sale, return, void, and so on) and cash management/store operation transactions (paid in, no sale, change to training mode, and so on). Xcenter uses these transactions for activities such as cross location returns.

2. Xcenter broadcasts all transactions to ReSA in the form of RTLogs generated multiple times per day. For more information, see "ReSA saimptlog/i".

3. After successful totaling and auditing, ReSA sends all sale/return transactions to RMS, where the transactions impact perpetual inventory. For detailed information about uploadsales_all.ksh, see Oracle Retail Merchandising System Operations Guide, Volume 1 - Batch Overviews and Designs.

Technical Implementation

The technical implementation of the foundation/price data from Merchandising to Xcenter/Xstore consists of three main components:

• Xstore Broadcaster

• RTLog Generator

• ReSA saimptlog/i

Xstore Broadcaster

The broadcast system in Xcenter provides a means to transmit POSLog data to other systems. The data is transmitted just as Xcenter receives it from the registers through the replication system, which is approximately in real-time. The temporal ordering of the POSLog data is also preserved, just as it is with the replication system.

There are a few systems which the base version of Xcenter can readily broadcast data to, simply by making configuration changes.

For more detailed information, see the following documents:

• Retail Reference Architecture available on My Oracle Support

• Oracle Retail Xstore Technical Guide available on My Oracle Support

• Oracle Retail Xstore Suite Implementation Guide

RTLog Generator

RTLog generator is a component that collects and aggregates broadcaster transactions and transforms them to the RTLog file format. The RTLog generator is packaged with Xstore, but is generally deployed in the same file system as ReSA.

For more information, see Chapter 6.

ReSA saimptlog/i

ReSA is the gateway for POS transactions to integrate to Oracle Retail headquarter systems. There are two ReSA sub-processes that can upload POS files:

• saimptlogi.c validates files and directly inserts the transactions into the ReSA tables. This includes (as necessary) creating errors for the auditors to research and correct.

• saimptlog.c validates POS files and creates Sql*Loader Files. This includes (as necessary) creating errors for the auditors to research and correct. A subsequent Sql*Load process loads the transactions and errors into the ReSA tables.

saimptlog and saimptlogi are built with the same shared code and vary only in their approach to physically loading data into the database. The programs are collectively referred to as saimptlog/i.

There are a number of regular prerequisites in the ReSA batch schedule which must be completed before POS transactions can be loaded. For more information about supporting batch jobs, see Oracle Retail Merchandising System Operations Guide, Volume 1 - Batch Overviews and Designs.

For more detailed information about saimptlog/i and the RTLog file format, see the following documents:

• Retail Reference Architecture available on My Oracle Support

• Oracle Retail Merchandising System Operations Guide, Volume 1 - Batch Overviews and Designs