Clovertech

X12 Transaction Sets iteration 837.

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › X12 Transaction Sets iteration 837.

  • Creator
    Topic
  • January 10, 2008 at 3:59 pm #49736
    John Hamilton
    Participant

      Ok I know I ‘m new to X12 and I have lots to learn.  

      I have a vendor sending me an 837 file.

      It has multiple Transaction sets in it, each an 837.  

      I know this because I can run the X12 parse in the tester and see them.

      My question is how do I get my Xlate to iterate over them.

      I have looked at the EDI.tcl and don’t think there is an un transaction set procedure.  

      I have removed the header junk so it will run in the xlate tester.

      Is there a pre-xlt tcl proc I just don’t know about or is this an iteration thing I just need to figure out?  

      Any help and any comment will be appreciated.

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • January 10, 2008 at 5:15 pm #63348
        Jim Kosloskey
        Participant

          John,

          Here is my take:

          hciX12splitinterchange is used on mesages as they arrive and splits the X12 message into transaction sets each transaction set becoming a single message.

          It also extracts the Envelope (ISA, GS, IEA, GE) and places the needed information in the Metadata USERDATA. The separator cahracters (which are in the ISA) are extracted and placed in another keyed entry in the USERDATA (SEPCHARS is high level key).

          In the Xlate you see each 278 as a separate message and do whatever you need to.

          If you are generating another X12 message then hciX12buildinterchange will be used as the message is sent (OB TPS) to reassemble the messages with the envelope. It appears batching is handled at this point as well.

          Both of the above procs use the package X12lib which is in $HCIROOT/tcl/lib/X12lib/X12lib.

          IF you are building an X12 mesage from a non X12 message (like HL/7 or FRL, or…) then you need to write a proc to put the appropriate information for the envelope and the desired SEPCHARS in the metadata yourself.

          The Xlate appears to use a default set of separator characters for X12. Field = *, Segment = ~, Component = .

          IF you do not want to use those separators it appears (I am in the process of confirming this now) that the message’s metadata USERDATA field needs to have a SEPCHARS keyed list entry with your desired separators.

          If the above is true, that means one cannot use the XLate tester to acurately build an X12 message with other than the default separators. That is kind of a bummer!

          Jim Kosloskey

          email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

      • Author
        Replies
      Viewing 0 reply threads
      • The forum ‘Cloverleaf’ is closed to new topics and replies.