Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-3096

Allow external systems to apply Fund AND Expense classes when creating or updating POLs

    XMLWordPrintable

Details

    • Medium < 5 days
    • XL < 15 days
    • Thunderjet
    • 95
    • R1
    • R4
    • 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)

      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://wiki.folio.org/x/g4VFAw

      Questions

      TestRail: Results

        Attachments

          Issue Links

            clones

            New Feature - New feature requests UXPROD-2630 Thunderjet - R2 Enhancements/Bugfixes

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed
            defines

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODGOBI-123 Allow mapping for expense classes through GOBI

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFIN-199 Create API for retrieving combination of fund code and expense classes

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-243 Define DTO schema for combination of fund code and expense class

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-244 Add validation for special character to Fund Code and Expense class code and prepare migration script

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODGOBI-125 Support expense classes from LocalData fields

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODGOBI-128 Support expense classes from LocalData fields

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVOSTO-122 Migration script for Fund code in the fund distribution of the invoice line":" replace with hyphen "-"

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDSTOR-243 Migration script for Fund code in the fund distribution of the order line":" replace with hyphen "-"

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIF-320 Export combined Fund code list

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIF-323 Add validation for special character to Fund Code and Expense class code so user can't save invalid code

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            mentioned in

            Page Loading...

            Activity

              People

                dennisbridges Dennis Bridges
                dennisbridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases