Enabler Database Files - LOCAL

From EnablerWiki
Jump to navigationJump to search
Created: 16 March 2009. Last Reviewed: 16 March 2012
Enabler 4.74
Explanation of LOCAL Database files used by Enabler
Name Description Replace from other till Can file be replaced from upgbase Further Information
    without data loss? and exported from EEE?  
advsrch Advanced Search Fuzzy Logic Tokens Yes Yes.  No Export from EEE. Imported via ISLFUZZY.DAT
Anal10 Product categorisation - Analysis10 Yes Yes - export Analysis10 from EEE
Anal5 Product categorisation - Analysis5 Yes Yes - export Analysis5 from EEE
Anal6 Product categorisation - Analysis6 Yes Yes - export Analysis6 from EEE
Anal7 Product categorisation - Analysis7 Yes Yes - export Analysis7 from EEE
Anal8 Product categorisation - Analysis8 Yes Yes - export Analysis8 from EEE
Anal9 Product categorisation - Analysis9 Yes Yes - export Analysis9 from EEE
Bcodfefmt Embedded Barcode Formats table Yes Yes.  No Export from EEE. Imported via 2A/2C, Deleted by 2D records.  Also maintained in BO.
Branch All store codes Yes Yes - export Branches from EEE
Brchcpn Branch Continuing Permissions Number Yes Yes - export CPN Inter-Branch Maintenance from EEE
Brchseq Nibbler messages received from tills in branch sequence# log  No Yes.  N/A
Brchtill All store till codes Yes Yes - export Tills from EEE
Brnchlst Stores branch Code - 1 record Yes
Bu-param Backup of posparam.dbf NO!! Not required. If missing, Enabler will automatically create a new file
Cashperf Temp Table used by Cashier Performance Report Yes Yes.  N/A. Client Code 13 Only
CCBadlst Credit Card Hotlist Yes Yes. No Export from EEE. Imported via credta.dat under Client Code 4
Club Customer Clubs Yes Yes - export Clubs from EEE
ClubDisc Discounts attached to Club Codes Yes Yes - export Customer Discounts from EEE
Clubmemb Customers who are members of clubs Yes Yes - export Club Membership from EEE
Colprofc Product categorisation - Colour Profiles Yes Yes - export Colour Profile Colours and Colour Profiles from EEE
Colrprof Product categorisation - Colour Profiles Yes Yes - export Colour Profile Colours and Colour Profiles from EEE
Coupon *UNUSED* Yes replace from upgbase
Custcard Customer Loyalty Card numbers Yes Yes - export Customer Cards from EEE
Custcat Customer Category Master File Yes Yes - export Customer Category Maintenance from EEE
Custdisc Customer Discounts Yes Yes - export Customer Discounts from EEE
Custext Used by Customer Marketing Tool to hold results Yes Yes.  N/A
Filmid Film ID Table (PhotoPro Only) Yes Yes.  No Export from EEE. Imported via ISL-FILM.DAT
Forwardp Forward dated price changes Yes Yes - export Forward Price Change from EEE
Groupdis Customer Category Discounts Yes Yes - export Customer Discounts from EEE
Histdump Holds Results for Sales History in Reports Menu Not Reqd replace from upgbase
Hoipcbs Summary data created with the running of Head Office price changes by style report Not Reqd replace from upgbase
Invhold Temp table used by ISLINV.DAT import process Not Reqd replace from upgbase
Journal Temp table used by journal viewer Not Reqd replace from upgbase
Kit Product Kits and their components Yes Yes - export Kit Components from EEE
Ldexport Temp table used for exporting Layby snapshot to EEE Not Reqd replace from upgbase
Lhexport Temp table used for exporting Layby snapshot to EEE Not Reqd replace from upgbase
Liexport Temp table used for exporting Layby snapshot to EEE Not Reqd replace from upgbase
Location Stock Location Bins Yes Yes - export Stock Location (Bins) from EEE
Ltexport Temp table used for exporting Layby snapshot to EEE Not Reqd replace from upgbase
Mmaintbk Temp table used for creating local\mmaintlg.dbf if missing Not Reqd replace from upgbase
Mmaintlg Log file of possibly missing maintenance messages NO!! Yes if the file is empty. The size is 674 bytes when empty.
Nlog Log file used by nibbler when processing messages to keep track of what it has updated in that message in case of a crash NO!! Can cause parts of a sale to be doubled if this file is deleted and half a sale had been processed before crashing
Nseqlog Log of Nibble sequence numbers already processed at this location. NO!! If replaced, can cause messages to be reprocessed and sales doubled if they are manually reprocessed from a tills nibbler backup file and they had already been processed.
Nuancelk Duty Free Lookup Tables Yes Yes.  export Nuance Maintenance from EEE (Client Code 20)
Odexport Temp table used for exporting Order snapshot to EEE Not Reqd replace from upgbase
Ohexport Temp table used for exporting Order snapshot to EEE Not Reqd replace from upgbase
Option Products configured for add-on sales Yes Yes - export Add On Sales from EEE
Otexport Temp table used for exporting Order snapshot to EEE Not Reqd replace from upgbase
Pallet Temp table used for Beacon Pallet Manifest Report Yes replace from upgbase
Pctmmnt Not Used Yes replace from upgbase
Plrlmnt Nibbler messages received from tills by server - waiting to be processed. NO!! Yes if the file is empty. The size is 674 bytes when empty.  Replacing would be a last resort. If replacing, keep a backup copy. The store server will hopefully detect the missing messages and request resends from the tills. See Note 1 at end
Plrmmnt Nibbler messages waiting to go from store server to tills. NO!! Yes if the file is empty. The size is 674 bytes when empty. If a non empty file is replaced, a full load from the server to ALL tills should be performed. See Note 1 at end
Posareas Absent Reason Codes. Used with Time Clock Yes Yes - export Absent Reasons from EEE
Posbarc Product Barcodes Yes Yes - export Barcodes from EEE
Posbin Credit Card bin ranges Yes Upgbase folder contains database with all the credit card bin ranges
Posbrand Product categorisation - Brand Yes Yes - export Brands from EEE
Poscat Product categorisation - Category Yes Yes - export Product Category from EEE
Posclass Product categorisation - Class Yes Yes - export Class from EEE
Poscolor Product categorisation - Colours Yes Yes - export Colours from EEE
Poscust Customers Yes Yes - export Customers from EEE
Posdates Financial Period Dates Yes
Posdbom Bill Of Materials Detail  Yes
Posdept Product categorisation - Department Yes Yes - export Department from EEE
Posdiv Product categorisation - Division Yes Yes - export Division from EEE
Posdreas Discount Reasons Yes Yes - export Discount Reasons from EEE
Posdsale Temp. table used in Sales History Query (contains final output) Not Reqd replace from upgbase
Posdskum Not Used Yes replace from upgbase
Posdten2 Summary table generated from reports in Enabler Not Reqd replace from upgbase
Poshbom Bill of Materials Header table Yes
Poslmnt Nibbler messages from till ready to go to servers lanmnt folder NO!! Yes if the file is empty. The size is 674 bytes when empty. Replace as a last resort and ensure a backup is retained. See Note 1 at end
Poslreas Selling Low Stock Item Reason Codes Yes
Posmrkup Markup Rules Yes
Posnreas Non Sale reason codes (Petty Cash) Yes Yes - export Payouts Reasons from EEE
Posparam Parameters for this till. Contains last transaction, layby, etc numbers. NO!! Can be replaced with bu-param.dbf (copy to posparam.dbf)
Pospav Product categorisation - Class->Pavilion Yes replace from upgbase
Pospcode Australian PostCodes Yes Magenta have a file for importing that contains the latest postcodes
Pospreas Repair reason codes Yes Yes - export Repair Reasons from EEE
Posprice Product pricing/Markdowns/DutyFree/etc Yes Yes - export Product or Price Maintenance from EEE
Posprod Product Database Yes Yes - export Products, Costs, Prices, MinMax from EEE
Posrdb Contains information relating to Enabler reports Yes Can also be copied from any other store on the same version
Posrdbp Contains information relating to Client specific reports Yes Can also be copied from any other store on the same version
Posrdbu Defines which user/class can run each report Yes
Posround Price Rounding Rules Yes replace from upgbase
Posrreas Return Reasons Yes Yes - export Return Reasons from EEE
Posseas Product categorisation - Brand Yes Yes - export Seasons from EEE
Possize Product categorisation - Sizes Yes Yes - export Sizes from EEE
Possreas Stocktake Adjustment Reason Codes Yes Yes - export Stock Adjustment Reasons from EEE
Posssal2 Summary table generated from reports in Enabler Not Reqd replace from upgbase
Posstyle Product categorisation - Styles Yes Yes - export Styles from EEE
Possupp Product suppliers Yes Yes - export Suppliers from EEE
Postaxes Tax Rates
Postend Tender codes (CASH, EFT, etc) Yes Yes - export Tenders from EEE
Posureas Discount Sub-Reasons Yes Yes - export Discount Sub-Reason from EEE
Posuser Users Yes Yes - export Users from EEE. If users are not maintained in EEE, branch load of Users can be performed from Enabler HO
Posuserc User Classes Yes Yes - export User Classes from EEE. If users are not maintained in EEE, branch load of Users can be performed from Enabler HO
Posvreas Tender variance reason codes - balancing Yes Yes - export Variance Reasons from EEE
Poszone Product categorisation - Class->Pavilion->Zone Yes replace from upgbase
Powork Temp. Table used when importing P/O's Yes replace from upgbase
Ppmember Priority Parternship Number Not Reqd Yes. Client Code 1 Only (No longer Used)
Ppprod Priority Parternship Number Not Reqd Yes. Client Code 1 Only (No longer Used)
Pricemnt Product price change history
Prodanal Summary table generated from reports in Enabler Not Reqd replace from upgbase
Prodanl2 Summary table generated from reports in Enabler Not Reqd replace from upgbase
Prodfabr Not Used Yes replace from upgbase
Prodfram Not Used Yes replace from upgbase
Prodkey Used for Product searching Yes Gets re-generated if database blank
Prodsrch Used for Product searching
Promot Promotion Header Yes Yes - export Promotion Header from EEE
Promotc Promotion Exceptions by Customer Yes Yes - export Promotion Customer from EEE
Promotd Promotion Details Yes Yes - export Promotion Details from EEE
Promotx Promotion Exceptions Yes Yes - export Promotion Exceptions from EEE
qbrowse Temp. Table used for display HO Query results in a browse Not Reqd Yes
qbrowse2 Temp. Table used for display HO Query results in a browse Not Reqd yes
Range Product Range file. Not normally used. Yes Yes - export Products from EEE. Posprod will be updated also
Regen Not Used Yes replace from upgbase
Region Region Codes. All branches linked to a region Yes Yes - export Regions from EEE
Rptstkm Summary table generated from reports in Enabler Not Reqd replace from upgbase
Sales Summary table of sales data used by quick sales reports/menus No
Salesum2 Summary table generated from reports in Enabler Not Reqd replace from upgbase
Shiftsm Summary table generated from reports in Enabler Not Reqd replace from upgbase
Sizeprof Product categorisation - Size Profiles Yes Yes - export Size Profile from EEE
Sizprofs Product categorisation - Size Profile Sizes Yes Yes - export Size Profile Sizes from EEE
Stakedock Temp. Table used when reprinting PDT stocktake dockets & Enabler Monile in use Not Reqd replace from upgbase
Stkqury Temp. table used in Sales History Query Not Reqd replace from upgbase
Suppcpn Supplier Continuing Permissions Number Yes Yes - export CPN Supplier Maintenance
Tmpcpo Temp. table used by some CPO functions Not Reqd replace from upgbase
Tmpophst Temp. table used in generating data for Order Payment History Report Not Reqd replace from upgbase
Tmppurcd Temp. table used when receiving against a P/O Not Reqd replace from upgbase
Tmpseal Temp. table used for display seal history from balancing screens   Not Reqd replace from upgbase
Tour Tour Codes Yes Yes.  No Export from EEE. Imported via JC, Deleted by JD records.
Tours Tour Operators Yes Yes.  No Export from EEE. Imported via oC, Deleted by oD records.
Trandump Temp. table used in generating data for Transaction Detail Dump Report Not Reqd replace from upgbase
Trgt2rpt Summary table generated from reports in Enabler Not Reqd replace from upgbase
Trgtrpt Summary table generated from reports in Enabler Not Reqd replace from upgbase
Trnlmnt Nibbler maintenance messages saved from POS NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Trnlmnt2 Alternate file to hold nibbler maintenance messages saved from POS when local\poslmnt.dbf busy NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Trnlmnta Alternate file to hold nibbler maintenance messages saved from POS when local\trnlmnt.dbf busy NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Trnlmntb Alternate file to hold nibbler maintenance messages saved from POS when local\trnlmnt.dbf busy NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Trnlmntc Alternate file to hold nibbler maintenance messages saved from POS when local\trnlmnt.dbf busy NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Trnlmntd Alternate file to hold nibbler maintenance messages saved from POS when local\trnlmnt.dbf busy NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Trnlmnte Alternate file to hold nibbler maintenance messages saved from POS when local\trnlmnt.dbf busy NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Trnlmntf Alternate file to hold nibbler maintenance messages saved from POS when local\trnlmnt.dbf busy NO!! If this is replaced and the original is NOT empty (not 674 bytes), any sales in this file will be lost. Replace only as a last resort and ensure a backup of the existing file is retained. See Note 1 at end
Tsdef Touch Screen Definition Yes
Tstkqury Temp. table used in Sales History Query Not Reqd replace from upgbase
Usranl4 Temp. table used in generating data for Pagani Sales Person Report Not Reqd replace from upgbase
Usrsum Temp. table used in generating data for User Summary Report Not Reqd replace from upgbase
Wslog Internal table used in debugging versions only Not Reqd N/A
RRBBTTb Backup Nibbler file for this till NO!! Auto purged based on configuration settings. If this file is replaced, nibbler messages cannot be re-sent upstream when upstream nibble detects missing messages and requests a resend
NOTE 1 When any files are replaced that contain transactions ebing sent from tills to server, e.g. plrmmnt.dbf, plrlmnt.dbf poslmnt.dbf and trn*mnt.dbf,  backups should always be retained and reports and bank balancing carefully checked to determine if any data loss has occured. In the event of data loss, contact Magenta Retail for advice. It is highly recommended that Magenta Retail is contacted for advice prior to replacing any files.