Recover HostLog TranIDs - Revision history

Bevan at 05:40, 9 September 2015

2015-09-09T05:40:29Z

← Older revision		Revision as of 05:40, 9 September 2015
Line 30:		Line 30:

	Multi-row transactions such as goods receipts and transfers are unhandled - the TranIDs for these are created by EEE not POS so should not need recovery in the same way. However should the need arise, Magenta could extend this procedure to handle these using the same concepts as SH sale transactions.		Multi-row transactions such as goods receipts and transfers are unhandled - the TranIDs for these are created by EEE not POS so should not need recovery in the same way. However should the need arise, Magenta could extend this procedure to handle these using the same concepts as SH sale transactions.

			UPDATE: As of EEE version 1.76 SR-9 support for GH, XH, TH records and their children has been added.

Brant at 00:20, 9 September 2015

2015-09-09T00:20:33Z

← Older revision		Revision as of 00:20, 9 September 2015
Line 1:		Line 1:
	Created: 30 October 2013. Last Reviewed: ~~30 October 2013~~.		Created: 30 October 2013. Last Reviewed: 09 September 2015.


	Under some circumstances, it might become necessary to recover POS HostLog data processed via the EEE HostLogExportStaging tables if the original data was missing TranIDs. This could arise if a store server was mis-configured to not generate TranIds for a period of time and the ERP receiving data from HostLogExportStaging is dependent upon TranIds (this includes EEE .HOS file exporter if configured to use TranID validation).		Under some circumstances, it might become necessary to recover POS HostLog data processed via the EEE HostLogExportStaging tables if the original data was missing TranIDs. This could arise if a store server was mis-configured to not generate TranIds for a period of time and the ERP receiving data from HostLogExportStaging is dependent upon TranIds (this includes EEE .HOS file exporter if configured to use TranID validation).

	Should the need arise to recover POS HostLog data processed via the EEE HostLogExportStaging tables a stored procedure exists in EEE to assist.		Should the need arise to recover POS HostLog data processed via the EEE HostLogExportStaging tables a stored procedure exists in EEE to assist.

	~~create procedure usp_RecoverHostLog @branch TBranchCode, @datefrom datetime, @dateto datetime, @bRegenTranIdsOnly bit, @CopyBackToHostLogExportStaging bit~~ as		The parameters are as follows:

	You can execute ~~thus~~ to preview:		@branch TBranchCode
			@datefrom datetime
			@dateto datetime
			@bRegenTranIdsOnly bit
			@CopyBackToHostLogExportStaging bit

			You can execute the following to preview changes:
	exec usp_RecoverHostLog '723', '20131024', '20131024', 1, 0		exec usp_RecoverHostLog '723', '20131024', '20131024', 1, 0

	and ~~thus~~ to actually recover the data:		and to actually recover the data:
	exec usp_RecoverHostLog '723', '20131024', '20131024', 1, 1		exec usp_RecoverHostLog '723', '20131024', '20131024', 1, 1

Bevan at 23:18, 29 October 2013

2013-10-29T23:18:45Z

← Older revision		Revision as of 23:18, 29 October 2013
Line 21:		Line 21:
	rollback OR commit as appropriate		rollback OR commit as appropriate

	This proc should take care of recovering TranIds for SH and related records only - as well as miscellaneous / stand alone record types TS, VR, DS, BS, TV. It deliberately excludes EV, VI, HB as no likely ERP interface implementation would require these record types. There are other unhandled, miscellaneous record types - hence the preview mode which will reveal if records with unrecovered TranIDs - case by case assessment would be necessary to determine if further steps are required to ~~recovery~~ extra record types not handled by this procedure.		This proc should take care of recovering TranIds for SH and related records only - as well as miscellaneous / stand alone record types TS, VR, DS, BS, TV. It deliberately excludes EV, VI, HB as no likely ERP interface implementation would require these record types. There are other unhandled, miscellaneous record types - hence the preview mode which will reveal if there are other records with unrecovered TranIDs - case by case assessment would be necessary to determine if further steps are required to recover extra record types not handled by this procedure.

	Multi-row transactions such as goods receipts and transfers are unhandled - the TranIDs for these are created by EEE not POS so should not need recovery in the same way. However should the need arise, Magenta could extend this procedure to handle these using the same concepts as SH sale transactions.		Multi-row transactions such as goods receipts and transfers are unhandled - the TranIDs for these are created by EEE not POS so should not need recovery in the same way. However should the need arise, Magenta could extend this procedure to handle these using the same concepts as SH sale transactions.

Bevan: Created page with "Created: 30 October 2013. Last Reviewed: 30 October 2013. Under some circumstances, it might become necessary to recover POS HostLog data processed via the EEE HostLogExportS..."

2013-10-29T23:16:59Z

Created page with "Created: 30 October 2013. Last Reviewed: 30 October 2013. Under some circumstances, it might become necessary to recover POS HostLog data processed via the EEE HostLogExportS..."

New page

Created: 30 October 2013. Last Reviewed: 30 October 2013.

Under some circumstances, it might become necessary to recover POS HostLog data processed via the EEE HostLogExportStaging tables if the original data was missing TranIDs. This could arise if a store server was mis-configured to not generate TranIds for a period of time and the ERP receiving data from HostLogExportStaging is dependent upon TranIds (this includes EEE .HOS file exporter if configured to use TranID validation).

Should the need arise to recover POS HostLog data processed via the EEE HostLogExportStaging tables a stored procedure exists in EEE to assist.

create procedure usp_RecoverHostLog @branch TBranchCode, @datefrom datetime, @dateto datetime, @bRegenTranIdsOnly bit, @CopyBackToHostLogExportStaging bit as

You can execute thus to preview:
exec usp_RecoverHostLog '723', '20131024', '20131024', 1, 0

and thus to actually recover the data:
exec usp_RecoverHostLog '723', '20131024', '20131024', 1, 1

or better:
select * from HostLogExportStaging
begin tran
exec usp_RecoverHostLog '723', '20131024', '20131024', 1, 1
select * from HostLogExportStaging
rollback OR commit as appropriate

This proc should take care of recovering TranIds for SH and related records only - as well as miscellaneous / stand alone record types TS, VR, DS, BS, TV. It deliberately excludes EV, VI, HB as no likely ERP interface implementation would require these record types. There are other unhandled, miscellaneous record types - hence the preview mode which will reveal if records with unrecovered TranIDs - case by case assessment would be necessary to determine if further steps are required to recovery extra record types not handled by this procedure.

Multi-row transactions such as goods receipts and transfers are unhandled - the TranIDs for these are created by EEE not POS so should not need recovery in the same way. However should the need arise, Magenta could extend this procedure to handle these using the same concepts as SH sale transactions.