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

EDIFACT invoice import refinement

    XMLWordPrintable

Details

    • Not Scheduled
    • Folijet
    • 0
    • R1
    • R2
    • R4

    Description

      Current situation or problem: The EDIFACT invoicing import work done in R1 2020/Iris needs additional refinement to cover invoice and invoice line surcharges and possibly a few additional field mappings

      In scope

      • Invoice level surcharges (current workaround: manually add after FOLIO invoice is created)
      • Invoice-line level surcharges (current workaround: manually add after FOLIO invoice is created)
      • Extracting start/end subscription info from larger test string (current workaround: ask vendors to use the simplified version of start/end dates)
      • Review/confirm that mapping for currency is working (current workaround: default the currency in the field mapping profile, instead of reading from the incoming file)
      • Ensure file with .txt extension will import properly (Hein)
      • POL/vendor identifier matching

      Out of scope

      Use case(s)

      Proposed solution/stories

      Links to additional info
      https://wiki.folio.org/display/FOLIOtips/Field+mapping+syntax+for+EDIFACT+files

      Questions

      TestRail: Results

        Attachments

          Issue Links

            continues

            New Feature - New feature requests UXPROD-195 Import invoice in EDIFACT format (Folijet work)

            • P2 - normal priority level, must be included in the current development 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
            has to be finished together with

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

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODDICORE-123 Create EDIFACT mapping for qualifiers in separate lines from their values

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

            Bug - A problem which impairs or prevents the functions of the product. MODDICORE-124 Invoice LINE level adjustments do not work

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

            Bug - A problem which impairs or prevents the functions of the product. MODDICORE-125 Invoice level adjustments do not work

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVOICE-236 User alert when incoming Invoice line cannot be linked to a PO Line

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

            Page Loading...

            Activity

              People

                abreaux Ann-Marie Breaux
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases