Kuali Cloud Internal test 1-AP, AR & Purchasing
Click "Edit" (above right) to make changes to this page. Click "Update" when done.
Accounts Receivable Processing eDoc | eDoc code | Comments | Assigned To | Notes | JIRA | Complete Y/N |
Billing Statement | On Hold - Not Ready for Testing | 6/7: Jira not assigned | FINUCONN-76 | |||
Cash Control | CTRL | search for CTRL, within CTRL search for Customer, and adding Cash Controls detail line. | Alex | Successfully created control and payment application docs, routed properly through workflow. Docs 12645946 and 12645947 | Y 4/4/23 | |
Customer Credit Memo | CRM | Stack trace error when trying to print a Customer Credit Memo. | Alex/Bruce | Entered new CRM, 12646253. Printed successfully. | FINUCONN-409 (compl) | Y 5/24/23 |
Customer Invoice | INV | Successfully created doc 12645922, but getting a stack trace error when trying to print the invoice. | Alex/Bruce | Retested Invoice 12645922, printed successfully. | FINUCONN-409 (compl) | Y 5/24/23 |
Customer Invoice recurrence | INV Low | No testing necessary - Don't use/won't be used requires entry of recurring invoice settings on the invoice, see current documentation. Not sure this was resolved from KFS-"7" upgrade (2020): was able to enter all info, but when submitted, the eDoc went to exception status. see error message in JIRA. 3/5/20 update: found that this issue is also present in 5.3 KFS Production. Also this issue is not present in Monsters. David and I believe this is likely a permission or workflow issue that is not specific to the upgrade. This still needs to be tested but may not be ready for the UAT. see KPS-1005 Also note that we are no longer using recurring invoices. | N/A | |||
Customer Invoice Writeoff | INVW | Successfully created doc 12645949, which routed to FO on account for approval. Pending entries correct, open amount on original invoice is $0.00. test as amp03015 | Alex | Y 4/4/23 | ||
Customer Invoice Writeoff Lookup | Successfully looked up invoice for customer PRA25548. Selected one for writeoff and an xml file was created in the correct batch directory. | Alex | Y 4/4/23 | |||
Payment Application | APP | Successfully created control and payment application docs, routed properly through workflow. Docs 12645946 and 12645947 | Alex | Y 4/4/23 |
Purchasing eDoc (without HuskyBuy) | eDoc code | Comments | Assigned To | Notes | JIRA | Complete Y/N |
Requisition | REQS High | Test No Print and Vendor Search. | Lan | Edoc# 12646186, Building and Vendor search work fine. | Y 4/25/2023 | |
Bulk Receiving | RCVB | Lan/Bruce | entered eDoc 12646306, no PO. entered all data and submitted. eDoc routed to Final status with no issues. clicked on "PRINT" button and went to stack trace error. | FINUCONN-459 (resolved 6/28) retested 7/5 successfully. Receiving ticket printed properly, no errors. | Y 7/5/2023 | |
Line Item Receiving | RCVL High | 4/14/20 - note that this function is not actually used. although this has never been retested, it is being changed to "N/A". | N/A | N/A | ||
Shop Catalogs | n/a | On Hold - Not Ready for Testing hold off until ready to test HuskyBuy interfaces | Micah | |||
Payment Request (vendor invoice) | PREQ | Bruce | 4/5/23: Per Lesley Markesbury, still removing UConn customization so we can evaluate baseline for immediate pay. 7/19: sam-not ready. 8/8/23: tried it out and was able to process several PREQ's against a single PO. still should be retested when Lesley indicates it's completed. | Y 8/9/2023 | ||
Disbursement Voucher | DV High | successfully created doc 12646144. Certain payment methods not available, creating Jira | Brett | 8/9/23: was able to enter a simple DV for employee non-travel expense reimb. successful, however did not test pay method dropdown. RETEST when Jira complete. | Y 8/9/23 | |
Contract Manager Assignment | ACM | Tested search criteria. Successfully created doc 12646271 | Alton | Yes | ||
Vendor Credit Memo | CM | Tested initiation fields. | Alton | Yes | ||
Vendor - add | PVEN | Created a new vendor and then make a change to that division. | Micah | Y 03/27/23 | ||
Vendor - edit | PVEN | Created a new vendor and then make a change to that division. | Micah | Y 03/27/23 | ||
Vendor Search | PVEN | Successfully tested search fields | Alton | Yes |