Run Ticket Reconciliation - Revision history

Cody Gallagher at 17:55, 19 December 2019

2019-12-19T17:55:13Z

Cody Gallagher at 17:55, 19 December 2019

2019-12-19T17:55:01Z

Cody Gallagher at 21:15, 23 August 2019

2019-08-23T21:15:30Z

Cody Gallagher at 19:03, 14 June 2019

2019-06-14T19:03:11Z

Cody Gallagher at 18:39, 14 June 2019

2019-06-14T18:39:45Z

Cody Gallagher at 18:31, 14 June 2019

2019-06-14T18:31:25Z

Cody Gallagher: Created page with "With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low..."

2019-06-14T14:18:19Z

Created page with "With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low..."

New page

With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low variances depending on the threshold set.
----

← Older revision		Revision as of 17:55, 19 December 2019
Line 15:		Line 15:

	Select start import to continue.		Select start import to continue.
−

	===Purchaser Check===		===Purchaser Check===

@@ Line 1: / Line 1: @@
-[[File:Under Construction.png|center|frame|This page is currently under construction. Information displayed may not be 100% accurate.]]
+[[File:Under Construction.png|right|frame|This page is currently under construction. Information displayed may not be 100% accurate.]]
 With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low variances depending on the threshold set.
@@ Line 47: / Line 47: @@
 The tickets that have a match with little to no variance will be displayed at the bottom showing that nothing needs to be done on them.

← Older revision		Revision as of 21:15, 23 August 2019
Line 1:		Line 1:
		+	[[File:Under Construction.png\|center\|frame\|This page is currently under construction. Information displayed may not be 100% accurate.]]
		+
	With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low variances depending on the threshold set.		With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low variances depending on the threshold set.
	----		----

@@ Line 22: / Line 22: @@
 This section will only look at tickets that have no purchaser associated with them. The tickets must have a valid purchaser or it will be excluded.
-After all site have the appropriate purchaser either Re-import or start the process over.
+After all tickets have the appropriate purchaser click next to save and continue.
 ===Ticket Errors and Variances===
 ----
-When all the purchasers have been filled out for each site then this will be the next screen after the import.
+If all purchasers have been filled out on each ticket you will arrive at this screen. If not this will be the next screen after purchasers have been set up.
-This section will be the main part of the wizard showing any errors or variances that have occurred during the import.
+This section will be the main part of the wizard showing any errors or variances that have occurred during the import. All panels will be searchable using the icon.
-Errors displayed will be separated into two grids, PRAMS and Statement errors, that can be searched. The program will look for ticket '''''and tank ''''' numbers when searching for matches.
+Errors displayed will be separated into two grids, PRAMS Tickets Not Found In Statement and Statement Tickets Not Found In PRAMS.
 The PRAMS section will show any run ticket that does not have a match for the statement provided.
@@ Line 37: / Line 38: @@
 The Statement section will show any sites that do not have a match in the PRAMS database. An example could be a site that does not belong to the company.
 All errors must be addressed as it could result in them being excluded from the final summary causing a difference from what the actual total may be.
-The sites that have matching tickets and little to no variance will be displayed at the bottom showing that nothing needs to be done on them.
+The tickets that have a match with little to no variance will be displayed at the bottom showing that nothing needs to be done on them.

@@ Line 18: / Line 18: @@
 ----
-After continuing from the import screen and a purchaser is not found on a sites product for the period you will be directed to this screen.
+After continuing from the import screen and a purchaser is not found on a ticket for the period you will be directed to this screen.
-This section will only look at sites that have a run ticket for the period provided.
+This section will only look at tickets that have no purchaser associated with them. The tickets must have a valid purchaser or it will be excluded.
 After all site have the appropriate purchaser either Re-import or start the process over.

← Older revision		Revision as of 18:31, 14 June 2019
Line 1:		Line 1:
	With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low variances depending on the threshold set.		With this tool you will be able to import a purchaser statement directly into PRAMS. It will then automatically show how many run tickets are missing and show any high or low variances depending on the threshold set.
	----		----
		+
		+	===Import===
		+	----
		+	From Monthly Processes in the menu select the Run Ticket Reconciliation. This will bring you to the first screen of the wizard, the Import.
		+
		+	This screen will be the parameters needed to start the process. For Period select the month that will be affected.
		+
		+	The Purchaser can be selected from the drop-down menu. This process will have to be done multiple times per purchaser as it can only run one at a time.
		+
		+	Finally select the file from the browser and select open.
		+
		+	Select start import to continue.
		+
		+
		+	===Purchaser Check===
		+	----
		+
		+	After continuing from the import screen and a purchaser is not found on a sites product for the period you will be directed to this screen.
		+
		+	This section will only look at sites that have a run ticket for the period provided.
		+
		+	The sites and their products must have a valid purchaser in order to continue. Its recommended to pop this screen out using the controls at the top and fixing each error. You can also export this list to Excel or PDF.
		+
		+	After all site have the appropriate purchaser either Re-import or start the process over.
		+
		+	===Ticket Errors and Variances===
		+	----
		+
		+	When all the purchasers have been filled out for each site then this will be the next screen after the import.
		+
		+	This section will be the main part of the wizard showing any errors or variances that have occurred during the import.
		+
		+	Errors displayed will be separated into two grids, PRAMS and Statement errors, that can be searched. The program will look for ticket '''''and tank ''''' numbers when searching for matches.
		+
		+	The PRAMS section will show any run ticket that does not have a match for the statement provided.
		+
		+	The Statement section will show any sites that do not have a match in the PRAMS database. An example could be a site that does not belong to the company.
		+
		+	All errors must be addressed as it could result in them being excluded from the final summary causing a difference from what the actual total may be.
		+
		+
		+
		+	The sites that have matching tickets and little to no variance will be displayed at the bottom showing that nothing needs to be done on them.