Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
None
-
ACQ Sprint 132
-
3
-
Thunderjet
-
Lotus R1 2022
Description
Overview:
Fix/improve mapping of FOLIO orders to EDIFACT format (MODEXPW-41) according to the latest information available https://wiki.folio.org/display/ACQ/Sample+EDIFACT+Orders
Requirements/Scope:
- Update mapping of fields that are already mapped
- Implement mapping of fields that aren't currently mapped
- For fields that can't be mapped investigate what to omit and where to put default values
Additional information:
1. From the wiki page: These samples may not have every field that FOLIO may want to support. Should review/confirm with the SMEs, for one-time/ongoing and physical/E/mixed
2. Not quire clear whether we should also support EDIFACT orders for ongoing. From the wiki page: The response from the group so far has been that no one uses EDIFACT for ongoing. Though it is possible in theory to do so, this would make it very difficult to get examples of how it should be done. GBV has said that as long as the note to Vendor is included in the EDI details there is no need to exclude them.
3. From the wiki page: This example does not account for POLs with multiple locations/funds, but that is supported by the EDIFACT format. Will need to find an example
Acceptance criteria:
- Mapping corresponds to the table in https://wiki.folio.org/display/ACQ/Sample+EDIFACT+Orders
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-531 Export FOLIO orders in EDIFACT format
-
- Closed
-
- is cloned by
-
MODEXPW-68 Remaining fixes and improvements for FOLIO orders to EDIFACT format mapping
-
- Closed
-
- relates to
-
MODEXPW-41 Implementation : Mapping FOLIO orders to EDIFACT order file
-
- Closed
-