Enabler History Purging - Revision history

Trevor at 05:42, 20 June 2012

2012-06-20T05:42:08Z

← Older revision		Revision as of 05:42, 20 June 2012
Line 1:		Line 1:
	Created: 29 April 2009. Last Reviewed: ~~29 April 2009~~		Created: 29 April 2009. Last Reviewed: 20 June 2012

	== History Purging ==		== History Purging ==
Line 20:		Line 20:
	'''Purge customer file (Temporary customer records)'''		'''Purge customer file (Temporary customer records)'''

	- Always purges LOCAL database. - If “Purge all customers” is not on, then only customer records with the poscust.cu_temp flag set to true are candidates for deletion.- If “Purge all customers” IS on, then all customer records are candidates for deletion.- Candidacy for deletion is further narrowed down based on whether an entry exists in the Layby/Customer Order header tables for this customer. If there is, the record is not a candidate for deletion – regardless of active status for that layby/order. i.e. a customer record will only be deleted if all layby/order records for the customer have also been purged.- poscust.cu_temp is set to true in the following conditions:Customer record retrieved from HO via Q/S and did not previously exist at storeCustomer record does not already exist, HO Q/S cannot be reached, and the customer is a valid Rockmans Fashion Account or Rockmans Reward Account card number (Rockmans Client Code 27)Customer record does not already exist, HO Q/S cannot be reached and a valid customer prefix was included with the card number (Country Road Client Code 4)'''Tables Purged: '''LOCAL\POSCUST.DBF		- Always purges LOCAL database. - If “Purge all customers” is not on, then only customer records with the poscust.cu_temp flag set to true are candidates for deletion.- If “Purge all customers” IS on, then all customer records are candidates for deletion.- Candidacy for deletion is further narrowed down based on whether an entry exists in the Layby/Customer Order header tables for this customer. If there is, the record is not a candidate for deletion – regardless of active status for that layby/order. i.e. a customer record will only be deleted if all layby/order records for the customer have also been purged.- poscust.cu_temp is set to true in the following conditions:Customer record retrieved from HO via Q/S and did not previously exist at storeCustomer record does not already exist, HO Q/S cannot be reached, and the customer is a valid Rockmans Fashion Account or Rockmans Reward Account card number (Rockmans Client Code)Customer record does not already exist, HO Q/S cannot be reached and a valid customer prefix was included with the card number (Country Road Client Code)'''Tables Purged: '''LOCAL\POSCUST.DBF

	'''Cascade deletes on poscust.cu_cust:'''LOCAL\custdisc.dbfLOCAL\clubmemb.dbfLOCAL\posprice.dbfLOCAL\clubpts.dbf		'''Cascade deletes on poscust.cu_cust:'''LOCAL\custdisc.dbfLOCAL\clubmemb.dbfLOCAL\posprice.dbfLOCAL\clubpts.dbf

Trevor at 07:07, 29 April 2009

2009-04-29T07:07:13Z

← Older revision		Revision as of 07:07, 29 April 2009
Line 295:		Line 295:
	== See Also ==		== See Also ==

	[[~~Disk_Maintenance_With_Enabler~~]]		[[Disk_Maintenance_with_Enabler]]

	[[EEE_History_Purging]]		[[EEE_History_Purging]]

Trevor at 07:06, 29 April 2009

2009-04-29T07:06:15Z

← Older revision		Revision as of 07:06, 29 April 2009
Line 295:		Line 295:
	== See Also ==		== See Also ==

	[[~~Disk_Maintenance_With Enabler~~]]		[[Disk_Maintenance_With_Enabler]]

	[[EEE_History_Purging]]		[[EEE_History_Purging]]

Trevor: /* See Also */

2009-04-29T07:05:07Z

Trevor at 07:03, 29 April 2009

2009-04-29T07:03:29Z

← Older revision		Revision as of 07:03, 29 April 2009
Line 6:		Line 6:
	'''Page 1'''		'''Page 1'''

	[[Image:]]		[[Image:Enabler_History_Purging_Figure_1.jpg]]

	'''Purge product file (if product purge flag is on and SOH=0)'''		'''Purge product file (if product purge flag is on and SOH=0)'''
Line 37:		Line 37:
	Flagging the options will include the transaction records in the purging process. Enter a time frame in days, to set the amount of data that is to be retained. The amount of data to be retained is a purely personal choice but keep in mind the impact on reporting performance and file sizes.  Data retention should be kept to a minimum and where EEE is installed historical data should be retained in EEE rather than Enabler wherever possible.- The underlying tables have a maximum size limitation of 2GB. So if any tables are approaching that threshold (e.g lantran\posdsale.dbf at HO), please review the amount of history you are keeping.		Flagging the options will include the transaction records in the purging process. Enter a time frame in days, to set the amount of data that is to be retained. The amount of data to be retained is a purely personal choice but keep in mind the impact on reporting performance and file sizes.  Data retention should be kept to a minimum and where EEE is installed historical data should be retained in EEE rather than Enabler wherever possible.- The underlying tables have a maximum size limitation of 2GB. So if any tables are approaching that threshold (e.g lantran\posdsale.dbf at HO), please review the amount of history you are keeping.

	[[Image:]]		[[Image:Enabler_History_Purging_Figure_2.jpg]]

	'''Purge Tender/banking records '''(Conditional on being a HO or Store Server)		'''Purge Tender/banking records '''(Conditional on being a HO or Store Server)
Line 147:		Line 147:

	== Page 3 ==		== Page 3 ==
	[[Image:]]		[[Image:Enabler_History_Purging_Figure_3.jpg]]

	'''Purged expired promotions and prices '''		'''Purged expired promotions and prices '''

Trevor: New page: Created: 29 April 2009. Last Reviewed: 29 April 2009 == History Purging == History Purging Setup is used to establish what information and transaction records are to be purged (removed) ...

2009-04-29T07:01:38Z

New page: Created: 29 April 2009. Last Reviewed: 29 April 2009 == History Purging == History Purging Setup is used to establish what information and transaction records are to be purged (removed) ...

New page

Created: 29 April 2009. Last Reviewed: 29 April 2009

== History Purging ==
History Purging Setup is used to establish what information and transaction records are to be purged (removed) from databases after set amount of days. This function must be configured to run on every till and server. If the options below are not tagged the system will retain all information in these options which could result in database errors when databases reach its maximum capacity.

'''Page 1'''

[[Image:]]

'''Purge product file (if product purge flag is on and SOH=0)'''

Switch on this flag to allow products to be purged from the system when the product record has “purge when no stock remains”. When enabler is configured as such the system checks the local inventory (unless using EEE for stock levels) when performing a Data purge and will purge (delete) product records that have a zero SOH level.

Also when purging SKU’s that are linked to a style code, the style record will also be deleted if there are no more SKUs existing in product database for that particular style.

- Always purges LOCAL database. - If using EEE stock levels, no local inventory level will be checked - in fact, no inventory level is checked. Refer the document “EEE History Purging” for details on purging in EEE.- If not using EEE stock levels, purges when SOH is LESS THAN OR EQUAL TO ZERO.'''Tables Purged: '''LOCAL\POSSTYLE.PDFLOCAL\POSPROD.DBF

'''Cascade deletes on posprod.pd_plu:'''LOCAL\posbarc.dbfLOCAL\posprice.dbfLOCAL\promotd.dbfLOCAL\promotx.dbfLOCAL\coupon.dbfLOCAL\inventry.dbfLOCAL\wac.dbfLOCAL\fifo.dbfLOCAL\prodkey.dbfLOCAL\kit.dbf

'''Purge customer file (Temporary customer records)'''

- Always purges LOCAL database. - If “Purge all customers” is not on, then only customer records with the poscust.cu_temp flag set to true are candidates for deletion.- If “Purge all customers” IS on, then all customer records are candidates for deletion.- Candidacy for deletion is further narrowed down based on whether an entry exists in the Layby/Customer Order header tables for this customer. If there is, the record is not a candidate for deletion – regardless of active status for that layby/order. i.e. a customer record will only be deleted if all layby/order records for the customer have also been purged.- poscust.cu_temp is set to true in the following conditions:Customer record retrieved from HO via Q/S and did not previously exist at storeCustomer record does not already exist, HO Q/S cannot be reached, and the customer is a valid Rockmans Fashion Account or Rockmans Reward Account card number (Rockmans Client Code 27)Customer record does not already exist, HO Q/S cannot be reached and a valid customer prefix was included with the card number (Country Road Client Code 4)'''Tables Purged: '''LOCAL\POSCUST.DBF

