| Subject: | Include Date and User details on the Purchase Order Receive report. |
| Summary: | Hi Team, There are scenarios, when clients want to know the user who has received the Purchase Order. They also want the date the Purchase Order was received. Improvement add the following details on the Purchase Order Receive report.. - Date and Time
- User who received the Purchase Order.
Sample 
|
| Audit Notes: | |
| 08 Sep 2017 | 11:40AM Comment 1 by Sanjay (Link Technologies) Case 8800 added to project 8.18 |
| 12 Sep 2017 | 09:08AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 12-09-2017 09:08 AM |
| Assignment changed to development |
|
| 14 Sep 2017 | 10:10AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-09-2017 10:10 AM Time Taken: 2.00 |
| The following has been completed: - Added "Date Received" and "Received By" below "Supplier Ref."
|
|
| 20 Sep 2017 | 08:39AM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 20-09-2017 08:39 AM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test Step 2 - Product expert allocated by Consulting Manager for Product QA. Consulting Manager to allocate resource Consulting Manager to sign off on UAT and Generic Test
STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Tested in QA1 with 818. Database - LINKSOFT Demo Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | Create, Approve, Print and Receive a Pass | Pass | | 2 | User receiving the PO should be successfully updated on the report. | Failed. "Received By" should show the name of the user. See attached sample in header,
The report currently outputs the sign on ID. The Sign ID is not always the name of the user. Figure 1: User receiving PO is "John" but the report outputs "INV". | | 3 | Date and Time of PO received should be updated on the report. | Pass |
Figure 1: 
WORKFLOW:
- Original case assigned to Development
- When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
- If system test passes, assign case to Consulting Manager for UAT
- If UAT Passes, Assign case for Documentation or close case
|
|
| 21 Sep 2017 | 02:53PM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 21-09-2017 02:53 PM Time Taken: 1.00 |
| Added user's name to the report. |
|
| 28 Sep 2017 | 06:46AM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 28-09-2017 06:46 AM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test Step 2 - Product expert allocated by Consulting Manager for Product QA. Consulting Manager to allocate resource Consulting Manager to sign off on UAT and Generic Test
STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | Create, Approve, Print and Receive a Pass | Pass | | 2 | User receiving the PO should be successfully updated on the report | Pass | | 3 | Users should be updated where PO has been partially received by 2 users. | Pass | | 4 | Date and Time of PO received should be updated on the report. | Pass |
Figure 1: Updated Report 
WORKFLOW: - Original case assigned to Development
- When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
- If system test passes, assign case to Consulting Manager for UAT
- If UAT Passes, Assign case for Documentation or close case
|
|
| 09 Oct 2019 | 08:14AM Comment 7 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |