2013-04-01 - 5721.100 - Spec - Partner Compliance -Fix Partner Compliance application. #PartnerComplianceApplication
SPECIFICATIONS
Fix Partner Compliance Application
Purpose
Fixing the new changes and issue in the partner compliance application.
Admin Info
| Purpose |
Fixing the new changes in Partner Compliance application |
| Requested By |
Baiwa zhange, Rohal Attardi |
| Spec Created By |
Satish.K |
| Spec Created Date |
04/01/2013 |
| Spec QA by |
Satish.K |
| Document Status |
Complete |
References
Prior Tickets
NADocuments
Feedback_2.0.docxFunctional Requirement
1. Remove leading zeros in quantity field of 'Non-Compliant Summary' section of 'Receiving Compliance Report'.
2. I was trying to check “Chargeback invoice issue entry closed” checkbox then clicked Save in step #3.
Then nothing saved but received the tiny error message on top:
“SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.”
I don’t understand this error message.
Error message should specify which field is having issues and what the valid format should be.
3. Users should be able to remove date values from non-mandatory fields,(Previously all the date fields, once entered, cannot be removed.) in the Step1,Step 2 & 3 of
PENDING CHARGEBACK DATE & INITIAL CHARGEBACK DATE.
4. All the users should be able to edit tickets as long as they have access to that page. Security is only limiting the pages that the user can access.
Whether a user can see a certain ticket, depends on if the plant of the ticket is assigned to that user or not.
If not, error message “No records found.” should be displayed like the ticket doesn’t exist.
5. while creating a test ticket and checked 'Damage on Load' checkbox, but it is not reflected in the email.
6. Sort plant dropdown alphabetically by plant description. Keep same display (number - description).
7.Sort vendor dropdown alphabetically by vendor description. Keep same display (number - description).
8. Sort NC Type dropdown alphabetically by NC Type description.
9. Besides carton numbers, any fields that user can manually enter numbers, should not allow commas. But thousand separators should still be displayed, not saved.
And admin fee field.
DC Compliance
10.Sort vendor dropdown alphabetically by vendor description. Keep same display (number - description).
11.Sort department dropdown alphabetically by department description.
12.Sort customer dropdown alphabetically by customer description. Keep same display (number - description).
13. Quantity field should not allow commas. Thousand separators should still be displayed, not saved.
The comma in quantity 1,234,567 will stop the ticket from saving changes although there will be a pop up saying it is saved.
14. User should be able to remove date value from the following fields.
15. When the user enters a PO line detail with zero quantity or total cost, this should save too. Eg. Line 3.
Admin Page:
16. Admin can edit any field alone and save it. ADID is the unique identifier. Anything can be changed.
17. After users click “Delete”, the record is deleted no matter user click “OK” or not. Plus that’s the only button user can click except for closing the window.
Either way the record is deleted. The alert should say “Delete selected record?”, and deletion will happen upon “Yes.” while the other option is “Cancel”.
18. Charge back code and cost: once failed to save due to existing record, data is removed from the grid. Change this and keep the data.
19. Charge back code and cost: once inserted, change alert to “Charge back code and cost saved successfully.”
And change the edit confirmation to “Charge back code and cost saved successfully.” upon successfully operation.
20. Cannot delete material cost for newly created records.
Since If the record/Plant is using in other tables then user get a prompt message of “can’t be deleted because this value exist in more than one table” with ‘OK’ button.
21. Once a ticket is been created by an 'User A' and the same ticket is been edit by other 'User B', then “Entered By” field will always display the 'User A' name only.
This field should always display original creator of the ticket. Because normally the ticket creator will not be the one who sends out chargebacks and invoices.
This is worked for 'Vendor Compliance' and 'DC Compliance' page.
22. Able to edit existing material costs by highlight and rewrite.
23. Able to edit CB code and cost by highlight and rewrite.
Enhancements:
| Project Name: Partner Compliance |
||||
| Role Based Security User Checklist |
||||
| S.No |
Page Name |
Users |
||
| Admin User |
Logistic User |
DC User |
||
| 1 |
Vendor Compliance |
YES |
YES |
YES |
| 2 |
DC Compliance |
YES |
YES |
NO |
| 3 |
Reports |
YES |
YES |
NO |
| 4 |
Upload |
YES |
YES |
YES |
| 5 |
Admin |
YES |
NO |
NO |
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
1) Leading zeros in quantity field of 'Non-Compliant Summary' section of 'Receiving Compliance Report' will be removed while displaying.
2) Validate the step 3 in charge back page to fix the issue, date fields will be made mandatory before saving.
3) All the date fields will be made removable which are non-mandatory.
4) Apply a security check on ticket access by DC user, if admin user has created a ticket then if plant is assigned to DC user then he can check that ticket if not then he will get a message "No records found." message.
5) Damage? value will be shown in the email which is sent in vendor compliance pages.
6) Sorting will be applied to description and will be displayed based on sort order on description fields in all the drop downs.
7) Thousand separators will be applied to all the numeric fields in vendor compliance and non-compliance pages.
8) When user enters a PO line detail with zero quantity or total cost, will be saved in non-compliance page.
9) User details in Admin section can be saved based on userid field/column.
10) All the delete options will prompt an alert message "Delete selected record?" before deleting.
11) Charge back code and cost in record will be retained if it is not saved.
12) Charge back code and cost once inserted or saved the following message will be displayed "Charge back code and cost saved successfully."
13) Ticket creator will always remain as creator in entered by fields through out application. Even though any other user edits the page and saves again, the entered by field will display the original ticket creator name always.
14) The data is sorted by CB code on admin - Chargeback code page.
Test Plan
[List test scenarios/cases to be executed here]Partner Compliance_Change Request_TestCases.xlsx
Solution Details
[Discuss this section with Requester and get approval prior to beginning work]
1) Leading zeros in quantity field of 'Non-Compliant Summary' section of 'Receiving Compliance Report' will be removed while displaying.
2) Validate the step 3 in charge back page to fix the issue, date fields will be made mandatory before saving. (Validators are used).
3) All the date fields will be made removable which are non-mandatory. (Dates can be removed and re-selected from the calander).
4) Apply a security check on ticket access by DC user, if admin user has created a ticket then if plant is assigned to DC user then he can check that ticket if not then he will get a message "No records found." message. (Based on roles defined on DC and admin users the access to tickets are applied).
5) Damage? value will be shown in the email which is sent in vendor compliance pages. (Message of Damage? value will be shown in email which is sent).
6) Sorting will be applied to description and will be displayed based on sort order on description fields in all the drop downs. (sorting of all the dropdowns will be on description field and displayed in the sorted order).
7) Thousand separators will be applied to all the numeric fields in vendor compliance and non-compliance pages. ("," separator are displayed in the numeric fields but while saving the thousand separators are not saved).
8) When user enters a PO line detail with zero quantity or total cost, will be saved in non-compliance page. (Quantity with zero and cost with zeros will be allowed to be saved).
9) User details in Admin section can be saved based on userid field/column.
10) All the delete options will prompt an alert message "Delete selected record?" before deleting.(Confirmation message before deleting the record is applied).
11) Charge back code and cost in record will be retained if it is not saved. (Maintaining the entered data when not saved successfully).
12) Charge back code and cost once inserted or saved the following message will be displayed "Charge back code and cost saved successfully."
13) Ticket creator will always remain as creator in entered by fields through out application. Even though any other user edits the page and saves again, the entered by field will display the original ticket creator name always.
14) The data is sorted by CB code on admin - Chargeback code page. (In grid the data is sorted by CB code).