Skip to main content
ExLibris

  • Subscribe by RSS
    • Aleph
    Ex Libris Knowledge Center

    Wrong file name format generated for EDI claims to Harrassowitz?

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    When EDI claims are being generated to Harrassowitz, the format is edi.20080319.095027.0:

    From Harrassowitz' documentation, we should use the following naming convention for EDIFACT claims: Date/Time yyyymmddhhmmss
    For example:
    20070718160000.XXX.edi.claims
    Where XXX is your HARRASSOWITZ customer code.
    The data should be transferred in binary code.

    The table edi_out_attr in xxx50/tab seems to be modified correctly with switch 1 defined "4" for the correct Harr format:
    4 = Harrassowitz format. YYYYMMDDHHMMSS.XXX.edi.xxxxxx
    ! XXX is the edi library code defined in tab35 and xxxxxx is the
    ! message type (orders, ostenq or ordchg)

    and switch 2 set at "B" for Binary.

    Also, tab35 has been set up and used for both EDI invoicing and ordering. Is there another table that needs to be configured, I can't seem to figure out what I'm missing. I checked the KB and wasn't able to find any info on this problem.

    Resolution:
    The renaming of the file is only done at the time of actual ftp, so what you are seeing in the directory on ALEPH is not indicative of what was sent. If you want to confirm that the correct file name is being used to send your claims to Harrassowitz, the best way to check for sure is to send a test claim to a local ftp address and looked at the results there.

    • Article last edited: 10/8/2013