Uploaded image for project: 'ui-invoice'
  1. ui-invoice
  2. UINV-165

Make invoice line 'vendor reference number' and type repeatable, paired fields and populate from POL

    XMLWordPrintable

Details

    • ACQ Sprint 107
    • 2
    • Thunderjet

    Description

      Overview: Often there may be multiple vendor reference number for a single order line - example: a vendor title number and a vendor order transaction number. It would be helpful to make this a repeatable field. All Vendor reference numbers should be populated into the invoice line when creating an invoice line from POL

      Acceptance criteria:

      Given the user is adding invoice line(s) based on POL(s)
      When adding invoice line
      Then the system populates all vendor numbers and their corresponding type in invoice line from POL

      Given the user is working with invoices
      When viewing or editing the invoice line
      Then vendor reference number(s) and vendor reference type(s) display as table in view pane

      TestRail: Results

        Attachments

          1. Current vendor ref types.PNG
            Current vendor ref types.PNG
            19 kB
          2. details.png
            details.png
            133 kB
          3. form.png
            form.png
            104 kB
          4. Make vendor ref repeatable.PNG
            Make vendor ref repeatable.PNG
            5 kB
          5. screenshot-1.png
            screenshot-1.png
            75 kB
          6. screenshot-2.png
            screenshot-2.png
            200 kB

          Issue Links

            defines

            New Feature - New feature requests UXPROD-2588 Prep for Create/Renew orders in FOLIO from EBSCONET

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVOSTO-81 Support pair of "refNumber" and "refNumberType" in Invoice line should be an array

            • 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. MODORDERS-421 Spike : User should be able to edit Pair of "refNumber" and "refNumberType" in the POL and see that update on the Invoice line

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-422 User should be able to edit Pair of "refNumber" and "refNumberType" in the POL and see that update on the Invoice line

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDSTOR-146 Pair of "refNumber" and "refNumberType" in PO line should be an array

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-519 Make POL vendor reference number and type repeatable, paired fields

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODGOBI-100 Update the logic of checking the availability of orders and acq-module

            • 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. UIDATIMP-296 Data Import Field Mapping Profile details: Create/Edit Invoice and Invoice line from EDIFACT Invoice

            • 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. UIDATIMP-779 Invoice Field Mapping Profile details: Update Vendor reference number fields - DRAFT

            • 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. UIDATIMP-845 Invoice field mapping profile: Adjust vendor reference number

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

            Activity

              People

                abreaux Ann-Marie Breaux
                dennisbridges Dennis Bridges
                Dennis Bridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases