epicor retail merchandising 4.3.3 price lookup … lookup... · 1 getting started the epicor retail...

Epicor RetailMerchandising 4.3.3

Price Lookup ManagementUser Guide

© 2012-2013 Epicor Software Corporation

Worldwide HeadquartersEpicor Software Corporation7683 Southfront RoadLivermore, CA 94551 USA

Toll Free: +1-800-999-1809Direct: +1-949-585-4000Fax: +1-949-585-4091www.epicor.com

Merchandising 4.3.3 Price LookUp Management User GuidePublication date: December 12, 2013

TrademarksEpicor is a registered trademark of Epicor Software Corporation and its subsidiaries. All other trademarks are the property of their respective owners and are acknowledged.

DisclaimerThis manual is provided for informational purposes only. Epicor Software Corporation and its affiliates and subsidiaries (hereinafter collectively referred to as “Epicor”) make no representations or warranties with respect to the contents of this manual and Epicor specifically disclaims any and all implied warranties including, but not limited to, merchantability and fitness for any particular purpose. Use of the software is governed by and subject to the terms of your agreement with Epicor.

This manual is subject to change without notice. The contents of this manual are believed to be current and accurate as of its date of publication. Changes to this manual between reprintings and other important information about the software product are made or published in release notes and you are urged to obtain the current release notes for the software product. We welcome user comments and reserve the right to revise this publication and/or make improvements or changes to the products or programs described in this publication at any time, without notice.

The information contained herein is confidential and proprietary to Epicor Software Corporation and/or a subsidiary or affiliate thereof.

Documentation feedbackSend comments on this or other Epicor publications using the feedback form located on the last page of this document. If you are sending comments on this publication, click the Fill In Document Info button to automatically add the document information to the form. Click the Submit Form button to send the information to Epicor via email.

You can also send your comments to [email protected]. Be sure to include the name and publication date of the book. If you are commenting on specific text, include its location (for example, a help topic title, a chapter and section title, a table number, or a page number).

www.epicor.com

mailto:[email protected]?subject=Documentation feedback

tTable of Contents1. Getting Started.............................................................. 1

About Merchandising ........................................................................................................1About this manual .............................................................................................................2The basics ..........................................................................................................................3Retrieving information from your database ....................................................................9Printing ............................................................................................................................ 12Using help ....................................................................................................................... 12

2. PLU Flow...................................................................... 14Merchandising PLU Flow for STORE with Data Exchange Polling .............................. 15Merchandising PLU Flow for Triversity with Data Exchange Polling ........................... 16Merchandising PLU Flow for Triversity with Unix Polling ............................................. 17Merchandising PLU Flow for PC Register with Unix Polling ......................................... 18Merchandising PLU Flow for non-Epicor POS systems ................................................ 19Merchandising PLU flow details ................................................................................... 20

3. PLU Setup .................................................................... 25Setup checklist ............................................................................................................... 25Preliminary PLU setup procedures .............................................................................. 27PLU Procedures in Product Management/Enterprise Data Management ................ 40

4. PLU Maintenance......................................................... 62PLU maintenance when creating locations .................................................................. 62PLU maintenance when creating merchandise groups .............................................. 62Overriding inherited PLU information by style .............................................................. 63Reviewing PLU file errors ............................................................................................... 64Regenerating PLU files .................................................................................................. 64Review/Resend PLU backup files ................................................................................. 66Style Resend ................................................................................................................... 68

Appendix ..........................................................................69PLU and setting up taxability ......................................................................................... 69Loading PLU Profiles using EDM & PROD Import ........................................................ 71Sending retail and cost information to POS ................................................................. 71PLU and Thin Store POS ................................................................................................ 72Differences by register types ......................................................................................... 72STORE PLU file layouts .................................................................................................. 75Triversity PLU file layouts ............................................................................................... 75PC Register file layout .................................................................................................... 97How PLU fits into the Merchandising implementation ..............................................106Polling with legacy POS systems .................................................................................107

1 Getting Started

The Epicor Retail Price Lookup (PLU) Management System provides price and item information to a cash register or any point-of-purchase device.

The PLU Management system extracts information from Enterprise Data Management, Product Management, Infobase and Price Management and sends it to a specific location during polling.

The PLU Management system is set up in the PLU Tables in Enterprise Data Management. The PLU Tables allow you to define the PLU settings used by your organization and to create a link between these settings, locations and the merchandise hierarchy.

Note: Epicor Retail was previously known as Connected Retailer. Any instances of the former name (either in documentation or user interfaces) or any instances of “NSB” should be understood to refer to Epicor Retail.

About MerchandisingThe Epicor Retail Merchandising Solution for retail enterprises streamlines the key processes of business. With the integration of key components including order management, pricing, inventory and margin management, the retailer is equipped with accurate, up-to-the-minute information that facilitates powerful management and analysis of merchandise. The Merchandising Solution includes the following:

Allocation & Replenishment (A&R) satisfies the changing merchandise needs of your stores, including a seamless communication with Purchase Order Management. By enabling you to balance inventories and distributions of merchandise allocated in a pre- and post-allocation environment, its powerful module components serve to increase turns, reduce markdowns, improve gross margins, and optimize merchandise performance, to maximize your sales, profits and ROI.

Enterprise Data Management (EDM) offers a single point of entry for all information that defines a retail enterprise, such as locations, vendors, hierarchies, currencies, etc. It feeds common information to all Merchandising modules, thereby ensuring that all modules get the same information at the same time.

Foundation enables the integration of all functions across your organization, streamlining information flow and simplifying internal processes. It facilitates data transfer across all areas while maintaining security setup.

Inventory Management (IM) supports all inventory movement transactions including receipts, RTVs, transfers, ASNs, adjustments and physical inventory. Common receiving procedures provide consistency at the warehouse and the stores. Real-time updates and user-defined inventory statuses offer retailers in-depth and timely information for analysis.

About this manual 2

Invoice Matching (IMAT), a component of Inventory Management, provides your accounts payable system with complete details for matching and reconciling invoices from your vendors.

Merchandise Planning enables you to create and manage your merchandise plans at chain level, store level or both. Flexible and unlimited merchandise and location hierarchies streamline the planning of multiple channels, allowing you to develop plans that truly meet the demands at a micro-level.

Merchandising Analytics (MA) provides decision support for analyzing all retail activities, including sales, orders, receipts, distributions, price changes, inventory adjustments, and returns to vendors.

Price Management (Price Mgt) and Price Look Up (PLU) provide complete support for simulating and executing temporary and permanent price changes (including deal documents, which are a special type of temporary price change) and sending this information to your stores. Price Management allows you to manage prices by any combination of style, style/color, and style/color/location, thus increasing your return on inventory.

Product Management (Prod Mgt) allows you to maintain a comprehensive list of the merchandise your company sells that can be used across all selling channels, including the Web, in kiosks, and in catalogs.

Purchase Order Management, also known as POM, provides options for managing your entire purchase ordering process, including seamless communication with the Allocation & Replenishment module. POM lets you monitor the progress of buys and their delivery dates while maintaining strict financial and open-to-buy control, as well as providing a user-defined approval process and in-depth reporting capabilities.

Stock Ledger, a component of Inventory Management, allows you to define the components and calculations that interface to your general ledger system in the way that best meets your business needs.

Warehouse Management streamlines receiving, processing, and distribution, and enables you to accurately monitor items as they move from supplier to store or individual customer. It supports multiple channels and gives you the ability to efficiently manage all warehousing functions.

About this manualThis manual is divided into five sections.

Chapter 1: Getting Started is meant to be read before you start working in PLU. This chapter contains background information and explains some of the basics.Chapter 2: PLU Flow gives an overview of how the system works.

Chapter 3: PLU Setup contains step-by-step procedures on how to set up PLU in Enterprise Data Management.Chapter 4: PLU Maintenance describes the PLU tasks that must be performed when locations, styles or merchandise groups are added.

The Appendix contains detailed file layout information for the three types of registers that PLU supports, as well as information on how to use Help and how to perform a Query.

3 Getting Started

The basicsThe Merchandising modules use standard Windows navigation tools and techniques and their look can be customize. For example, to change the default color scheme at any time, select Start > Settings > Control Panel > Display. In the Display Properties dialog box, select the Appearance tab and apply the scheme you prefer.

Starting Merch

To start Merchandising:

1. Double-click the Epicor Retail icon on the Windows desktop or in the program group folder. If you are presented with a login screen, enter a valid user name and password.The Start page is displayed.

2. At the Start Page, click the module you want to launch from the module bar.The Module bar and other bars and tools are explained below. You can open any module by clicking its tab on the Module Bar. On the Navigation Bar, click one of the available options to display the page. To close any displayed page, click ×. To move between open pages, click their tabs on the Tab bar. If there are too

many to view all tabs, click the back and forward buttons to move to the beginning or end of the Tab bar.

Exiting Merch

To exit Merchandising: Click the X in the top right corner of the application.

The module barThe module bar allows you to access a module and to change modules within Merchandising without having to exit the module. On the Module Bar, select the name of the module you want to change to.

Note: POM and A&R can be open at the same time and you can switch back and forth between them. However, only one of the other Merchandising modules can be open at a time. For example, if you open Pricing and then open Inventory, Pricing closes and Inventory opens.

Navigation bar 4

Navigation barAt any time, you can display or hide the Navigation Bar. When you open a module, the Navigation Bar is displayed by default:

The Navigation bar with the vertical divider activated.

To hide the Navigation Bar, click . The Navigation Bar collapses to a tab on the left side of the window: To temporarily view the hidden Navigation Bar, point to the tab.

To expand the Navigation Bar again, click .

To close the Navigation Bar, click . To resize the Navigation Bar, drag the vertical divider to the left or right.

Tab listThe Tab List, located just below the Module Bar, allows you to navigate between modules or related dialogs.

Exiting a module

To exit a module, click the X in the top right corner of the tab.

The Quick Access toolbarThe Quick Access Toolbar is located in the top left corner of the window and contains frequently used commands such as Save, Open, Print and Close.

The Ribbon barCommands are organized in labeled groups. The group label explains the purpose of the command. You can obtain more detailed information by scrolling over the command.

The buttons you see on the ribbon bar depend on the menu item and window you are working in. Some buttons are multipurpose and are used for different functions depending on which window is active.

5 Getting Started

CalendarIn any window with a date field requiring user input (for example, the Effective From date),

you can type the date you want or click to open the Calendar.

The Calendar opens at the current month, with the current date highlighted in red and also noted at the bottom. Click the directional buttons at the top of the Calendar to move forward or backward by month. Click any date to enter it automatically in the current field.

Changing displayed datesIn any screen with a date field that you want to change (for example, the Release date), select the portion of the date you want to change (month, day or year), and then type the new information or click the arrows to select a different month, day or year.

WorklistsWorklists are used in tables that have numerous fields to maintain.The worklist displays one row of information for each record. You can use the query function to select the records that you want to view. For example, if you want to view all Calvin Klein styles that have been designated as “regular Winter 2004” styles, you can include each of the following fields in your query criteria: Calvin Klein, regular style, Winter 2004. The style worklist will display only those styles that meet all of the criteria.

To configure a worklist or

lookup window

view

In all modules, you can change the columns that display in a worklist or lookup window, the order in which they display and their size.

1. Do one of the following: In a worklist, on the Table tab, click Layout. In a lookup window, click Configuration.

Entering information 6

2. The worklist/lookup configuration window opens and you can customize the view in whatever way you prefer.

Note: If you want to save this configuration for future use, select Save as and type a name for it in Configuration List and then click OK.

Entering informationAs you enter, retrieve and change information throughout the application, remember that gray fields can't be edited. Gray areas usually indicate values that have been defined elsewhere, often in Enterprise Data Management and Product Management.

As you work with modules, you may see message boxes. Depending on the message contained, various buttons are available in this type of message box:

Click this button To do this

Retry Try again to perform the action that generated the message.

Cancel Close the message box without further action.

OK Accept any prompt in the message box.

Yes/No Agree or disagree with any prompt in the message box.

Print Print the contents of the message box (requires a local or network printer connection).

E-mail Launch your e-mail program so that you can send the contents of the message box to someone.

Save As Save the contents of the message as a text file.

Select column headings you want the worklist to display

Clear the column headings you don’t want the worklist to display

To arrange the order of the column headings in the worklist, click the Up and Down Order buttons

7 Getting Started

The Errors and Warnings ListAs you work, you may occasionally violate certain business rules governing the action you chose. Before you continue, any such violations must be corrected.

The Errors and Warnings list is helpful in letting you know of any such problems, as well as how to correct them.When an error occurs, the Errors and Warnings list appears at the bottom of the window and displays information about the problem, including a brief message telling you how to fix it.

Right-click functionalityIn most places requiring you to type information, you can right-click and select from standard Windows functions including Undo, Cut, Copy, Paste, Delete and Select All.

There are many other types of right-click functionality available, depending on the window you are currently working in.

Pointing to an item on a context menu performs that action, the same as selecting an item from the menu bar.

Toolbar buttons and keyboard shortcutsThe buttons you see on a toolbar depend on the menu item and window you are working in. Some buttons are multipurpose and are used for different functions depending on which window is active. Toolbar buttons that are unique to a specific window are discussed in the relevant section of the manual.If you prefer to use a keyboard instead of a mouse, standard Windows keyboard shortcuts usually work in Merchandising applications. The next two tables list some of the most common shortcuts.

F2 Edit the content of a grid without erasing the existing contents. Press F2, then click in the cell at the position you want to begin your edits.

Shortcut Action Toolbar Button

Alt + Opens a list of choices to select from.

Find out about Epicor Retail Solutions.

Click this button To do this

Toolbar buttons and keyboard shortcuts 8

Navigates back to the previous window.

Ctrl + F4 Closes the active window.

Close

View the online help documentation.

Ctrl + D Deletes the selected data. The name of this button depends on the window.

Alt + G Selects and displays the First, Previous, Next, or Last record in the active item window, depending on your selection.

Search and find solutions to your questions.

Configure the table of worklist layout and specify filters and sort orders.

Alt + L Displays a list of all options allowed in field. Only applies to fields with ellipsis button .

Plays a macro to perform a function. For example, Approve PO

Ctrl+P Prints the current table.

Print

Displays a preview of the report ready to print

F8 Opens the Query dialog box (where you define specific search criteria) to retrieve specific records or a Lookup window (where you make a selection)

May remove the selected row from the table depending on conditions.

Alt + R Retrieves all information, usually worklist records.


9 Getting Started

Retrieving information from your databaseWhether you want to look at one item, a group consisting of several items, or all items, you must retrieve this information from the database.

To retrieve all

information

On the Table menu in some windows, you can select Retrieve All to retrieve all available records. (This may not always be practical, since some fields have numerous records – for example, you may have hundreds or even thousands of styles.)

To retrieve specific

information

Usually, you retrieve specific information, whether a single item or a range of items. The Merchandising Solution uses two information-retrieval tools: the Lookup window and the Query search window. While in your application, click in the field where you want to enter information, then

press F3. (You can also click … if the field contains it, or press F8 to open the Query window.) If a Lookup window opens, double-click the item you want to select. (Example on

the following page.)

Ctrl+S Saves new data or saves changes to existing data.

Save

Esc Stops the current action being performed (for example, retrieving documents).

Stop

Ctrl + Alt + V

Validates the selected record.

Keyboard shortcut Action

Ctrl + shortcut letter or Alt + shortcut letter

Opens a window, changes applications, activates a menu item or tab, may move to a different field. Examples include:Ctrl + O = Open; Alt + R = Retrieve All

Shortcut letter Selects the highlighted choice on a list.

Tab Moves through screens, field by field, skipping fields that can't be edited.

Back Space + Tab May move to previous field. (If not, use cursor keys.)

Cursor keys Move from field to field, both backward and forward.

Space bar Selects and clears check boxes. Also cycles through choices in some lists.

Cursor keys or Tab Selects buttons.

Cursor Cycles through choices in lists.

Enter key Selects the highlighted choice on a submenu, list, button or tab.

Esc Escapes current shortcut selection.


Specify using 10

If the Query window opens, complete the following steps to define specific criteria to narrow your search: In the Field box, click the Down Arrow and select an information type for your

search. Under Specify using, select your search method. See “Specify using” on

page 10 for more information. Under Values, enter your choices and click OK. See “Values” on page 11 for

information on making your search more specific.

Sometimes the Query dialog box opens with default values displayed in the List area. To clear them, select the Clear button. To clear all values displayed in the Criteria section, select the Clear All button.

When a Lookup button is available here, you can click it to open a Lookup window from which you can choose one or more items to add to the List box.

Specify using

Note: The search methods available in the Specify using box depend on the information type that you select from the Field list in Step 1 on the preceding page.

To search based on Select

Specific values of the selected information type List

A range of values for the selected information type Range

Empty fields or on all fields except those that are empty State

A field as it relates to another field Column

11 Getting Started

Values

If Do this

You selected List in the Specify using box

1. To further narrow your search, type specific values in the List box or select a value from a list, if one displays. If you enter more than one value, put a comma between them. Select Not equal to if you want to retrieve all values except

the ones you specify Select Match case if you want your search to be case-sensitive.

2. Click Apply. Your search criteria display automatically in the Criteria window.

3. Repeat Steps 1-3 on previous page if you want to enter more search criteria.

4. Click OK to finish your search.

You selected Range in the Specify using box

1. In the From field, type the first value in the range.

2. In the To field, type the second value in the range. Select Not equal to if you want to retrieve all values except

the ones you specify Select Match case if you want your search to be case-sensitive.

3. Click Apply. Your search criteria display automatically in the Criteria window.

4. Repeat Steps 1-3 on previous page if you want to enter more search criteria.


You selected State in the Specify using box

Choose Empty if you want the search to find all records that contain no information in the field you selected.

Choose Not Empty if you want the search to find all records that do contain information in the field you selected.

You selected Column in the Specify using box

1. Select an operator to compare the field you choose in the Field box with the field you choose in the To field. Choices of operators are: = (equal to) <= (equal to or less than) <> (less than or none) < (less than) >= (equal to or more than) > (more than).


Lookup example 12

Lookup example

Example of Lookup

You are creating a new price change. In the Price Change Category Code field, you click the Lookup button (…) to open a Lookup window.

To enter a selection in the field where you opened the Lookup window, double-click it in the Lookup window.

PrintingTo print, you can: Print worklists, pre-defined reports and many grid displays View (known as print preview) documents and worklists.

To define your page layout for printing, select Document > Page Layout.

Printing a document

Documents can be printed either from the worklist (highlight the document in the worklist and then click Print) or while you have a document open (simply click Print). In the Print dialog box, select the appropriate printer, the pages and the number of

copies to print and then click OK.

Print previewing a

document

Documents can be print previewed either from the worklist (highlight the document in the worklist and then click Print Preview) or while you have a document open (simply click Print Preview). It is recommended that you do not print while you are in Print Preview mode to prevent print flags from being set incorrectly. Instead, print from the Print Worklist.1. Once the document is displayed on the screen, use the toolbar arrow buttons (first

page, previous page, next page or last page) to navigate your document.

2. To increase or reduce the size of the document displayed on the Print Preview screen, click Zoom, select the size to zoom and then click OK.

Using helpFinding information in Help is easy. Help provides you with: Step-by-step instructions on how to accomplish tasks Field definitions and key terms.

You can look up information from the table of contents or the index, or you can specify your own search using a word, phrase or topic.

13 Getting Started

Finding information through the

Contents

1. While in a module, click Tools, Epicor Retail Help or press F1 to open help.

2. In the Table of Contents, click the “plus sign” next to the general topic you want to look at. If there is more than one under the subject you want to look at, click the one you

are interested in To collapse a list of topics, click the “minus sign” next to the list.

3. Click the square dot next to the specific topic that you want to look at. The topic then opens in the adjacent pane.

Finding information

through your own search

1. While in a module, click Tools, Epicor Retail Help or press F1 to open help.

2. In the left pane, click Search.

3. In the search pane, enter the word(s) you want to search on and then click Go.4. In the search results, click the topic(s) you want to open. The topic then opens in the

adjacent pane.

Other sources of helpIf you require help but cannot find the information in either this manual or the online help, open a support request by visiting http://www.epicor.com/Customers/Pages/CustomerPortal.aspx and clicking eService: NSB Group Client Care Portal for Retail Customers. Your existing login and password are effective from this screen; you can also request a password if you don't have one.

Electronic manualsYou can download the latest version of our documentation in electronic format (PDF) from the Premiere section of our web site. Premiere is restricted to our valued clients and strategic partners. To obtain a password to access documentation, visit http://www.epicor.com/Customers/Pages/CustomerPortal.aspx and click eService: NSB Group Client Care Portal for Retail Customers. Your existing login and password are effective from this screen; you can also request a password if you don’t have one.

From the Premiere site, click User Documentation and then select the product documentation that you want to download. To view PDF documents you'll need Acrobat Reader, which can also be downloaded free from the Premiere site.

Electronic documents can be read on your screen or printed. When viewing a document on-screen, you can search for a topic in the table of contents and click it to jump to it.

2 PLU Flow

The PLU (Price Lookup) Management system provides merchandise group, price, item and promotional price information to all the point-of-purchase devices used by your organization.

Style, location and price information stored in EDM, Product Management, Infobase and Price Management are fed to the PLU Management system which creates the PLU files that are sent to specific locations (stores) during nightly polling. Any addition, modification or deletion to this information triggers the PLU management system to generate or update the PLU files and send them to the locations (stores) where they are needed.

This chapter describes how PLU files are created and gives an overview of the flow of information between the components that make up the PLU Management system.

15 PLU Flow

Merchandising PLU Flow for STORE with Data Exchange Polling

EDM

Merch Groups Styles UPCs Colors Sizes Profile linking

(styles) Style PLU

QueueReplication

Profile Linking (merch groups)

Locations Vendors Location plu

attribute linking Regenerates Style Resend

Pipeline

If Offline Inventory Management flag is NOT selected, the following PLU files are built by location: Dept. Group Dept. Item UPCs Promo ItemGroup

PRODMerchandising Data Exchange Polling

If Offline Inventory Management flag is selected or Allow Customer Order is True, the following additional PLU files are built by location: Vendor Facility Store Size Color Style

Polling picks up the PLU files from the polling directory based on the store’s polling reference no embedded in the PLU file name.

PLU files are moved across the network to the stores, where the files are merged at the register

Permanent PC documents

Promotional PC documents

Deals/discounts Item Groups

PriceMgmt

Merchandising PLU Flow for Triversity with Data Exchange Polling 16

Merchandising PLU Flow for Triversity with Data Exchange Polling

PriceMgmt

Merch Groups Styles UPCs Mix Match

Flag

QueueReplication



Pipeline

The following PLU files are built by location: Dept. file

(Merchandise groups)

X-Reference file (UPCs)

PLU files (Style or style-color based on PLU key parameter

Promo file

PRODMerchandising Data Exchange Polling

Polling picks up the PLU files from each location’s polling directory based on the store’s polling reference.

PLU files are moved across the network to the stores, where the files are merged at the register

17 PLU Flow

Merchandising PLU Flow for Triversity with Unix Polling

PriceMgmt

Merch Groups Styles UPCs

QueueReplication



Pipeline

The following PLU files are built by location: Dept. file


X-Reference file (UPCs)

PLU file Promo file

PRODMerchandising UNIX/BSC Polling

PLU file is automatically moved to UNIX machine

PLU files are downloaded to the stores via nightly polling. The files are merged at the register.

Merchandising PLU Flow for PC Register with Unix Polling 18

Merchandising PLU Flow for PC Register with Unix Polling

PriceMgmt

Merch Groups Styles UPCs

QueueReplication



Pipeline

The PLU files are built by location and then bundled into one file called POLLPLU.AS1 or POLLPLU.AS2. For more information, see “PC Register file names” on page 106.

PRODMerchandising UNIX/BSC Polling

PLU file is automatically moved to UNIX machine

PLU files are downloaded to the stores via nightly polling. The files are merged at the register.

19 PLU Flow

Merchandising PLU Flow for non-Epicor POS systems

PriceMgmt

Merch Groups Styles UPCs Colors * Sizes *

QueueReplication



Deals/Discounts (supported in Deal Management) *

Item Groups *

Pipeline

The following PLU files are built by location: Dept. file *


X-Reference file * (UPCs)

PLU file * Promo file *

PRODMerchandising Non-Epicor POS system

Determined by client depending on POS system. Client is responsible for picking up the PLU files for downloading and reformatting to their register’s format.

The files are merged at the register.

* Some of these items and file formats may differ depending on the register type.

Merchandising PLU flow details 20

Merchandising PLU flow details

Product ManagementStyles, UPCs and Merchandise Groups are created in Product Management.

As soon as merchandise groups are created that belong to the level defined as the POS Department or POS Department Group level, they are fed to the replication queue.

When a new style has a status of Ordered or Received, Product Management updates the replication queue with the style information. At that time, any associated UPCs are also added.

Price ManagementPermanent price changes, promotions, and discounts/deals are entered in Price Management. On the issue date of these documents, Price Management updates the replication queue with the price change information. The price change is picked up by PLU on the issue date, unless the Activation days number is defined for the register type.

The Activation days number specifies the number of days prior to the document’s effective date that the information must be sent to the register. This register setting is valid only if Future retail price management is not selected.

Note: The Activation days number applies only to permanent prices.

PipelineThe PLU Pipeline segment is typically scheduled to run automatically. Data is retrieved from the replication queue and the PLU files are created/updated.

Note: If the issue date for a promotional price change or deal document has already passed, it is picked up and then populates the PLU files immediately.

PLU files are created when segment EDM & PROD to Price Look-Up (1006) or EDM & PROD to Price Look-Up (Store) (1007) is run. These files are created in a directory on the server. You choose the directory the files will be built in.

Triversity filenames

STORE filenames

Department file <4-digit polling reference or call file number>depttxn.asc

Item file <4-digit polling reference or call file number>plutxn.asc

UPC file <4-digit polling reference or call file number>xreftxn.asc

PROMO file <4-digit polling reference or call file number>promotxn.asc

Department Group file

<4-digit polling reference>deptgroup<yyyymmddThhmmss>.dcn

Department file <4-digit polling reference>dept<yyyymmddThhmmss>.dcn

Item file <4-digit polling reference>item<yyyymmddThhmmss>.dcn

21 PLU Flow

PC Register filenames

These are combined into one file, either POLLPLU.AS1 (created first) or POLLPLU.AS2 (created next).

Merchandise Group files

Department Group file for STOREThis file contains all the merchandise groups that belong to the POS Department Group level of the main merchandise hierarchy. The following actions trigger updates to the Department Group file, which will be downloaded to the stores:

Department file for STORE and Triversity, 2F file for PC RegisterThis file contains all the merchandise groups that belong to the POS Department level of the main merchandise hierarchy.

Item group file <4-digit polling reference>itemgroup<yyyymmddThhmmss>.dcn

UPC file <4-digit polling reference>upc<yyyymmddThhmmss>.dcn

PROMO file <4-digit polling reference>promo<yyyymmddThhmmss>.dcn

Style file <4-digit polling reference>style<yyyymmddThhmmss>.dcn

Color file <4-digit polling reference>color<yyyymmddThhmmss>.dcn

Size file <4-digit polling reference>size<yyyymmddThhmmss>.dcn

Store file <4-digit polling reference>store<yyyymmddThhmmss>.dcn

Facility file <4-digit polling reference>facility<yyyymmddThhmmss>.dcn

Vendor file <4-digit polling reference>vendor<yyyymmddThhmmss>.dcn

2F Merchandise Group file

25 Item master file

27 Promo master file

50 Item updates

60 Promo updates

Action

Merchandise groups belonging to the POS Department Group level are added or deleted

The description of a merchandise group at the level of the POS Department Group is modified

Item file 22

The following actions trigger updates to the Department file, which will be downloaded to the stores:

Item file Item file for STORE PLU file for Triversity 25 and/or 50 file(s) for PC Register

This file contains all the styles that are carried by a specific store.

Only styles with a status of Ordered or Received will be downloaded to the stores. The styles that are downloaded to a store is determined by a style/location attribute called Ownership.

For more information on the Ownership attribute, see Determining whether all locations receive all styles (step 5) on page 36.The following actions trigger updates to the PLU file, which will be downloaded to the stores:

Action

Merchandise groups belonging to the POS Department level are added or deleted

Changes are made to the Description or profile linking for a merchandise group at the level of the POS Department

The active status for a merchandise group at the level of the POS Department is modified

Action PLU Update

Style information (such as Description, Mix & MatchCodes, etc.) is modified

Only the modified information and certain key fields (like references to the style) will be sent to the stores.

Styles are deleted This information will be sent to the stores only if the style previously existed in the PLU file at the stores. If the file never populated PLU (because it did not have a status of Ordered or Received), the information is not sent to the stores.

A different Ownership attribute set is assigned to a style (for example, a style's Ownership attribute set is changed from Outlet to Concept)

The style will be added to the files for the stores with the location attribute set for the OWNRSP attribute that matches the newly-assigned style attribute set. Deletes will not be sent to the stores with the location attribute set for the OWNRSP attribute that matches the original style attribute set value.

Permanent price changes are entered in Price Management

This information updates the EDM Replication Queue on the issue date of the price change unless the Activation days number is defined for the register type. The information will be included in the files for the locations that are (1) included on the price change and (2) have a location ownership attribute set code that matches the style ownership attribute set code.

23 PLU Flow

UPC file UPC file for STORE Cross-Reference (x-ref) file for Triversity 25 and/or 50 file(s) for PC Register

This file contains all the UPCs that are carried by a specific store. UPCs will be included in the files for a specific location if the location's ownership attribute set code matches the style ownership attribute set code of the style the UPC is linked to. The styles the UPC is linked to must also have a status of Ordered or Received.The following actions trigger updates to the UPC file, which will be downloaded to the stores:

Note: If a UPC is inserted and then deleted in the same day, no action will be taken.

Promotions file Promo file for STORE Promotion file for Triversity 27 and/or 60 file(s) for PC Register

This file contains promotional price changes and deals. Promotions will be included in the files for a specific location if the location's ownership attribute set code matches the style attribute set code of the style on promotion. In other words, only promotions belonging to a style that the store carries are downloaded.The following actions trigger updates to the Promo file, which will be downloaded to the stores:

Action PLU Update

UPCs are assigned This information is sent to the stores.

UPCs are deleted This information is sent to the stores.

UPCs are reassigned; that is, deleted and then inserted in another style

This information is sent to the stores.

Action PLU Update

A promotion that is effective is canceled in Price Management

A cancel flag is sent to the store. If the promotion is canceled on the same day that it was issued, it will not be sent to the store.

The ending date of a promotion is modified before the promotion ends

The new information is sent to the store. The new End date overwrites the original End date.

Additional Store files 24

Additional Store filesIf a location’s Offline Inventory Management flag is selected and the register type is Store (ID 6) or Coalition (ID 2), the following files will also be built by PLU:

Action PLU update

Supplier

Vendor created This info is sent to the store

Vendor address added This info is sent to the store

Vendor return address type (defined in the RTV parameters) is modified

Change is sent to the store

Vendor is deleted This info is sent to the store

Facility

Location created This info is sent to the store

Address is added or modified This info is sent to the store

Store

Location created This info is sent to the store

Address is added or modified This info is sent to the store

Location phone or fax number is modified This info is sent to the store

Size

New size is created Size and size category sent to store

Size is deleted (no longer referenced on a style) Deletion feeds to store

Color

New color is created Info is sent to stores

Short or long color descriptions modified Info is sent to stores

Color code deleted Deletion is sent to stores

Style

New style is created Info sent to stores

The style’s ownership attribute is modified Info sent to stores

Style (short description or PLU description) is modified

Info sent to stores

Style is deleted Deletion is sent to stores

3 PLU Setup

The PLU Management system is set up in Enterprise Data Management. This setup is performed only once. However, some PLU maintenance is required as styles, locations and merchandise groups are added to Product Management and Enterprise Data Management. For more information see “PLU Maintenance” on page 62.The following is a brief outline of the steps that must be performed to set up the PLU Management System. Detailed procedures can be found later in this chapter. The PLU setup must be performed in the order outlined in the steps that follow.

Note: Merchandise hierarchies and their levels must be defined before you begin the PLU setup. The main merchandise hierarchy is set up when Merchandising is installed. See Chapter 2 of the Product Management User Guide for an overview of the merchandise structure.

Setup checklist

Preliminary setup

procedures

Before you begin setting up the PLU Management System, complete the following steps (these brief summaries are explained more fully later in this chapter). You can check off each step as you complete it.

Pre PRM

1. For Triversity and STORE, speak to the POS resource to find out whether registers will print description from the Dept. file or Item/PLU file on receipts.

PRM

2. Review the Settings document with the client and decide which register settings will be used.

3. Find out from the client the level of the merchandise hierarchy at which the decision on each setting value will be made. Indicate the setting values for the merchandise groups that belong to this level.

4. Review with the client how locations are grouped and setting decisions are made. Indicate the grouping of locations used to decide how the value is set and indicate the setting values for each of the groups.

5. Review with the client whether all locations will get all styles.

Setup procedures performed in EDM/Product Management 26

Setup procedures

performed in EDM/

Product Management

After you complete the preliminary procedures, the following steps must be performed in EDM/Product Management.

6. Review with the client the following:a) For STORE, review

Which level should populate the Department Group file Which level should populate the Department file Which Merch group description should populate the Department Group file

(must be, POS Department Group level or higher) Which Merch group description should populate the Department file

(must be, POS Department level or higher). which style attribute they will set up to reflect the Brand of the style that will print on

the receipt at POS.b) For Triversity, review

Which level should populate the Department file Which Merch group description should populate the Department file

(that is, Department level or higher).

7. For Triversity and STORE, review with the client which description the style PLU description field that populates the PLU/Item file will default to: No default, Style Short Desc. or POS Department Level Desc.

Post PRM

8. Determine values for PLU parameters. (Discussion with client is not usually required.)

9. Assign the POS Department and POS Department Group Characteristic Default levels.

10. Assign a level to the POS Department Group Description Characteristic Default and a level to the POS Department Description Characteristic Default.

11. Set the Style PLU description default value in EDM System Parameters, based on step 7 above.

12. Create the Ownership (OWNRSP) style attribute with the appropriate attribute sets. This attribute must be mandatory and exclusive.

13. For Triversity and STORE, set Activation days value to 1. For other register types, set Future Retail Price Management and Activation Days as required.

14. Create PLU Collections and assign all PLU settings to a PLU collection.

15. Create location attributes and attribute sets that correspond to each collection that has been defined. The attributes must be mandatory and exclusive.

16. Create the Ownership (OWNRSP) location attribute with attribute sets that match those created for the style attribute. This attribute must be mandatory and can be non-exclusive.

27 PLU Setup

PLU setup is now complete and the rest of the Merchandising setup can be performed. See the Merchandising System Administration Guide for more information. For more detailed information on any of the above steps, continue in this current chapter.

Preliminary PLU setup procedures

Step 1: Determine

source of description on receipts

For Triversity and STORE, speak to the POS resource to find out whether registers will be printing descriptions on receipts from the Department file or the Item/PLU file. This will determine the setting of the PLU description parameter (see Step 7, on page page 37).

Step 2: Review PLU

register settings

Review the register settings in the PLU Register Settings table on the following page and indicate which ones will be used for each register type. Not all register settings are available for every register type. The register-type columns (STORE, Triversity and PC Register) indicate whether a setting is available for that register type.

Legend (for Type column in PLU Register Settings table)

0/1 indicates that a setting value is either false (0) or true (1). A number followed by AN indicates that a setting must be assigned an alphanumeric

value (for example, 255 AN indicates a value of up to 255 alphanumeric characters). One or more 9s indicates that a numeric value consisting of that number of digits

must be assigned to a setting (for example, 999 indicates a value of up to three numeric characters).

17. Set PLU Parameters in EDM/Parameters/PLU, based on step 8 above.

18. In the PLU Collection Linking table, for all PLU collections, create a link between a PLU Collection, a location attribute and a level within the main merchandise hierarchy. You must select a level from the main merchandise hierarchy that is equal to or higher than the level that has been defined for the POS Department level (see step 1).

19. Define profiles for each PLU Collection.

20. Create links between PLU profiles, merchandise groups and attribute sets.

21. Verify all locations to see whether the default attribute sets for the PLU Location attributes need to be modified.

22. If the client has Enterprise Selling integrated with Epicor Retail Store, set the Pipeline parameter Send Concatenated Item Description to 1 on segment 1006 (if using Coalition, Triversity or PC Register registers) or segment 1007 (if using the Store register).

23. If the client has Epicor Retail Store version 6.4 or later and a style mask greater than 10, change Pipeline parameter Enforce Style Code Limit to 0 (false) on segment 1006 (if using Coalition, Triversity or PC Register registers) or segment 1007 (if using the Store register).

PLU Register settings 28

PLU Register settingsRegisterSelect the level on the merchandise hierarchy at which setting decisions are made

Setting Definition Type STORE Triversity PC Register Used (Y/N)

Prompt form name This field specifies the name of a form at POS. Prompt forms may be set up to appear when certain items are rung in at the register. For example, a prompt form may be created to provide data input prompts.

AN Yes No No

Prompt for price If this check box is selected, price lookup will be disabled and the point of sale terminal will prompt for a price when items are entered.

0/1 Yes Yes Yes

Validate This check box indicates that validation of the price will occur at POS when the item is rung in.

0/1 No Yes No

Accumulate This check box indicates that items can qualify for more than one promotion at the same time.

0/1 No Yes No

Prompt for additional data

Indicates that the register will prompt for additional data.

0/1 No Yes Yes

Quantity required This check box indicates that a quantity must be entered during item entry at the point of sale.

0/1 No Yes No

Limited quantity This field indicates the maximum quantity of some items that can be purchased during a transaction.

999 No Yes No

29 PLU Setup

Photo This field specifies the filename or URL address for the item at POS. Note that the photo file itself is loaded on the register.

255 AN Yes No No

Sound file This field specifies the path to a wave file entered in the PLU Profiles table. Note that the sound file itself is loaded on the register.

255 AN No No No

Prompt ID This field indicates the prompt sequence linked to the item. Prompt sequences are defined at the register.

999 Yes Yes Yes

Tax group code Represents the code used to group styles based on how they are taxed across the chain. See example on page 57.

999 Yes Yes (populates Frequent Buyer Code field in the PLU file)

No

Generate coupon ID This field indicates which coupon will be generated when the item is sold.

99 No Yes No

Commissions ID This check box indicates that a commission scheme is used.

9 No Yes (Future) No

(Allow) Returns This check box indicates that items can be returned to the retailer by the customer.

0/1 Yes Yes No

(Allow) Layaways This check box indicates that items can be put on layaway.

0/1 No Yes No

(Allow) Discounts This check box indicates that items can be discounted.

0/1 Yes Yes No


PLU Register settings 30

(Allow) Employee discounts

This check box indicates that employee discounts can be applied.

0/1 Yes Yes No

(Allow) Quantity key This check box indicates that the quantity key is allowed.

0/1 Yes Yes No

(Allow) Zero price This check box indicates that a zero price ($0.00 or 100% discount) can be entered (for example, a free item).

0/1 No Yes No

Print additional copy This check box indicates that a second copy of the customer receipt should be printed.

0/1 No No Yes

Print retail price This check box indicates that the retail price of the item is printed on the receipt.

0/1 No Yes No

Print sugg. retail price

This check box indicates that the suggested retail price is printed on the receipt.

0/1 No Yes No

GST Federal Goods and Services tax (CANADA)/TAX TABLE 1 (OTHER)

0/1 No Yes Yes

PST/State Provincial or State tax/TAX TABLE 2 (OTHER)

0/1 No Yes Yes

VAT Value Added Tax (EUROPE) 0/1 No Yes Yes

Threshold tax 1 Threshold 1 Tax/TAX TABLE 3 (OTHER) 0/1 No Yes Yes

Threshold tax 2 Threshold 2 Tax/TAX TABLE 4 (OTHER) 0/1 No Yes Yes

(User defined tax tables) Table 6-16

The check boxes for Tables 6-16 indicate the tax tables that are used.

0/1 No Yes Yes


31 PLU Setup

(User defined field) Fields 1-4

Fields 1- 4 indicate the user-defined values that are used by POS to group items.

10 AN No Yes Yes

Linked Item Group Code

Indicates that an item group code is associated with an item group. When an item is entered at the register, the list of items belonging to the associated linked item group appears. The cashier can then select one or more of these items to add to the transaction. The association between the item and the item group code is made in the PLU Profiles table.

AN Yes No No


Step 3: Select the level on the merchandise hierarchy at which setting decisions are made 32

Step 3: Select the

level on the merchandise hierarchy at

which setting

decisions are made

a) Using the following PLU Settings worksheet illustrated next in this user guide, indicate for each setting that will be used the level on the merchandise hierarchy at which setting decisions will be made. For this step, complete column D of the worksheet only. This information will be used in step 14 (Creating PLU Collections).

If a particular setting is not used, it should be set to the highest level on the merchandise hierarchy (because the decision to not use a setting is being made at the company level). Lower levels of the merchandise hierarchy inherit decisions made at a higher level. For example, if your merchandise structure is Company > Department > Class, decisions made at the Department level are inherited by the Class level.

b) After you have determined the level at which setting decisions will be made, you must indicate setting values for the merchandise groups that belong to this level. For example, if you indicate that the Returnable settings will be decided at the Department level, you must indicate which departments will be returnable and which ones won't (for example, all departments are returnable except for the Swimwear department). Write this information in column D of the PLU Settings worksheet illustrated next in this user guide.

33 PLU Setup

PLU Settings worksheet Complete column C only in step 2. “Step 2: Review PLU register settings” on page 27

for more information. Complete column D only in step 3 (A) and (B). See “Step 3: Select the level on the

merchandise hierarchy at which setting decisions are made” on page 32 for more information.

Complete column E only in step 4 (A) and (B). See “Step 4: Define how locations are grouped and where setting decisions are made” on page 36 for more information.

Column A: Setting Column B: Definition

Column C: Used? (Y/N)

Column D: Merchandise level/Details

Column E: Location level/Details

Prompt form name

Indicates that a prompt form name can be associated with specific items. When the item is rung in at the register, the associated prompt form appears. This value is defined in the PLU Profiles table.

Prompt for price Indicates whether price lookup will be disabled and cashier will be prompted for price at the point of sale terminal.

Validate Indicates whether validation will occur. Validation may be used at the register for non-merchandise transactions such as alterations.

Accumulate Indicates whether items can qualify for more than one promotion at the same time.


Indicates that the register will prompt for additional data.

Quantity required

Indicates whether a quantity must be entered during item entry at the point of sale.

Limited quantity Indicates that a limited quantity of some items may be purchased during a transaction. This value is defined in the PLU Profiles table.

PLU Settings worksheet 34

Photo Indicates that a photo is available for item(s) being entered in the point of sale device. The filename or URL address of the photo is entered in the PLU Profiles table.

Sound file Indicates that a sound file (.WAV) is available. The path to a wave file is entered in the PLU Profiles table.

Prompt ID Indicates that a prompt sequence is linked to items. Prompt sequences are defined in a separate table at the register, such as suggested selling etc.

Tax group code Represents the code used to group styles based on how they are taxed across the chain. See example on page 57).

Generate coupon ID

Indicates that a coupon will be generated when items are sold.

Commission ID Indicates that a commission scheme is used.

(Allow) Returns Indicates whether items can be returned to the retailer by the customer.

(Allow) Layaways

Indicates whether items can be put on layaway.

(Allow) Discounts

Indicates whether items can be discounted.


Indicates whether employee discounts can be applied.

(Allow) Quantity key

Indicates whether the quantity key is allowed.





35 PLU Setup

(Allow) zero price

Indicates whether a zero price ($0.00 or 100% discount) can be entered; for example, a free item.

Print additional copy

Indicates whether a second copy of the customer receipt should be printed.

Print retail price Indicates whether the retail price of the item is printed on the receipt.


Indicates whether the suggested retail price is printed on the receipt.

GST Federal Goods and Services tax (CANADA)

PST/State Provincial or State tax

VAT tax VAT Tax (EUROPE)

Threshold 1 Threshold 1 Tax, such as Massachusetts

Threshold 2 Threshold 2 Tax


Indicates the tax tables that are used.

(User defined)Fields 1-4

Indicates the user-defined values that are be used by POS to group items.

Linked item group code

Indicates that an item group code is associated with an item group. When an item is entered at the register, the list of items belonging to the associated linked item group appears. The cashier can then select one or more of these items to add to the transaction. The association between the item and the item group code is made in the PLU Profiles table.





Step 4: Define how locations are grouped and where setting decisions are made 36

Step 4: Define how

locations are grouped and

where setting

decisions are made

a) Using the PLU Settings worksheet on page 33, determine how locations will be grouped for setting decisions. For this step, complete column E of the worksheet only. For example, returns may be allowed for regular stores but not for outlet stores.

If a particular setting is not used, it should be set to the highest level on the location hierarchy (because the decision to not use a setting is made at the company level).

b) After you have determined how locations will be grouped for setting decisions, you must indicate setting values for the location groups. For example, if you indicate that the PST/State tax setting will be decided by Region, you must indicate which regions will be have PST/State tax and which ones won't. If you decide that the Allow on layaway setting should be set based on store type you must indicate which group of locations will allow layaways (for example, regular stores allow layaways while outlet stores do not). Write this information in column E of the PLU Settings worksheet. This information will be used in step 15 (PLU location attributes and attribute sets).

Step 5: Determine

whether all locations

receive all styles

Answer the following questions:

Will all locations receive all styles? Yes / No

If no, what determines which locations get which styles?

___________________________________________________________________________________________________________________________________________________________________________Ownership attributes let you control which style information is downloaded to which stores.

For example, if your company has two types of stores, Regular and Outlet, some styles may only be sent to the Regular stores, some may only be sent to Outlet stores, and others may be sent to both.

The ownership attributes and their attribute sets are created in step 16.

Step 6: Determine

what levels and which

description will populate

the Department

and Department Group files

For STORE, determine: Which level should populate the Department Group file Which level should populate the Department file Which Merch group description should populate the Department Group file (that is,

Department Group level or higher) Which Merch group description should populate the Department file (that is, POS

Department level or higher) will a style attribute be created to describe the brand of items? If so, should it be

downloaded to POS for printing on the customer’s receipt? The style attribute created or selected must be exclusive.

For Triversity, determine: Which level should populate the Department file Which Merch group description should populate the Department file (that is,

Department level or higher)

These descriptions will be used on any department-level reports at POS.

37 PLU Setup

Step 7: Determine

what description

will populate the PLU/Item file

What description should populate the PLU/Item file? (Group PLU description, Style short description or No default)A parameter determines which value will automatically appear in the PLU description field in Style Maintenance when a style is created. If you select “No default”, this field will need to be entered by the user when the style is created.

Note: If Group PLU description is selected, the system will populate the Style PLU description field with the Merchandise Group description of the Merchandise Group at the POS Department level that the style is linked to.

This is the planning step for the parameter you will set in step 11.

Step 8: Determine values for

PLU parameters

This is the planning step for the parameters you will set in Step 12 (page 43). Although it is recommended that you decide in advance what values you want for PLU parameters, this step is not mandatory at this point.

File DirectoriesAt each day end, PLU builds files for each location that has the Generate PLU file flag selected.

These directory names are required before PLU can create and transmit files.

You can modify or delete these settings at any time.If you change or delete directories, the new settings become effective only at the next PLU file transmission.

PLU Parameters

Main Identifies the directory where PLU builds and stores daily PLU files. 50 alphanumeric characters. Set at installation.

Note: For STORE and Triversity, files are built in a subfolder of this directory called Polling

Transmission log Identifies the directory where PLU logs successful data transmissions. 50 alphanumeric characters. Set at installation.

Error log Identifies the directory where PLU logs information about unsuccessful data transmissions. Not used by segments 1007 and 1537.50 alphanumeric characters. Set at installation.

PC Register setup 38

PC Register setupThese settings determine what data PLU should put in files for PC Register. They can be modified at any time, if the characteristics of the store registers should change.

Backup filesPLU will back up the files generated before transmitting them to stores. Backups allow for retransmission in case of communication failure. Directory names are required before PLU can back up transmission files.You can modify or delete these settings at any time.If you change or delete directories, the new settings become effective only at the next PLU file transmission. Backup files in an old directory will not be transferred to a new directory, and will not be automatically deleted at the end of the retention period.

PLU Parameters

Use style send This indicates whether PLU will send the whole UPC or just the first x digits of the UPC number. Yes: PLU sends only the first part of the UPC. The actual length is determined in the UPC style code length parameter (below). Registers can identify styles from style code segments embedded in UPCs.No: PLU sends the full UPC. Default = No

UPC style code length

This field is active only if the Use style send option (above) has been set to Yes. It specifies the number of digits of the UPC that PLU will send. PLU always sends the first x digits. 1 < Integer < 13

Send description This indicates whether PLU will send a PLU item description instead of the Merchandise Group description. Yes: PLU will send style PLU description.No: PLU will not send style PLU desc. Default = No

Send check digit This indicates whether PLU will send the UPC check digit to the registers. Yes: PLU will send the UPC check digit.No: PLU will not send the UPC check digit. (Register will calculate check digit.) Default = No

PLU Parameters

Pipeline directory

Identifies the directory where PLU stores backup files from the Pipeline server. 50 alphanumeric characters

Application directory

Identifies the path to the Pipeline directory where PLU stores backup files from the application server. 50 alphanumeric characters

39 PLU Setup

Retention period The length of time in days that PLU retains backup files. Each backup file is given a date stamp. When the current date is later than a file date stamp by the number of days in this field, PLU deletes the backup file. If you change this value, the new value becomes effective only at the next PLU file transmission. If you reduce the value, be aware that it might trigger a mass cleanup of backup files the next time the PLU segment is run. 1< Value < 366 days

Use mix and match

Indicates whether to send mix & match codes. Applies only to Triversity.Yes: Send mix & match codesNo: Don’t send mix & match codes. Default = No

Tax by size Indicates whether PLU profiles for tax will be overridden at style/size level in Product Management.

Override PLU settings for style

Indicates whether PLU profile overrides will be done at style level in Product Management. Yes: PLU settings will be overriddenNo: PLU settings will not be overridden.Default = No

Retrieve group code with UPC

Indicates whether Merchandise Group Code (POS Department Group No.) should be included in the UPC file. Applies only to Triversity.Default = No

Send price change to Warehouse Management

Active only if your Merchandising Solution includes Warehouse Management. If you don't use Warehouse Management, this value can't be modified. Yes: Permanent price changes are passed on to Warehouse Management.No: Permanent price changes aren't passed on to Warehouse Management. Default = No

Use FTP Active if you must use File Transfer Protocol to send PLU files to the UNIX/BSC polling server. Once set, this value can't be modified. Applies only to Tiversity POS. PC Register always FTPs files; STORE never FTPs.Yes: PLU files are transmitted to the UNIX/BSC polling server using FTP.No: PLU files remain on the Pipeline server.Default = No

PLU Parameters

PLU Procedures in Product Management/Enterprise Data Management 40

PLU Procedures in Product Management/Enterprise Data Management

These procedures should only be performed after you have reviewed the preliminary procedures (steps 1 – 8). See the overview on page 25 for more information.

Step 9: Assign the

POS Department

level and the POS

Department Group level

Assigning the POS Department level sets the level of information that will be included in the Department file sent to the stores.Assigning the POS Department Group level sets the level of information that will be included in the Department Group file sent to the stores.

When determining the POS Department level, you must review the merchandise levels selected for the settings in Step 3. The POS Department level must be set at the lowest of those levels, or lower.

Note: When determining the Department Group level, bear in mind that the Department Group level must be the same as, or higher than, the POS Department level.

PLU key The level of information included in the PLU/item file: Style/color ID Style code. Default = Style code If client is doing color price changes, set this value to Style/color ID.

Note: If the location’s Offline Inventory Management flag is selected, this parameter is ignored and sku_id is put in the item file.

Shared attribute code

A six-alphanumeric-character attribute code created as both a style and a location attribute. It must match the following requirements: Valid active code defined as style attribute and as location

attribute Mandatory and exclusive as a style attribute Mandatory and non-exclusive as a location attribute Currently must be “OWNRSP”. In the future, you will be able to modify this code to a different value.

Brand attribute code

The style attribute code whose attribute sets will populate the Brand field in the Item DCN if attached to the style. This attribute must be exclusive. Only applicable to STORE.

PLU Parameters

41 PLU Setup

Assigning the POS

Department No. and POS Department

Group No. to a level on

the merchandise

hierarchy

1. In Merchandising, navigate to the Product Management module.

2. From the Product Management Main Menu, do the following:a) From the Navigation Bar, select Hierarchy.

b) From the Navigation Bar, select Characteristic Level Defaults.3. In the POS department group no. field, select the level that you want to assign the POS

department group level to.

4. In the adjacent Max length field, select the maximum length allowed for the POS department group number. (This value is user-defined, with a maximum of six characters in length.)

5. In the POS department no. field, select the level that you want to assign the POS department to.

6. In the adjacent Max length field, select the maximum length allowed for the POS department number. (This value is user-defined, with a max of six characters in length. Should be set to 4 for clients with STORE, Triversity and PC Register).

7. Save changes.

Modifying the POS

Department and POS

Department Group levels

Note: The POS Department level can't be modified after Collection Linking has been done.


b) From the Navigation Bar, select Characteristic Level Defaults.2. Select the new level that you want to assign the POS Department or POS Department

Group levels to.

3. In the adjacent Max length field, select the maximum length allowed for the number of the field whose level you are changing. (This value is user-defined, with a maximum of six characters in length.)

4. Enter a new group characteristic value for the level you selected and then click OK. This will be the value set for all groups at the new POS Department level or POS Department Group level, depending on the selected level.

5. Save changes.

Step 10: Assign the POS Department Group Description and POS Department Description to levels on the merchandise hierarchy 42

Step 10: Assign the

POS Department

Group Description

and POS Department Description to levels on

the merchandise

hierarchy

1. In Merchandising, navigate to the Product Management module.2. From the Product Management Main Menu, do the following:

a) From the Navigation Bar, select Hierarchy.b) From the Navigation Bar, select Characteristic Level Defaults.

3. Select the level that you want to assign the POS department description or POS department group description to.

4. Save changes.

Modifying the POS

Department Group and

POS Department Description

levels


b) From the Navigation Bar, select Characteristic Level Defaults.

2. Select the new level that you want to assign the POS department description or POS department group description to.

3. Enter a new group characteristic value for the level you selected and then click OK. This will be the value set for all groups at the level you selected.

4. Save changes.

Step 11: Set the Style

PLU default description

(parameter)

The Style PLU default description parameter determines which value will appear by default in the PLU description field in style maintenance when a style is created. Possible values include: No default (the field remains empty), Style short description or Group PLU

43 PLU Setup

description. Note that this is just a default and the value can be overridden on a style-by-style basis.

1. In Merchandising, navigate to the Enterprise Data Management module.

2. From the EDM Main Menu, do the following:a) From the Navigation Bar, select Parameters.

b) From the Navigation Bar, select System.

3. Select the Style tab.

4. From the drop-down list in the field, select the value for the Style PLU description default.

5. Save changes.

Step 12: Creating the

Ownership (“OWNRSP”)

style attribute

and its attribute

sets

The style Ownership attribute is assigned to styles to indicate which locations the style information should be downloaded to. Styles will go to stores where the store’s OWNSRP attribute set matches the style’s OWNSRP attribute set.

a) Create a style attribute called OWNRSP (Ownership). This attribute must be set to Mandatory and Exclusive.

b) Do one of the following:

If you answered “Yes” to the question “Will all locations receive all styles? ” in step 5, create an attribute set called Shared. This attribute set will be used for styles that will be received by all locations.

If you answered “No” to the question “Will all locations receive all styles? ” in step 5, create an attribute set for each group of locations that will receive the same styles, for example, Regular and Outlet.

For more information on attributes, see the section in the Enterprise Data Management User Guide entitled Attributes and Attribute Sets.

Step 13: Working with Register Types 44

Step 13: Working

with Register

Types

A list of all the register types used at all locations, along with the PLU parameters used by these registers, must be maintained in the Register Type table. PLU register settings may define other characteristics of an item being sold (for example, returnable, discountable) or the POS configuration (for example, print an additional receipt copy). After the PLU register settings have been defined, they are downloaded to the POS device during nightly polling to activate the functionality in the register.

Note: Currently, the only register settings that are used are Future retail price management and Activation days number. (See following definitions.)

Note: For Triversity, STORE and PC Register, set Activation days value to 1. For other register types, set Future retail price management and Activation days as required.

The following register types are included as part of the install process:

Register Setting Definition Type Store Triversity PC Register Used?

(Y/N)

Future retail price management

This check box indicates that the register can manage future retail prices. These future retail prices will be sent to the register when the price change is issued. This is selected by default.

0/1 Yes Yes Yes

Activation days number

This field specifies the number of days prior to the effective date that the new price must be sent to the register. This is a numeric field with a maximum 14 characters. Mandatory if the Future retail price management check box is not selected.

N Yes Yes Yes

ID Code Name Version PLU segments

1 SW Triversity 4.0 1006, 1536

2 NSB Coalition 5.5 1006, 1536

Note: The Coalition register type is being phased out. Use STORE instead.

3 PCR PC Register 8.0.4 1006, 1536

4 NTS Thin Store 6.0 See note.

5 CRS CRS 3.6 1038

6 STORE STORE 6.0 1007, 1537

45 PLU Setup

Customers who have purchased Thin Store POS and that do not have a custom modification should use register type STORE; Customers who have purchased Thin Store POS and do have a custom modification should use register type NTS (Thin Store) after confirming with Epicor ‘s Custom Development Team. Please see “PLU and Thin Store POS” on page 72 for further details.

Creating a register type

The standard register types will be loaded as part of the installation process; any new register types would be created only as part of custom modifications.1. From the EDM Main Menu, do the following:

a) From the Navigation Bar, select General. b) From the Navigation Bar, select PLU.

c) From the Navigation Bar, select Register Types.

2. In the first empty Register Code field, type a register code.3. Enter a Name for this register (that is, the maker of the register).

4. Enter the Version of the register.

5. Save changes.

Assigning PLU register

settings to register

types

After the register types have been defined, the PLU register settings used by each register type must be set. Refer to the table that you completed in Step 1 to determine whether a setting should be used for a particular register type.

Note: Currently, the only available settings on this tab are the Future retail price management check box and, if applicable, the Activation days number field.) See “Step 13: Working with Register Types ” on page 44 for definitions.

Register Types

Register Code Mandatory. Unique field that identifies the register type.

Name Mandatory. Unique alphanumeric field, maximum 40 characters. The name of this register type.

Version Mandatory reference field. Alphanumeric field, maximum 10 characters. This field indicates the version of the register.

Active Determines whether or not this register type is active. The status defaults to Active.

Modifying a register type 46

1. From the EDM Main Menu, do the following:a) From the Navigation Bar, select General.b) From the Navigation Bar, select PLU.


2. From the Table menu, select Retrieve All.3. On the Register Types tab, select a register type. (You must select the entire row

before the second tab becomes available.)

4. Click the PLU Settings for tab. 5. Select the appropriate check boxes and/or enter information in the appropriate fields

to assign PLU parameters to this register type.

6. Save changes.

Modifying a register type

The following fields can be modified: Version and Active status.

1. From the EDM Main Menu, do the following:a) From the Navigation Bar, select General.

b) From the Navigation Bar, select PLU.c) From the Navigation Bar, select Register Types.

2. From the Table menu, select Retrieve All.

3. Make all necessary changes.4. Save changes.

47 PLU Setup

Modifying PLU register settings for

a register type (Future

retail and Activation

only)


b) From the Navigation Bar, select PLU.

c) From the Navigation Bar, select Register Types.2. From the Table menu, select Retrieve All.

3. Select the register type whose register settings you want to modify.

4. Click the PLU Settings for tab.5. Make desired changes. (Currently, the only settings being used on this tab are the

Future retail price management check box and the Activation days number field. See “Step 13: Working with Register Types ” on page 44 for definitions.)

6. Save changes.

Deleting a register type

A register type can be deleted as long as it has not been assigned to any location. The Active check box must be cleared before a register type can be deleted.




2. From the Table menu, select Retrieve All.3. Clear the Active check box for the register type that you want to delete.

4. Save changes.

5. Select the entire row.6. From the Table menu, select Remove.

7. At the confirmation prompt, click Yes.

8. Save changes.

Step 14: Creating PLU

Collections

A PLU collection is a group of settings whose value is set at the same level on the merchandise hierarchy. Every PLU collection must contain at least one setting. As there are 43 PLU settings, the maximum number of collections that can be created is 43. At least one PLU collection must exist (in the case where all settings are being decided at the same level on the merchandising hierarchy). All settings must be assigned to a collection.

Determining the number of collections required Each of the 43 PLU settings fall into one of the following three categories:

a) The setting is not used by your company.b) The setting is used and has the same value across the entire company.

c) The setting is used but its value depends on the type of merchandise (for example, tee-shirts are refundable, but bathing suits are not).

Any settings that fall under category (a) or (b) should be assigned to an Enterprise/Company collection (that is, the highest level of the merchandise hierarchy).

Any settings that fall under category (c) must be assigned to collections other than the enterprise collection. Group the settings based on the level of the merchandise hierarchy at which they are defined. For example, if your merchandising hierarchy is Company > Department > Class, and the decision as to whether items are returnable or not is made

Creating a PLU collection and assigning settings to it 48

at the class level, then you could create a collection called Class that would include the setting Returnable. Use the information you provided in column D of the Settings worksheet (step 3) to create the PLU Collections.

Creating a PLU

collection and

assigning settings to it

You can create new PLU collections only until the first link is created between a PLU collection, a location attribute and a level on the main merchandise hierarchy. These links are created in the PLU Collection Linking Table.

After creating a PLU collection, you must assign PLU settings to it.A setting can only be assigned to one PLU collection. At least one PLU setting must be assigned to each collection.

All of the PLU settings must be assigned to the PLU collections before you create the first link between a PLU collection, a location attribute and a level on the main merchandise hierarchy. These links are created in the PLU Collection Linking Table.

PLU Collection Description

PLU Collection Code

Mandatory. Unique, alphanumeric field that identifies the PLU Collection.


Mandatory. Unique, alphanumeric field describing the PLU Collection.

49 PLU Setup



c) From the Navigation Bar, select Collections.2. On the PLU Collections tab, in the first empty PLU Collection Code field, type a

collection code.

3. In the PLU Collection Description, enter a brief description.4. Click the PLU Settings for tab.

5. In the Unassigned PLU settings list, select the PLU setting(s) that you want to assign to this PLU Collection.

Note: To select more than one PLU setting at the same time, hold down the CTRL key and click each item.

6. Click Add. Your selections appear in the PLU settings assigned to collection list.

Note: Click Add All to assign all the PLU settings displayed in the Unassigned PLU settings list to this PLU collection.

7. Save changes.8. Repeat steps 2-7 to create other PLU collections and assign PLU settings to them.

Modifying a PLU

collection

You can modify PLU collections until the first link is created between a PLU collection, a location attribute and a level on the main merchandise hierarchy. These links are created in the PLU Collection Linking Table.

Note: The only field that can be modified after collection linking is done is PLU Collection Description.

1. From the EDM Main Menu, do the following:a) From the Navigation Bar, select General.b) From the Navigation Bar, select PLU.

c) From the Navigation Bar, select Collections.

2. From the Table menu, select Retrieve All.3. Make all necessary changes.

4. Save changes.

Deleting a PLU

collection

You can only delete a PLU collection until the first link is created between a PLU collection, a location attribute and a level on the main merchandise hierarchy. These links are created in the PLU Collection Linking Table. Before you delete a PLU collection, you must first remove any settings that have been assigned to it.


b) From the Navigation Bar, select PLU.c) From the Navigation Bar, select Collections.


Removing settings from a PLU collection 50

3. On the PLU Collections tab, select the entire row of the PLU collection that you want to delete and then click the PLU Settings for tab.

4. Click Remove All.

5. Save changes.

6. Select the PLU Collections tab again and then select the entire row of the PLU collection that you want to delete.

7. From the Table menu, select Remove.

8. At the confirmation prompt, click Yes.9. Save changes.

Removing settings

from a PLU collection

You can remove a setting from a PLU collection only until the first link between a PLU collection, a location attribute and a level on the main merchandise hierarchy is created.



c) From the Navigation Bar, select Collections.2. From the Table menu, select Retrieve All.

3. On the PLU Collections tab, select the entire row of the PLU collection that you want to remove settings from, and then click the PLU Settings for tab.

4. On the PLU Settings for tab, in the PLU settings assigned to collection list, select the PLU settings that you want to remove from this collection.

Note: To select more than one PLU setting at the same time, hold down the CTRL key and click each item.

5. Click Remove. Your selections appear in the Unassigned PLU settings list.

Note: To remove all PLU settings, click Remove All.

6. Save changes.

Step 15: Creating PLU

location attributes/

attribute sets

PLU location attributes and their attribute sets are used by the PLU Management system to link locations to PLU settings.

You must create a location attribute for each PLU collection that was created in step 11. For example, if you created three PLU collections in step 11 – Enterprise, Department and Class – you will need to create three PLU location attributes. These location attributes will be linked to the PLU Collections in the PLU Collection Linking Table (step 16).

When naming the attribute, we recommend that the name begin with PLU. This clearly indicates that the attribute is used for PLU purposes and that it should not be used for other modules such as A&R.

These attributes must be exclusive and mandatory. This creates a one-to-one relationship between each PLU collection and a location attribute.

After you have created the attributes, you must define their corresponding attribute sets. Use the information you provided in column E of the PLU Settings worksheet (step 4) to create the attribute sets. For more information on attributes, see the Attributes and Attribute Sets chapter of the Enterprise Data Management User Guide.

51 PLU Setup

Determining the number

of PLU location

attribute sets

required for a PLU

location attribute

To determine the number of PLU location attribute sets required for a particular attribute, answer the following question for each attribute you created:Are all the settings that belong to the PLU Collection associated with the PLU location attribute defined at the highest level on the location hierarchy? Refer to the information you provided in column E of the PLU Settings worksheet (step 4). If the answer is Yes, you need only create one attribute set. See Scenario A for an

example. If the answer is No, you must create an attribute set for each group of locations that

will receive different PLU settings. See Scenario B for an example.

Scenario A:The PLU Collection called Department contains the setting Allow on layaways. Although this setting is defined at the Department level on the Merchandise hierarchy (because layaway is not available for accessories, for example), it is defined at the company/enterprise level on the Location hierarchy (because all stores have layaway). Only one PLU location attribute set is required.

Scenario B: The PLU Collection called Class contains the setting Returnable. This setting is not defined at the enterprise/company level on the Location hierarchy because its value depends on store type (returns are not allowed in outlet stores, but are allowed in regular stores, for example). Since there are two groups of locations that receive different PLU settings, two attribute sets must be created, as follows:

Step 16: Creating the

Ownership ("OWNRSP")

location attribute

and its attribute

sets

The Ownership location/style attribute combination enables you to determine which style information is downloaded to which stores. Styles will go to stores where the store’s OWNSRP attribute set matches the style’s OWNSRP attribute set.

1. Create a location attribute called OWNRSP (Ownership). This attribute must be set to Mandatory. It does not need to be exclusive.

2. Create the same attribute sets for the location attribute that you created for the style attribute. For example, if you created the attribute sets Shared, Regular and Outlet for the OWNRSP style attribute, you must create attribute sets called Shared, Regular and Outlet for the OWNRSP location attribute. For more information on attributes, see the section in the Enterprise Data Management User Guide entitled Attributes and Attribute Sets.

PLU Collection PLU settings assigned

PLU location attribute

PLU location attribute set(s)

Department Allow on layaways Layaways Layaways

PLU Collection PLU settings assigned


PLU location attribute set(s)

Class Returnable Store Type Regular

Outlet

Step 17: Set the PLU Parameters 52

Step 17: Set the PLU

Parameters

PLU parameters are set in Enterprise Data Management. In this step, you set the parameters that you planned in Step 8. (If you didn’t do Step 8, plan and set the parameters now at the same time.)

Note: The values pictured in the sample screen below may differ from the values required for your PLU setup.

1. From the EDM Main Menu, do the following:a) From the Navigation Bar, select Parameters.


2. Enter the values in the required fields. 3. Save changes.

Step 18: PLU Collection

Linking

Link each collection to the corresponding location attribute created in Step 15 and to the Merchandising hierarchy level where decisions are being made for the settings in the collection.

Note: All PLU settings must be assigned to PLU collections before any links are created.Each PLU collection must be linked to both a location attribute and a level on the main merchandise hierarchy before profiles are created. The merchandise level selected for PLU Collection Linking cannot be lower than the level defined as the POS Department.Each PLU collection can only be linked to one location attribute.

53 PLU Setup

Creating links

between PLU

collections and

attributes and the main merchandise

hierarchy



c) From the Navigation Bar, select Collection Linking.2. In the first empty PLU Collection Code field, select a PLU collection from the list.

3. Click in the Location Attribute Code field and then click to look up the valid location attribute codes entered in the system.

4. Select the location attribute code that corresponds to the PLU collection and then click OK.

5. In the Hierarchy Level field, select a valid hierarchy level from the main merchandise hierarchy list.

6. If necessary, select the Department Data check box.

7. Save changes.8. Repeat steps 2-8 to create links for the remaining PLU collections.

PLU Collection Linking

PLU Collection Code Mandatory field. Select a valid PLU Collection Code defined in the PLU Collections table.


The description displays automatically when you select a valid PLU Collection Code.

Location Attribute Code

Mandatory field. Select a valid location attribute. Press F3 to see a list of valid location attribute codes.

Hierarchy Level Mandatory field. Select a valid level from the main merchandise hierarchy.

Department Data Indicates whether PLU files should only be updated at the department level whenever the location attribute is modified.Used only for Triversity.

Modifying links between PLU collections and attributes and the main merchandise hierarchy 54

Modifying links

between PLU

collections and


hierarchy

All the information in the PLU Collection Linking Table can be changed until PLU Profiles have been linked to attribute sets.1. From the EDM Main Menu, do the following:

a) From the Navigation Bar, select General.b) From the Navigation Bar, select PLU.

c) From the Navigation Bar, select Collection Linking.

2. From the Table menu, select Retrieve All.3. Select a link to modify and then make all necessary changes.

4. Save changes.

Deleting links

between PLU

collections and


hierarchy

Links in this table cannot be deleted after PLU Profiles have been linked to attribute sets.



c) From the Navigation Bar, select Collection Linking.2. From the Table menu, select Retrieve All.

3. Select the entire row for the link that you want to delete.

4. From the Table menu, select Remove.

5. At the confirmation prompt, click Yes.6. Save changes.

Step 19: PLU Profiles

PLU profiles define a combination of setting values. One or more PLU Profiles must be created for every PLU collection.

Example: PLU Profile 1 (returns allowed) will be used for stores that allow returns. PLU Profile 2 (returns not allowed) will be used for stores that don’t allow returns.

The following table illustrates the example:

PLU profiles are linked to location attribute sets in the PLU Profile Linking table.The first step in creating PLU profiles is to name the profiles for a specific PLU collection. After you have defined the PLU profiles for each PLU collection, you can define the values for each profile.

PLU Collection

PLU settings assigned


PLU location attribute sets PLU Profiles

Class Returnable Store Type Regular PLU Profile 1 (returns allowed)

Outlet PLU Profile 2 (returns not allowed)

55 PLU Setup

Defining PLU Profiles

PLU SettingsThe availability of PLU settings in a PLU profile depends on the settings that were assigned to the PLU Collection that the profile is being created against.

PLU settings that have not been assigned to a collection will be unavailable in the associated profiles. You cannot select values for these fields. Values displayed can be inaccurate but it is not a concern.

PLU Profiles

PLU Collection Code Mandatory field. Select a valid PLU Collection Code from the list.


The description displays automatically when you enter a valid PLU Collection Code.

PLU Profile code Mandatory field. Unique alphanumeric code.

PLU Profile desc Mandatory field. Unique description of the PLU profile.

Active Determines whether or not this profile is active. The status defaults to Active.

PLU Settings 56

In the following table, the default value for each setting is indicated after the definition. For check boxes, “No” means that by default, the check box will not be selected and “Yes” indicates that by default it will be selected.

Setting Definition

Prompt form name This field contains an optional description for the name of the form associated with the item.

Prompt for price If this check box is selected price lookup will be disabled for this item and the point of sale terminal will prompt for a price when the item is entered. Default: No.

Validate This check box determines whether validation will occur. Default: No.

Accumulate This check box determines whether an item can qualify for more than one promotion at the same time. Default: No.


This check box determines whether an item should trigger a prompt for additional data. Default: Yes.

Quantity required This check box determines whether a quantity must be entered during item entry at the point of sale. Default: No.

Limited quantity Numeric field, max. 999 characters. This field indicates the quantity of this item that can be purchased during one sale transaction. A value of zero indicates that there is no quantity limit on this item. Default: 0.

57 PLU Setup

Prompt ID This field indicates the prompt sequence that is linked to this item. Prompt sequences are defined in a separate table at the register, e.g., prompt for serial number, suggested selling etc. A value of zero indicates that there is no prompt ID linked to this item. Default: 0.

Tax group code Represents the code used to group styles based on how they are taxed across the chain.

In the above example, Items A and C would share the same tax group code because all stores tax those two items at the same rate. See the “PLU and setting up taxability” on page 69 for more information on setting tax group codes.

Generate coupon ID This field indicates the coupon that will be generated when the item is sold. Different types of coupons can be set up in a separate table and are linked to this field. A value of zero indicates that no coupon should be generated for this item. Default: 0.

Commissions ID This field is used to set up a commission scheme. Commissions are defined in a separate table. Default: 0.

(Allow) Returns This check box determines whether an item is allowed to be returned to the retailer by the customer. Default: Yes.

(Allow) Layaways This check box determines whether the item can be put on layaway. Default: Yes.

(Allow) Discounts This check box determines whether an item can be discounted. Default: Yes.


This check box determines whether employee discounts can be applied. Default: Yes.

(Allow) Quantity key

This check box determines whether the quantity key is allowed. Default: Yes.

(Allow) Zero price This check box determines whether a zero price ($0.00) can be entered—that is, a free item. Default: Yes.

Print additional copy

This check box determines if a second copy of the customer receipt should be printed. Default: No.

Setting Definition

Creating a PLU Profile 58

Creating a PLU Profile


b) From the Navigation Bar, select PLU.c) From the Navigation Bar, select Profiles.


3. On the Create PLU Profiles tab, in the first empty PLU Collection Code field, select a collection code from the list.

4. In the PLU Profile Code field, type a unique alphanumeric identifier.

5. In the PLU Profile desc field, type a brief description.6. Save changes.

7. Select the entire row for this profile and then click the PLU Settings for tab.

8. Define the values for the PLU settings that belong to this profile by selecting or clearing the appropriate check boxes or entering the appropriate information.

9. Save changes.

10. Repeat steps 3-9 to create the remaining PLU profiles.

Modifying a PLU Profile

A PLU Profile cannot be modified after it has been saved.

Print retail price This check box determines whether or not the retail price of the item is printed on the receipt. Default: Yes.


This check box determines whether or not the suggested retail price is printed on the receipt. Default: No.

Linked item group Select the item group associated with the item.

GST Federal Goods and Services tax (CANADA). Default: No.

PST/State Provincial or State tax. Default: Yes.

VAT VAT Tax (EUROPE). Default: No.

Threshold tax 1 Threshold 1 Tax (for example, Massachusetts). Default: No.

Threshold tax 2 Threshold 2 Tax. Default: No.


The check boxes for Tables 6-16 indicate the tax tables that are used. Default: No.

(User defined field)Fields 1-4

Alphanumeric fields, max. 10 characters. User-defined fields 1-4 can be used by POS to group items.

Photo Alphanumeric field, max. 255 characters. Filename or URL address of a picture of the item. The photo is held at the register and can be used for a Web server, Kiosk, or a price verification process.

Sound file Alphanumeric field, max. 255 characters. Enter the path to a wave file that is held at the register.

Setting Definition

59 PLU Setup

Deleting a PLU Profile

A PLU Profile cannot be deleted if it has been assigned to an attribute set in the PLU Profile Linking table.The Active check box must be cleared before a PLU profile can be deleted.



c) From the Navigation Bar, select Profiles.2. From the Table menu, select Retrieve All.

3. On the Create PLU Profiles tab, clear the Active check box for the PLU profile that you want to delete.

4. Save changes.

5. Select the entire row.

6. From the Table menu, select Remove.7. At the confirmation prompt, click Yes.

8. Save changes.

Step 20: PLU Profile

Linking

After you have created all your PLU profiles, you must link them to the corresponding attribute sets that you created in step 13 and to merchandise groups.

Note: For information on loading links between the PLU Profiles and attribute sets using the Pipeline EDM and PROD import instead of manually entering the information in the Profile Linking table below, see “Loading PLU Profiles using EDM & PROD Import” on page 71.

This is how you specify for each Merchandise Group/Attribute Set combination what values should be applied for the associated settings. All possible PLU profile/Merchandise Group/PLU location/attribute set combinations must have a profile linked prior to running segment 1006 (for Coalition, Triversity and PC Register) or segment 1007 (for Store). Otherwise, errors will be generated and any PLU files that are generated will not be complete.

Creating links

between PLU profiles, Merchandise

groups and attribute

sets

Creating a link between PLU profiles and attribute sets 60

Creating a link between PLU profiles

and attribute

sets


b) From the Navigation Bar, select PLU.c) From the Navigation Bar, select Profile Linking.

2. From the PLU Collection drop-down list, select the PLU Collection that contains the attribute sets that you want to link to PLU profiles. The attribute sets linked to the PLU Collection display in the lower portion of the screen.

3. Click the empty PLU Profile Code field next to the first attribute set that you want to link to a PLU profile and then click … to see a list of PLU profiles. (If the PLU Profile Code field isn’t empty, it indicates linking has already been done for that Collection/Hierarchy Group/Attribute Set combination.)

4. Select the PLU Profile that you want to link to this attribute set and then click OK.5. Save changes.

6. Repeat steps 3-4 to create more links for the attribute sets in this PLU collection.

7. Repeat steps 2-6 to link PLU profiles to attribute sets in other PLU collections.

Note: You will not be able to save until all Merchandising group/attribute set combinations have a PLU profile linked.

Modifying links

between PLU profiles

and attribute

sets


b) From the Navigation Bar, select PLU.c) From the Navigation Bar, select Profile Linking.

2. From the PLU Collection drop-down list in the upper portion of the screen, select the PLU Collection containing the link that you want to modify.

Profile Linking

PLU Collection Select a valid PLU Collection.

Attribute The attribute that was linked to this PLU Collection (in the PLU Collection Linking table) displays automatically.

Hierarchy level The hierarchy level linked to this PLU Collection (in the PLU Collection Linking table) displays automatically.

Hierarchy groups The hierarchy group(s) belonging to the hierarchy level display(s) automatically.

Attribute Set Code/Attribute Set Label

All the attribute sets defined for the attribute linked to this collection display automatically.

PLU Profile Code Select a valid PLU Code. Click … to see a list of valid PLU codes.

PLU Profile Description

The description displays automatically when you select a PLU Profile Code.

61 PLU Setup

3. Click in the PLU Profile Code field that you want to modify and then click … to see a list of PLU profiles.

4. Select the new PLU Profile that you want to link to this attribute set and then click OK.

5. Save changes.

Step 21: Change

default PLU location

attribute set value for

locations, if required

When a location is created, the default values for any mandatory location attribute sets are automatically assigned to the location. You must verify the PLU attribute set assigned to existing locations and make any necessary changes. For more information see “PLU maintenance when creating locations” on page 62 Location Maintenance in the Enterprise Data Management User Guide.

Step 22 If the client has Enterprise Selling integrated with Epicor Retail Store, set the Pipeline parameter Send Concatenated Item Description to 1 on segment 1006 (if using Coalition, Triversity or PC Register registers) or segment 1007 (if using the Store register). This will trigger PLU to send a concatenated description consisting of the style code plus the style color short description plus the size code in the item’s DCNs ItemDesc field, to be used by POS in integrating with Enterprise Selling.

This change should be done in conjunction with the changes done at POS to support this integration.

Step 23 If the client has Epicor Retail Store version 6.4 or later and a style mask greater than 10, change Pipeline parameter Enforce Style Code Limit to 0 (false) on segment 1006 (if using Coalition, Triversity or PC Register registers) or segment 1007 (if using the Store register).

Done PLU Setup is now complete. As new locations, merchandise groups and styles are created, some PLU maintenance is required. For more details see “PLU Maintenance” on page 62.

4 PLU Maintenance

On an ongoing basis, some PLU maintenance may be required when: New locations are created New merchandise groups are created Errors are generated by the Pipeline segments (1006 or 1007).Other tasks that may need to be done from time to time are as follows: Overriding inherited profiles at the style level Regenerating PLU files Reviewing/resending PLU backup files Style resend

PLU maintenance when creating locationsYou must do the following for each location that you create: Assign a PLU location OWNRSP attribute set. Assign the other PLU attributes Select a Register type Enter a Polling reference

Note: For Data Exchange Polling, this number must match the store number.For UNIX/BSC Polling, this number is the Download Call File number.

Select the Generate PLU file and Offline Inventory Management flag (if applicable). This should only be done immediately before PLU is run prior to the store opening (for example, if the store opens Wednesday and PLU is run at 9:00 p.m. every night, this check box should be selected before 9:00 p.m. on Tuesday).

If your stores operate in languages other than the default company language, you must ensure that the language of operation of the location is correct so that the style and merchandise group descriptions that have been defined in the other languages are sent to the appropriate locations.

For detailed information on creating locations see Working with Locations in the Enterprise Data Management User Guide.

PLU maintenance when creating merchandise groups Assign a unique POS Department No. if the new merchandise group is at the POS

Department level. Assign a unique POS Department Group No. if the new merchandise group is at the

POS Department Group level. Perform profile linking for the new merchandise group if there is a collection linked to

the Merch Group Level that your new merchandise group belongs to.

63 PLU Maintenance

Overriding inherited PLU information by styleYou can override any inherited profile code for a selected style using the PLU Profiles window in Style Maintenance. Note that for this to be sent via PLU, the parameter Override PLU settings for style must be selected.

PLU ProfilesAll the PLU Profiles that were linked to attribute/attribute sets and a level on the merchandise hierarchy in the PLU Profile Linking table are inherited by styles belonging to these levels, along with the values for each setting. These PLU Profiles can be overridden at the style level or style/location level in the Style Overridden PLU Profiles tab.

Inherited PLU Profiles tab

Style Overridden PLU Profiles tab

Style Overridden PLU Profiles

Attribute Set Code Select an attribute set code from the drop-down list.

Attribute Set System-maintained. Displays the label associated with the selected attribute set code.

PLU Collection Code

System-maintained. Displays the PLU collection code linked to the selected attribute set.

Reviewing PLU file errors 64

Note: For more information, see the Styles chapter in the Product Management User Guide.

Reviewing PLU file errorsAll business rule violations encountered during the PLU file building process are written to the Pipeline Error Queue (visible from the Pipeline Administrator application). After every run, review the error queue. If an error is displayed, fix the problem in Merchandising and then rerun the segment.

Note: For segment 1007, the error queue is display only and cannot be used to resubmit errors.

For additional troubleshooting information on Pipeline segments 1006 and 1007, see the Merchandising Job Management Reference Manual.

Regenerating PLU filesYou can regenerate all PLU files for a location in the event of a POS system failure or a change in process (i.e. transitioning from one register type to another). As well, all PLU files are regenerated at start-up time.

The regenerate will include all data required by the location (not just the changes since last PLU download). It will also generate the full set of PLU files for the location. Files cannot be regenerated separately.

The following Merchandising actions will trigger a regenerate: A regenerate request was added to the Regenerate PLU files function (from the EDM

module, click General > PLU). The Generate PLU flag was turned on for a location The location's flag for Offline Inventory Management was turned on The location's register type was modified from one register type to another (for

example, a location was running PC Register and has upgraded to Store) The location's language was modified

PLU Collection Desc

System-maintained. The PLU collection description linked to the attribute that the attribute set belongs to displays automatically.

Size Code Select a size from the drop-down list.

Location Code If you want to override the PLU profile at the style/location level for only one location with the attribute set, enter the location that you want to affect. If you leave this field blank, all locations with the attribute set will be affected.

Location Name System-maintained. Displays the name of the selected location.

PLU Profile Code Select a PLU profile code to assign to the selected attribute set.

PLU Profile Desc System-maintained. Displays the description associated with the selected PLU profile code.

Style Overridden PLU Profiles

65 PLU Maintenance

A location's flag for Allow Customers Order was turned on. Note, if the location flag for Offline Inventory Management is already turned on, then a regenerate will not be issued since that store's PLU files was already downloaded at the SKU level

The location's ownership attribute set was modified Location's PLU profile attribute set was modified

When a regenerate is issued at the Merchandise Enterprise level, PLU files already at the registers will be deleted and replaced with new ones. If the regeneration is issued at a level below Enterprise (for example, Class), then the PLU files will only be updated.

Note: If a regenerate exists for a location (regardless on how it was triggered), then any changes since the last PLU download for that specific location that were done before and/or after the regenerate action will be ignored by PLU (since the regenerate will include the same information).



c) From the Navigation Bar, select Regenerate PLU Files.2. Click in the first empty Merchandise Group Code field and click … to look up the valid

merchandise groups entered in the system.

3. Select the merchandise group that you want to regenerate the PLU files for. If you select the enterprise level, a complete set of PLU files will be generated, overwriting the existing files for the specified location. If you select another level, the PLU files will be updated with the information for the styles belonging to the merchandise groups that you selected.

4. Click in the Location Code field and click … to look up the valid location codes entered in the system.

5. Select the location that you want to generate the PLU files for and then click OK.6. Save changes.

Note: After the PLU files are successfully generated during the scheduled Pipeline processes, the entries are deleted from this table.

Review/Resend PLU backup files 66

Review/Resend PLU backup filesBefore the PLU files (Department Group (if applicable), Department, Item/PLU, Promotions and UPC/Cross-Reference) are moved to the UNIX/BSC or Data Exchange polling machine for download to the locations, a backup is made of each file so that, in the event of a communications failure, the files can be retransmitted. From the Resend Poll Backups window you can view these backup files and resend them to the appropriate locations.

If you resend files generated prior to the latest file generation, it is important to also resend the later files, as a subset of the data in the file you are resending may have changed. For example, on 08/13/2012, resend all files for 08/11/2012 which includes style ABC with price of $20.00. If a price change for style ABC to $10 was sent on 8/12, then that file must be resent as well.If you need to resend other PLU files (for example, Store, Supplier, Color, Size, etc.), then you must copy the files from the backup folder and paste them into the polling folder.

Resend Poll Backups

Locations Enter the locations whose PLU files you want to view.

File types Select the file types that you want to view: Permanent prices, Promotional prices, Departments (displays Department and Department Group files), UPCs. All file types are selected by default.

As of The date as of which backup files will be displayed.

Backup file directory

The location of the backup file for the application directory, as defined in the EDM parameters.

Backup File Names for Resend

The list of files that you selected to view displays in this table.

67 PLU Maintenance

Reviewing PLU backup

files



c) From the Navigation Bar, select Review/Resend PLU Backups.2. Do one of the following to select the location(s) whose PLU files you want to view:

3. Select the File types that you want to display. (All file types are selected by default. If you do not want to display one of these file types, clear the appropriate check box.)

4. In the As of field, select the beginning date for which you want to view PLU backup files.5. Click Review. Files display in the Backup File Names for Resend table at the bottom of

the screen.

Resending backup files

1. After selecting the files that you want to view, you can resend any files to the appropriate location, as required.

2. From the Backup File Names for Resend table, select the file that you want to resend and then click Resend.

If you want to Do this

Select one or more locations from a lookup list

a) Click Location Lookup. b) Select the location whose PLU backup files you want to view

from the list and then click OK. The location you selected displays in the Locations list.

Select a location by searching on the merchandise hierarchy

a) Click Location Hierarchy. b) In the Hierarchy Locations window, select the Hierarchy name

from the list. c) Click the location group containing the location(s) whose PLU

backup files you want to view.

Note: If necessary, click + to see more levels contained in the hierarchy. All locations belonging to the location group that you selected display in the Hierarchy Locations box. If the list is empty, click Fill Lists.

d) Select the locations and then click >. Note: Click >> to select all the locations that are displayed.

e) Click Add Locations. The Hierarchy Locations window closes and the locations you selected display in the Locations list in the Resend Poll Backups window.

Style Resend 68

Style ResendThe Style Resend function lets you resend information about specific styles to the locations that carry them. This is done, for example, when the style information is wrong at the register and POS needs to be corrected at all locations that carry that style.

The information sent depends on the register type and the segment that is run.

For Coalition, Triversity and PC Register registers, where the PLU files are generated using segment 1006, only the PLU/Item file (permanent prices) and Cross-Reference/UPC file are re-sent.

Note: In this scenario, to resend a promotion price, you must end the promotion and issue a new one.

For STORE registers, where the PLU files are generated using segment 1007, Promo and Item Group files are generated and resent in addition to the Item and UPC files.

Note: Only promotional price changes and deals whose document status is ether in Issued or Effective status where the current system date <= document's effective end date will be included in the download.

Resending styles


b) From the Navigation Bar, select PLU.c) From the Navigation Bar, select Style Resend.

2. From the Table menu, select Query (or press F8) to perform a query and retrieve the styles that you want to resend.The styles you retrieve display in the Styles to resend list.

3. Select the styles that you want to resend and click Resend. The styles are sent to the replication queue. To see the styles in the queue, click Review.

AppendixThis appendix contains information about the following: PLU and setting up taxability Loading PLU profiles using EDM/Prod Import Sending retail and cost information to POS PLU and Thin Store POS Differences by register types PLU file specifications for STORE Triversity PLU file layouts PC Register file layout How PLU fits into the Merchandising implementation Polling with legacy POS systems

PLU and setting up taxabilityIn PLU, the only setup done for tax purposes is identifying the taxability of items. Taxability refers to whether items are taxable or not, rather than the actual rate of tax, which is set up at the register. Depending on the register type, PLU may also need to provide information about which tax table the register needs to access to get a particular item’s tax rate.

STOREEpicor STORE has several different components that work together to establish the amount of tax to be charged for an item. These components are: Tax item group: Groups styles that have the same pattern of taxability across the

enterprise Tax authority: Government agencies that levy taxes Tax zone: A geographic region that is uniquely taxes Tax rule: The Actual tax rates Zone authority: Links tax authority to tax zone Store: A standard store Zip code tax zone: The zip code that defines a tax zone Tax Rule Assign: Links the item group to an authority with a tax zone to a tax rule.

Stores and zip codes are linked to tax zone.In PLU, the tax item group code is linked first to merchandise groups via profile linking. This link can also be overridden on a style-by-style basis. (See “Overriding inherited PLU information by style” on page 63 for more information on overriding inherited PLU profiles at the style level).

To determine the tax item group code (known as Tax Group Code in PLU), you will need to get information on how the merchandise groups are taxed across the chain. Merchandise

PLU and setting up taxability 70

groups that have the same pattern of taxation across the enterprise will share a tax group code.The following example represents the code used to group styles based on how they are taxed across the chain:

In the above example, Items A and C would share the same tax group code because the stores have the same pattern of tax.The actual tax group code does not have to be a specific number, as long as PLU and POS are in synch. POS typically uses 1-20 for non-merchandise setup at stores, so tax group codes in PLU usually start at 21.

TriversityTriversity uses the concept of tax tables to establish the tax rate of an item. For example, a register might have three tax tables set up: Tax table 1: 8% (Federal/GST) Tax table 2: 7% (State/Provincial tax) Tax table 3: 6% (other tax)PLU would then send down a link between the item and the tax table, so that when the item is rung up, the register would select the correct table to obtain the correct rate. To select tax table 1 in a profile, select the GST check box. To select tax table 2 in a profile, select the PST/State check box. To select tax table 3 in a profile, select the Threshold 1 check box. To select tax table 4 in a profile, select the Threshold 2 check box. To select tax table 5 in a profile, select the VAT check box. To select tax table 6 in a profile, select the Tax Table 6 check box. To select tax table 7 in a profile, select the Tax Table 7 check box. To select tax table 8 in a profile, select the Tax Table 8 check box. To select tax table 9 in a profile, select the Tax Table 9 check box. To select tax table 10 in a profile, select the Tax Table 10 check box. To select tax table 11 in a profile, select the Tax Table 11 check box. To select tax table 12 in a profile, select the Tax Table 12vcheck box. To select tax table 13 in a profile, select the Tax Table 13 check box. To select tax table 14 in a profile, select the Tax Table 14 check box. To select tax table 15 in a profile, select the Tax Table 15 check box. To select tax table 16 in a profile, select the Tax Table 16 check box.

Item Tax Rate At Store 1 Tax Rate At Store 2 Tax Rate at Store 3 Tax Group

A 7.5 8 No tax 1

B 6 9 6 2

C 7.5 8 No tax 1

D 7.5 8 5 3

71 Appendix

PC Register If one tax, select the PST/State tax check box If two taxes, select the GST tax check box and one of the following:

PST/store for tax table 1 at the register Threshold 1 for tax table 2 at the register Threshold 2 for tax table 3 at the register VAT for tax table 4 at the register tax table 6 for tax table 5 at the resister Tax table 7 for table 6 at the register

If no tax, don’t select any of the tax check boxes.

Loading PLU Profiles using EDM & PROD ImportThis procedure allows you to load links between the PLU Profiles and attribute sets using a Pipeline job instead of manually entering the information in the Profile Linking table.

1. Create an Excel spreadsheet that contains the following fields for every Attribute Code/PLU Collection Code/Attribute Set Code/PLU Profile Code combination: The letters "MP" (for merchandise profiles) The letter "A" (for add) The merchandise group code The attribute code The PLU collection code The attribute set code The PLU profile code

2. Save the spreadsheet as a text (tab delimited) file.3. Rename the file so that it has a .go extension instead of the .txt extension.

4. Load the file on the Pipeline server in the folder specified in the parameters for the “Text File to EDM and PROD Import Tables - Import Master Entities” Pipeline segment. (Go into MapEditor and select the segment.)

5. Run the Pipeline segment “Text File to EDM and PROD Import Tables - Import Master Entities”.

6. Check the folder where the file was loaded to see if it contains a file with an .ERR extension. If so, correct any errors.

7. Run the Pipeline segment “EDM and PROD import tables to EDM and PROD”. After the segment has run, the PLU profiles should be loaded.

Sending retail and cost information to POSPLU sends the following retail and cost fields if the POS-specific file format supports them: Compare at retail Selling retail Current cost of the item for the style’s primary vendor

The currency these fields are displayed in depends on whether the company is a single- or multi-jurisdiction company.

PLU and Thin Store POS 72

Single-jurisdiction companyFor a single-jurisdiction company, there is only one currency: that of the head office. The Compare at retail and the Selling Retail are held in Merchandising in the currency of the head office and sent to the location in that currency.

The Current Cost is held in Merchandising in the primary vendor’s currency, but is sent to the location in the head office’s currency, using the purchasing exchange rate in effect at the time of PLU file building.

