Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

EDIFACT invoices fail to import properly - Juniper env (GOBI)

Description

Current workaround Manual entry

Steps to Reproduce:

  1. Scenario

    • Log into Juniper Bugfest

    • Go to Settings/Data Import and review the Job/Action/Field mapping profiles for KP Test YBP Serials Invoice against the attached invoice file 565780us20210618.edi.docx and confirm that the field mappings are correct

    • Go to Data Import and upload the file 565780us20210618.edi

    • Assign the YBP job profile cited above, and import the file

Expected Results: should create 2 invoices with a total of 5 line items

Actual Results: Scenario 1: completed with errors. No log details, no error details in the log.

Additional Information: EDIFACT files (file extension .edi) and corresponding human-readable Word versions (file extension .docx)

NOTES:

  • The organizations attached to each field mapping profile DO NOT have account numbers. In the field mapping profile, any checkbox that says "Output to Accounting" should be UNchecked

  • I did not have a chance to test them against folio-snapshot-load, to see if they would succeed there

Interested parties:

CSP Request Details

Approved by CPT on Slack release_bug_triage channel 21 Sept 2021

CSP Rejection Details

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux October 8, 2021 at 3:37 AM

Hi All looks good on Juniper bugfest! Closing this bug...

Ann-Marie Breaux October 4, 2021 at 1:23 PM

And I see you just released it, so I've moved to Awaiting deployment

Volodymyr Rohach September 30, 2021 at 8:35 AM

Hi ! Yes, it is OK to move it to Awaiting release. I'll move this one to this status if you don't mind (because we already tested it on the hosted-ref-envs). 

And continue working on Harrazowitz one. 

Mariia Aloshyna September 30, 2021 at 8:33 AM

Hi  We do not need an additional UI story for the second scenario, looks like it is BE issue only. UIDATIMP-1005 can be moved to the Awaiting release, all work is done in the scope of this ticket. If the second scenario requires some UI work, we'll create a new ticket for that, thank you!

Ann-Marie Breaux September 29, 2021 at 4:12 PM
Edited

Hi and This covers scenario 1 (the GOBI invoice). OK to move it to Awaiting release?

Do we need to clone the UI story also? UIDATIMP-1005

And do we need to clone MODINVOICE-304?

I'm guessing no for both of those.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Development Team

Folijet Support

Parent

Fix versions

Release

R2 2021 Hot Fix #3

RCA Group

Implementation coding issue

CSP Approved

Yes

Affected Institution

Cornell
TAMU

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 29, 2021 at 4:07 PM
Updated January 26, 2022 at 10:34 AM
Resolved September 30, 2021 at 8:37 AM
TestRail: Cases
TestRail: Runs