280855 - Revision history

DuttonT: /* Functional Description */

2011-05-13T09:21:00Z

Functional Description

← Older revision		Revision as of 11:21, 13 May 2011
Line 56:		Line 56:
	== Data ==		== Data ==
	= Functional Description =		= Functional Description =

	'''3.1 Generate All Invoices'''		'''3.1 Generate All Invoices'''


	[[Image:280855_1.png]]		[[Image:280855_1.png]]


	Currently, when the user selects GENERATE, they are then prompted for the Debit and Credit accounts to generate the Invoices for. Once they have entered the Debit and Credit account, the system finds all Actualised payments for the Credit and Debit accounts where the revenue date is less than today, which have not yet been allocated to an invoice and generates a new invoice.		Currently, when the user selects GENERATE, they are then prompted for the Debit and Credit accounts to generate the Invoices for. Once they have entered the Debit and Credit account, the system finds all Actualised payments for the Credit and Debit accounts where the revenue date is less than today, which have not yet been allocated to an invoice and generates a new invoice.


	An additional button will be added called Generate Weekly Invoices. When this is selected, the user will not be prompted for a Debit and Credit account. The system will look for all actualised payments on the system within the revenue date, which have not been allocated to an invoice and the credit account has a GENERATION_METHOD of G. This will provide a list of Credit Accounts and the Generate Invoice code will automatically run for each Credit account in the list until all the Invoices have been generated.		An additional button will be added called Generate Weekly Invoices. When this is selected, the user will not be prompted for a Debit and Credit account. The system will look for all actualised payments on the system within the revenue date, which have not been allocated to an invoice and the credit account has a GENERATION_METHOD of G. This will provide a list of Credit Accounts and the Generate Invoice code will automatically run for each Credit account in the list until all the Invoices have been generated.


	Once the Generate Weekly Invoices has completed, the screen will be updated to display all of the Draft Invoices which have been generated.		Once the Generate Weekly Invoices has completed, the screen will be updated to display all of the Draft Invoices which have been generated.


	'''3.2 Approve All Invoices'''		'''3.2 Approve All Invoices'''


	[[Image:280855_2.png]]		[[Image:280855_2.png]]


	Currently in the system, the user highlights an invoice line and right clicks to Set the Status. A new menu item will be added to the Set Status menu called APPROVE ALL. When this menu item is selected, the system will find all Draft invoices in the system within the last 2 months and attempt to set the status to Approved. If the approval of an invoice fails, the system will continue with the next invoice.		Currently in the system, the user highlights an invoice line and right clicks to Set the Status. A new menu item will be added to the Set Status menu called APPROVE ALL. When this menu item is selected, the system will find all Draft invoices in the system within the last 2 months and attempt to set the status to Approved. If the approval of an invoice fails, the system will continue with the next invoice.


	'''3.3 Print All Invoices'''		'''3.3 Print All Invoices'''


	[[Image:280855_3.png]]		[[Image:280855_3.png]]


	Currently, a user selects an invoice and right clicks Print and Invoice. This will display the Reports screen, where the user selects print to display the invoice on screen. A new item will be added to the PRINT menu called PRINT ALL.		Currently, a user selects an invoice and right clicks Print and Invoice. This will display the Reports screen, where the user selects print to display the invoice on screen. A new item will be added to the PRINT menu called PRINT ALL.


	Code will run to select all invoices which have been generated but not yet printed. Rather than display the Reports screen and rely on the user to select print, the print code will be called directly, which will generate the Invoice Report as a PDF file for each Invoice selected.		Code will run to select all invoices which have been generated but not yet printed. Rather than display the Reports screen and rely on the user to select print, the print code will be called directly, which will generate the Invoice Report as a PDF file for each Invoice selected.


	Each Invoice will generate a separate pdf on the application server. The files will be generated with the customer name and current date and time as the file name. The destination of the pdf files will be controlled using the existing web server and pdf system parameters.		Each Invoice will generate a separate pdf on the application server. The files will be generated with the customer name and current date and time as the file name. The destination of the pdf files will be controlled using the existing web server and pdf system parameters.


	A new package will be created to write to the server using the UTIL_HOST_CMD to zip all the PDF files into one folder. The procedure AS_TO_CLIENT within the WEBUTIL_FILE_TRANSFER package will be used to move the zipped folder onto the users pc. Once this has been successfully completed, the PDF files will be removed from the server.		A new package will be created to write to the server using the UTIL_HOST_CMD to zip all the PDF files into one folder. The procedure AS_TO_CLIENT within the WEBUTIL_FILE_TRANSFER package will be used to move the zipped folder onto the users pc. Once this has been successfully completed, the PDF files will be removed from the server.


	The following parameters must be set in the WEBUTIL.CFG		The following parameters must be set in the WEBUTIL.CFG


	transfer.database.enabled=TRUEtransfer.appsrv.enabled=TRUEtransfer.appsrv.workAreaRoot=c:\temptransfer.appsrv.accessControl=TRUE<nowiki>#Listtransfer.appsrv.read.<n>directories</nowiki>transfer.appsrv.read.1=c:\temp<nowiki>#Listtransfer.appsrv.write.<n>directories</nowiki>transfer.appsrv.write.1=c:\temp		transfer.database.enabled=TRUEtransfer.appsrv.enabled=TRUEtransfer.appsrv.workAreaRoot=c:\temptransfer.appsrv.accessControl=TRUE<nowiki>#Listtransfer.appsrv.read.<n>directories</nowiki>transfer.appsrv.read.1=c:\temp<nowiki>#Listtransfer.appsrv.write.<n>directories</nowiki>transfer.appsrv.write.1=c:\temp

	'''		'''Table Updates Required'''
	Table Updates Required'''

DuttonT: /* Solution */

2011-05-13T09:20:13Z

Solution

DuttonT: /* Functional Description */

2011-05-13T09:19:30Z

Functional Description

← Older revision		Revision as of 11:19, 13 May 2011
Line 136:		Line 136:

	\|-		\|-

	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|
	~~\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|~~
	~~\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|~~
	\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|

DuttonT: /* Functional Description */

2011-05-13T09:18:41Z

Functional Description

← Older revision		Revision as of 11:18, 13 May 2011
Line 136:		Line 136:

	\|-		\|-
	~~\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|~~
	~~\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|~~
	~~\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|~~
	\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|

	\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|
	\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|		\| style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|
Line 196:		Line 191:

	\|}		\|}


	=AUTHORISED BY=		=AUTHORISED BY=

DuttonT: /* Solution */

2011-05-13T09:17:05Z

Solution

← Older revision		Revision as of 11:17, 13 May 2011
Line 38:		Line 38:


	'''3)Print All Invoices'''		'''3) Print All Invoices'''


Line 59:		Line 59:

	Before each run, any exisiting PDF and ZIP files will be removed.		Before each run, any exisiting PDF and ZIP files will be removed.


	== Scope ==		== Scope ==

DuttonT at 09:13, 13 May 2011

2011-05-13T09:13:34Z

Show changes

DuttonT: /* Client Requirement */

2011-05-13T08:52:01Z

Client Requirement

← Older revision		Revision as of 10:52, 13 May 2011
Line 4:		Line 4:

	== Client Requirement ==		== Client Requirement ==

	# At the end of the week, on demand from a button, generate all the invoices		# At the end of the week, on demand from a button, generate all the invoices

	## Approve all invoices at once or by exception		# Approve all invoices at once or by exception

	Then print all invoices and backing sheets at once or by exception. The print should create a PDF file to a folder on the users PC for each invoice and its backing sheet so perhaps 100 separate files on each run named using the supplier code and invoice number.		Then print all invoices and backing sheets at once or by exception. The print should create a PDF file to a folder on the users PC for each invoice and its backing sheet so perhaps 100 separate files on each run named using the supplier code and invoice number.

DuttonT: /* Client Requirement */

2011-05-13T08:51:47Z

Client Requirement

← Older revision		Revision as of 10:51, 13 May 2011
Line 6:		Line 6:
	# At the end of the week, on demand from a button, generate all the invoices		# At the end of the week, on demand from a button, generate all the invoices

	# Approve all invoices at once or by exception		## Approve all invoices at once or by exception

	Then print all invoices and backing sheets at once or by exception. The print should create a PDF file to a folder on the users PC for each invoice and its backing sheet so perhaps 100 separate files on each run named using the supplier code and invoice number.		Then print all invoices and backing sheets at once or by exception. The print should create a PDF file to a folder on the users PC for each invoice and its backing sheet so perhaps 100 separate files on each run named using the supplier code and invoice number.


	== Solution ==		== Solution ==

DuttonT: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Invoice Generation CR020|Reference=280855 AS-882D8G |Version=0.1|Date=|Sysver=10.6|Client=DHL MTS}} == Client Requirement == # At the e...

