Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Incoming EDI not being translated to xml

    • Product: Aleph    
    • Product Version: 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care


     


    Description

    Incoming EDI files are not translated correctly. When they are moved to XML for some fields the field tag name is missing.

     

    The affected fields are:

    IMD:011 has no form name, correct one would be <last name> 
    IMD:060 has no form name but is also not listed in the mapping so maybe is not considered on purpose

    IMD:120 has no form name but is also not listed in the mapping so maybe is not considered on purpose

     

    Consequently the XML file can’t be handled but an error is reported

    Resolution

    This problem is corrected with rep_change #2339 in Aleph 22 and rep_change #2029 in Aleph 23.

     

    Description: ACQ, EDI - Incoming messages. For some values of the IMD tags (such as IMD+L+011, IMD+L+060, IMD+L+120), the matching xml tags were created with empty tag names (invalid XML file).

     

    Solution: This has been corrected. The value of IMD tags which are not supported by Aleph will not be created in the Aleph XML file.

     

     


    • Article last edited: 30-Aug-2016
    • Was this article helpful?