General Question About Xlate Routes

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf General Question About Xlate Routes

  • Creator
    Topic
  • #50000
    Jared Parish
    Participant

    This might be an basic question about the configuration of routes… I’m trying to figure out what is best practice for creating routes.  Do you create routes for each messages type (i.e. one for ADT_A01, one for ADT_A03, etc).  Or, do you try to make one all encompassing message type that works for all message types with just one route?  I believe when I went to class (five years ago, so my memory might be faulty) they suggested I work toward the all encompassing message type, but, I’m finding that is leading to a lot of “This segment is not defined” error messages.

  • Windows 2000 SP 4

    Quovadx 5.4.1P_REV1


  • Thanks,

    - Jared Parish

Viewing 5 reply threads
  • Author
    Replies
    • #64453

      That answer to your question is … it depends!  😀

      I prefer to use wildcard routes with a single xlate where the logic is the same or very close to the same for every event type. Then for events with different requirements, I create a seperate route.

      For example:

         ADT_A(01|02|03|04|05|06|07|08|11|13)

         ADT_A17

         ADT_A40

      -- Max Drown (Infor)

    • #64454
      Vince Angulo
      Participant

      Agreed, although we do slightly differently.   Typically we’ll route:

      ADT.*      –> ADT xlate (that suppresses A17’s).

      ADT_A17  –> A17 xlate.

      But I don’t think that will necessarily get rid of your segment not defined warnings.

      For example, your ADT.* translate is based on a robust message type like A01 or A08.  But an A06 has a unique Z-segment in it.  I don’t think you’ll get the warning from the xlate.  If the variant used for your TrxID on the Inbound tab doesn’t have that Z-segment for the A06 defined, I’m pretty sure you’ll still get the segment not defined warning as it tries to unpack the message.

      Then again, I’m sure someone will correct me if I’m wrong — that’s what I like about this forum…

    • #64455
      Jim Kosloskey
      Participant

      Vince,

      Are you indicating the standard ADT^A06 Message/Event Type Message has a Z segment in it?

      What version of HL/7 do you see that in?

      I have checked from 2.1 through 2.4 and do not see any Z segments in any Message/Event Type (as I would expect since Z segments are User segments).

      Jim Kosloskey

      email: jim.kosloskey@jim-kosloskey.com

    • #64456
      Rod Kromrey
      Participant

      We have done both ways with defining routes for each event and also using wild cards.  

      To avoid the problem with segments not being defined we usually create a new message type in the Variant that is called ADT_ALL and usually base if off of a A04 then add all your Z segments or any other segments you may need. Then copy that message structure to all the ADT message types.  Use that message type in your Xlate definition. By doing this we avoid undefined segments in the process logs.

      Hope that makes sense.

      Rod Kromrey

    • #64457
      Vince Angulo
      Participant

      Sorry, Jim — my post was poorly worded.  Instead of “But an A06 has”, I should’ve said something like “Suppose a vendor has a unique Z-segment in the inbound A06…” or words to that effect.  😳

    • #64458
      Jim Kosloskey
      Participant

      Vince,

      No problem – I was just doubting my sanity for a while (not an unusual occurrence).

      Thanks,

      Jim Kosloskey

      email: jim.kosloskey@jim-kosloskey.com

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

Forums

Forum Statistics

Registered Users
5,042
Forums
28
Topics
9,200
Replies
34,023
Topic Tags
267