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

Import invoice in EDIFACT format (Folijet work)

    XMLWordPrintable

Details

    • Medium < 5 days
    • Small < 3 days
    • XXL < 30 days
    • Folijet
    • 99
    • R5
    • R1
    • R1
    • R1
    • R1
    • R4
    • R4
    • R4
    • R1
    • R1
    • R1
    • R4
    • R1
    • R1
    • R1
    • R1
    • R1
    • 7
    • Yes
    • Hide
      [Steven from Five Colleges: Five Colleges Showstopper Majority of invoices now loaded as EDI. Not having this would be a cause an major slowdown in Invoice processing] [John from TAMU: I'll second Steven's comment. About 80% of our invoices are loaded via EDI for one time and recurring purchases so this is a showstopper.] [Response from Ann Marie: We are going to have the UI work done in Iris (being able to create a field mapping profile, action, and job profile). The acquisitions dev team is also doing some prep work so that we can connect Data Import and Invoices. The actual connection work and testing will be early in Juniper. My intention is also to have data import provide default field mapping profiles for all the vendors who have been identified so far (12 vendors), which can be edited, duplicated, or deleted by the library. That should make the setup work easier for everyone.] [Tod from Chicago: This is a showstopper for us as well. From Scott: "There are ~ 6,000 lines created this way annually, almost all of them in the months of November/December (when the large serial renewal invoices are issued)." The staffing increase needed to handle these in a short time is not just possible.][Kay and Shawn from MI St U. All workflows are built around import of EDI invoices, we are not staffed to pay one at a time.]
      Show
      [Steven from Five Colleges: Five Colleges Showstopper Majority of invoices now loaded as EDI. Not having this would be a cause an major slowdown in Invoice processing] [John from TAMU: I'll second Steven's comment. About 80% of our invoices are loaded via EDI for one time and recurring purchases so this is a showstopper.] [Response from Ann Marie: We are going to have the UI work done in Iris (being able to create a field mapping profile, action, and job profile). The acquisitions dev team is also doing some prep work so that we can connect Data Import and Invoices. The actual connection work and testing will be early in Juniper. My intention is also to have data import provide default field mapping profiles for all the vendors who have been identified so far (12 vendors), which can be edited, duplicated, or deleted by the library. That should make the setup work easier for everyone.] [Tod from Chicago: This is a showstopper for us as well. From Scott: "There are ~ 6,000 lines created this way annually, almost all of them in the months of November/December (when the large serial renewal invoices are issued)." The staffing increase needed to handle these in a short time is not just possible.][Kay and Shawn from MI St U. All workflows are built around import of EDI invoices, we are not staffed to pay one at a time.]
    • Hide
      This is a 'showstopper' for 4 libraries, and a major annoyance for others like Cornell. This feature mostly impacts big libraries, and is the last feature in a trio. Thunderjet's is responsible for one of three features, and has split it in two (part 2 is UXPROD-2847). This is the final feature that pulls everything together. TAMU needs the feature 1 month before implement, but the other libraries indicated that a month after implementation would be o.k. (Given a month before implementation for TAMU is July 1, perhaps we should aim for that?)
      Show
      This is a 'showstopper' for 4 libraries, and a major annoyance for others like Cornell. This feature mostly impacts big libraries, and is the last feature in a trio. Thunderjet's is responsible for one of three features, and has split it in two (part 2 is UXPROD-2847 ). This is the final feature that pulls everything together. TAMU needs the feature 1 month before implement, but the other libraries indicated that a month after implementation would be o.k. (Given a month before implementation for TAMU is July 1, perhaps we should aim for that?)
    • Hide
      The Capacity Planning Team recommended to the FOLIO Product Council that the Iris release date be extended to May 3 (from March 1) so that all of the at-risk 'showstopper' features could be completed and released before the July implementations. (Slide deck presented to PC: https://docs.google.com/presentation/d/12s_fs3vqjm4hAGIfZ_HX1jm--v8QOEFber5uvo0VTGw/edit?usp=sharing)
      Show
      The Capacity Planning Team recommended to the FOLIO Product Council that the Iris release date be extended to May 3 (from March 1) so that all of the at-risk 'showstopper' features could be completed and released before the July implementations. (Slide deck presented to PC: https://docs.google.com/presentation/d/12s_fs3vqjm4hAGIfZ_HX1jm--v8QOEFber5uvo0VTGw/edit?usp=sharing)
    • Hide
      FOLIO Product Council compromised and allowed the Iris release to be delayed by one month, to April 5. Due to the size of the t-shirt estimate for this feature, it is not likely to be completed as part of the Iris release (Holly is confirming with Anne-Marie, but she is out right now). The Capacity Planning Team will be meeting to discuss how/when this feature will be delivered to the libraries needing it before implementation.
      Show
      FOLIO Product Council compromised and allowed the Iris release to be delayed by one month, to April 5. Due to the size of the t-shirt estimate for this feature, it is not likely to be completed as part of the Iris release (Holly is confirming with Anne-Marie, but she is out right now). The Capacity Planning Team will be meeting to discuss how/when this feature will be delivered to the libraries needing it before implementation.

    Description

      Purpose: This mechanism will allow the automation of Invoice/Invoice line creation for Vendors that can supply EDIFACT invoices (e.g. EBSCO, GOBI, Harrassowitz, WT Cox, etc.)

      High-Level Requirements:

      • Receive EDIFACT files in a specified location
      • Create a couple event handlers
      • Parser
      • Test with invoices from the key vendors

      Confirm which vendors, in which order, will be contacted and tested with

      If other formats needed (e.g. xInvoice for Europe, add more features to cover those)

      Note that this feature relies on Data Import's development of EDIFACT field mapping profiles (UXPROD-1381)

      Per OleksiiKuzminov and Taras_Spashchenko: may require a research spike to look at available open source EDIFACT parsers/libraries (similar to MARC4J for MARC records; decided that we will use staedi library

      Here is the Google Drive folder with official documentation, draft of field mapping syntax, default profiles, and sample invoices: https://drive.google.com/drive/folders/1ePm2M3FcHIZFVolxD4-WX8joEc1S_iVC

      TestRail: Results

        Attachments

          Issue Links

            has to be finished together with

            New Feature - New feature requests UXPROD-2622 Support for "Import invoice in EDIFACT format" (TJet work)

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

            New Feature - New feature requests UXPROD-2847 Part 2 - Support for "Import invoice in EDIFACT format" (TJet work)

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

            New Feature - New feature requests UXPROD-3068 EDIFACT invoice import refinement

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

            Task - A task that needs to be done. MODDATAIMP-317 SPIKE- Research Open source parser for EDIFACT files

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

            Task - A task that needs to be done. MODDATAIMP-328 SPIKE - Research data structure schema for EDIFACT parsed record content

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

            Task - A task that needs to be done. MODDATAIMP-330 SPIKE - Research EDIFACT record reading using smooks framework

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

            Task - A task that needs to be done. MODDATAIMP-339 SPIKE - Review EDIFACT syntax details and create implementation stories

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

            Task - A task that needs to be done. MODDATAIMP-352 Implement source reader for EDIFACT files.

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

            Task - A task that needs to be done. MODDATAIMP-364 Set up Rancher env for EDIFACT invoice testing

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

            Task - A task that needs to be done. MODDATAIMP-373 Fill Rancher environment via sample data for EDIFACT invoice testing

            • 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. MODDICONV-164 Create default EDIFACT field mapping profiles, part 1

            • 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. MODDICONV-165 Create default EDIFACT field mapping profiles, part 2

            • 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. MODDICONV-166 Create default EDIFACT field mapping profiles, part 3

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

            Task - A task that needs to be done. MODDICONV-172 Update default EDIFACT mapping profiles to include vendor reference number type

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

            Task - A task that needs to be done. MODDICORE-115 Add implementation for EDIFACT reader

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

            Task - A task that needs to be done. MODDICORE-116 Support for invoice adjustments mapping

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

            Task - A task that needs to be done. MODDICORE-117 Create invoice and multiple invoice lines from the same EDIFACT record

            • 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. MODINVOICE-108 Create EDIFACT invoice parser to create Invoices

            • 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. MODINVOICE-227 Implement action profile handler for invoice creation

            • 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. MODINVOICE-229 Logic for POL-Invoice line matching - DRAFT

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVOICE-231 Logic for Invoice line data from Purchase Order Line

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

            Task - A task that needs to be done. MODSOURCE-233 Support for storing EDIFACT records in the database

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

            Task - A task that needs to be done. MODSOURCE-234 CRUD operations support for EDIFACT records

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

            Task - A task that needs to be done. MODSOURCE-249 Receive event with parsed EDIFACT records

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

            Task - A task that needs to be done. MODSOURMAN-399 Implement processing of EDIFACT records chunk

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

            Task - A task that needs to be done. MODSOURMAN-408 Publish event about EDIFACT record creation

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

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-443 Iris Bugfest: EDIFACT invoices get stuck

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Task - A task that needs to be done. UIDATIMP-868 Adjust "vendor name" field value

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

            New Feature - New feature requests UXPROD-190 Create/Renew orders in FOLIO from EBSCONET

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

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-1152 CRUD invoices and resolve/process invoices

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

            New Feature - New feature requests UXPROD-1381 CRUD for EDIFACT Invoice Field Mapping Profiles

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

            Activity

              People

                abreaux Ann-Marie Breaux
                abreaux Ann-Marie Breaux
                Oleksii Kuzminov Oleksii Kuzminov
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases