Create, close, cancel, Purchase Orders
(UXPROD-1141)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Kiwi (R3 2021) | Parent: | Create, close, cancel, Purchase Orders |
| Type: | New Feature | Priority: | P1 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Done | Votes: | 0 |
| Labels: | acquisitions, integration, orders | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Create, close, cancel, Purchase Orders | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 95 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
Current situation or problem:Given a FOLIO tenant is using expense classes in their Fund structure. Third party systems must be able to indicate which Fund and Expense classes should be associated with a purchase order line. This list of Fund and Expense classes needs to be exportable so users can share this information with Vendors. This is what allows a vendor to populate their interface with Fund codes for the user to choose from when creating orders in that system. In scope:
Out of scope:
Use case(s)
Proposed solution/stories See links below Links to additional info https://folio-org.atlassian.net/wiki/x/BSAb Questions |
| Comments |
| Comment by Dennis Bridges [ 31/May/21 ] |
|
Note: this work was split from
|
| Comment by Ann-Marie Breaux (Inactive) [ 07/Jun/21 ] |
|
Hi Dennis Bridges - this may be tricky for libraries that need expense classed on July 1, e.g. Michigan State. We also may need a story to check or confirm that fund + expense class being sent from the vendor in an EDIFACT invoice is parsed properly in FOLIO. Not sure if that's on Thunderjet or Folijet. If the EDIFACT file has the same format for fund:expense class, then maybe it's on the Thunderjet side? |
| Comment by Dennis Bridges [ 07/Jun/21 ] |
|
Ann-Marie Breaux as code freeze has already passed this will not be completed for Juniper. Keep in mind ordering will still work but expense classes will need to be added after. Better to know ordering will still work from that system in Juniper than risk breaking the integration and requiring hot fixes. I certainly appreciate that it will be an issue for those going live before kiwi but I recommend we continue to focus on stability over speed. |
| Comment by Dennis Bridges [ 25/Nov/21 ] |
|
All issues resolved and verified in bugfest-kiwi |