-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Won't Develop
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Allocations, OrderGuide, Ordering, Reports
-
Labels:None
-
Sprint:System Health Sprint 1, System Health 2021R1 Sprint 6
-
SCRUM Team:Watchmen
-
Story Points:21
-
Work Type Classification:Sustaining
Update tbTransactionSalesOrderDetail and tbTransactionSupplyOrderDetail to include vendorentityitemid, and populate whenever creating a new sales or supply order. At this first story, we don't necessarily need to pass the data from code, it will be enough to populate from inside the insert/update stored procedures and sql (this may still result in the same multi-order item issues we have today).
- implements
-
CFAMX-2397 Rewrite Ordering to use VendorEntityItemId to identify ordered items
-
- Closed
-
1.
|
Review Test Scripts |
|
Ready for QA | Unassigned |
|
|||||||
2.
|
Deploy |
|
Ready for QA | Unassigned |
|
|||||||
3.
|
Functional Review |
|
Ready for Developer | Unassigned |
|
|||||||
4.
|
DIT |
|
Ready for Developer | Unassigned |
|
|||||||
5.
|
Update tables to include vendorentityitemid, populate whenever creating a new sales or supply order |
|
Ready for Developer | Unassigned |
|
|||||||
6.
|
Update mxconnect to use vendorentityitemid when retrieving ordered items |
|
Ready for Developer | Unassigned |
|
|||||||
7.
|
Update integrated Unit tests to use VendorEntityItemId |
|
Ready for Developer | Unassigned |
|
|||||||
8.
|
Update Server Manager tasks and stored procedures to use vendorentityitemid |
|
Ready for Developer | Unassigned |
|
|||||||
9.
|
Update any reports that display ordered items to use vendorentityitemid |
|
Ready for Developer | Unassigned |
|
|||||||
10.
|
Script for populating VendorEntityItemId Field for Existing Orders |
|
Done | Unassigned |
|
|||||||
11.
|
Update any exports/imports that display ordered items to use vendorentityitemid |
|
Done | Unassigned |
|
