furniture retail system (frs) - oracle till... · oracle® retail furniture retail system ......

Oracle® Retail Furniture Retail System (FRS)

MIDAS Till Interface Guide Release 1101

October 2015

Oracle® Retail Furniture Retail System (FRS) MIDAS Till Interface Guide, Release 1101

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

Primary Author: John Hardwick

Contributors:

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

iii

Value-Added Reseller (VAR) Language

Oracle Retail VAR Applications

The following restrictions and provisions only apply to the programs referred to in this section and licensed to you. You acknowledge that the programs may contain third party software (VAR applications) licensed to Oracle. Depending upon your product and its version number, the VAR applications may include:

(i) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation (MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.

(ii) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of Kirkland, Washington, to Oracle and imbedded in Oracle Retail Mobile Store Inventory Management.

(iii) the software component known as Access Via™ licensed by Access Via of Seattle, Washington, and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.

(iv) the software component known as Adobe Flex™ licensed by Adobe Systems Incorporated of San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization application.

You acknowledge and confirm that Oracle grants you use of only the object code of the VAR Applications. Oracle will not deliver source code to the VAR Applications to you. Notwithstanding any other term or condition of the agreement and this ordering document, you shall not cause or permit alteration of any VAR Applications. For purposes of this section, "alteration" refers to all alterations, translations, upgrades, enhancements, customizations or modifications of all or any portion of the VAR Applications including all reconfigurations, reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or confidential information of the VAR Applications for purposes of competitive discovery.

The VAR Applications contain trade secrets of Oracle and Oracle's licensors and Customer shall not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to replace, with functional equivalent software, any of the VAR Applications in future releases of the applicable program.

v

Contents Send Us Your Comments ........................................................................................... vii

Preface ......................................................................................................................... ix

Audience ........................................................................................................................... ix

Documentation Accessibility ........................................................................................... ix

Related Documents .......................................................................................................... ix

Customer Support ............................................................................................................ ix

Improved Process for Oracle Retail Documentation Corrections ................................. ix

Oracle Retail Documentation on the Oracle Technology Network ................................ x

Conventions ....................................................................................................................... x

MIDAS Till Interface Guide ......................................................................................... 11

Overview.......................................................................................................................... 11

Configuration .................................................................................................................. 12

Application Controls ................................................................................................ 12

Role Privileges .......................................................................................................... 13

Workstations ............................................................................................................. 13

Till Products .............................................................................................................. 14

Sending Products to the Till ..................................................................................... 15

Till Sales .................................................................................................................... 17

Operation ......................................................................................................................... 17

Payments within FRS ............................................................................................... 19

Customer Enquiry .................................................................................................... 22

Appendix ..................................................................................................................... 23

Configuration .................................................................................................................. 23

Merlin Overnight 1st Poll .......................................................................................... 23

Merlin Overnight 2nd Poll......................................................................................... 23

MIDAS Live – Trickle Feed ...................................................................................... 24

Send Us Your Comments vii

Send Us Your Comments

Oracle Retail Furniture Retail System (FRS), MIDAS Till Interface Guide, Release 1101

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.

Your feedback is important, and helps us to best meet your needs as a user of our products. For example:

Are the implementation steps correct and complete?

Did you understand the context of the procedures?

Did you find any errors in the information?

Does the structure of the information help you with your tasks?

Do you need different information or graphics? If so, where, and in what format?

Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available).

Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the Online Documentation available on the Oracle Technology Network Web site. It contains the most current Documentation Library plus all documents revised or released recently.

Send your comments to us using the electronic mail address: [email protected]

Please give your name, address, electronic mail address, and telephone number (optional).

If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services.

If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.

http://www.oracle.com/

Preface ix

Preface

This guide describes the Furniture Retail System (FRS) user interface. It provides step-by-step instructions to complete most tasks that can be performed through the user interface.

Audience This user guide is for users and administrators of Oracle Retail Furniture Retail System (FRS). This includes merchandisers, buyers, business analysts, and administrative personnel.

Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are

hearing impaired.

Related Documents For more information, see the in the Oracle Retail Furniture Retail System (FRS) Release 1101 documentation set.

Customer Support To contact Oracle Customer Support, access My Oracle Support at the following

URL:

https://support.oracle.com

When contacting Customer Support, please provide the following:

Product version and program/module name

Functional and technical description of the problem (include business impact)

Detailed step-by-step instructions to re-create

Exact error message received