'''Cascade deletes on poscust.cu_cust:'''LOCAL\custdisc.dbfLOCAL\clubmemb.dbfLOCAL\posprice.dbfLOCAL\clubpts.dbf

'''Purge All customers '''

Delete all customers '''except '''those who have a layby/order associated (regardless of layby/order status) - See Above

'''Run Scan Disk and Re-index after purging data'''

This function will run a scan disk as part of the end of day process. The system will also automatically run a re-index. These processes will also run as part of the purging process.- If for whatever reason POS or BO are running during the data purge, the Disk Maintenance will be skipped.- The disk check is only designed to work on Windows 95/98. Only the reindex is performed for other O/S. Refer to the document “Disk Maintenance with Enabler” for details on running a disk maintenance batch file during Enabler EOD.

== Page 2 ==
Flagging the options will include the transaction records in the purging process. Enter a time frame in days, to set the amount of data that is to be retained. The amount of data to be retained is a purely personal choice but keep in mind the impact on reporting performance and file sizes.  Data retention should be kept to a minimum and where EEE is installed historical data should be retained in EEE rather than Enabler wherever possible.- The underlying tables have a maximum size limitation of 2GB. So if any tables are approaching that threshold (e.g lantran\posdsale.dbf at HO), please review the amount of history you are keeping.

[[Image:]]

'''Purge Tender/banking records '''(Conditional on being a HO or Store Server)

lantran\shift.dbf

lantran\ posstend.dbf

lantran\posdtend.dbf

lantran\poscash.dbf

lantran\posclear.dbf

lantran\seal.dbf

lantran\posfladj.dbf

'''Purge event log '''(Conditional on being a HO or Store Server)

lantran\posevent.dbf

'''Purge Customer History '''(Conditional on being a HO or Store Server)

lantran\custhist.dbf

'''Purge Journals '''(Conditional on being a HO or Store Server)

lantran\journal\*.jnl

'''Purge completed orders '''(Conditional on being a HO or Store Server)

lantran\orderh.dbf

'''Cascade deletes on orderh.oh_num:'''lantran\orderd.dbflantran\ordert.dbf

'''Purge Stock Ledger '''(Conditional on being a HO or Store Server)

lantran\stockled.dbflantran\grech.dbf

'''Purge completed laybys '''(Conditional on being a HO or Store Server)

lantran\laybyh.dbf

'''Cascade deletes on laybyh.lh_num:'''lantran\laybyd.dbf

lantran\laybyt.dbflantran\laybyi.dbf

'''Purge Sales '''

local\sales.dbf

These are conditional on being a HO or Store Server

lantran\poshsale.dbf

'''Cascade deletes on poshsale.sh_invno:'''

lantran\posdsale.dbflantran\posdisc.dbf

lantran\refunds.dbflantran\staffsl.dbflantran\target.dbf

lantran\ustarget.dbf

lantran\tsales.dbf

lantran\salecmnt.dbf

'''Purge nonsales '''(Conditional on being a HO or Store Server)

lantran\nonsllog.dbf

'''Purge sales summary '''(Conditional on being a HO or Store Server)

lantran\posssale.dbf

lantran\salesumm.dbf

'''Purge Suspended '''(Conditional on being a HO or Store Server)

lantran\susph.dbf

'''Cascade deletes on susph.sh_trannno:'''

lantran\suspd.dbf

lantran\suspi.dbf

lantran\suspn.dbf

'''Purge Franchisee Purchase Orders '''(Conditional on being a HO or Store Server)

lantran\pospurch.dbf

lantran\pospurcd.dbf- deletes all purchase orders for branches other than current branch, irrespective of status and date. This is unconditional!

== Page 3 ==
[[Image:]]

'''Purged expired promotions and prices '''

local\promot.dbf

'''Cascade deletes on promot.pn_code:'''

local\promotd.dbf

local\promotx.dbf

local\promotc.dbf

local\posprice.dbf

'''Purge nibbler files '''(We recommend retaining at least 7 days)

<nowiki>local\<rrbbtt>b.dbf</nowiki>

<nowiki>lanmnt\<rrbbtt>b.dbf</nowiki>

<nowiki>where <rrbbtt> is the nodes logical address.</nowiki>

These are conditional on being a HO or Store Server

<nowiki>lanmnt\<rrbb>back.dbf</nowiki>

<nowiki>where <rrbb> is the branches logical address</nowiki>

local\nseqlog.dbf

local\nlog.dbf

'''Purge completetd Xfer (Interstore Transfers) '''(Conditional on being a HO or Store Server)

lantran\poshpend.dbf

'''Cascade delete on poshpend.ph_xferno:'''

lantran\posdpend.dbf

'''Purge salelog (reprints and void prevoius) '''(Conditional on being a HO or Store Server)

lantran\salelogh.dbf

'''Cascade delete on salelogh.sh_tranno:'''

lantran\salelogd.dbf

lantran\salelogt.dbf

lantran\salelogn.dbf

'''Purge Price changes '''(Conditional on being a HO or Store Server)

lantran\pricechg.dbf

'''Purge completes P/O (Purchase Orders) '''(Conditional on being a HO or Store Server)

lantran\pospurch.dbf

'''Cascade delete on pospurch.po_num:'''

lantran\pospurcd.dbf

lantran\porderh.dbf

'''Cascade delete on porderh.ph_num:'''

lantran\porderl.dbf

lantran\porderd.dbf

'''Purge time and attendance records '''(Conditional on being a HO or Store Server)

lantran\tclock2.dbf

'''Purge expired vouchers '''(Conditional on being a HO or Store Server)

lantran\vouchreg.dbf

'''Purge GST history '''(Conditional on being a HO or Store Server)

lantran\taxhist.dbf

'''Purge completed drops '''(Conditional on being a HO or Store Server)

Purges from dropd based on date first and then unconditionally deletes records from droph that have no child records in dropd.

lantran\dropd.dbf

lantran\droph.dbf

'''Purge Redeemed vouchers '''(Conditional on being a HO or Store Server)

local\vouchreg.dbf

'''Purge Trade Ins '''(Conditional on being a HO or Store Server)

lantran\tradein.dbf

'''Purge Debtors Interface files '''(Conditional on being a HO or Store Server)

* Only used when “Enable Debtors Interface” is turned on in “Debtors Interface Setup” screen.
* Uses lantran\ifacelog.dbf and deletes matching *.syb files from the defined Debtors Inteface “Archive Path”, then deletes the entry from lantran\iface.log

'''Purge Repairs '''(Conditional on being a HO or Store Server)

lantran\repairs.dbf

'''OTHER'''

* Purges *.dbe in Enabler folder. Kept for 60 days.
* Purges *.err in Enabler folder. Kept for 60 days. HO/Store Server only.
* Purges *.err in defined LANMNT folder. Kept for 60 days. HO/Store Server Only
* Purges *.clg from Enabler folder. Kept for 60 days. (Hostlog Export Comms Logs)
* Purges *.eftlog from Enabler folder. Kept for 60 days. (Integrated EFT logging)
* Purges *.transavelog from Enabler folder. Kept for 60 days. (Transaction save logging)
* Purges *. Translogjnl from Enabler folder. Kept for 60 days. (Transaction Recovered Files)
* Purges *. Eftpospld from Enabler folder. Kept for 60 days. (Integrated EFT Recovered Files)
* Purges *.implog from Enabler folder. Kept for 60 days. (Import Index Drop/Table Zap logs)
* Purges *.prl from Enabler folder. Kept for 60 days (Beacon Pallet Receiving logs)
* Purges *.ctl from Enabler folder. Kept for 45 days. (Nibbler Client Thread log)
* Purges *.4gb from Enabler folder. Kept for 10 days. (Fix BDE 4GB error files)
* Purges *.resttem* from defined LOCAL folder.
* Purges *.resttem* from defined LANTRAN folder. HO/ Store Server Only
* Purges *.resttem* from defined LANMAST folder. HO/ Store Server Only and system is NOT using LOCAL database for LAN Master Files.
* Purges LANTRAN\laybytoEEE\archive\*.boz. Kept for 30 days. HO/Store Server Only & Q/S is turned ON.
* Purges LANTRAN\ordertoEEE\archive\*.boz. Kept for 30 days. HO/Store Server Only & Q/S is turned ON.

== See Also ==

← Older revision		Revision as of 07:05, 29 April 2009
Line 294:		Line 294:

	== See Also ==		== See Also ==

			[[Disk_Maintenance_With Enabler]]
			[[EEE_History_Purging]]