EDIFACT invoices fail to import properly due to invalid "value" retrieving for vendor's accountingCode - Juniper env

Discovered information from Back-end side:

After deep investigation, it seems like the root cause of this issue is that UI-side does NOT  retrieve the vendor's accounting code on the bugfest-juniper enivronment(even if the vendor has this code) for invoice-mapping-profile in section "Vendor information". That's why "value" field in JSON for invoice-mapping profile for field "accountingCode" does not represent(see screenshots below). Moreover, this JSON-field has "enabled" : "true" - and BE-side brakes in this case (this field enables BUT "value" doesn't exist). 

Moreover, on the hosted-ref-envs it processes fine(see attached).
=================================

Overview: I've written up as 1 bug, but it may actually be 2 separate bugs. Also, it might be related to MODDATAIMP-516, or it may not be. Library is trying to import invoices in Juniper Bugfest, but jobs complete with errors.

Current workaround Manual entry

Steps to Reproduce:

1. Scenario 1
   • 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
2. Scenario 2
   • Go to Settings/Data Import and review the Job/Action/Field mapping profiles for KP TEST - Harrassowitz 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 Harrassowitz job profile cited above, and import the file

Expected Results:

• Scenario 1: should create 2 invoices with a total of 5 line items
• Scenario 2: should create 18 invoices with a total of 1104 line items

Actual Results:

• Scenario 1: completed with errors. No log details, no error details in the log.
• Scenario 2: completed with errors. Some lines show in the log, but not all

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
• The Harrassowitz file has 1000+ invoice lines in it. I'm not sure if we have ever tested that large of a file
• I did not have a chance to test them against folio-snapshot-load, to see if they would succeed there 

Interested parties: kpamplin