| Oracle® Retail Central Office User Guide Release 14.1 E54471-01 |
|
 Previous |
 Next |
The Transaction Tracker feature provides enterprise-wide accumulation of transaction, electronic journal, customer, and signature data with the ability to query entries based on business needs and to monitor for potential fraud or training issues, such as deleted items, tenders, and discounts. The use of a centralized corporate database gives retailers the ability to resolve credit disputes quickly, reduce paper storage and handling, and decrease general auditing efforts. Transaction Tracker provides the following benefits:
Import of transaction, electronic journal, customer, and captured signature data to the corporate database
Extensive transaction search capabilities including transaction identifiers, tender types, IDs (for example, credit card numbers), sales associate information, and types of data such as a captured signature
Support for transaction types including sales, returns, voids, till functions, house accounts, layaways, orders, and other operations
Web-based views of transaction, electronic journal, customer, and signature data
Support to export information to PDF and RTF formats
Access to customer information and captured signatures is controlled by security role and user ID
For information on each available search, see Table 4-1.
Transaction data including any captured signatures and customer information, as well as electronic journal data and POSLog that show a step by step log of events, are sent from stores to the corporate database. For more information on how to import the transaction data, see "Importing Data" in Chapter 3.
For a transaction, the following data is available:
Transaction number.
Each transaction is identified by a transaction number. By default, a transaction number is composed of the store number plus a register number plus a transaction sequence number. The transaction number is not unique as the transaction sequence number is reused. When a transaction number is combined with the date and time of the transaction, this creates a unique identifier for a transaction.
Type of transaction.
Store where the transaction occurred.
Employee who performed the transaction.
Description of items.
Customer information, if captured with the transaction.
Payment information including signatures captured.
Results from a search can be exported to PDF or RTF format.
Click a left navigation link to choose the type of search. Table 4-1 describes the types of search information which is available for each search.
Table 4-1 Types of Search Information
| Type | Description |
|---|---|
|
Choose to search nodes in the store hierarchy or to search by store number. To search by node, click Use Hierarchy to search. Choose the node in the store hierarchy. A check next to a node name indicates that node is selected for the search. You can click a triangle next to any node name to display the child nodes or to hide the child nodes from view. To search by store number, click Or search by store number. Enter the start and end store numbers. |
|
|
Choose the specific criteria for the search. See the section in this chapter for the criteria available for each search. Some searches allow multiple sets of information to be used. For example, search by item also allows the selection of transaction information. |
|
|
Enter the maximum number of customers displayed on a page. If the number of customers found is greater than this number, navigation is provided at the bottom of the results list to enable you to select the next, previous, or specific page of data. |
See Figure 4-1 for an example of a search selection screen.
For each set of search information available, a check box allows you to choose if that criteria should be used. When you select a check box, more fields appear on the screen. Enter any of the information. If a box is not selected, none of the fields are shown and that information is not used for the search. By default, Hierarchy Information and the information specific to the type of search chosen have the check box selected.
Only transactions that meet all of the search criteria are displayed.
Searching by transaction is used here as an example to describe the available functions for searching for transactions and viewing the results.
Click Transaction. The Search By Transaction screen is displayed.
To search for transactions:
Select the check box to choose any of the information you want to use in the search. Enter the information. If you want to reset all the fields to the default values, click Clear Search.
Click Search. The Transaction Search Results screen is displayed. If only one transaction is found that meets the criteria, the Transaction Detail screen is displayed instead.
The Transaction Search Results screen shows the list of transactions that meet all of the selection criteria. This screen displays the same information for all the searches.
The following information is shown for each transaction:
Select to Export. A selected checked box indicates the transaction information is selected to be exported. Select the Select All check box to choose all of the transactions found on the search.
Store number and name where the transaction occurred
Register number
Transaction number
Date and time when the transaction occurred
Type of transaction
Currency
To return to the Search By screen, click Done.
To view the transaction details, click the transaction number. The Transaction Detail screen is displayed.
The Transaction Detail screen is displayed when you click a transaction number on the Transaction Search Results screen or the Data View link.
The following hierarchy and transaction information is shown for all types of transactions:
Path in the store hierarchy where the transaction occurred
Transaction number
Date and time the transaction occurred
Type of transaction
Name and ID of the employee who performed the transaction
Indicator if training mode was in effect at the Oracle Retail Point-of-Service register when the transaction occurred
Indicator if the transaction was entered when reentry mode was in effect at the Oracle Retail Point-of-Service register
Status of the transaction
Store Currency
Original Transaction Currency
Additional information displayed is dependent on the type of transaction. For example, for a sale transaction, the items sold, totals, and tenders applied are shown.
At the top left of each detail screen, links are provided to view other information that is available. You can click Data View (transaction details), Journal View, Signature Capture View, and Customer Information View. Click a link and the data is displayed. If the data is not available or you are not allowed to see that detail view, the link is not displayed.
Value added tax (VAT) is a tax added at various stages of production based on the value added to the product at that stage.
For transactions that occurred at a store with VAT enabled, the Tax column is not shown in the Totals section. Instead, the Tax Summary section is added at the bottom of the screen. This section contains information on the VAT applied to the transaction. The following figure shows an example of this section.
Table 4-2 describes the columns shown in this section of the Transaction Detail screen.
Table 4-2 Tax Summary Columns
| Column | Description |
|---|---|
|
VAT Rate/Code |
The percentage rate and the code for each VAT. |
|
Excluding Tax |
Total amount of items to which this VAT was applied. A total of all the amounts is shown at the bottom of this column. |
|
Tax |
Total amount of VAT applied at this rate. A total of all the VAT applied is shown at the bottom of this column. |
|
Including Tax |
Total amount of items plus the total amount of VAT applied. A total of the amounts is shown at the bottom of this column. |
The journal is an audit log of the operator and system events that occurred for the transaction in the order in which they occurred. The information and events that are displayed depend on how the journal entry is defined by the retailer.
|
Note: The information on this screen is displayed in the default locale of the store where the transaction occurred. |
Click Journal View. The Journal View screen is displayed.
This view is only available if signature data was captured for the transaction. Click Signature Capture. The Signature Capture View screen is displayed.
Table 4-3 describes the information shown on this screen.
Table 4-3 Signature Capture View Sections
| Section | Description |
|---|---|
|
Hierarchy |
Path in the store hierarchy where the transaction occurred |
|
Transaction |
|
|
Signature Capture(s) |
If the signature was captured for a credit card, the following information is displayed:
If the signature was captured for a pickup or delivery, only the captured signature is displayed. |
This view is only available if customer information is attached to the transaction. Customer information is not captured through a credit or debit card, but is specifically attached and maintained in customer tables. This data is part of the POSLog.
Click Customer Information. The Customer Information screen is displayed.
The following information is shown in this screen:
Customer ID and type
Name, including any salutation or suffix, address
Address and telephone number
Preferred language
Birthday
Indicators if mail, telephone, or e-mail is allowed
Preferred customer discount
Employee ID, if an employee is linked to the transaction
From the Transaction Search Results screen or any of the detail screens, the results can be exported in order to be viewed in a supported output format. You choose the output format and view the results using an application intended for that format. The application reformats the data, if needed, before it is displayed. The available formats are PDF and RTF. The results can only be viewed in the chosen output format if the application required to view that format is available.
|
Note: To export signatures for credit dispute research, PDF should be used. Other formats do not render the signature as a drawing. |
To export the search results you are viewing:
Click Export. The Export screen is displayed.
Enter the file name and select the output format.
Click Save. The application that is required for the selected output format is started. The results are displayed using that application.
Click the left navigation link for the search you want.
Transaction IDs are a combination of store number, register number, and sequence number. To search by a range of transaction numbers, you can enter any of the following information:
|
This search is used to find transactions based on item criteria.
The following item information can be chosen:
Serial number
Item number
UPC
Price Override Applied—a manual price override was entered
Item Cleared—item was rung up and then cleared from the transaction
Transaction information can also be chosen.
This search is used to find transactions based on transaction and tender criteria.
The following transaction information can be chosen:
Transaction number
Order number
External order number
Start and end sequence numbers
Start and end register numbers
Start and end system dates and times
Business date
Transaction type
Training mode—if an employee was being trained when a transaction occurred
Reentry mode—if transactions were manually entered from paper, for example, when recovering from a power outage
Store Currency
Original Transaction Currency
The following tender information can be chosen:
Tender type
Tender ID—identification number associated with the tender, for example, credit card number
Minimum and maximum tender amount
This search is used to find transactions based on sales associate criteria.
The following sales associate information can be chosen:
Sales associate employee ID
Cashier number
Transaction and item information can also be chosen.
This search is used to find transactions based on customer criteria.
The following customer information can be chosen:
Customer ID
First and last name
Address
Telephone number
Transaction information can also be chosen.
This search is used to find transactions based on signature capture data. Only transactions with signatures captured for a tender used for a retail transaction are found by this search.
The following signatures captured information can be chosen:
Transaction number
Transaction date
Tender amount
Transaction amount
Tender type
Tender ID
Card number (first 6 digits)
Card number (last 4 digits)
This search is used to find transactions based on minimal transaction criteria. It searches through the minimal key data that has been captured with the electronic journal at the Oracle Retail Point-of-Service application and imported to the corporate database.
The following electronic journal information can be chosen:
Transaction number
Start and end sequence numbers
Start and end register numbers
Start and end system dates and times
Business date