2011-05-13T08:51:20Z

New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Invoice Generation CR020|Reference=280855 AS-882D8G |Version=0.1|Date=|Sysver=10.6|Client=DHL MTS}} == Client Requirement == # At the e...

Show changes

← Older revision		Revision as of 11:20, 13 May 2011
Line 13:		Line 13:
	== Solution ==		== Solution ==
	'''1 ) Generate All Invoices'''		'''1 ) Generate All Invoices'''


	Create a new button on the invoice screen called GENERATE WEEKLY INVOICES.		Create a new button on the invoice screen called GENERATE WEEKLY INVOICES.


	Currently when selecting the GENERATE button, the user is taken to a pop up screen where they are prompted to select a debit and credit account. Selecting the Generate Weekly invoices will run the generate invoice code for every customer account where the Generation method = ‘G’.		Currently when selecting the GENERATE button, the user is taken to a pop up screen where they are prompted to select a debit and credit account. Selecting the Generate Weekly invoices will run the generate invoice code for every customer account where the Generation method = ‘G’.


	If the generation fails at any point the appropriate error message will be displayed on screen and once acknowledged the generation process continues.		If the generation fails at any point the appropriate error message will be displayed on screen and once acknowledged the generation process continues.


	'''2) Approve All Invoices'''		'''2) Approve All Invoices'''


	Within the Invoice screen, add a new menu item to the set status menu called Approve ALL.		Within the Invoice screen, add a new menu item to the set status menu called Approve ALL.


	A query will be run which selects all DRAFT invoices where the invoice date is within the last two months.		A query will be run which selects all DRAFT invoices where the invoice date is within the last two months.

	Each invoice id will then be passed to the existing code where they will be approved individually.		Each invoice id will then be passed to the existing code where they will be approved individually.


	Currently when the status setting fails, the error is displayed to screen. To allow all invoices to be approved, any errors will be displayed on screen and once the error is acknowledged, the process will continue until all orders have been processed.		Currently when the status setting fails, the error is displayed to screen. To allow all invoices to be approved, any errors will be displayed on screen and once the error is acknowledged, the process will continue until all orders have been processed.


	'''3) Print All Invoices'''		'''3) Print All Invoices'''


	A new menu item will be added to the PRINT MENU called PRINT ALL. When selected the invoice report will run for each invoice generated but not yet printed. Currently, when a user selects to print an invoice, they are directed to the REPORTS screen where they select print and the invoice is displayed in a new browser window.		A new menu item will be added to the PRINT MENU called PRINT ALL. When selected the invoice report will run for each invoice generated but not yet printed. Currently, when a user selects to print an invoice, they are directed to the REPORTS screen where they select print and the invoice is displayed in a new browser window.


	When selecting the PRINT ALL functionality, the REPORTS screen will not be displayed. A cursor will be created to identify the invoices to be printed. Report parameters will be set as required and rather than WEB.SHOW_DOCUMENT which displays the report in a new browser window, RUN_REPORT_OBJECT will be called to generate each PDF file.		When selecting the PRINT ALL functionality, the REPORTS screen will not be displayed. A cursor will be created to identify the invoices to be printed. Report parameters will be set as required and rather than WEB.SHOW_DOCUMENT which displays the report in a new browser window, RUN_REPORT_OBJECT will be called to generate each PDF file.


	The files will be generated with the customer name and the current date and time. The system parameters		The files will be generated with the customer name and the current date and time. The system parameters

	REP_WEB_SERVER_NAME, REP_WEB_SERVER_URL, REP_PDF_DEST_FILEPATH will be used to determine where the pdf files are stored.		REP_WEB_SERVER_NAME, REP_WEB_SERVER_URL, REP_PDF_DEST_FILEPATH will be used to determine where the pdf files are stored.


	Once the generation of the pdf files is completed, the Host command procedure of the UTL package will be used to zip the pdf files .		Once the generation of the pdf files is completed, the Host command procedure of the UTL package will be used to zip the pdf files .


	The procedure AS_TO_CLIENT within the WEBUTIL_FILE_TRANSFER package of the WEBUTIL library will be called to transfer the zipped file from the application server to the users PC.		The procedure AS_TO_CLIENT within the WEBUTIL_FILE_TRANSFER package of the WEBUTIL library will be called to transfer the zipped file from the application server to the users PC.


	Before each run, any exisiting PDF and ZIP files will be removed.		Before each run, any exisiting PDF and ZIP files will be removed.