Exporting Orders and Importing Invoices in EDIFACT format (Thunderjet work) (UXPROD-1153)

[MODINVOICE-108] Create EDIFACT invoice parser to create Invoices Created: 10/Jul/19  Updated: 30/Jun/21  Resolved: 13/Jan/21

Status: Closed
Project: mod-invoice
Components: None
Affects versions: None
Fix versions: None
Parent: Exporting Orders and Importing Invoices in EDIFACT format (Thunderjet work)

Type: Story Priority: P3
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Duplicate Votes: 0
Labels: acquisitions, cap-mvp, invoices, po-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-195 Import invoice in EDIFACT format (Fol... Closed
Relates
relates to UINV-2 Duplication checking for vendor invoi... Closed
Sprint:
Development Team: Thunderjet
Tester Assignee: Dennis Bridges
Epic Link: Exporting Orders and Importing Invoices in EDIFACT format (Thunderjet work)
Analysis Estimate: Very Small (VS) < 1day
Back End Estimate: Medium < 5 days
Front-End Confidence factor: Low
Front End Estimate: Very Small (VS) < 1day

 Description   

Purpose: The batch loader has to be able to parse incoming invoice files and create invoices using mod-invoice inside FOLIO.

Requirements:

  • Invoice will be linked to related order and inventory records as part of import
  • Invoice could be marked as paid at time of creation
  • Invoice will carry Vendor Invoice number
  • Import will not duplicate invoices or will provide a means of error handling for duplication


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 04/Nov/19 ]

Hi Dennis Bridges and Craig McNally How does this differ from MODDATAIMP and UIDATIMP creating the mapper from an EDIFACT invoice to the various data elements? At some point, data import will need to be delivering a payload of info to the Invoicing app to create the Invoice and invoice lines, whether that data is coming from MARC or from EDIFACT. Is this a separate requirement of some kind?

Comment by Dennis Bridges [ 04/Nov/19 ]

Ann-Marie Breaux It sounds like the parser will actually be built into the import module. In which case those modules will parse the EDIFACT into jason and send it to the appropriate APIs in invoices, orders, inventory etc to create what is needed. If so this issue could potentially be moved to a different project.

Comment by Ann-Marie Breaux (Inactive) [ 13/Jan/21 ]

Parsing will happen in Data Import, then MODINV will get the payload

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