Skip Headers
Oracle® Retail Sales Audit (ReSA) Oracle Retail Sales Audit (ReSA) User Guide
Release 15.0.1
E75843-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

3 Setting up ReSA

Before you proceed with processing the raw transaction data, you need to set up system options to allow importing and exporting data from ReSA. This chapter covers the following topics:

Setting up System Administration Options in ReSA

Use the system administration module of the ReSA application to customize information for your organization.

You can change system options to configure system validations around escheatment, voucher options, and information related to the Automated Clearing House (ACH).

Defining System Options

You can customize various parameters, defaults, and constants that are used throughout the system. Normally, these elements are set when ReSA is installed by the system or database administrator. They tend to remain fixed unless a business practice is changed which necessitates a change in ReSA.

A System Administrator can set the following system options in ReSA.

  • Balancing Level: Define the level (Cashier, Register, and Store) at which the system totals are summarized and reconciled against the reported value.

  • Unit of Work: Defines the level at which transactions are processed within ReSA. It is used to determine when to export data to external systems, and it needs to indicate that a transaction or store day must be free of any errors that prevent export.

    • For Transaction level, an individual transaction is exported from ReSA as soon as it is validated.

    • For Store Day level, the data imported in ReSA is exported only once the entire store day is processed.

  • Maximum Number of Days Sales Audit Data Stored: Defines the number of days for which the audited data is stored in the ReSA system.

  • Maximum Number of Days Post-Dated Trans. Allowed: Define the number of days after a store day has elapsed, within which backdated transactions will be permitted for upload into the system.

  • Maximum Number of Days to Compare Duplicates: Defines the number of previous days over which the ReSA system should look for duplicate transactions.

  • Inventory Reservation for Layaway: Specifies whether the inventory for Layaway orders is reserved.

  • Inventory Reservation from SIM: Specifies whether the inventory reserve for customer orders will come from SIM or ReSA will generate the flat file for RMS.

  • Credit Card Security Level: Indicates the level of Credit Card security used within the system. Valid values are: No security imposed (None), Restricted Access, or Block Credit Card information from coming into ReSA. By default this option is set to None.

  • Execute Automated Audit After Import: Indicates whether the automated audit should run after each import or if the ReSA system should wait until the transaction data for the entire store day is loaded.

  • Store Days Must Be Worked in Order: Indicates whether the ReSA system can close a current day if the previous day is still open.

  • Check for Duplicate and Missing Transactions: Indicates whether the ReSA application should look for duplicate and missing transactions. ReSA can accept duplicate transaction numbers from OMS and POS. If this field is set as 'Y', then ReSA filters duplicate transactions when the transaction is originating from the same system. Whereas, if the transaction is originating from a different system, then a different sequence number is inserted in the record.

  • Tran. No. Appended with Workstation ID: Indicates whether ReSA should append the workstation ID of the employee with their employee ID.

  • Partner ID: Specify whether the partner ID is unique across all partner types.

  • Partner Type: Specify the type of the partner the deal applies to. Valid values are: S1 for supplier hierarchy level 1, S2 for supplier hierarchy level 2, and S3 for supplier hierarchy level 3.

  • Credit Card Number Mask: Specify the masking character used for credit/debit card numbers.

  • Default Chain: Defines the primary chain.

  • Fuel Merchandise: Specify whether items for audit include fuel items.

  • Fuel Department: If the items for audit include fuel item, specifies the department the fuel items reside in.

  • Escheatment Details: Specify whether you would like to escheat vouchers (such as, gift certificates and credit vouchers) back to the state after a defined period of time. The value in the Escheatment field depends on the laws of the state/area where your organization's headquarters is located.

Adding Escheatment Details

To add Escheatment details:

  1. From the Tasks menu, select Foundation Data > Application Administration > System Options. The System Options window appears.

  2. In the Escheatment section, select Yes in the Escheat to Government Authorities field.

  3. Select the appropriate option in the Partner for Income Adjustment field.

  4. In the Escheatment Details section, select Actions > Add. The System Options - Add Escheatment Details window appears.

  5. In the Escheat To field, select either Country or State.

    • If you select country, in the Country field, enter the country code, or select the country.

    • If you select state, in the Country and State fields, enter the country and state codes, or select them from the list.

      Figure 3-1 System Options - Add Escheatment Details Window

      Surrounding text describes Figure 3-1 .
  6. In the Escheat To Location Of field, select the location to which the escheatment should be applied.

  7. Click OK to save your changes and close the window.

Defining Voucher Options

To define Voucher Options:

  1. From the Tasks menu, select Foundation Data > Application Administration > System Options. The System Options window appears.

  2. In the Vouchers section, select Actions > Add. The System Options - Add Voucher Options window appears.

  3. In the Tender Type field, select the tender type.

  4. In the Escheat No. Days field, enter the desired number of escheatment days.

  5. In the Purge No. Days field, enter the number of days a voucher will be valid before it is purged from RMS.

    Figure 3-2 System Options - Add Voucher Options Window

    Surrounding text describes Figure 3-2 .
  6. Click OK to save your changes and close the window.

Managing Data

ReSA and RMS allows the setup and configuration of a set of standard templates which allow you to upload and update data using spreadsheets. These spreadsheets can be uploaded to the system using the Manage Data window.

The following process is followed to update data for the above ReSA and RMS modules:

  1. Download the spreadsheet template for the module you want to update using the Manage Data window.

  2. Make the updates in the spreadsheet.

  3. Upload the data using the Manage Data window.

Downloading Data

To download data as spreadsheets:

  1. From the Tasks menu, select Foundation Data > Data Loading > Manage Data. The Manage Data window appears.

  2. In the Action field, select Download.

  3. In the Template Category field, select ReSA or RMS.

  4. In the Template Type field, select the type of template.

    The following template types are available for the category ReSA:

    • Error Codes

    • GL Cross Reference

    • Reference Fields

    • Currency Rounding Rules

    • Store Data

    The following template types are available for the category RMS:

    • Administration

    • Financial

    • Foundation

    • Franchise

    • Import

    • Inventory

    • Price and Cost

    • Item Maintenance

    • Sales Audit

  5. In the Template field, select the template you want to download.

    Figure 3-3 Manage Data Window for a Template Download from ReSA

    Surrounding text describes Figure 3-3 .

    Figure 3-4 Manage Data Window for a Template Download from RMS

    Surrounding text describes Figure 3-4 .
  6. You cannot enter a process name in the Process Name field as the field is dimmed.

  7. You cannot select the spreadsheet to be downloaded in the Source File field as the field is dimmed.

  8. Click Submit.

Uploading Data

To upload data using spreadsheets:

  1. From the Tasks menu, select Foundation Data > Data Loading > Manage Data. The Manage Data window appears.

  2. In the Action field, select Upload.

  3. In the Template Category field, select ReSA or RMS.

  4. In the Template Type field, select the type of template.

    The following template types are available for the category ReSA:

    • Error Codes

    • GL Cross Reference

    • Reference Fields

    • Currency Rounding Rules

    • Store Data

    The following template types are available for the category RMS:

    • Administration

    • Financial

    • Foundation

    • Franchise

    • Import

    • Inventory

    • Price and Cost

    • Item Maintenance

    • Sales Audit

  5. In the Template field, select the template of the spreadsheet.

    Figure 3-5 Manage Data Window for a Template Upload from ReSA

    Surrounding text describes Figure 3-5 .

    Figure 3-6 Manage Data Window for a Template Upload from RMS

    Surrounding text describes Figure 3-6 .
  6. Enter a process name in the Process Name field. The value specified in this field enables you to find the process created to identify the status of the upload and view any errors that were identified.

  7. Select the spreadsheet to be uploaded in the Source File field.

  8. Click Submit. The relevant data corresponding to the template is uploaded into the spreadsheet file specified.

Manage Employees

The Employees window is used for associating auditors with the locations based on location traits in the system. This screen has two tables, the Employee table and the Location Trait table. Data displayed in the Location Traits table is based on the records elected in the Employees table. The Employees table displays the Employee ID and the associated display name from the LDAP.

Adding an Employee

To add an employee:

  1. From the Tasks menu, select Foundation Data > Application Administration >Employee. The Employees window appears.

  2. In the Employees section, select Actions > Add. The Add Employee window appears.

  3. Enter the employee name in the Employee field.

  4. Click OK. If the employee exists in LDAP, the employee name is added.

Assigning Stores to an Employee

After an employee is added, you must assign stores using a location trait to the employee.

To assign a location trait:

  1. From the Tasks menu, select Foundation Data > Application Administration >Employee. The Employees window appears.

  2. Select an employee from the Employees section.

  3. In the Assign Stores by Location Traits section, select Actions > Add. The Add Location Trait window appears.

  4. Select the location trait in the Location Trait field.

  5. Click OK. The location trait is assigned to the selected employee.