Developer Testing
Confirmation of Standards Adherence
Activity | Date Tested | Notes |
N/A | Application has no user interface | |
N/A |
| |
N/A |
|
Note
There are three applications in this project:
- process Purchase Orders from Sciquest (sciquestPOs)
- process Goods Receipts from Sciquest (sciquestGRs)
- send financial Codes and User Combinations to Sciquest (sqimport)
1 Process Purchase Orders from Sciquest
How to run the sciquestPOs application
The application resides on fin-app-kb1d.is.ed.ac.uk in the efin unix account.
Log in as efin and go to /u01/software/finance/sciquest/sciquestPOs.
(Use only the provided scripts to compile or run the application - otherwise the wrong version of java will be used and the application will fail.)
Run the application by executing the script run_sciquestPOs.sh with the appropriate argument. Acceptable arguments are as follows:
| arg | meaning |
| "full_run" | Collect unprocessed purchase orders from the sqstage schema and process them. |
| "manual_with_dataloaded" | Process the purchase orders that are currently in the load tables in the sciquest schema. This should only be used if the previous run failed BEFORE it could transfer the data to the efin schema. |
The arguments are case-insensitive. The double quotes are unnecessary.
Run the application like this:
>./run_sciquestPOs.sh FULL_RUN
If any changes are made to application.properties (for example, changing email addresses), re-package the application using
>./compile.sh
These scripts MUST be used, in order to ensure the correct versions of java and maven are set.
Developer Tests and Outcomes - SciquestPOs
| Test | Outcome |
Run with valid arguments: "FULL_RUN" "MANUAL_WITH_DATALOADED" | The process should run to completion. |
Run with invalid arguments: "bananas" And with no arguments | Error detected, process stops, email sent out. |
Check the value in the table sciquest_processed_pos. Run the process with the full_run argument. | Only POs with a higher ID number than that in sciquest_processed_pos should be retrieved from the sqstage schema. The sciquest_processed_pos table should be updated with the highest ID number of the POs retrieved. Purchase units are updated to values in the efin.units table, if necessary. If a PO has no purchase lines, or if a PO has revision number = 0 and it is already in the clink_purchase_orders table, the PO is copied to the sciquest_error_ tables and removed from the load tables. The description in each purchase line in the xml is split into shorter lines and written to the sciquest_pl_hf and clink_pl_header_footer tables. Valid POs are written to the efin clink tables (clink_purchase_orders, clink_purchase_lines and clink_pl_header_footer). POs with a revision number of 0 are treated as New POs (efin.clink_purchase_orders = N). Those with a revision number higher than 0 are treated as Amended POs (efin.clink_purchase_orders = A). If there is more than one revision of the same PO at the same time, they should be processed in order so that the most recent revision is the one that is transferred to the purchase_orders table (if it is postable). |
| Archiving | The raw xml messages of POs that were processed should be written to files in the directory /u01/software/finance/sciquest/archive. If the archive sub-directory does not exist, the application should create it. |
| Deleting old archived files | Files older than the retention period should be deleted from the archive directory. |
| Deleting old log and error records | Records older than the retention period should be deleted from the log table sciquest_log_po and the error tables sciquest_error_po, sciquest_error_pl and sciquest_error_pl_hf. |
| Emails | An email is sent out listing any data errors and summarising all the New POs that were processed and all the Amended POs that were processed. The report generated by the pop_r47 routine should be attached to the email. |
| When there are no POs to process | An email should be sent saying that there were no POs. |
2. Process Goods Receipts from SciQuest
How to run the sciquestGRs application
The application resides on fin-app-kb1d.is.ed.ac.uk in the efin unix account.
Log in as efin and go to /u01/software/finance/sciquest/sciquestGRs.
(Use only the provided scripts to compile or run the application - otherwise the wrong version of java will be used and the application will fail.)
Run the application by executing the script run_sciquestGRs.sh with the appropriate argument. Acceptable arguments are as follows:
| arg | meaning |
| "full_run" | Collect unprocessed goods receipts from the sqstage schema and process them. |
| "manual_with_dataloaded" | Process the goods receipts that are currently in the load tables in the sciquest schema. This should only be used if the previous run failed BEFORE it could transfer the data to the efin schema. |
The arguments are case-insensitive. The double quotes are unnecessary.
Run the application like this:
>./run_sciquestGRs.sh FULL_RUN
If any changes are made to application.properties (for example, changing email addresses), re-package the application using
>./compile.sh
These scripts MUST be used, in order to ensure the correct versions of java and maven are set.
| Test | Outcome |
|---|---|
Run with valid arguments: "FULL_RUN" "MANUAL_WITH_DATALOADED" | The process should run to completion. |
Run with invalid arguments: "bananas" And with no arguments | Error detected, process stops, email sent out. |
Check the value in the table sciquest_processed_grs. Run the process with the full_run argument. | Only goods receipts with a higher ID number than that in sciquest_processed_grs should be retrieved from the sqstage schema. The sciquest_processed_grs table should be updated with the highest ID number of the goods receipts retrieved. Purchase units are updated to values in the efin.units table, if necessary. If a goods receipt is invalid it is copied to the sciquest_error_ tables and removed from the load tables. Errors include: - a goods receipt that has no receipt lines - more than one purchase order is indicated in the lines of a single goods receipt - more than one supplier is indicated in the lines of a single goods receipt - the trans_type is neither "OG" nor "OR" (OG = receipt, OR = return) If a receipt contains both received goods and returned goods, a new goods receipt will be created for the returns. The suffix "_rtn" will be appended to the source number of the new goods receipt. Valid goods receipts are written to the efin clink tables (clink_goods_receipts and clink_grn_lines). |
| Archiving | The raw xml messages of goods receipts that were processed should be written to files in the directory /u01/software/finance/sciquest/archive. If the archive sub-directory does not exist, the application should create it. |
| Saffron | Goods receipts and returns within the load that were for the supplier Bunzl (supplier code 16771I) and were received by Accommodation Services departments (identified by 'ACS_' prefix) should be earmarked for copying to the Saffron server. The Saffron data should be written to two separate csv files, one containing receipt data and the other containing returns. The csv files should be transferred to Saffron by sftp. In Dev and Test they should be transferred to the /Test/ directory on the remote Saffron server. The csv files intended for Saffron should also be copied to the local archive directory. |
| Deleting old archived files | Files older than the retention period should be deleted from the archive directory. |
| Deleting old log and error records | Records older than the retention period should be deleted from the log table sciquest_log_gr and the error tables sciquest_error_gr sciquest_error_gl. |
| An email is sent out listing any data errors and summarising all the goods receipts and returns that were processed. The report generated by the pop_r59 routine should be attached to the email. | |
| When there are no goods receipts to process | An email should be sent saying that there were no goods receipts. |
.