Multi-jurisdiction companyFor a multi-jurisdiction company, there are two currencies: Home (head office) currency and the selling location’s currency. The Compare at retail and Selling Retail are held in Merchandising and sent to the location in the location’s currency.

The Current cost is held in the currency of the style’s primary vendor and is sent to the location in the location’s currency, using the purchasing exchange rate in effect at the time of PLU file building.

PLU and Thin Store POSA Thin Store POS implementation means that each POS store will retrieve all of its master and pricing information from a centralized POS database rather than from its own local database. This means that all stores will have the same item and pricing information.The POS application is the same between Thin Store and Regular Store implementations. The difference is how Merchandising is configured for PLU. Briefly: In a Thin Store environment, a dummy store representing the centralized POS server is created in Merchandising, and only that dummy store is setup for PLU (the Generate PLU flag is only turned on for the dummy store, and all other selling stores will have the Generate PLU flag turned off). Based on this setup, PLU will then generate one set of PLU files that is downloaded to the centralized POS database rather than generate a set of PLU files for each store.

Differences by register types

Field STORE Triversity PC Register

POS Department Group No.

Y N/A N/A

POS Department No. 4N 4N 4N

Activation days parameter required for permanent price changes?

Y Y Y

Polling type with Merchandising

Data Exchange Polling Data Exchange Polling Unix/BSC Polling

Unix/BSC Polling

73 Appendix

What to put in the location Polling Reference field

store number Using Data Exchange Polling: store numberUsing BSC Polling: Download Call File number

Download Call File number

Name of file with styles and permanent price changes

Item file PLU file 50 and 25

Supports download of deals from Deal Management?

Y N N

Can item be sold if not downloaded via PLU?

Y Y Y


Differences by register types 74

How non-merch is handled

Non-merchandise is set up at the register, but when full PLU files are sent down, they overwrite the non-merch as well (since merch and non-merch are held in the same table in the current version). The following setup illustrates this:

1. Non-merch is set up in a file that is kept on the Data Exchange Polling server.

2. A batch is set up in the scheduled events of Windows that moves the file to the /NTPolling/Data/Download/Merch directory on a nightly basis.

3. Polling is set up to distribute the file to all stores every night.

If you decide to send a full PLU file during the day, you must manually move the non-merch file.

Non-merchandise files are created by store in any text editor (for example, NotePad) in the following format:D1XXXXYY00SSSSSSSSSSSSS<cr> Where D1 is always D1 (code so that register knows what it is receiving).X = department/class reference from legacy IPLU (for example, DDCC). Y = tax table reference (tells register which tax table to look at). 0 = reportability flag. S = description of non-merch item that will show up on the register.<cr> = carriage return/ enter. For more details on the tax table reference and the reportability flag, see the PC Reg file specifications. A backup of these files should be saved in a subdirectory of the PLU file directory. Each store’s PLU folder should have a copy of the non-merch file for that store. The file should be renamed to nonmerch.as1. When a regenerate is done, CORE-to-PLU will pick up a copy of this file from this folder and include it in the full file built for the store.

Style description length 50 characters 40 characters Parameterized – if checked, 20 character maximum

Merch Group description length

25 characters 20 characters 12 characters


75 Appendix

STORE PLU file layoutsFor detailed information on the Store PLU register file layouts, see the IDMD.PLU_ Download_to_STORE(segment_1007) document, available on request from Epicor.

Triversity PLU file layouts

File Formats All fields are separated by a comma and each record is terminated with a carriage return/line feed.

Note: * indicates fields that are required and $ indicates future fields.

If the Update Type is set to 99 in any transaction type files, this feature will delete the corresponding file at the POS and build a new file. Update Type “2”, Insert and Modify respectively, can be used interchangeably. With a type “2”, if the record does not exist, it will be added to the database. The PLU field from the XREFTXN.ASC is the key that makes the link between this file, PLUTXN.ASC (PLU field) file and the

PROMOTXN.ASC file (PLU field). The Department field from PLUTXN.ASC makes the link between this file and DEPTTXN.ASC file (Department/Class field). The Activation Date field from PLUTXN.ASC file is used only with the following fields: Update Type, PLU, Retail Price and

Retail Price Status to add a permanent price that will be effective from the date indicated in this field. Only those fields marked with Yes will be filled by PLU system for one of the following actions: Insert, Modify and Delete. Only those fields that are marked with Yes(*) in PLUTXN.ASC action Modify are mandatory when an update will be sent to

the register. When Update Type is 99, all other fields from a record will be empty (for example, XREFTXN.ASC 99,,,,).

Triversity PLU file layouts 76

PLU Cross ReferenceFILE: Xreftxn.asc

PLU File Update RecordsFile: Plutxn.asc

Field Name Field Type Field Description Values Insert/Modify Delete Field from Merchandising

Update Type * 9 2 – Modify;3 – Delete;99 – Delete File

Yes Yes

PLU * 18 AN This field contains the number that is referenced back to the PLU.

Yes Yes Style code or Style_color_ID, depending on PLU parameter “PLU Key”

Cross Reference PLU *

18 AN This field contains a number representing an item used at the POS terminal.

Yes Yes UPC

Capture PLU Only

1 AN This field determines whether or not the PLU information will be captured and printed.

N/Y or 0/1 No No

Field Name Field Type Values Insert Modify Delete Field from Merchandising

1. Update Type * 99 2-Modify, 3-Delete, 99-Delete existing PLU file & rebuild from transactions

Yes Yes(*) Yes

2. PLU * 18 AN Style code or style/color reference, depending on the setting of the PLU key parameter

Yes Yes(*) Yes Style code or style/color reference, depending on the setting of the PLU key parameter

77 Appendix

3. Old PLU 18 AN When changing PLU number No No No

4. Department 9999 Yes No No

5. PLU Description

40 AN Yes Yes No Style PLU description

6. Retail Price 9999.99 Yes Yes No Location’s selling retail (see “Sending retail and cost information to POS” on page 71 for more information

7. Mix Match ID 999 Up to 250 IDs Yes Yes No Style or style/color’s mix match rule 1

8. Tax Table 1 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the GST option is selected)

9. Tax Table 2 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the PST/state option is selected)

10. Link Item 1 AN Y/N or 1/0 No No No

11. Discountable 1 AN Y/N or 1/0 Default Yes Yes Yes No Profile linking (whether or not the Allow discounts option is checked

12. Commission ID

9 Future No No No

13. Vendor ID 9 AN Yes Yes No The vendor_id from the Merchandising database that the PLU is for.



14. User field 1 10 AN Yes Yes No Profile linking (value from user-defined flag 1)

15. Prompt ID 999 Up to 250 IDs Yes Yes No Profile linking (value from Prompt ID field)

16. Family Code 999 No No No

17. Frequent Buyer Code

999 Yes Yes No Profile linking (value form Tax Group Code field)

18. Use Department

1 AN Y/N or 1/0 (See below) Yes Yes No

19. Scale Item 1 AN Y/N or 1/0 No No No

20. Returnable 1 AN Y/N or 1/0 Default YES Yes Yes No Profile linking (whether or not the Allow Returns option is selected)

21. Coupon Item 1 AN No No No

22. Tax Table 3 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Threshold 1 option if selected)

23. Tax Table 4 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Threshold 2 option if selected)

24. Itemizer 1 1 AN Y/N or 1/0 No No No

25. Itemizer Tax 1

1 AN Y/N or 1/0 No No No

26. Itemizer Tax 2



79 Appendix

27. Itemizer Tax 3


28. Itemizer Tax 4


29. Activation Date

8 AN yy/mm/dd No Yes No The effective date of the permanent price change for the item indicated by the record

30. Tare Weight 999 No No No

31. Has Cross Ref. PLU


32. Has Quantity Price


33. Has Level Price


34. Mix/Match 2 999 Yes Yes No Style or Style/Color’s Mix Match Rule 2




38. Itemizer 2 Tax 1



























1 AN Y/N or 1/0 No No No Profile linking (whether or not the Validate option is selected)

52. Verify Price when sold

1 AN Y/N or 1/0 Yes Yes No

53. Quantity Description

10 AN No No No


81 Appendix

54. Limited Quantity

999 Yes Yes No Profile linking (quantity from Limited quantity field)

55. Item Size 9.999 No No No

56. Employee Disc. Allowed

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Allow Employee Discounts option is selected)

57. Suggested Retail (SRP)

9999.99 Yes Yes No Style’s Compare at retail (see “Sending retail and cost information to POS” on page 71 for more information)

58. User field 2 $ 10 AN Yes Yes No Profile linking (value from User-Defined 2 field)



61. User field 5 $ 10 AN No No No

62. User field 6 $ 10 AN No No No

63. Generate Coupon ID#

99 Yes Yes No Profile linking (value from Generate Coupon ID field)

64. Auto Disc. ID#

99 No No No

65. Filler $ 9999 No No No





68. Quantity Required

1 AN Y/N or 1/0 Yes Yes No Profile linking (value from Quantity Required field)

69. Selling Quantity

999 No No No

70. Allow on Layaways

1 AN Y/N or 1/0 Yes Yes No Profile linking (value from User-Defined 2 field)

71. Match MFG Code


72. Tax Table 5 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Table 5 option is selected)






83 Appendix








84. Cost 9999.99 No No No

85. Competitive Price 1

9999.99 No No No

86. Competitive Price 2

9999.99 No No No



87. Alternate Vendor 1

9 AN No No No

88. Alternate Vendor 2

9 AN No No No

89. Price Label Format ID

999 No No No

90. Shelf Label Format ID

999 No No No

91. Inventory Group ID

18 AN No No No

92. Supplemental Length

99 1-20 No No No

93. Loyalty Program ID 1

99 1-20 No No No


99 1-20 No No No


99 1-20 No No No


99 1-20 No No No


85 Appendix

Department File – update recordsFile: Depttxn.asc


1. Update Type 99 2 – Modify,3 – Delete, 99 - Delete existing dept file before applying new txns

Yes Yes Yes Additions/modifications - 2Regenerate - 9

2. Department/Class

9999 Yes Yes Yes POS Dept Group code

3. Department Group

999 No No No

4. Description * 20 AN Yes Yes Yes POS Dept Description

5. Deposit 999.99 No No No

6. Allow Quantity

1 AN Y/N or 1/0 Yes Yes No Profile Linking (whether or not the Quantity Key Allowed option is selected)

7.Force Preset 1 AN Y/N or 1/0 No No No

8. Positive Department


9. Tax Table 1 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the GST option is selected)


10. Tax Table 2 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the PST/state options is selected)

11. Quantity Required

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Quantity required options is selected)

12. Allow Decimal Quantity


13. Future 1 AN Y/N or 1/0 No No No


15. Cost Prompt Required

1 AN (C)ode or (D)ollar No No No

16. Quantity Description

5 AN No No No

17. Preset Department Amt.

99.99 No No No

18. Allow Returns

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Allow Returns option is selected)


87 Appendix

19. Allow Discounts

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the allow Discounts option is selected)

20. Deposit Description

12 AN Yes Yes No A space will be put in this field

21. Tax Table 3 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Threshold 1 option is selected)

22. Tax Table 4 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Threshold 2 option is selected)

23. Scale Item 1 AN Y/N or 1/0 No No No

24. Future 999 No No No

25. Future 3 AN No No No


27. Allow Zero Price

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Allow Zero o Price option is selected)

28.Authority Level

9 No No No



29. Maximum Unit Price

999.99 No No No

30. Print Slip 1 AN Y/N or 1/0 No No No

31. Slip Advance 99 No No No

32. Slip Lines 99 No No No

33. Validate 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Validate option is selected)

34. Tare Weight 999 No No No

35. Menu Number

9 No No No

36. Profile ID 999 Up to 250 IDs No No No

37. Mix/Match Number

999 Up to 250 IDs No No No

38. Min/Max 2 999 Up to 250 IDs No No No

39. Mix/Match 3 999 Up to 250 IDs No No No

40. Mix/Match 4 999 Up to 250 IDs No No No







89 Appendix



















54. Itemizer 3, Tax 3















61. Allow Employee Disc.

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Allow Employee Discount option is selected)

62. Generate Coupon


63. Auto Discount ID

999 Up to 250 No No No

64. Future 99 No No No

65. Minimum Price

9.99 No No No

66. PLU Required


67. Allow in Layaway

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Allow Layaways option is selected)


91 Appendix

68. Print Regular Price

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Print Retail Price option is selected) (see Sending retail and cost information to POS on page 71 for more information)

69. Print Suggested Retail

1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Print Suggested Retail Price option is selected) (see “Sending retail and cost information to POS” on page 71 for more information)

70. Tax Table 5 1 AN Y/N or 1/0 Yes Yes No









77. Tax Tabld 12 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Table 12 option is selected)




93 Appendix

80. Tax Tble 15 1 AN Y/N or 1/0 Yes Yes No Profile linking (whether or not the Table 15 option is selected)


82. Remote Printer Number

99 Remote printer # (0-99) No No No

83. Remote Print Control

1 AN Y/1 if print entire transactionN/0 if print item onlyDefault N

No No No

84. Employee Disc

9.99 Percentage discount rate No No No


99 1-20 No No No


99 1-20 No No No


99 1-20 No No No


99 1-20 No No No



Promotions - update recordsFile: Promotxn.asc

Field Name Field Type Values Description Insert/Modify Delete Field from Merchandising

1. Update Type * 9 2-modify, 3-delete99 - Delete Profile file and rebuild from transactions

Yes Yes Additions/modifications - 2Cancels - 3Regenerate - 99

2. Start Date 8 AN yy/mm/dd This field determines the date the promotion is to be implemented.

Yes Yes Price change effective date

3. Stop Date 8 AN yy/mm/dd This field determines the date the promotion is to be terminated.

Yes Yes Price change end date

4. Start Time 5 AN hh:mm This field determines the time the promotion is to be implemented.

No No

5. Stop Time 5 AN hh:mm This field determines the time the promotion is to be terminated.

No No

6. PLU 18 AN This field determines the product to be affected by the promotion.

Yes No Style code or style/color reference, depending on the setting of the PLU key parameter

7. Filler 18 AN No No

8. User field 1 10 AN This field determines the User value to be used in a promotion.

No No

9. User field 2 10 AN No No

95 Appendix

10. DEPT 9999 This field determines the department to be used in a promotion.

No No

11. Filler 9999 No No

12. Group 999 This field determines the group to be used in a promotion.

No No

13. VENDOR 9 AN The field determines the Vendor to be used in a promotion.

No No

14. From PRICE POINT

999.99 If a promotion is to be made by selecting a group of items within the same price boundary, the lowest price would be entered here.

No No

15. To PRICE POINT

999.99 If a promotion is to be made by selecting a group of items within the same price boundary, the lowest(highest) price would be entered here.

No No

16. Percent Off 99 This field determines whether or not the markdown will be made by a percentage amount.

No No

17. Markdown 99.99 Future No No



18. New Price 9999.99 This field determines whether or not the markdown will be made by entering a new price.

Yes No New price

19. Promotion Number

999 Yes Yes Price change document number

20. Category 999 This field determines the group to be used in a promotion.

No No

21. Accumulate 1 AN Y/N or 1/0 This field determines if this item can qualify for more than one promotion.

No No

22. Exception 1 AN Y/N or 1/0 This field should be selected only when a promotion for an exception item is created.

No No

23. Exception Number

999 This field defines the number associated with the exception item.

No No

24. Filler 99 No No

25. Filler 9999 No No

26. Filler 99 No No

27. Filler 99 No No

28. Filler Y/N or 1/0 No No


97 Appendix

PC Register file layout

ASCII PLU file layoutsThere are five (5) file types that can be downloaded to the register:

1. “DDCC” Department/Class File. Also known as the “2F” File.2. Active PLU File (style file). Also known as the “25” File.

3. Active Promo File (styles on promotion). Also known as the “27” File.

4. Pending PLU File (modifications to the style file: adds, modifies, or deletes). Also known as the “50” File.

5. Pending Promo File (modifications to pending promotions: adds, or deletes). Also known as the “60” File.

Each file type is made up of two parts: Header - one record per file type Details - multiple records per file type.

Note: All records are of a fixed length of 32 bytes long – ASCII characters only. All records are terminated with Carriage Return + Line Feed characters (Hex 0D0A).