Screen shots of each step you take

Improved Process for Oracle Retail Documentation Corrections To more quickly address critical corrections to Oracle Retail documentation content, Oracle Retail documentation may be republished whenever a critical correction is needed. For critical corrections, the republication of an Oracle Retail document may at times not be attached to a numbered software release; instead, the Oracle Retail document will simply be replaced on the Oracle Technology Network Web site, or, in the

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

https://support.oracle.com/

x Oracle Retail Furniture Retail System (FRS)

case of Data Models, to the applicable My Oracle Support Documentation container where they reside.

This process will prevent delays in making critical corrections available to customers. For the customer, it means that before you begin installation, you must verify that you have the most recent version of the Oracle Retail documentation set. Oracle Retail documentation is available on the Oracle Technology Network at the following URL:

http://www.oracle.com/technetwork/documentation/oracle-retail-100266.html

An updated version of the applicable Oracle Retail document is indicated by Oracle part number, as well as print date (month and year). An updated version uses the same part number, with a higher-numbered suffix. For example, part number E123456-02 is an

updated version of a document with part number E123456-01.

If a more recent version of a document is available, that version supersedes all previous versions.

Oracle Retail Documentation on the Oracle Technology Network Oracle Retail product documentation is available on the following web site:


(Data Model documents are not available through Oracle Technology Network. You can obtain them through My Oracle Support.)

Conventions

Navigate: This is a navigate statement. It tells you how to get to the start of the procedure and ends with a screen shot of the starting point and the statement “the Window Name window opens.”

This is a code sample

It is used to display examples of code


MIDAS Till Interface Guide 11

MIDAS Till Interface Guide

Overview This document is intended for use with system linked to the MIDAS touch screen till and details the configuration of the interface.

It does not detail commissioning of the MIDAS till which will be addressed by your MIDAS consultant.

The till interface is designed to perform the following data integration.

FRS to MIDAS (periodic processing)

Accessory classed products and prevailing promotional pricing data

Mark down products and prices

Customer file download (not currently operational)

FRS to MIDAS (real time)

FRS seeded deposits sent to MIDAS

MIDAS to FRS (periodic processing)

End of day transaction log files (not currently operational)

MIDAS to FRS (real time)

Anonymous sales (cash and carry / pay and take) upon completion of the transaction

Paid deposit payments (plus any extra items sold at the till)

Known customer cash and carry sales (not currently operational)

Note: MIDAS tills offer a number of features and options, however unless stated above these features are not reported

back to FRS unless stated above.

12 Oracle Retail Furniture Retail System (FRS)

Configuration To enable FRS to send product data to MIDAS the following script must be added to the AccountsInterfaceConfix.xml table which resides within the FRS application folder.

AccountsConfig settings

The highlighted sections indicate the data paths to be used by FRS to save product export data files.

Standard configuration is to set this to C:\Epos-Files\Import

Note: Standard configuration is to set this to C:\Epos-Files\Import

The C:\Epos-Files folder needs suitable read/write

permissions to be assigned.

Application Controls

The following application controls require definition.

Navigate: Administrator – set up application parameters

Application parameters


Parameter Description

TAKE_NON_TILL_DEPOSITS Tick to indicate that payments are to be processed via the MIDAS till

TILL_DYNAMIC_LINK Tick to indicate that payments are to be processed via the MIDAS till

TILL_IFC Set to Megabyte

TILL_IFC_PATH Set to the folder FRS is to send export data to

E.g. C:\Epos-Files\Export

TILL_MIDAS_DESCRIPTION Choose which description is to be sent to the till

Choose from –

Not set

Description 1

Description 2

Description 3

Description 1,2 and 3 concatenated

Model, description 1,2 & 3 concatenated

All descriptions are truncated to 80 characters

Role Privileges

The following roles should be made available to the relevant operators.

Navigate: Administrator – security – set up roles

Parameter Description

SETUP_TILL_PRODUCTS Add this role to enable the operator to identify which ‘accessory’ classed SKUs can be sent to the till using for locations visible to their login code only.

SETUP_TILL_PRODUCTS_GLOBAL Add this role to enable the operator to identify which ‘accessory’ classed SKUs can be sent to the till using for visible companies and locations accessible by their login code only.

Workstations

Locations operating tills will require the ‘is Pos’ tick box setting.

If the till requires its own data path the TILL_IFC_PATH application should be set to multiple and the path for the till set in the workstation’s Till Data Path field.

Navigate: Administrator – utilities – set up workstations

Set up workstations

It is essential to make sure the EPOS ID matches that set within the till.


Where multiple till exist within the same trading location multiple workstation records are required.

Note: Standard folder settings are C:\Epos-Files\Export\??? (Where ??? is the branch ID set in FRS)

For security it is recommended that EPOS tills have fixed IP Addresses.

Till Products

Operators possessing one of the two SETUP_TILL_PRODUCTS... privileges will have access to this routine.

Navigate: Administrator – products – set up till products

The routine offers the company drop

Set up till products

The list contains only accessory classed good suppliers and will default to allowed, this means the Midas till will be sent all ‘accessory’ classed SKUs from these suppliers.

To block a supplier, range or item from being ‘sent’ to the till select the blocked option.

To block a range click on the supplier name to drill down into the range list, click on a range to drill down in to the list of SKUs setting the appropriate controls at each level.

Using the company and location filters it is possible to restrict accessory product visibility by location.

Note: The system will automatically send unique classed stock which has been marked down to the till using the stock ID as the index which means specific stock items can be sold via the till where applicable. Only mark down stock linked

to the tills location will be sent to the till.


Sending Products to the Till

Sending products to the till can be an automated process and / or a manual (on request) operation.

Automatic processing will be configured by your implementation team.

Navigate: Administrator – accounts interface

Accounts interface

To instigate the product export to the till select the products button.

Processed record message

Once completed the system will show the number of products exported alongside the product button.

Note: Exporting products generates two data files ALTPLU.DAT and FULPLU.DAT in the path set within the TILL_IFC_PATH application parameter.

These files will be consumed by the till when the next till session is instigated.

Consumed files will be moved to the PROCESSED folder.

FULLPLU.dat contains the ID, description, product group and price of each exported item. This table also contains

markdown stock records.

Data file


Note: ALTPLU.dat contains alternative IDs (SKUs) for items within the FULLPLU table.

Data file

When loading the till the splash screen will show the loading PLU message whilst initiating. This process consumes the products exported from FRS which will be available for sale once at the POS.

MIDAS load menu

Note: Midas offers a setting (which is usually enabled) which enables the till to upload new product files at time of operator signing in. It can be found in epos manager -> system -> till system options ‘Enable update checking at sign on’.

This feature also offers the ability to specify the times files

are imported and the frequency of checking.


Till Sales To send sales made on the till back to FRS the till must be configured to replicate FRS VAT rates and trading locations, your implementation consultant will assist with this.

The till should be configured to send real time exports to the designated export folder (the standard configuration is shown below)

Configuration screen

Each sale processed via the till generates an output file adhering to file format specified in the designated location.

Data folder

Note: Files waiting to be processed by FRS have the .DAT suffix.

Processed files have .ok appended to the file

The file references the location, till and transaction ID.

Operation Where configured FRS will process these data file automatically, the frequency of update is modifiable.


Manual processing of data files is via the accounts interface routine.

Accounts interface

To manually instigate the till sales import process select the till transactions button. Once completed the screen will display the number of till transactions processed.

Data imported

Imported sales, when viewed within the FRS application usually appear as fully processed ‘pay and take’ sales (as shown below)

Note: The import process will report any invalid data elements on screen, however in some circumstances the file will be rejected prior to FRS consistency checks. In these circumstances the system will rename the .DAT file to a .BAD file.

It is therefore recommended that periodic checking be performed on the import folder checking for any .BAD files.

Till sale

In certain circumstances the sales order will not be completed and will require manual progression – it is recommended that the find sales order routine operated daily with the ‘show open orders only’ selected. This will show any till sale transactions (along with any FRS sales) which require some form of action to ‘complete’ the sale.

Note: The till transaction reference is shown within the pad reference number field allowing searches by receipt reference where necessary.

In certain circumstances the sales order will not be completed and will require manual progression – it is recommended that the find sales order routine operated daily with the ‘show open orders only’ selected. This will show any till sale transactions (along with any FRS sales)

which require some form of action to ‘complete’ the sale.


It is recommended that the end of day / session audits be run on the till this be compared to a suitable report in FRS to ensure all transaction have successfully imported. Alternatively periodically check the import folder for files

with the .BAD suffix.

Payments within FRS

When configured to operate with till FRS will request the deposit payment but not the tender of the payment. This applies to initial and all secondary payments.

Payment screen

When indicating a payment is to be made the operator should specify the payment in the ‘payment amount’ and click the accept button.

Control will then return to the order. At this time the payment has not been processed and therefore the order will not register the tender value. The order will only be updated once the payment has been confirmed via the till.

This process creates a file in the TILL_IFC data path in a deposits sub folder.

Data file

Confirmation of payment should be processed via the till, by selecting the ‘deposit recall’ button configured by your implementation consultant.


This generates a screen similar to that shown below, the operator may enter an order number or customer name if desired. Clicking the find button presents a list of payment ‘seeded’ within FRS waiting to be completed within the till.

Pending payment screen

Selecting the deposit creates a ‘999999999’ line within the sale. The value of the line is that of the ‘seeded’ deposit and cannot be changed.

It is not possible to add a second deposit line to the sale but it is possible to add other products before completing the sale as shown below.

Deposit line added to basket

Completing the sale produces a sales receipt and where configured automatically updates FRS with the payment.


When viewed within FRS the order will show any ‘point of sale’ additions to the order, in this case the ‘25cm Taper Candles pack of 10’ is SKU code 10-2-128.

Sales order

Note: The 10-2-128 SKU is processed as a fully paid order line which was ‘taken by the customer’, the system automatically reducing the stock on hand in the selling location as a result of the sale.

Stocking levels of goods sold by the till can go negative – the next receipt of free to sell stock will be used to correct negative stocking levels at the selling location.

The order value has been adjusted by the payment value which can be seen by viewing the customer’s account. In this example the till sale came to £135.44 however the customer tendered £140.00 in cash resulting in change of £4.56

Payment summary


Customer Enquiry

Where configured the till will offer a direct connection to FRS. When clicked this will generate an FRS page allowing the till operator to view customer details, from which they can, subject to permissions, select an order and where applicable seed a deposit payment.

FRS enquiry within MIDAS

Logging out of the screen via the close button returns control back to the till.

Note: To operate the user’s login code must replicate the user code within the till.

Appendix 23

Appendix

Configuration When interfacing with MIDAS tills wherever possible fixed IP addressing is recommended.

It is important to provide the MIDAS install team with IP addresses and gateways to allow the communication protocols to be configured.

Communication between FRS and till uses two packages (Midas Live and Merlin) which reside on the server and run in background moving data between the sever and the tills.

Midas Live runs constantly pushing deposits to the till and pulling completed basket sales back into FRS.

Merlin runs periodically pushing product, sales and customer (customers are future developments) data files to the till.

Standard FRS-MIDAS configuration of data folders is as follows –

Merlin Overnight 1st Poll

Receive at POS

POS Loc & Name c:\matrix32\export\

FRS Location & File Name Notes

btoday.dat

Epos-Files\Import\???Sal.dat

Transaction details (a complete record of all transactions done on tills in one branch)

??? = Branch Number

Merlin Overnight 2nd Poll

Send to FRS

POS Loc & Name c:\matrix32\import\


fulplu.dat

\Epos-Files\Export\???\fulplu.dat

Complete PLU Update i.e. all previous PLU’s are deleted

altplu.dat

\Epos-Files\Export\???\altplu.dat

Complete Alternative code update i.e. all previous are wiped

stkadj.dat

\Epos-Files\Export\???\stkadj.dat

Stock adjustment

??? = Branch Number

promo.dat

\Epos-Files\Export\promo.dat Promotion codes

full-cust.dat

\Epos-Files\Export\full-cust.dat Complete customer update i.e. all previous customers are deleted


MIDAS Live – Trickle Feed

Receive at POS

POS Loc & Name FRS Location & File Name Notes

c:\Matrix32\FRS\In\*.Dat \Epos-Files\Export\Orders\???\*.DAT FRS sales orders

??? = Branch Number

In a master/slave system only copy to master. On slave(s) set epos32.ini -> FRSFilePath to the master’s file location.

Format: ORDER-CUST-DATE.DAT

c:\Matrix32\FRS\In\*.Dat \Epos-Files\Export\Orders\???\Deposits\*.DAT

FRS Deposits

Format: ORDER-CUST-DATE.DAT

Send to FRS

POS Loc & Name

c:\matrix32\export\


SAL001-01-000001.DAT \Epos-Files\Import\*.DAT Set trickle feed file format to

{SAL}BBB-TT-RRRRR.DAT

BBB = Branch

TT = Till

RRRRR = Transaction Number