Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-3810] Allow user to edit Fund distribution even when invoice is connected in current FY Created: 12/Sep/22  Updated: 30/Nov/23  Resolved: 28/Mar/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Orchid (R1 2023)
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P2
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODORDERS-836 Encumbrance detail not shown in POL f... Closed
is defined by MODORDERS-841 Encumbrance current amount is calcula... Closed
is defined by MODORDERS-743 Prevent order encumbrance updates onl... Closed
is defined by MODORDERS-788 Implement fetching related invoices o... Closed
is defined by MODORDERS-800 Implement moving encumbered value fro... Closed
is defined by MODORDERS-801 Check and correct encumbrance ID link... Closed
is defined by MODORDERS-803 Implement Edit Fund Destribution bloc... Closed
is defined by MODORDERS-804 Remove validation for editing fund di... Closed
is defined by MODORDERS-818 Spike: FLOW #2 Finance and Rollover V... Closed
is defined by MODORDERS-834 Flow #2. Copy the amount awaiting pay... Closed
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Development Team: Thunderjet
PO Rank: 61
Rank: Duke (Full Sum 2021): R2
Solution Architect: Raman Auramau

 Description   

Purpose/Overview: Allow users to edit Fund distribution when invoice is connected in current FY. Users often need to update fund distributions in this situation.

Requirements/Scope:

  1. Relationship between order and invoice is maintained.
  2. User is able to edit order fund distributions when there is an invoice connected to the order
  3. Awaiting payment and Expended amount is present in new encumbrance.

Approach:

See MIRO: https://miro.com/app/board/uXjVPQunluM=/?share_link_id=771554660290

 



 Comments   
Comment by Lisa Smith [ 16/Sep/22 ]

We regularly need to update funds on ongoing orders.  For example, sometimes 2 funds are collapsed into one, and we update the smaller fund code to the larger fund code.  Also, new standing orders are paid out of one-time money for the first payment, before moving money into an on-going fund.  And sometimes the fund needs to be updated because a new fund was created and it's a better fit in the new fund category.  (We are looking into creating an open-access fund; if we do, several subject funds will need to be updated.)

Comment by Lisa Smith [ 16/Sep/22 ]

We regularly need to update funds on ongoing orders.  For example, sometimes 2 funds are collapsed into one, and we update the smaller fund code to the larger fund code.  Also, new standing orders are paid out of one-time money for the first payment, before moving money into an on-going fund.  And sometimes the fund needs to be updated because a new fund was created and it's a better fit in the new fund category.  (We are looking into creating an open-access fund; if we do, several subject funds will need to be updated.)

Comment by Dennis Bridges [ 28/Mar/23 ]

All stories resolved for release in Orchid

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