File Header Records

Queue File Header

The first record in the queue file will always be an “HO”-type record. This identifies the stores to which the queue applies. If there are fewer than 10 stores, the remaining part of the record will be blank filled; if there are more than 10, the additional stores will be listed on the following “HO” record. The store list may be blank.H1 - “DDCC” Department/Class File Header (2F File)

The DDCC file header will be followed by any number of “D1” -type details.H2 - Active PLU File Header (25 File)

Field Description Length Merch

1 Code “HO” 2 System-set to “HO”

2 Store List 999 (*10 stores) 30 Numeric Only. Currently not supported.


1 Code “H1” 2 System-set to “H1”

2 Filler (blanks) 30




PC Register file layout 98

The ACTIVE PLU file header will be followed by any number of “D2” -type details.

H3 - Active Promo File Header (27 File)

The ACTIVE PROMO file header will be followed by any number of “D3” -type details.

H4 - Pending PLU File Header (50 File)

The PENDING PLU file header will be followed by any number of “D2” and “D4” -type details. H5 - Pending Promo File Header (60 File)

The PENDING PROMO file header will be followed by any number of “D3”-type details.

File Detail Records

D1 - “DDCC” Department/Class Detail (2F File)






2 Activation Date MMDDYY 6 Numeric Only




2 Activation Date MMDDYY 6 Numeric Only Promo effective date



1 Code “D1” 2 System-set to “D1”

2 DDCC 9999 4 Numeric Only POS Dept Group No.

Where Non-merchandise; 0001 – 0099 ; 0031 = “Other Non-Merchandise”, usually a default non merchandise category.0095 = “Special Fee”0096 = Reserved for future use.0097 = Reserved for future use.0098 = “Layaway Fee”.0099 = “Gift Certificate”Merchandise Items

99 Appendix

0101 to 9999 (“CC” portion cannot be “00”).DepartmentsIf the “CC” portion is “00” then a department will be created.

3 Key Taxability 99 Profile linking (see “PLU and setting up taxability” on page 69 for how to set up tax for PC registers).

Where: DDCC KEY TAXABILITY field: (two digits “99”)[0-9,A-D] [0-7]. The first byte tells the register which tax table to use if the item is taxable. The second byte tells the register if the item is taxable. First digit, tax table numberSingle Tax Rate (or non-GST)Up to 6 tables are supported0 = register table 11 = register table 22 = register table 33 = register table 44 = register table 55 = register table 66 = currently not supported7 = currently not supported. Note: At the register, each table above can be associated to one of two rates set at the register. Dual Tax Rate (or with GST). Up to six tables are supported0 = register table 1 + second rate taxable (GST)1 = register table 2 + second rate taxable (GST)2 = register table 3 + second rate taxable (GST)3 = register table 4 + second rate taxable (GST)4 = register table 5 + second rate taxable (GST)5 = register table 6 + second rate taxable (GST)



8 = register table 1 + second rate non-taxable (non GST)9 = register table 2 + second rate non- taxable (non GST). A = register table 3 + second rate non- taxable (non GST)B = register table 4 + second rate non-taxable (non GST); C = register table 5 + second rate non- taxable (non GST); D = register table 6 + second rate non- taxable (non-GST). At the register, each table above can be associated to one of two rates set at the register. The second rate can only be associated to one rate at the register. Thus, if needed, the register can have three rates.Second digit, taxabilityAn even value for the second digit indicates taxable; odd indicates non-taxable. Start with 0 = taxable item. Add: +1 to make it non-taxable+2 to prompt for additional data at the register+4 to print a additional receipt.

4 Reportability 99[0-9] [0-9]

2 Numeric OnlyUser-defined fieldCurrently not supported.

System-set to “00”

5 Description ############ 12 POS Dept Description

Where: DESCRIPTION FLAGS: /V - Printer validation of this SKU. “/V” is placed at the beginning of the description. %99 - Employee discount rate on this SKU. “%99” (where 99 is the rate) is placed at the end of the description.



101 Appendix

D2 - PLU Detail (25 and 50 Files)



2PLU/UPC key 99999999999999 14, right-justified, zero-filled Numeric Only

UPC

Where: For example: UPC = 401010010001PLU key = 00401010010001Non-merchandise. If using preset fees,Format: 00DDCC00000000. Also see “D1 - “DDCC” Department/Class Detail (2F File)” above. 00003100000000 = Not used (“Other Non-Merchandise”).Special Fee = 0000950000000000009600000000 = Reserved for future use.00009700000000 = Reserved for future use. Layaway Fee = 0000970000000000009800000000 = Not used (Gift certificate).

3 Tax/Prompt 99 2 Numeric Only Profile linking (see “PC Register” on page 71 for how to set up tax for PC Register)

Where TAX/PROMPT FIELD: (two digits “99”[0] [0-9][1] [0-9][2] [0-9][3] [0-9][4] [0-9][5] [0-9][6] [0-9][7] [0-9][8] [0-9]

Price lookup; *Not used. Enter price; * Not used. Not used. Not used. Not used. Not used. Delete PLU entry (pending file only)

* The second digit is a “FOR” quantity (0 and 1 are equivalent). Currently only 0 and 1 are supported.

4 Price (cents) 9999999 7 Numeric Only Current selling retail)


D3 - Promo Detail (27 and 60 Files)

5 DDCC key 9999 4 Numeric Only POS Department No. that Style or Style/Color is linked to

6 Filler (blanks) 3




2 PLU/UPC key 99999999999999 14, right-justified, zero-filled Numeric Only

UPC

For example: UPC = 401010010001; PLU key = 00401010010001

3 Promo 99 2 Numeric Only System-set to “00”

Where: PROMO FIELD: (2 digits “99”)

[0] [0-9] New price; second digit is a “FOR” quantity*

* The second digit is a “FOR” quantity (0 and 1 are equivalent). Currently only 0 and 1 are supported.

[2] [0] % off

[4] [0] $ off

[8] [0] Delete Promo (pending file only)

All other values(Default)

New Price

4 Discount %, Dollar off amount, or new price

9999999 7 Numeric Only New price

5 Expiry Date MMDDYY 6 Numeric Only Price change end date

6 Filler (blanks) 1

103 Appendix

D4 - PLU Description Detail (25 and 50 Files)

Note: D4 records will follow every D2 record if sending style descriptions down to the register.

ExamplesA file may be made up of the following records:H0 – Queue File Header

H1 – “DDCC” Department/Class File Header (2F File)Plus multiple D1 records

D1 - DDCC Detail

H2 – Active PLU File Header (25 File)Plus multiple D2 + D4 records

D2 - PLU DetailD4 - PLU Description Detail (optional)

H3 – Active Promo File Header (27 File)Plus multiple D3 records

D3 - Promo Detail

H4 – Pending PLU File Header (50 File)Plus multiple D2 + D4 records

D2 - PLU DetailD4 - PLU Description Detail (optional)

H5 – Pending Promo File Header (60 File)Plus multiple D3 records

D3 - Promo Detail



2 Style Description

#################### 20 Stle PLU Desc.

Where DESCRIPTION FIELDS

%99 – Employee discount rate on this SKU.“%99” (where 99 is the rate) is placed at the end of the description.

3 Filler (blanks) 10 10


Example 1:

1 2 3 12345678901234567890123456789012

H0 CrLf Queue header

H1 CrLf DDCC File

D1010100 Shoes CrLf

DDCC 0101, Description “Shoes”; Taxable

D1020101 Socks CrLf

DDCC 0201, Description “Socks”Non-taxable

H2 CrLf Style File

D2004010100100010000124990101 CrLf

Style 0101.001UPC = 401010010001Price = $124.99DDCC = 0101Price lookup; For quantity = 1

D4Dress Shoes CrLf Style 0101.001 Desc. Dress Shoes

D2004010100200000000049990101 CrLf

Style 0101.002UPC = 401010020000Price = $49.99DDCC = 0101Price lookupFor quantity = 1

D4Leather Sandals CrLf Style 0101.002 Desc. Sandals

D2004020100100080000009000201 CrLf


D4Dress Socks CrLf Style 0201.001 Desc. Dress Socks

D2004020100200070000004500202 CrLf


D4Casual Socks CrLf Style 0201.002 Desc. Casual Socks

H3 CrLf Active Promo

105 Appendix

Example 2: H0 Queue Header FileH1 DDCC FileD1DDCCttbbddddddddddddDDCCH2 Style FileD2UUUUUUUUUUUUUU00$$$$$$$DDCC Style D4sssssssssssssssssss Style description H3 Active Promo FileD3UUUUUUUUUUUUUUppPPPPPPPmmddyy Style on PromoH4mmddyy Pending PLU FileD2UUUUUUUUUUUUUU00$$$$$$$DDCC Pending StyleD4ssssssssssssssssssss Style description H5mmddyy Pending Promo FileD3UUUUUUUUUUUUUUppPPPPPPPmmddyy Style on Promo

D300402010010008000000450123198 CrLf

Dress Socks on promo till 12/31/04New price = $4.50

D300402010020007000000225123198 CrLf

Casual Socks on promo till 12/31/04New price = $2.25

H4120198 CrLf Pending PLU Starting 12/01/98

D2004010100300090000079990101 CrLf

Style 0101.003 UPC = 401010030009Price = $79.99DDCC = 0101Price lookupFor quantity = 1

D4Sneakers CrLf Style 0101.003 Desc. Sneakers

D2004010100400080000049990101 CrLf


D4Casual Shoes CrLf Style 0101.004 Desc, Casual Shoes

H5121198 CrLf Pending Promo Starting 12/11/04

D300401010010001400002500123198 CrLf

Dress shoes on sale: $25.00 offEnding 12/31/04

D300401010040008000002999123198 CrLf

Casual shoes on sale: New price $29.99Ending 12/31/04

How PLU fits into the Merchandising implementation 106

POS processing rulesThe POS processing logic is as follows: The 2F file (class) can be sent without the 25 file (style) only if NO classes are deleted. If the 25 (style) and 2F (class) files are sent down, then all PLU files are deleted. If the 27 file (promo) is sent down, then the 60 file (PLU promo pending) is deleted.

Note: There is a parameter to allow the system to process a 25 file (style) without a 2F file (class) downloaded (system parameter 429).

PC Register file namesThe downloaded file name is: POLLPLU.AS1 or POLLPLU.AS2.

POLLPLU.AS1 will be merged before POLLPLU.AS2.

File location is \PCREG\directory

How PLU fits into the Merchandising implementationA typical PLU project entails the following steps:1. Start with the Product Review Meeting. This is where the flow is explained to the client

and questions related to the setup are asked (see PRM manual for more details). At this time, you must ask the client to provide you (post-PRM) more detailed information related to the questions you asked during the PRM (for example, if PLU settings values are being specified at a Merchandising level lower than chain or differently by location, then you need the specifics for each merchandise group or group of locations).

2. Remind the client to return the data requested at the PRM.

3. Ensure all the preliminary steps are done (see Steps 1 through 8 of “Preliminary PLU setup procedures ” on page 27).

4. Ensure that Merchandising groups and Locations have been set up.

5. Ideally, PLU setup will be done in the database that will be used as a backup of the master tables prior to the copy from this backup database to the Live and Test databases; this eliminates having to do the PLU setup multiple times. The parameters for the paths related to file, error, log and backups will need to be changed after the copy.

6. Do the PLU setup in the system (see Steps 9 through 21, “PLU Procedures in Product Management/Enterprise Data Management” on page 40).

7. Test the PLU setup after styles have been loaded into the system.

8. Put together the maintenance procedures specific to the client (see “PLU maintenance when creating locations” on page 62 and “PLU maintenance when creating merchandise groups” on page 62).

9. Review the maintenance procedures with the client so that they are comfortable with what they will have to do.

10. Support the client with any PLU issues that come up when they go live.

11. Attend the Handover-to-Support meeting.

107 Appendix

Polling with legacy POS systems

Data Exchange polling (Triversity)This section describes what happens as the PLU files move from Merchandising to Data Exchange Polling. It covers Triversity only.When PLU files are created, they are made available to Data Exchange Polling.

At the same time that the PLU files are made available to Data Exchange Polling, a script called S_filer.ini is automatically created for each location. This script file is sent to the stores with the PLU files. It contains instructions for the register to move the PLU files from the directory where the files are received at the register (C:\STS\In) to another directory within the register (C:\XPS40\PARM).

Note: The S_filer.ini file is created only for Triversity. The remaining steps describe what occurs when PLU files are downloaded to a Triversity register.

When the PLU files are in this new directory, the Goodnight process (overnight process at the register) creates a trigger file that merges the PLU files into the PLU database at the register (BACKOFF.db). When the register is opened the next morning, the new information is available when sales are rung up. If the register polls successfully, the PLU files and the associated S_filer.ini files are

deleted from the NT machine. If the register does not poll successfully, the PLU files remain in their directory on the

NT machine. The script files are moved to a temporary file until the store polls successfully.

If the PLU files are successfully downloaded, but the S_filer.ini scripts are not, the PLU files will remain in the C:\STS\In directory until an S_filer.ini file is successfully downloaded and moves them to C:\XPS40\Parm.

UNIX/BSC polling (Triversity)This section describes what happens as the PLU files are moved from Merchandising to the UNIX machine in preparation for polling. It covers Triversity only.

1. When PLU files are created, they are automatically moved to the UNIX machine by the Pipeline segment that created the files.

2. The files will reside in the following directory on the UNIX machine: SYSRES/EMAIL.FD/MISC/SCRIPT/XXXX, where XXXX represents the polling reference number for a particular location.

As a location is set up in EDM, it is linked to a polling reference number. This four-digit number indicates the location on the UNIX machine where the polling application will pick up PLU files for this location. For example, if the polling reference number for Store 3 is 1003, the PLU files for Store 3 would be moved to the following location on the UNIX machine: SYSRES/EMAIL.FD/MISC/SCRIPT/1003. The polling application picks up the PLU files from this location and sends them to Store 3 during the polling process.

If the polling reference number set up in EDM for a particular location has fewer than four digits, leading zeroes will be added to that number to create the required four-digit number.

If the polling reference that has been defined for this location in EDM does not exist on the UNIX machine, the PLU files will remain on the Pipeline server until the polling

Polling with legacy POS systems 108

reference does exist on the UNIX machine and the Pipeline segment runs again. Any subsequent PLU files that are created will be appended to the files that remain on the Pipeline server – they will not overwrite these files.

At the same time that the PLU files are moved to the UNIX machine, a script called S_filer.ini is automatically created for each location. This script file is sent to the stores with the PLU files. It contains instructions for the register to move the PLU files from the directory where the files are received at the register (C:\STS\In) to another directory within the register (C:\XPS40\PARM).

Note: The S_filer.ini file is created only for Triversity.The remaining steps describe what occurs when PLU files are downloaded to a Triversity register.

Once the PLU files are in this new directory, the Goodnight process (overnight process at the register) creates a trigger file that merges the PLU files into the PLU database at the register (BACKOFF.db). When the register is opened the next morning, the new information is available when sales are rung up. If the register polls successfully, the PLU files and the associated S_filer.ini files are

deleted from the UNIX machine. If the register does not poll successfully, the PLU files remain in their directory on the

UNIX machine. The script files are moved to a temporary file until the store polls successfully.

If the PLU files are successfully downloaded, but the S_filer.ini scripts are not, the PLU files will remain in the C:\STS\In directory until an S_filer.ini file is successfully downloaded and moves them to C:\XPS40\Parm.

User Documentation Feedback FormUse this form to send Epicor comments on documentation. Thank you for taking the time to help us improve our publications.

After completing the fields, click the Submit Form button (in the top-right corner) to send your comments to Epicor.

User Info (optional)

Documentation Info

Comment

Rating

Name:

Company:

Email address:

Can we contact you if we need further information? Yes No

Document name: Publication date (inside cover):

If you are commenting on specific text, include the location of the text (for example, a help topic title, a chapter and section title, a table number, or a page number):

Comments (including corrections and suggestions):

Please rate the document: Excellent Good Average Fair Poor

Did the document meet your needs? Yes No If not, fill in the Comments field above, describing your situation.