Create, close, cancel, Purchase Orders (UXPROD-1141)

[UXPROD-3096] Allow external systems to apply Fund AND Expense classes when creating or updating POLs Created: 31/May/21  Updated: 06/Jan/22  Resolved: 25/Nov/21

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:
Cloners
clones UXPROD-2630 Thunderjet - R2 Enhancements/Bugfixes Closed
Defines
defines MODGOBI-123 Allow mapping for expense classes thr... Closed
is defined by MODGOBI-125 Support expense classes from LocalDat... Closed
is defined by MODGOBI-128 Support expense classes from LocalDat... Closed
is defined by MODFIN-199 Create API for retrieving combination... Closed
is defined by MODFISTO-243 Define DTO schema for combination of ... Closed
is defined by MODFISTO-244 Add validation for special character ... Closed
is defined by MODINVOSTO-122 Migration script for Fund code in the... Closed
is defined by MODORDSTOR-243 Migration script for Fund code in the... Closed
is defined by UIF-320 Export combined Fund code list Closed
is defined by UIF-323 Add validation for special character ... Closed
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:

  • Update edge-orders and mod-GOBI as needed to establish a pattern for how third-party systems can apply Fund AND Expense class when creating or updating POLs through the order APIs

Out of scope:

  • Update any mapping modules other than mod-gobi and mod-ebsconet (EBSCONET update split out to Lotus release, see MODEBSNET-13 Closed )

Use case(s)

  • Fund structure is built with expense classes and library does a lot of ordering at vendor systems for physical and electronic material. Expense classes are shared with accounting and thus need to appear on voucher. If they are left off the orders if will make it very difficult to control spending and provide accurate reporting to inform daily purchasing activities

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 UXPROD-2630 Closed as we do not have the capacity in R2 to complete it before the code freeze.

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

Generated at Fri Feb 09 00:29:19 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.